ServiceTitan cuts off Podium: what happens when the front end learns to sell the back end

Podium co-founder and CEO Eric Rea posted last week that ServiceTitan gave roughly 1,000 shared customers about 30 days notice that the Podium integration was being switched off, in the middle of peak HVAC season and after nine years as a partner ^[1]. ServiceTitan says it tried to bring Podium into its certified program on new post-agent terms and that certification did not go forward ^[2]; the reason this matters beyond home services is that the layer in front now sells a substitute for the layer behind, and the API was the distribution channel for building it.

The original trade was clear. ServiceTitan is the system of record for contractors, holding scheduling, dispatch, price book, invoicing and the customer file across roughly 7,500 companies, priced per technician per month ^[3]. Podium started in front of it: the phone number on the truck, the texting, the webchat, the review request after a job closes ^[4]. Contractors turned on four flows, and three of them pushed data inward, with leads, payments and message history landing on the ServiceTitan customer record ^[5]. ServiceTitan got a communications layer it did not have to build; Podium got distribution into those 7,500 contractors plus a live feed of job, appointment and customer data ^[6]. Podium was never exclusive, running the same integrations with Housecall Pro and ServiceFusion ^[7].

Then the product changed. Podium's agent business went from zero to $100M ARR in under 24 months, the company began calling the product an AI Operating System, and it shipped a field service management product with a migration team ^[8], averaging more than $4M of new ARR a month over that window ^[16]. Podium's own site says the FSM replaces your scheduling and dispatch software, with a team that migrates contacts, job history and price book in 14 days ^[9]. As SaaStr puts it, a marketplace app does not need a migration team; a 14-day migration is a rip-and-replace motion aimed at customers who arrived through ServiceTitan's own API ^[17].

ServiceTitan had written the rule down first. Its June 24 Marketplace post sets out six certification requirements: security, performance, predictability, data transparency, revenue share and mutual benefit ^[10], and says it "welcomes partners whose products overlap with parts of its own, as long as they're not using the partnership and ServiceTitan's support to gradually displace additional parts of ServiceTitan" ^[11]. That went up seven weeks before the shutoff notice ^[12]. Its API terms, updated April 15, 2026, go further, barring any AI system from independently choosing which endpoints to call and reserving the right to permit AI use at all ^[13].

The cost landed on parties to none of it: roughly 1,000 contractors, about 13 percent of ServiceTitan's stated company count, given 30 days in peak season ^[14][15].

Watch three things. Whether Housecall Pro and ServiceFusion adopt similar certification and AI clauses, since Podium runs the same integrations there ^[7]. Whether the endpoint-selection restriction becomes standard language in system-of-record API terms ^[13]. And whether the 1,000 disconnected accounts churn toward Podium's FSM or stay put and rebuild their comms layer, which is the only real test of who was holding the customer ^[9][14].