I. "ServiceTitan AI is what we need, just configured well."
The most common misread. The Pro Services team configures the standard AI features tightly: call summarization, technician scheduling, basic retention triggers. The features work. The platform CEO sees green dashboards.
What the dashboards don't show: the leverage points specific to multi-brand PE platforms. Cross-brand dispatch normalization. EBITDA-bridge reporting in the format the Operating Partner reads. Acquisition-integration FSM bridges. Membership-conversion priming with cross-brand customer history. None of these are in ServiceTitan's roadmap because the average ServiceTitan customer doesn't need them.
The honest read: if the LP deck math depends on multi-brand consolidation, off-the-shelf doesn't get there. Custom AI on top of ServiceTitan does. The ServiceTitan AI Integration Playbook describes what we'd commission.
II. "Each acquired brand can run its own AI configuration."
The second misread. Newly-acquired brands inherit their own ServiceTitan tenant configurations, their own dispatch logic, their own retention cadence. The platform's ops team doesn't want to flatten this immediately because each brand has institutional muscle memory tied to its current configuration.
The cost: dispatch optimization is brand-by-brand. Technician utilization runs 12-18% below what cross-brand routing would deliver. The platform's $42M-running-rate becomes a $40M-running-rate not because revenue is lower but because operational density is.
The honest read: letting brands run separate AI configurations costs the platform 12-18% of dispatch leverage. Cross-brand normalization is a custom AI workflow; it's not configuration. Same pattern at platforms running mixed FieldEdge + ServiceTitan stacks.
III. "The Operating Partner doesn't need technical AI conversations."
True, but the consequence is misread. Most platforms hold the OP at arm's length from AI implementation, on the theory that the OP doesn't need the technical detail. What the OP actually wants is the EBITDA-bridge math: this AI line item moves these specific operational metrics, which translate to these EBITDA dollars, which at our exit multiple translate to this exit-value uplift.
Platforms that don't translate AI work into exit-multiple math get less budget than platforms that do. Same actual operational improvement; different OP-level perceived value. The OP funds what they can put in the LP deck.
The honest read: every AI line item should arrive at the OP with the EBITDA bridge already built. "Membership conversion priming" is not the right framing. "$846K of recurring-revenue exit-value uplift, modeled at 9x multiple" is.
IV. "We'll do AI after the next acquisition closes."
Common, defensible, wrong. The argument: M&A integration absorbs all the platform team's bandwidth; AI can wait until the dust settles.
What this misses: AI compresses the integration window. Platforms that commission AI before the next acquisition can absorb that acquisition with a shorter synergy timeline. Platforms that wait until after re-create the same 18-month integration drag every cycle.
For platforms acquiring 2-3 companies per year, this is the highest-multiple-impact line item available. The integration cycle compresses from 18 months to 6 months for the workflows the AI bridges. Synergies start landing earlier; the next acquisition arrives with the previous one already absorbed.
The honest read: AI is the integration accelerator, not the post-integration project. Sequence accordingly.
V. "ServiceTitan is the only system the platform runs on."
Half-true and the half that's wrong matters. ServiceTitan is the FSM. The platform also runs on a phone system, a customer-call layer, a marketing automation tool, a CRM (sometimes), an accounting system, a payroll system, an HRIS, and increasingly a separate analytics layer the OP relies on.
Off-the-shelf ServiceTitan AI lives inside ServiceTitan. The leverage in many workflows lives at the seams: the call layer into ServiceTitan dispatch, the marketing layer into ServiceTitan customer records, the analytics layer pulling from ServiceTitan + the accounting system + payroll into the OP's deck.
The honest read: the highest-leverage AI workflows often span ServiceTitan + 2-3 other systems. Custom AI architecture spans them; off-the-shelf ServiceTitan AI doesn't.
What we'd do.
If you're running a $20M-$100M PE-backed home services platform and any of the five above resonates, the next step is the Call-Center Leakage Calculator for a 90-second EBITDA-bridge read, or the diagnosis call for a written one-page scope. About 30% of the platform diagnoses we run end with us recommending the Pro Services + standard ServiceTitan AI path because the platform's specifics don't justify custom commission. The other 70% end with a custom-commission scope shaped against one of the five misreads above.