The Right CRM for a 1-Truck Shop vs. a 10-Truck Shop

A 1-truck owner buys the CRM the 10-truck shop uses — $300/month, forty features, pipelines with seventeen stages — and uses it as a phone book. A 10-truck owner runs the business on spreadsheets and a whiteboard, and wonders why nothing's trackable. Both have the wrong tool. Not the wrong brand — the wrong size. CRM mistakes are almost never about which software. They're about buying for the shop you wish you had instead of the shop you run.

This guide sits inside the 8-system Leveraged Owner framework — the CRM question touches all four pillars: lead capture, estimate follow-up, reviews, and scheduling. Size the tool to the shop, not the fantasy.

What "CRM" means at each size (different jobs, different tools)

CRM = customer relationship management software — but the job description changes completely with headcount:

• 1 truck: the job is remembering. Who called, what was quoted, when to follow up, who hasn't been serviced in 18 months. The tool needs to be simpler than the owner's memory — or it won't get used.
• 3–5 trucks: the job is coordinating. Multiple people touch the same customers; the tool has to keep everyone looking at the same truth — dispatch, history, and follow-up in one place.
• 10 trucks: the job is governing. Pipelines with stages, permissions, reporting, marketing attribution, accountability. The tool enforces the process because the owner can't watch everyone.

The 1-truck CRM: keep it embarrassingly simple

• What you need: every customer and lead in one searchable place, with last-contact date, next-follow-up date, and basic segments (customer vs. lead, service date, equipment notes). That's it.
• What works: a well-kept Google Sheet, the contacts in your field-service software's customer list, or GoHighLevel's free/Starter CRM if you're already there for texting. The $0 stack's spreadsheet (see the $0 automation stack) is a legitimate 1-truck CRM.
• What to avoid: anything with "pipelines," "deal stages," or per-seat pricing. You're one seat. You don't have deals, you have jobs. Complexity you don't use is a tax on the complexity you need.
• The test: can you find any customer's full history in under 30 seconds, on your phone, standing in their driveway? If yes, your CRM is sufficient. If no, fix that before buying anything.

The 3–5 truck CRM: the coordination layer

• What you need: shared customer records, job history visible to everyone, estimate pipeline with next-touch dates, and the communication history (texts, emails) attached to the contact. No more "I didn't know they called yesterday."
• What works: GoHighLevel ($97/mo Starter) as the communication CRM + your field-service software as the operational record — the pairing from GoHighLevel vs. Jobber, with the division of labor spelled out. One customer record, two views, synced.
• What to avoid: running two CRMs that don't sync (the "marketing database" vs. the "real customer list" split). The moment customer data lives in two places, neither is trustworthy.
• The test: the owner takes a week off. Can the team answer "what's the status of every open estimate" without calling the owner? If yes, the coordination layer works.

Compliance note: whichever tool sends your business texts, the 10DLC registration must be in place first — required before sending business texts, typically 1–7 days for approval and roughly $15–$20 one-time. Include opt-out language ("Reply STOP to opt out") in automated texts, and keep marketing texts inside 8am–9pm recipient local time. This is general information, not legal advice.

The 10-truck CRM: the operating system

• What you need: everything above, plus role-based permissions, pipeline reporting (close rate by estimator, by source, by week), marketing attribution to revenue, and automation that enforces process (stale-deal alerts, follow-up task creation).
• What works: GoHighLevel at higher tiers, a full field-service software platform (ServiceTitan territory — see when you're too small for it), or the combination. At this size the CRM decision merges with the platform decision.
• What to avoid: buying the enterprise platform before you have the admin to run it. A 10-truck shop with no operations lead on ServiceTitan is a 10-truck shop with an expensive spreadsheet.
• The test: can you answer, from the system, which lead source produced the most revenue last quarter and which estimator has the highest close rate? If yes, you're governed. If no, you're guessing at scale.

The migration path (growing through the sizes)

Most shops will live in all three sizes over a decade. The migration path that avoids the painful rip-and-replace:

1. 1 truck → 3 trucks: move the spreadsheet into GoHighLevel (or your field-service software's customer list). Import once, clean during import — dedupe, fill the missing phone numbers, tag the segments. This is the only migration that should hurt, and it hurts for a weekend.
2. 3 → 7 trucks: no migration — add structure inside the same tool. Pipelines get stages, permissions get roles, automations get deeper. The tool grows; the data stays.
3. 7 → 10+ trucks: evaluate the platform decision (field-service software upgrade or enterprise tier). Migrate with the playbook in switching CRMs without losing your data: export, clean, map, parallel-run.

The golden rule of migrations: clean the data during the move, not after. Nobody cleans data after. The migration is the one moment everyone accepts the work — use it.

The data hygiene that matters at every size

• One record per customer. Duplicates are the #1 CRM disease. Dedupe quarterly — or better, prevent them with phone-number matching on entry.
• Every record has a next action or it's dead. A lead with no next-follow-up date is a lead you've abandoned. The pipeline review (weekly, 20 minutes) catches them.
• Segments beat tags. "No service in 18 months" is a segment you can campaign to; a tag called "old customer" is decoration. Build segments around the campaigns you'll actually run.
• The owner audits monthly. Pull 10 random records. Are they complete? Current? If not, the process is broken — and no software fixes a broken process.

Example: the shop that sized it right twice

Example: An electrical shop starts as 1 truck with a Google Sheet — 200 customers, columns for last service and panel age. At 3 trucks, they import into GoHighLevel: the sheet becomes segmented contacts, the follow-up becomes automated sequences, the dispatch stays in their field-service software. At 9 trucks, they don't migrate — they deepen: pipeline stages, per-estimator reporting, the reactivation segments running quarterly. Total CRM migrations in 8 years: one. Total CRM cost over that time: a fraction of what the "buy enterprise on day one" path would have cost — and every byte of customer history survived, because it only moved once.

Related guides in this series

For the tooling at each size, the $0 stack, the $100 stack, and the $300 stack. For the field-service software pairing, GoHighLevel vs. Jobber. For the growth-stage view, from 3 trucks to 10. And the framework is the 8-system framework.

The done-for-you version

This post is part of the Leveraged Owner 8-system framework — the Starter Pack includes the CRM sizing worksheet, the migration checklist, the data-hygiene setup guide, and click-by-click setup instructions for all 8 systems.

No third-party stats used in this post — the frameworks are operational guidance from the Leveraged Owner system library.