CRM Consultant for Small Business: A Letter to a 5-Person Crew

A letter to the owner of a five-person service business: when a CRM consultant is worth it, what to have them build first, and what to skip in month one.

By Carlos Familia, CRM & AI automation expert. Updated October 15, 2026. 6 min.

If you run a roofing or HVAC company with one person in the office and a few in the field, and you are shopping for your first CRM, this letter is for you.

A roofer starting a company asked on r/Roofing which of three roofing CRMs to buy for one office employee and two to five sales reps. After a call with one vendor, they figured the plan they would really need was about $350 a month, because the $129 plan capped each job at 50 files and they end up with hundreds of photos per job. One reply warned against tools that "cost an arm and a leg before you even turn profit," and added that their own small business already carries about $700 in subscriptions. Another gave the best advice in the thread: demo one or two, upload a pile of photos and run a fake job.

Do you need a CRM consultant at your size? Rarely for the software choice. The fake job will settle that. You need one when the leads you already pay for slip through the gaps between your phone, your ads and your inbox, and nobody on the crew has time to fix it. The rest of this letter is about that case.

Start with the smallest shape that works

When I set up the GoHighLevel foundation for an HVAC company in California, it was a 7-stage pipeline, 10 custom fields, 18 tags and 2 calendars. That was the entire base, small enough for anyone on the crew to read.

Write your stages the way you already talk about jobs. If your office person cannot explain a stage out loud, it does not belong on the board yet.

Get every lead into one place before you automate anything

The founder of a private real estate lending marketplace had leads arriving as texts, Facebook messages and emails, and no follow-up system at all. The complaint that brought me in was "our contact form doesn't work." The form's code logged each submission, returned "success" and threw the enquiry away, so every message since launch had been lost. The "Contact" link in the footer opened an email app, which does nothing on a computer without one.

I rebuilt the form so each enquiry reaches the founder's inbox with reply-to set to the sender, and added a follow-up queue inside the lead tracker the business already used. The first read of that queue showed 337 leads with no contact in over 30 days.

Your version is probably smaller. Still, fill in your own website form and message your own Facebook page before you pay anyone, and see where each one lands.

Ask for three things in month one

A consultant for a crew your size should build three things first:

1. A first reply to every new lead, from every source. Ads, website, Facebook messages and the phone all land in the same pipeline.
2. A text back after a missed call. Your people are on roofs and in attics, so the phone goes unanswered by design. My missed call text back checklist covers the setup.
3. Confirmations the customer answers in one word. For a roofing contractor in Kentucky, the confirmation asked people to reply YES to confirm or NO to cancel. GoHighLevel can branch on an exact reply, one phrase per trigger, and a NO cancels the appointment without anyone in the office touching it.

Keep each one simple enough that you can read the whole thing on one screen.

Expect the quiet mistakes

On that Kentucky build, the problems were not dramatic. They were silent, and each one cost real leads or real goodwill:

• The workflow allowed no re-entry, so returning customers never got a sequence the second time.
• The reschedule path had no exit.
• The nurture sequence kept emailing customers who had already booked.
• A stop-on-reply ended sequences and told nobody that a person now owned the conversation.
• The account's time zone was set to Eastern while the business ran on Central time, so every timed message was off by an hour.

Ask your consultant how they would catch each of these. The honest answer is a test contact that walks every path, with someone reading the logs afterward. I describe that method in how I test GoHighLevel workflows.

Check that it is actually on

For a life insurance agency in California, the website chat agent was switched on and still answered nobody for a day, because no channel had been assigned to it in the routing settings. The test chat inside the builder worked the whole time. At your size, there is nobody whose job is to notice.

Ask who gets an alert when something stops, and ask to see a real message answered on each channel before you pay the final invoice.

Let one sequence run at a time

For the HVAC company, the estimate follow-up carried a "sequence lock" field, so a customer already inside one sequence could not be pulled into a second one at the same moment. On a crew your size, collisions are not abstract. A customer who gets a review request and an estimate reminder on the same afternoon does not see two workflows. They see a company that does not know what it is doing.

Ask how two sequences stay out of each other's way. The answer should name a field, a tag or a rule, not "the timing works out."

Click everything a customer clicks

Open your own booking link in a private window, on a phone, and try to book the slot you want. Calendars fail in quiet ways. A calendar created through the API for that life insurance agency had no slug, so its share link opened another company's calendar. At an auto body shop, one calendar had hours of 0:00 to 0:00. For a credit repair firm, a calendar with empty hours answered normally with no open days, so nobody could book from the bot or the website, and nothing showed an error.

Then read the names your own team reads. On the HVAC build, waits named "1440 minutes" annoyed the client, because that is a machine's way of saying one day. Name every wait, message and stage in plain words, so your office person can read the system without a manual.

Texting needs paperwork first

If you text customers in the US from a standard local number, carrier registration comes first. HighLevel's help center says registration is required when a business sends SMS or MMS to US recipients from standard 10-digit local numbers.

The Kentucky roofer had not registered yet, so email carried the follow-up while the paperwork moved. A consultant who builds a text-heavy system before you have approval has built something you cannot use yet. The steps are in my GoHighLevel A2P guide.

What I would keep out of month one

• Anything that talks to customers in free text without a person testing it first. On the Kentucky build, a test-mode string leaked to a lead.
• A second pipeline. One is enough for a crew your size.
• Dashboards. Count your leads, jobs booked and reviews by hand for a month, then decide what to measure.

What should this cost you?

I do not quote my own prices, so here are the numbers I trust. On the software side, HighLevel's pricing page lists Starter at $97 a month, the figure to set against the roofer's $350. Consultant ranges, and the monthly bills that come on top, are in CRM consultant cost. Ask any bidder to write down the pipeline, fields, calendars and automations by number, so you can compare two quotes line by line.

If you would rather install than hire, the roofing pack is $22 and carries confirmations, reminders, no-show follow-up, missed call text back and pipeline moves, tested with test contacts on every path. If your problem is leaving a tool you already pay for, read CRM migration consultant first. For trade-specific setups, see roofing CRM and the home services page. When you are ready, book a call and bring your three biggest leaks.

P.S. Run the fake-job test on the consultant too. Give them one made-up lead, from your real website form, and ask to see every step it triggered and every message it would have sent.

About the author

Carlos Familia, CRM & AI automation expert. GoHighLevel, n8n, AI agents, servers. Full-stack developer.

I build CRM systems in GoHighLevel, n8n automations on my own servers and AI voice and chat agents for service businesses. Full-stack developer: I write the workflow, the API integration, the database and the server it runs on, and I test every build with real journeys before handoff.