Key takeaways
- Start with shared definitions and evidence around jobs, commitments and exceptions; do not begin by replacing the local operating path.
- Reuse workflow skeletons for reporting, intake and evidence preparation while branch leaders retain customer, safety and physical-service decisions.
- Treat completed-job-to-invoice and similar financial workflows as reviewer-gated; this page does not automate accounting or money decisions.
- Pilot one branch and one process with source reconciliation, stop rules and fallback. Portfolio visibility is not proof that local execution transferred.
A home-services job crosses five operating records
| Record | Common evidence | Local control |
|---|---|---|
| Customer commitment | Requested window, scope, change and source | Promise and relationship owner |
| Dispatch state | Job, technician, skill requirement, time and status | Real-world conditions and reassignment decision |
| Field evidence | Notes, approved completion evidence and exceptions | Physical service judgment |
| Billing readiness | Required evidence present and missing-item route | Accounting review and invoice approval |
| Portfolio reporting | Definitions, period, source and adjustment ledger | Local sign-off on unresolved differences |
ServiceTitan's private-equity page is evidence that multi-location operators care about common reporting and operating visibility. It is not evidence that all-agents connects to ServiceTitan, replaces a field-service platform or produces the outcomes that vendor reports.
The useful automation boundary sits between systems: recognize the event, collect permitted evidence, apply stable checks, route exceptions and verify the destination state.
Reuse the skeleton; parameterize the branch
- 01Agree on one event envelopeTriggerUse a stable job identifier, branch, event time, current state and source reference.
- 02Map local status to common meaningCodePreserve the source value and write the mapping. Never overwrite the evidence to make the dashboard neat.
- 03Declare branch parametersHuman approvalCalendars, service areas, response clocks and approval roles need owners and effective dates.
- 04Keep local consequence gatesHuman approvalCustomer commitments, safety, licensing, employment and money actions remain with qualified accountable people.
- 05Test the final stateCodeCompare source and destination by job identifier, publish exceptions and keep a fallback route.
Choose first candidates by evidence and reversibility
| Process | Early bounded work | Permanent or specialist boundary |
|---|---|---|
| Weekly branch pack | Collect, validate and explain source exceptions | Controller reviews definitions and adjustments |
| Completed-job review | Check required evidence and route missing items | Field completion and accounting decisions |
| Customer request triage | Classify request and assemble history | Promise, credit and policy exception |
| Technician schedule review | Detect conflicts and propose alternatives | Safety, licensing, employment and customer context |
| CRM cleanup | Profile duplicates and prepare merge proposals | Data owner approves destructive merge |
Northline standardizes the evidence before the schedule
Northline is a fictional three-branch HVAC and plumbing group. Each branch uses its own dispatch statuses. The portfolio wants one schedule review, but “ready” means three different things.
The first pilot preserves every source status and maps it to a common evidence envelope: appointment, technician, required skill, promised window and blocking reason. The workflow can detect missing evidence and produce a proposed review list. A branch manager still decides any reassignment.
No connector, customer, savings, staffing or service result is claimed.
A portfolio pilot needs one branch, one process and one fallback
- Select a process with an observable trigger and source-backed finish.
- Publish the common definition and every local mapping.
- Test normal work, missing evidence, a local exception and recovery.
- Stop on unauthorized action, unmatched totals or an unowned exception.
- Reconcile final states and keep the local path until the accountable owner accepts the change.
The acquisition process inventory helps choose the candidate without turning consequence into readiness.
Limitations and when not to use this
- This is general process-design guidance, not home-services, safety, licensing, legal, accounting, financial, employment, tax or cybersecurity advice.
- No integration with ServiceTitan, QuickBooks or another named system is claimed. Vendor sources describe their own products and markets.
- Completed-job-to-invoice, payments, employment and licensing processes remain behind their named practitioner-review gates.
- Northline is simulated. No customer, savings, staffing, service-level or portfolio outcome is represented.
Sources
- HVAC Services M&A Update — Capstone Partners Accessed 9 August 2026
- Private Equity Solutions for the Trades — ServiceTitan Accessed 9 August 2026
- The First 90 Days After an HVAC Business Acquisition — Homestead Service Partners Accessed 9 August 2026
Inventory the first branch
Choose a recurring process with visible evidence and a bounded local owner.
Inventory the first branchUli Prantz
Builds and operates all-agents
Uli Prantz builds all-agents, the process-automation platform this site documents. He writes about the operational side of automating recurring business work: where deterministic code beats model judgment, where it does not, and where a human still has to approve.