Where this usually lands in our work: field service, service at volume and marketing automation.
Not in the work. In the handoffs. The estimate that never became a job. The crew sent to an address nobody confirmed. The change order agreed in a driveway and written down nowhere. Each one is small enough to shrug at, and together they are the margin.
We put the sale, the schedule and the job on one record, so the office stops reconstructing what happened in the field and the person who sold the work can see whether it was delivered the way they sold it. Dispatch gets a day that survives a cancellation, and the customer stops being the one who has to explain the history.
Home services money is made and lost in the handoffs. These are the five the system has to hold.
Field service software usually assumes a tidy world: one trade, one crew type, a calendar that behaves. Real service businesses run employee crews and subcontractors on the same property, sell work in October that cannot happen until March, and lose an afternoon to one emergency call. The configuration has to survive that.
So we model seasons as data rather than as something the office remembers. We cost work at the level margin actually lives, which for a multi-trade job is the trade and not the project. And we treat completing a job as the event that produces the invoice and the payroll line, because the alternative is a filing tray and a two-week lag.
Beyond phase one
Every one of these started as a complaint from somebody sitting in a truck.
Sell a spring irrigation activation in October and most systems put the work order nowhere useful. Tag the product with its season instead, and a job sold out of season books itself to the start of the next one. Sold work can no longer land in a dead calendar slot and quietly disappear.
One emergency does not cost you one emergency. It costs you the afternoon and then a day of calls to the customers whose appointments you just moved. Re-sequence the affected appointments in bulk against revised windows, then have the system generate the customer calls as actual tasks. The communication debt becomes work instead of guilt.
Maintenance contracts are the most reliably under-captured revenue in field services, because chasing them depends on somebody remembering. Have project completion generate the maintenance opportunity, and a signed service contract generate and schedule the appointments that follow. Recurring revenue stops being a discipline problem.
Field capture on the phone can trigger invoicing within hours of the crew leaving, and the same completed-job data can feed the payout calculation. One pool contractor went from quotes that took hours of geometry to quotes that take minutes, and from invoicing whenever the paperwork surfaced to invoicing the same day.
A roof that runs employee crews on shingles and subcontractors on gutters costs out as one number unless each trade is modeled as its own job under the project. Do that and leadership can finally see which trade drags margin, which is where the pricing conversation actually belongs.
Aspire, ServiceTitan and the trade platform you have run on for a decade are not the problem. Below is what we do at each connection point.
Work orders, scheduling and job completion, reconciled with the customer and the contract.
ServiceTitan Jobber Housecall Pro BuildOps
Where the trade economics do not fit a generic tool, from routes to crew hours per property.
Aspire FieldRoutes PestPac LMN
Stops per truck per day, which decides whether a territory is worth selling into.
WorkWave Route Manager Route4Me Samsara Verizon Connect
True cost per job, crew and property, and the rollups that come with acquisitions.
QuickBooks Sage Intacct Acumatica NetSuite
Hourly, multi-crew labour with overtime and prevailing-wage complexity.
ADP Workforce Now Paylocity Paycor
Homeowner financing that closes replacement work at the kitchen table.
Wisetack Sunbit Stripe
The reschedules, the callbacks, the jobs that slipped a day and then a week. Some of that a dispatch board can absorb. The rest is a data problem wearing a scheduling costume, and the two need different fixes.
