The phone rings while you're under a sink
A crew on a job can't answer, so the call goes to voicemail or a generic auto-text, and the homeowner dials the next plumber on the Google results before anyone calls back.
Who it's for
Home services companies
We replace the messy layer between website, intake, CRM, follow-up, and internal workflow so leads stop falling through handoffs and the owner gets one clean view of booked work.
Signals
When this is the right fit.
- Missed-call and form leads with no clear next step
- Quoting and scheduling run from memory
- Follow-up and review requests done manually
- Owner visibility into booked work comes from calling staff
- Estimates sent with no tracking of whether they were viewed
AI in this sector
- Missed-call triage — OpenClaw routes and scores incoming leads by source and urgency
- Follow-up drafts — estimate follow-up and review-request messages drafted from CRM records
Graph layer: Referral-source tracking surfaces which job sources produce the highest-value customers over time — not just the first lead, but the downstream work that follows from each intake channel.
Go deeper: Automation fabric · OpenClaw co-pilot
The problem
Where the work leaks.
Leads scattered across five inboxes
Calls hit the cell, web forms hit email, Angi and Thumbtack drop leads in their own apps, and referrals come by text — so no one place tells you who still needs a callback today.
Estimates sent into a black hole
A quote goes out by email or as a Jobber PDF and then nothing — you can't tell if the homeowner opened it, is comparing bids, or already hired someone else, so follow-up is a guess.
Scheduling lives in the dispatcher's head
Who's on which job, which truck has the part, and what's still open today are tracked in a whiteboard, a group text, and one person's memory — and it all stops when that person is out.
Review requests only when someone remembers
The five-star jobs never get asked for a review because the tech is already on the next call, so your Google profile undersells the work you actually do.
The owner finds out by calling around
To know what's booked this week, what estimates are still open, and which leads went cold, the owner texts the dispatcher and three techs instead of opening one screen.
Your stack today
From a ring of rented tools to one owned layer.
Most home services shops run a field-service app plus a stack of point tools and lead marketplaces, with the owner stitching it together by phone — here's the typical map and the owned surface that absorbs each job.
Job to be doneWhat you may be rentingIn the owned layer
- Lead captureMissed-call auto-text, Angi / Thumbtack / Google LSA inboxes, website form to emailOne intake pipeline where every call, form, marketplace lead, and referral lands scored, staged, and owned
- Scheduling & dispatchJobber, Housecall Pro, ServiceTitan, or a whiteboard plus a crew group textA dispatch-aware pipeline the owner sees live — who's assigned, what's booked, what's still open today
- Estimates & quotesEmailed PDFs, app-generated quotes with no read tracking, handwritten ballparksTracked estimates inside the CRM record, with follow-up that fires when a quote sits unanswered
- Follow-up & remindersManual texts, sticky notes, 'I'll call them Monday' in someone's headAutomated estimate chasing, appointment reminders, and re-engagement sequences off the customer record
- Reviews & reputationAsking in person if you remember, Podium or NiceJob bolted on as another subscriptionReview requests that fire automatically when a job closes, tied to the customer and the job source
- Invoicing & paymentQuickBooks, Square, paper invoices, 'we'll mail you a bill'Invoice and payment status sitting on the same job record the owner already watches
- Owner reportingCalling the dispatcher, exporting app reports, a spreadsheet rebuilt every monthOne live owner view of booked work, open estimates, no-response leads, and job status
Capabilities
What the operating layer does in this sector.
CRM & Dispatch Pipeline
Missed calls, web forms, quote requests, and referrals land in one dispatch-aware pipeline — scored, staged, and routed so the next crew action is always clear.
Automation
Estimate follow-up, review requests, and reminder sequences run automatically — so a sent quote or a finished job never depends on someone remembering to chase it.
Owner Dashboard
One live view of booked work, open estimates, and no-response leads — the owner sees job status without calling around the crew.
In practice
How a missed call becomes a booked, reviewed job
Capture
A missed call, web form, Thumbtack lead, or referral text lands in one pipeline as a real record — not a voicemail or an unread app notification — with the source tagged so you know where it came from.
Triage & route
OpenClaw scores the lead by source and urgency and routes it to the right person, so the emergency no-heat call surfaces above the routine quote request instead of waiting in line.
Quote & track
The estimate goes out attached to the customer record and the pipeline stage advances, so an unanswered quote is visible as 'open estimate' rather than disappearing into an email thread.
Follow up automatically
If the estimate sits unanswered, a follow-up sequence drafts from the CRM record and chases it on schedule — no one has to remember to call the homeowner back on Monday.
Book & dispatch
Once accepted, the job moves to booked and shows on the owner's dashboard with the assigned crew, so scheduling lives on a screen instead of in the dispatcher's memory.
Close & ask for the review
When the job closes, a review request fires automatically and the customer ties back to its original source, so your reputation and your best lead channels both compound.
Before / after
What changes when it runs on owned rails.
Leads live in voicemail, email, two marketplace apps, and a group text
Every lead enters one tracked pipeline with a source tag and an owner
A sent estimate disappears until the homeowner happens to reply
An open estimate is a visible pipeline stage with follow-up that fires on its own
Today's schedule lives in the dispatcher's head and a whiteboard
Booked work, assigned crews, and open jobs sit on one live owner view
Reviews get asked for only when a tech happens to remember
A review request fires automatically the moment a job closes
The owner learns what's booked by calling the dispatcher and the crew
The owner opens one screen for booked work, open estimates, and cold leads
How the work varies
The same Business OS idea, tuned to this operating model.
Lead & quote intake
Missed-call, quote, referral, and form intake into one dispatch-aware pipeline.
Job & crew flow
Crew, route, estimate, booking, invoice, and review follow-up handoffs.
Owner dashboard
Owner view of booked work, open estimates, no-response leads, and job status.
First build
Start with the highest-friction handoff.
Start where money leaks fastest: quote intake, response speed, booking, and follow-up before layering route or payment visibility.
Guardrail
Keep operational promises tied to scheduling, estimates, jobs, follow-up, and owner visibility until field-worker apps are scoped per client.
FAQ
Home services companies — straight answers.
Start where money leaks fastest: quote intake, response speed, booking, and follow-up before layering route or payment visibility.
Keep operational promises tied to scheduling, estimates, jobs, follow-up, and owner visibility until field-worker apps are scoped per client.
The owner gets one clean view of leads, work, and follow-up instead of piecing it together from memory and spreadsheets.
Ownership means portable data, exportable configuration, clear exit rights, and client-specific workflow IP. For managed cloud clients that is the model; literal infrastructure ownership is the self-host deployment case. Either way the operating layer is branded to your business, not rented from a vendor.
No. We start with the layer that leaks first — lead intake, response speed, estimate follow-up, and owner visibility — and connect to the field-service app you already run. The goal is one clean view over the work, not a forced rip-and-replace on day one. As more of the flow moves into the owned console, you decide what's still worth paying a separate subscription for.
Yes. Those marketplace leads, your website form, missed-call texts, and referrals all land in the same intake pipeline, each tagged with its source. That's also what makes the referral-source view work: you can see which channels produce customers who book again, not just which channel was cheapest per lead.
Field-worker apps are scoped per client rather than promised by default. The core build stays on what reliably moves money: lead and quote intake, response speed, scheduling visibility, follow-up, and the owner dashboard. If a crew-facing app makes sense for your operation, we scope it deliberately instead of bolting it on.
It works inside the console with you in the loop. It triages and scores incoming leads by source and urgency so the emergency call rises to the top, and it drafts estimate follow-ups and review requests straight from the CRM record. It suggests and drafts the next action — you approve what goes out.
Next step
Map this sector against your actual stack.
The consultation starts with your current public presence, intake, CRM, follow-up, software stack, and owner visibility. From there, the Business OS Diagnostic shows what to keep, replace, or connect first.