The Shop That Was Busy and Still Leaking Revenue

Most roofing, HVAC, and remodeling owners do not think they have a lead problem.

The phone rings. The inbox fills. The crew calendar looks full. Marketing is spending money. Someone is "in the CRM." On paper, the shop is busy.

Busy is not the same as under control.

This example combines recurring problems, and fixes, from real Full Throttle engagements across home-services businesses. No single client is described. Details are generalized on purpose. The leaks are real.

If you run a trades or home-services shop and this sounds familiar, that is the point.

Situation: a busy mid-market trades shop

Picture an established multi-crew home-services company in the mid-seven to low-eight figure range.

They had paid and organic lead flow that looked healthy on ad dashboards. A CRM that was purchased, partially configured, and mostly ignored after week one. Estimators living in text threads and email. Production learning about jobs late, or with missing scope. Finance reconciling reality in spreadsheets after the month closed.

Revenue was happening. Visibility was not.

Owners in this seat usually ask the same thing: estimates are going out, the calendar looks full, and cash still feels tighter than it should.

Leaks found

We did not start by buying another tool. We mapped how revenue moved: Marketing starts it, Sales closes it, Operations delivers it, Finance counts it. Then we pulled diagnostics the shop could already run.

Not every shop has every leak. This example brings several of those problems together.

Lead handoff with no owner and no clock. Inbound hit a shared inbox or a generic CRM queue. First human contact was hours or days, not minutes. Nobody could name the owner of a random lead in under ten seconds.

Estimate-to-job lag. Estimates went out. Follow-up died after a couple of touches. By the time someone called back, the homeowner had booked a competitor who simply stayed in the conversation.

CRM as a filing cabinet. Stages meant different things to different people. "Sold" sometimes meant verbal yes, sometimes signed contract, sometimes on the schedule. Exit criteria did not exist. Forecast was a feeling.

Marketing spend without attribution. Ad platforms claimed credit. The CRM could not prove which sources produced booked jobs versus tire-kickers. Budget meetings argued about creative instead of margin.

No real job costing. Price came from gut, competitor rumor, or last year's sheet. Labor, materials, callbacks, and change orders did not roll up to a job leadership trusted. The shop could be busy and still underpricing the work that filled the calendar.

Finance on spreadsheets. P&L landed late. Cash and accrual told different stories. Ops and finance argued about which number was real.

None of that is exotic. It is what happens when revenue is treated as a result to cheer for instead of a process to run.

What we changed

The work was RevOps in the trades sense: people, process, and platform across all four cycles.

Process first. Stage definitions tied to buyer and job milestones. Single-owner rules for every lead and opportunity. Exit criteria so deals could not sit mid-pipeline forever without a disposition. A simple next-step plan on late-stage work: owner, date, shared when it mattered.

Speed-to-lead and follow-up. Routing with fallback ownership. A real contact SLA on inbound. Codified sequences so touches after the third call still happened when the estimator got pulled to a site visit.

CRM made usable. Kept the fields that mattered, killed the ones that did not, trained the minimum daily discipline, and tied stage movement to something observable. We built one system people would actually open.

Marketing tied to outcomes. Source captured at intake. Reporting rebuilt around estimate volume, close rate by source, and job gross margin where data allowed.

Job costing and finance rhythm. Job-level cost visibility wired to how the shop already worked, with a weekly review Ops and Finance both attended. Spreadsheets stopped being the system of record for the number that mattered.

Cadence. Weekly pipeline and production review. Monthly closed-lost and margin review with one process change owned by a named person. Tripwires on stale stages and stale leads.

Engagement shape for work like this usually lands in two lanes: a focused build when one system is the problem, or a full system build when CRM, automation, reporting, and training move together. Pricing detail lives on the pricing page. This piece stays on the leaks and the rebuild.

What we typically see move

Across engagements where these leaks closed, this is what usually improves:

  • Speed-to-lead compresses from hours or days toward minutes on inbound that matters, once routing and ownership exist.

  • Follow-up coverage rises past the third touch. "No decision" piles shrink because the sequence still runs when the week gets loud.

  • Forecast stops being theater. One language for stages and exits.

  • Marketing spend gets a verdict. Some channels keep budget. Some get cut.

  • Margin shows up at the job, including during the week, not only when the month closes.

  • Finance and Ops argue less about which spreadsheet is true.

What does not change overnight: culture. People still skip the CRM when leadership stops inspecting it. The system sticks when the weekly review is sacred.

Who this is for

Owners and operators in trades and home services who are past "we need more leads" as the only strategy. Who have a CRM that is half-alive. Who feel the gap between a full calendar and tight cash. Who want Marketing, Sales, Operations, and Finance on one process. Who prefer a senior-led rebuild over a junior configuration project.

Not for teams that want a new logo, a motivational speech, or a tool install with no process underneath.

If you want the diagnostic before a call, start with the free Revenue Leak Checklist. Nine leaks. Four stages. Pulls you can run on data you already have.

If you already know where it hurts, book a Discovery Call. Thirty minutes. Bring what you found. We will tell you what we would chase first and what fixing it would take. If we can help, we will say how. If we cannot, we will say that.

Composite case study. No single client named. Problems and fixes drawn from real Full Throttle home-services engagements. Framework: Revenue = Business Process.

Next
Next

How Much Does a RevOps Consultant Cost? Real Numbers