From enquiry to invoice without a whiteboard.
In home services the job is won on the phone in the first ten minutes, and lost to whoever answered while you were under a sink. This pack models jobs, estimates, and crews, and puts an AI on first response so the enquiry gets a human-sounding answer before the customer calls the next name on the list.
What lands in your workspace on day one.
Not a template gallery — objects with real relationships, a pipeline with real stages, and automations already running.
- Jobservice type, address, scheduled window, crew, status, value
- Estimateline items, total, sent date, expiry, approval status
- Crewmembers, skills, service area, capacity
- Propertyaddress, access notes, equipment installed, service history
- Customerproperties, lifetime value, preferred contact, warranty status
Rename, reorder, or retire any stage. Add a second pipeline for a different motion.
Automations, not suggestions.
These are live the moment the pack installs. Every one is editable, and every run keeps a step-by-step trace.
Instant enquiry response
An enquiry from your site, a call you missed, or an ad form gets an immediate text asking the qualifying questions and offering booking windows.
Estimate chase
Estimates that go quiet get a scheduled nudge before they expire, and the sequence stops the moment the customer replies or approves.
Appointment windows
Confirmation on booking, a reminder the evening before, and an on-the-way message — the three messages that eliminate most no-access callouts.
Review requests and service reminders
A review request goes out while the job is fresh, and annual service reminders fire off the equipment record without anyone maintaining a list.
The problems this pack was shaped around.
The missed call is the lost job
You can’t answer the phone on a ladder, and voicemail is where enquiries go to die. An immediate text back that qualifies and offers a booking window converts the enquiry you would otherwise have called back at 7 p.m. — by which time they’ve booked someone else.
Service history belongs to the property, not the person
The customer moves; the boiler doesn’t. Modelling the property separately means the next visit starts with what’s installed, what was done last time, and where the key is — which is the difference between a fifteen-minute job and a wasted callout.
No-shows and no-access are scheduling failures
Confirm, remind, and notify on the way, automatically, in the customer’s timezone and inside quiet hours. It’s unglamorous and it recovers more margin than most pricing changes.
The same platform, whatever you sell.
A pack is configuration on top of one shared data model, one filter engine, and one automation engine. That is why you can change any of it without losing the parts that work.
Home services, answered.
Can I dispatch and see crew capacity?
Jobs carry a scheduled window and a crew, and crews carry skills, service area, and capacity — so unassigned jobs and over-committed crews are saved views, and a board grouped by crew is your dispatch screen.
Does it do invoicing and payments?
It tracks estimate approval and invoice status on the job, and integrates with your accounting system through the API. We’re a growth system, not a ledger — we don’t pretend to replace your accountant’s software.
Will customers know they’re texting an AI?
That’s your call, and we recommend transparency. Every AI message is labelled as AI internally regardless, and a human can take over the thread at any point.
Can it handle recurring maintenance contracts?
Yes — recurring jobs generate off the equipment or contract record, so annual services and quarterly visits schedule themselves and show up in the pipeline like any other work.
Start with the home services pack already installed.
Free workspace, the objects and automations above set up at onboarding, and every price published. Customise from something that works.
Free trial · no card required · every price published