What a shop actually needs from a CRM
A generic CRM is built around "leads" and "deals." A repair shop doesn't have those. It has customers, vehicles, and service records. If the software forces you to think in terms of opportunities and pipelines when you should be thinking in terms of ROs and next-service-due, you're fighting the tool every day.
So what does a shop actually need? Four things:
- A contact record that's anchored to a vehicle, not just a person. One person can have three cars. Each needs its own service history.
- A service history that records what was done, what was declined, and what's recommended next. This is the single most valuable dataset your shop owns, and most CRMs have no concept of it.
- Automated follow-up triggered by service events — jobs closed, services declined, intervals coming due. Not by arbitrary pipeline stages.
- Review, win-back, and reminder automation that runs without you. Because you are not going to open a CRM at 4pm on a Friday to manually text 40 people.
If the CRM you're evaluating can't do all four, it's not a CRM for an auto shop. It's a lead-tracker that happens to be called a CRM.
Generic CRMs: what breaks
Let's be specific about why HubSpot, Zoho, and Salesforce don't fit:
- Vehicles aren't first-class objects. You either shove the make/model into a text field or build a custom object. Either way, querying "show me every F-150 due for timing-belt service" is painful.
- No service-history model. You can fake it with notes or custom deals, but you can't easily answer "when was this customer's last brake job."
- No native service-interval logic. Oil changes are every 5,000 miles or 6 months. Timing belts are every 90,000. Transmission flushes are every 30,000–60,000 depending on fluid type. A generic CRM has no concept of this.
- Pricing built around sales teams. You'll pay per user for features you'll never use (deal pipelines, forecasting, lead scoring) and still lack features you need.
Auto-specific software: what breaks
Dedicated shop-management systems (SMS — confusing acronym, means "shop management system" in this industry) like Mitchell 1, RO Writer, Shopware, Tekmetric, and Shop-Ware solve the operations side. Scheduling, estimating, parts lookup, repair order writing. But they are typically weak on the customer-relationship side:
- Review automation is often an afterthought or a paid add-on.
- Win-back campaigns are either not present or clunky to configure.
- Modern SMS communication (A2P 10DLC-compliant) is often an extra module.
- Reporting is focused on operations metrics (ARO, hours sold, tech efficiency) — not on customer engagement (follow-up rate, review request conversion, repeat-visit percentage).
The best setup for most shops is an SMS for operations, plus a CRM that specifically integrates with an auto shop workflow for everything customer-facing.
What to look for
Score any CRM you're evaluating against this list:
- Does it have a vehicle object, with year/make/model/VIN/plate, tied to the customer?
- Can it store a service history I can search?
- Does it trigger follow-ups on service events, not just pipeline changes?
- Can it send review requests automatically two hours after pickup, with a 4-to-5-star filter?
- Does it support A2P 10DLC-compliant SMS?
- Can I run a win-back at 90/120/180 days without writing custom automation?
- Does it integrate with the major shop management systems I already use?
- Is pricing based on contacts or on features. Not per-user seat counts?
If you can check 6 of those 8, you've found one.
How the common options actually compare
| Tool | Category | Monthly price | Vehicle-aware CRM | Automated Google reviews (star-gated) | Win-backs (90/120/180) | A2P 10DLC included | Best fit |
|---|---|---|---|---|---|---|---|
| Pitlane | CRM + retention layer | $97–$297 | ✓ Core | ✓ Built in | ✓ Automated | ✓ Included | Shop that already has an SMS and needs the customer side |
| Shopmonkey | Full shop management | ~$250–$450+ | ✓ Built in | Basic | Manual campaigns | Varies | Shop running ROs end-to-end on one tool |
| Tekmetric | Cloud SMS | Quote-based, typically $300+ | ✓ Built in | Basic | Manual | Varies | Moving off paper/desktop SMS |
| Shopware | Established desktop/cloud SMS | Quote-based, often $300–$500+ with setup | ✓ Built in | Basic add-on | Manual | Varies | Long-tenured shop with existing workflows |
| Mitchell 1 | SMS + data | Quote-based, typically $250+ | ✓ Built in | — | — | — | Shops needing deep repair data + estimating |
| HubSpot / Zoho / Salesforce | Generic CRM | $45–$1,500+ depending on tier | ✗ No vehicle model | Manual setup | Manual | ✗ External provider | Not recommended for auto shops |
The short read: a generic CRM forces you to build everything the auto industry needs from scratch. A shop management system is strong on the RO workflow but thin on retention automation. Pitlane is purpose-built for the retention layer and is typically used alongside whichever SMS you already run.
The "good enough" CRM for most shops
Shops running $500k–$3M in annual revenue do not need a Fortune 500-grade CRM. They need something that:
- Takes under an hour to set up.
- Requires zero daily maintenance.
- Runs reviews, win-backs, and reminders on autopilot.
- Costs less than one repeat customer per month.
If you're spending $400/mo on a CRM that hasn't paid for itself in repeat business by month 2, you have the wrong CRM.
How Pitlane compares
Pitlane is built around vehicles and service records, not leads and deals. Review automation, win-back sequences, service reminders, and a 10DLC-registered SMS number come standard. Contact-based pricing, not per-user. Setup takes under 10 minutes, and there's no contract.