ServiceTitan is the most powerful FSM in field service. It also produces more data than most operators ever act on. A Spaid forward-deployed engineer connects via API, cross-references 6–12 months of job, invoice, dispatch, call, and membership data, and surfaces the patterns your standard ST reports weren’t built to show.
ServiceTitan records what happened. Spaid explains why — and what to do about it.
ServiceTitan is the operational backbone. Dispatch, scheduling, job management, pricebook, and memberships — all of it runs through ST. That’s not what Spaid touches.
ServiceTitan’s built-in reports give you revenue totals, job counts, and technician activity across branches and departments. The aggregates are solid.
ServiceTitan captures call volume, recording availability, and booking outcomes when Phones Pro is active. The raw data is in the system.
ServiceTitan’s pricebook and membership modules handle pricing consistency and recurring revenue tracking at the transaction level.
This requires an API join of job cost data and invoice data at the line-item level. It’s not in the standard ST dashboard — and it’s where the 8–14 point performance spread between your top and bottom techs lives.
ServiceTitan records callbacks when your CSRs book them as callback job types. Many aren’t. Spaid identifies callbacks by cross-referencing address, tech, job type, and return visit timing — regardless of how the job was booked.
ST shows calls answered and jobs booked. It doesn’t tell you which CSR is converting at 68% vs. 84% when joined to your call tracking data. That gap is a CSR coaching problem with a dollar amount attached.
By the time a ServiceTitan monthly report shows a margin problem, it’s been compounding for 3–4 weeks. Spaid monitors GM per job, booking rate, and callback rate daily — and flags variance the week it starts.
ServiceTitan captures what every tech does. It doesn’t extract the behavioral patterns that explain why your top techs close at higher margins and generate fewer callbacks. That’s the operational knowledge graph.
Full API access in 72 hours. Cross-system analysis before Week 1 ends. Revenue gap map in 30 days.
Reads dispatch, invoice, pricebook, call recording, and membership data automatically, in the background. 6–12 months of job records connected before Week 1 ends. No admin time, no IT project, no exports. The analysis starts immediately and the data stays current on a weekly pull cadence.
Surfaces GM variance using identical pricebook items on identical job types. Tells you which techs are driving the gap, which job types are highest-variance, and which patterns explain the difference. The findings your standard ST reports don’t show — quantified in the first 30-day audit.
Identifies callbacks in your ST data regardless of job type booking behavior. Cross-references address, technician, job type, and return visit timing to build the true callback rate by tech and job type. The patterns your standard ST callback report misses because of inconsistent booking practices.
Flags GM per job variance, booking rate drops, and callback pattern changes the week they start — not the month they compound. Monitors pricebook compliance, field execution consistency, and CSR performance daily. The operational monitoring layer that ServiceTitan’s built-in reports don’t provide.
Three things that distinguish a real ServiceTitan consulting engagement from someone who’s run a few ST training courses.
A genuine ServiceTitan consultant connects via the ServiceTitan API and joins data sources automatically. If they’re asking for CSV exports, they’re doing manual work that won’t scale and won’t be repeatable. The analysis breaks the moment your ops team changes a report format or a field name.
API-connected analysis is the only way to run GM by tech × job type on a continuous basisMargin analysis requires joining ST invoice data with job cost data. Callback analysis requires cross-referencing ST with call recordings. CSR booking rate requires joining ST with your call tracking system. If the consultant only works inside ST’s built-in reports, they’re seeing a fraction of the picture — and missing the patterns that explain the variance.
The 5 ST reports that matter require cross-referencing 3+ data sources outside the standard dashboardA good ServiceTitan consultant delivers quantified findings — GM by tech × job type, callback root cause map, CSR booking gap analysis — within the first 30 days. If there’s no commitment to a timeline and a dollar amount attached to each finding, there’s no accountability. The findings need to be measurable before a single process changes.
First quantified findings deliverable within 30 days of engagement startOur Full-Operation Audit (Days 1–30) maps every revenue leak — field and back of house — from your ServiceTitan data. If we don’t identify at least $200,000 in recoverable annual revenue, we refund Phase 1 in full. You keep all audit deliverables.
Your team keeps using ServiceTitan exactly as they do today. After kickoff, we ask for about 30 minutes a week of your ops leader’s time.
We’ll start with a recent export or sample data from your ServiceTitan account, show you the biggest leaks, and scope the engagement. Full API access happens only if you proceed to the audit.
The full ServiceTitan consulting engagement: API connection, GM variance by tech × job type, callback root cause map, and CSR booking gap analysis. $200K guarantee in 30 days.
GM per completed job by tech × job type, callback rate by tech × job type, CSR inbound booking rate by rep, unsold estimate aging, and pricebook compliance by tech. How to run each one and what to look for.
On Jobber at $5M–$25M? The same intelligence layer applies — API connection, GM variance by tech × job type, callback root cause, and CSR booking gaps. With a $200K guarantee.