What should the buyer be able to reproduce?
Explain metric and link to financial records. Identify report, period, date basis, units, job status, exclusions, formula, permissions, and export date. A buyer needs both result and method to reproduce the calculation.
The operations hub links price, staff, dispatch, demand, and duties. Software name shows a system in use. It does not establish correct setup or reliable figures; review actual records and workflow.
Save settings with output. Explain changed filters or excluded categories and why. Reviewer should trace differences between exports. The favorable number is not necessarily the comparable one; preserve original scope and changes.
How should a flat-rate pricebook be examined?
ServiceTitan's pricebook documentation describes service, material, and equipment items in estimates, invoices, and flat-rate workflows. It establishes vendor features, not a margin result. Check the operator's actual use and configuration.
Review version, service scope, materials, labor assumptions, discounts, and tax handling. Who approves changes, and how do crews use items? A standard task price may not cover a different job. Record actual variations before judging contribution.
Compare quoted and invoiced work with actual time and materials. Include changed scope, credits, and callbacks. Review earnings after delivering promises. List price alone does not show which work occurred, what was paid, or actual costs.
What evidence chain connects price to contribution?
Trace inquiry, booking, dispatch, estimate, approved work, completion, invoice, credit, payment, and costs. Use consistent IDs. Explain missing links. Unrelated totals should not become one assumed chain; source records must support the relationship.
IRS Publication 583 describes records for receipts, costs, and assets. They support financial review. Dispatch status and ledger balance can both be correct while using different dates or groups; reconcile scope before comparison.
| Data stage | Record to preserve | What remains to reconcile |
|---|---|---|
| Listed price | Dated pricebook item and scope | Actual job variation and discounts |
| Approved estimate | Customer authorization and version | Completion and changed work |
| Completed job | Status, service date, time, and materials | Invoice and callback treatment |
| Invoice | Actual line items and adjustments | Revenue timing and credits |
| Collection | Receipt, refund, and outstanding balance | Earned amount and payment timing |
| Contribution | Reconciled direct costs and included revenue | Shared overhead and remaining obligations |
This table guides review, not accounting policy. Document treatment of taxes, deposits, refunds, and prepayments. Reconcile actual report settings to the chosen financial view so readers can follow what each amount represents.
How can a hypothetical price example expose the assumptions?
Suppose an invented task has a $600 list price. A documented $50 discount produces a $550 invoice before taxes and other adjustments. Recorded labor, materials, and travel total $350, leaving $200 of direct contribution under those limited assumptions.
A later $80 callback cost reduces that contribution to $120 if it belongs to the same job under the stated method. Collection timing remains separate: a $550 invoice is not proof that cash has arrived.
These invented figures set no recommended price or margin. Include admin and shared costs where measure requires them. Trace realized economics rather than call the initial $600 revenue or profit. The stated direct-cost case omits other costs.
Which average-ticket definitions can mislead a buyer?
ServiceTitan's KPI guide defines job averages. Opportunity-job average excludes specified warranty, no-charge, and recall categories. Completed-job views may use other denominators. Save actual definition before treating displayed averages as like measures.
Which measure suits the question? Bridge excluded work so workload and costs remain visible. A dashboard average should not remove callback hours or warranty work from purchase economics. Show included and excluded activity alongside its costs.
The technician-productivity guide reviews labor bases. Revenue per person, per available hour, and contribution per job answer different questions. Use the needed measure with its scope and limits, rather than one favorable ratio for every decision.
Vendor examples or suggested metrics are not verified national benchmarks. Buyer needs repeatable target records and a supported operating explanation. Context may help questions without proving a company should achieve a particular result.
What happens when prices or workflows change?
Date versions for pricebook, service codes, discounts, statuses, and definitions. Use consistent periods or explain differences. Coding changes may look like better operations. Preserve settings and bridges so reports do not silently change basis midway through a trend.
Separate price, volume, mix, capacity, and cost effects where supported. Higher invoices may reflect different jobs. Lower cost share may reflect reclassification. If data cannot separate causes, show that limit rather than claim a price rise or savings is proven.
The technician-retention guide connects staff and work. Training and availability affect delivery under price plans. Pricebook alone does not explain every result; check the actual labor and services behind the reporting period.
Test findings with field and finance teams, linked to records. Explanations help review but do not replace proof. If drivers cannot be separated, retain that limit in the buyer's summary rather than select one convenient cause.
What does an export actually include?
ServiceTitan's report-export guidance describes output affected by filters and permissions. PDF or spreadsheet gives a defined view. It is not proof of complete backup or migration package; check required data separately.
Its pricebook import/export guidance describes selectable units and inactive items. For acquisition-related transfer it directs customers to the Customer Success Manager. Check provider process and rights for actual terms rather than assume unrestricted copy or import.
Other systems may differ. Check current provider guidance and target contract before assuming like fields or portability. A readable file proves neither ownership nor consent and may omit relationships, history, attachments, or settings needed to recreate the system.
Save originals and approved versions. Review migration scope, responsible people, and validation separately. Diligence access is no uncontrolled operations change. An import affecting live services needs actual authority and a tested plan, beyond permission to read reports.
How should sensitive data be shared?
The FTC information-security guide recommends knowing sensitive fields, limiting retention, and controlling access. Apply to customer, staff, and payment data. Share evidence through appropriate roles and scope rather than provide every personal field to all reviewers.
Share fields needed for the question. Coded IDs and summaries support some reviews; authorized advisers may need controlled source access. Record permissions and permitted use. A reproducible metric need not require public disclosure of every underlying personal detail.
The membership-design guide covers status, consent, and benefits. Retain fields needed to reconcile duties while limiting private detail. A transfer plan needs those actual rights and records, not merely a total member count.
Which operating summary is useful before a sale?
Show definition, period, mix, included jobs, reconciliation, and limits. Link work to invoices, payments, direct costs, and callbacks. Make pricebook and reporting changes visible. Reviewer should know which basis supports the result and which questions remain unresolved.
The marketing-cost guide adds demand denominators. Booked, completed, and paid jobs differ. Use the relevant endpoint; combining lowest marketing cost with highest revenue denominator can mix scopes and conceal real delivery or cash outcomes.
Summary should identify further proof needed. It supplies no guaranteed software premium, pricebook gain, or universal productivity target. State supported operating facts and scope so buyer can review proposed earnings changes against actual evidence.
What sequence makes the data decision-ready?
- Preserve current pricebook versions and approved service definitions.
- Document dispatch, invoice, payment, and cost identifiers and dates.
- Record report settings, populations, exclusions, and formulas.
- Reconcile prices through collected revenue and job contribution.
- Verify export scope, permissions, contractual rights, and provider requirements.
- Share a reproducible summary with controlled access to supporting evidence.
Assign records during normal work. Last-minute reconstruction may leave gaps even with a polished dashboard. Dates, settings, source links, and responsible people make review repeatable rather than dependent on one staff member's memory.
Pricing and dispatch records help assess margins, capacity, and transition when the economic chain is visible. Flat-rate method and software brand alone settle none of those questions. Use traceable work and costs to support actual findings and any proposed change.