Home services and trades
KPIs PE buyers track in home services and where they live in your data
By SourceX Editorial · Updated
Short answer
Private equity buyers in home services track booking rate, close rate, average ticket, membership conversion, technician revenue per day and callback rate, and they rebuild each from your field service and accounting data. Write down every definition, name its source report and fix common data errors before diligence, when restated numbers cost credibility.
Key takeaways
- Buyers rebuild KPIs from raw exports, so your definitions must be written down and repeatable.
- Most KPI disputes come from what is counted: zero-revenue tickets, callbacks, warranty jobs and unbooked calls.
- Every KPI should trace to a named system, report and filter set.
- A software change or job type change mid-period needs a documented bridge.
- Branch and technician detail matters as much as company totals.
Which KPIs do PE buyers ask for first?#
The KPIs PE buyers ask for first describe how efficiently a home services company turns demand into revenue: how many calls become jobs, how many estimates close, what each job is worth and how productive each technician is. Recurring revenue and quality measures follow close behind.
Expect the request list to arrive grouped roughly as below. Buyers usually want each measure by month, by trade and by branch, not only as an annual company figure.
- Demand: inbound call volume, booking rate and lead source mix.
- Sales: close rate on presented estimates and average ticket by job type.
- Labor: technician revenue per day and billable hours.
- Recurring revenue: membership count, conversion, renewal and visit completion.
- Quality: callback rate and warranty work.
- Margin: gross margin by trade, job type and branch.
KPI definitions, formulas, sources and common errors#
KPI definitions are where most diligence questions start, because the same name can hide different math. The table lists common home services KPIs with a plain-language formula, where the inputs usually live and the errors buyers most often find.
Notice how often the error is a counting rule rather than a typo. Two companies on the same software can report very different booking rates from identical call volumes, simply because one counts existing-customer calls as opportunities and the other does not.
| KPI | Formula | Source report | Common data errors |
|---|---|---|---|
| Booking rate | Booked calls divided by calls that were real booking opportunities | Call tracking or field service call reports | Spam and existing-job calls counted as opportunities; unbooked calls never tagged |
| Close rate | Sold estimates divided by estimates presented | Estimate or sales reports | Unpresented, duplicate or test estimates included |
| Average ticket | Revenue divided by completed jobs with revenue | Invoice or job revenue reports | Zero-revenue callbacks and warranty jobs mixed in or dropped inconsistently |
| Membership conversion | Memberships sold divided by eligible non-member jobs | Membership and job reports | Free bundled memberships counted as sold |
| Technician revenue per day | Revenue attributed to a technician divided by days worked | Technician performance and timesheet reports | Revenue split rules changed; days taken from schedules instead of time records |
| Callback rate | Return visits for the same issue divided by completed jobs | Job reports with recall or callback tags | Callbacks booked as new jobs and never linked |
| Gross margin by job type | Revenue less labor, materials and direct costs, by job type | Job costing reports and the general ledger | Materials not costed to jobs; labor burden missing |
- 01Your work records
- 02Personal details removed
- 03You approve the release
- 04Licensed to AI developers
Why do buyers rebuild KPIs instead of trusting dashboards?#
Buyers rebuild KPIs instead of trusting dashboards because dashboard settings are configurable and rarely documented. A filter that excludes warranty jobs, or a date field that uses scheduled rather than completed dates, can move a KPI without anyone noticing.
The buyer's analysts will pull raw job, invoice, call and membership exports and recompute the figures. Where their numbers differ from your management reports, they will ask why, and every unexplained gap lowers confidence in the rest of the data.
Reconciling to the general ledger is the final check. Revenue in the field service system should tie to revenue in the accounting system, with known differences such as financing fees, refunds or timing explained in writing.
How to build a KPI definitions sheet#
A KPI definitions sheet is a single document that states, for each metric, exactly how it is calculated and from which data. It turns a diligence argument into a lookup and gives a new controller or branch manager the same answers the CFO would give.
Keep the sheet versioned. When a definition changes, record the date and the reason, and keep the old version so historical figures can still be reproduced on their original basis.
- Metric name and plain-language definition.
- Formula, including what is excluded.
- Source system and report name, with the filter settings used.
- Date basis: created, scheduled, completed or invoiced.
- Owner responsible for the number.
- Known exceptions, such as a branch that used different job types.
- Date of the last reconciliation to the general ledger.
Where KPI data usually breaks#
KPI data usually breaks at the handoffs between systems and people: call tracking to booking, technician to office, field service to accounting. Each handoff is a place where a tag can be skipped or a job recorded twice.
The fixes are mostly procedural. Make the call outcome tag required before a call can be closed, link every callback to the original job, and cost materials to jobs at the time of use rather than at month end. Changes like these take effect going forward, which is why they need to start well before a sale process.
| Handoff | What goes wrong | Fix |
|---|---|---|
| Call to booking | Unbooked calls left untagged | Require an outcome tag before a call closes |
| Booking to dispatch | Duplicate jobs for one request | Merge duplicates and lock job creation rules |
| Technician to office | Callbacks entered as new jobs | Link every return visit to the original job |
| Job to invoice | Zero-revenue and warranty jobs handled inconsistently | Use one rule for every branch |
| Field service to accounting | Revenue and materials booked in different periods | Reconcile monthly and record the differences |
Illustrative: a multi-branch services company rebuilds its KPIs#
Illustrative: a fictional multi-branch HVAC, plumbing and electrical company is preparing for a sale process. Management reports show strong booking rates and steady average tickets, built from ServiceTitan dashboards and the accounting system.
The CFO rebuilds each KPI from raw exports and finds two problems. One branch tagged unbooked calls only some of the time, which inflated its booking rate, and warranty jobs with no revenue were excluded from average ticket at two branches but not the third.
The CFO restates the figures on one written definition per KPI, documents the branch differences and notes the date each fix took effect. In diligence, the buyer's numbers match the restated set, and the conversation moves to growth plans rather than data quality.
The same records describe how the work gets done#
The same records that produce KPIs also describe how the work gets done: calls, bookings, dispatch decisions, diagnoses and outcomes. AI developers study job histories like these to build dispatching, scheduling and service agents, so clean, linked records carry value beyond a sale.
SourceX begins any data licensing conversation with a metadata-only fit check in the Supply step of the SourceX five-step transaction, then moves through Rights, Preparation, Approval and Delivery. A company that has already defined its KPIs and documented its systems usually finds that inventory step faster.
Frequently asked questions
What is a good booking rate for a home services company?
There is no single benchmark worth quoting without context, because booking rate depends on lead sources, call mix and how opportunities are defined. Buyers compare your rate with your own history and with similar companies they know. A consistent, written definition matters more than hitting any outside target.
Should KPIs be reported by branch or company-wide?
Both. Buyers start with company totals, but branch, trade and technician detail shows whether performance is broad or concentrated. Branch-level numbers also expose definition differences between locations, which are better found by you than by the buyer.
How far back should KPI history go?
Buyers usually ask for several years so they can see trends and seasonality. Go back as far as your current definitions can be applied reliably, and note where earlier figures come from a different system or definition.
What if we changed field service software mid-period?
Build a bridge. Map old job types, tags and membership types to the new system, recompute overlapping months on both bases if you can, and note where history could not be migrated. A documented bridge is far better than numbers that jump at the cutover date.
Do buyers look at technician-level data?
Often, yes. Revenue, callbacks and membership sales by technician show how much performance depends on a few people. Use technician IDs rather than names in shared files, and be ready to explain how revenue is attributed when several technicians work one job.
Who should own KPI preparation before a sale?
The CFO or controller should own the definitions and the reconciliation, with operations leaders confirming how tags and job types are used in practice. Outside advisers can pressure-test the numbers, but the people who run the systems need to explain them when buyers ask.
Related resources
- IndustryBPO & contact centers data
- QuestionDo AI labs buy financial data?
- QuestionDo AI labs buy spreadsheets?
- InsightCan call centers and BPOs sell their data to AI companies?
- InsightCan banks and credit unions sell their data to AI companies?
- InsightCan roofing contractors sell their data to AI companies?
See if your company qualifies
A short company assessment. No data uploads are needed.