From 6 hours a day to 12 minutes: rebuilding intake for a regional services company

The situation

The client was a regional home services company with a healthy book of recurring customers and a steady inflow of new leads. But inside the office, intake had become a bottleneck the team had stopped noticing.

Every inbound order touched four systems:

1. The email inbox where leads and orders arrived.
2. The CRM where customer records lived.
3. The scheduling platform that dispatched crews.
4. A shared spreadsheet the finance team used for weekly reconciliation.

One coordinator — call her Lisa — was responsible for keeping all four in sync. She did it well. She'd been doing it for three years. She was also spending roughly six hours a day doing it, and the company had grown 40% year-over-year with no plan for how this would scale.

What we found in discovery

In the first two weeks, we shadowed the intake workflow, interviewed five stakeholders, and mapped every step from "email arrives" to "crew dispatched."

Three things surfaced:

1. Three of the four systems had APIs that had never been connected. The integration work to link them was genuinely available — it just hadn't been prioritized.
2. One of the four systems — the spreadsheet — existed only because of a reporting gap in the CRM. That gap had been closed in a CRM update 14 months earlier. Nobody had noticed.
3. Quote response time was averaging 18 hours because intake had to clear Lisa's queue before a quote could be produced. The team believed it was averaging "a few hours."

The approach

Rather than propose a big-bang replatforming, we staged the work in three 2-week increments:

• Increment 1: Eliminate the spreadsheet. We built a direct report from the CRM that produced the same numbers the finance team needed, delivered to the same channel on the same cadence. The spreadsheet retired. Lisa's workload dropped by 25% immediately.
• Increment 2: Connect email to CRM. We introduced an inbound parser that extracted structured data from the order emails and created CRM records automatically, with a confidence score. Anything above threshold flowed straight through. Anything below went to a review queue — which is where Lisa's job moved.
• Increment 3: Connect CRM to scheduling. We built a thin integration that pushed approved orders from CRM into the scheduling platform. Dispatcher now pulls from a single queue instead of re-typing.

Total engineering work: about four weeks. Total project: seven weeks including discovery and cutover.

The outcomes

Measured four weeks after go-live, compared to a pre-project baseline:

• Intake time: from 6 hours/day to ~12 minutes/day for exception handling.
• Quote SLA: from 18 hours to under 4 hours (and trending toward under 2).
• Transcription errors: down 92%. Remaining errors cluster in the review queue and get corrected before they reach customers.
• Lisa's role: shifted to managing the exception queue, owning the integration, and training the next coordinator to do the same. She got a raise.

What didn't happen

• No one lost their job. The 30 hours a week we removed went back into work that had been chronically under-served: customer follow-up, quote refinement, and crew scheduling optimization.
• No platform replacement. The client kept the four systems they already had. We just made them talk to each other.
• No ongoing retainer. The client's internal team now owns the integration. We remain on a light-touch advisory relationship for when they want to extend it.

Why it worked

Three things.

First, the win that funded the rest of the project came from deletion, not addition. Eliminating the spreadsheet took a week and freed enough capacity to build confidence for the bigger moves.

Second, we staged delivery so Lisa and the team saw improvements every two weeks. Change management is real, and big-bang cutover projects fail in places smaller ones succeed.

Third, we designed for the client's team to own the result. The integration is documented, the runbooks are written, and the team knows how to extend it. The engagement is over. The value keeps compounding.