ServiceTitan–Podium Integration Ends Sept. 15. Nearly 1,000 Contractors Are Caught in the Middle

Status check — September 14, 2026

A contractor can own two software subscriptions and still not own the connection between them.

What contractors need to know before the cutoff

• ServiceTitan told affected customers the Podium integration would end September 15, 2026, after a roughly nine-year partnership.
• Podium CEO Eric Rea has said nearly 1,000 shared contractors are affected; ServiceTitan has not publicly confirmed that count.
• The workflows at risk are the ones that depended on ServiceTitan data or events reaching Podium—or Podium data writing back into ServiceTitan—including customer sync, job-triggered messaging, review automation and conversation or lead writeback.
• Podium itself does not disappear on September 15. The issue is the direct ServiceTitan integration. Contractors should separate 'my Podium account still works' from 'my Podium workflows still know what happened in ServiceTitan.'
• ServiceTitan's current approved integration model centers on Certified Apps and Customer-Built Apps. Its documentation says third-party tunneling through a customer's App Key is prohibited.
• Podium is now openly selling its own FSM and says ServiceTitan migrations average 10 to 14 days, which turns the partnership dispute into a direct platform competition story.
• ServiceTitan reported $292.8 million of fiscal Q2 revenue and $26.8 billion of gross transaction volume last week, underscoring the scale of the system-of-record side of this fight.

The cutoff by the numbers

Scheduled cutoff

Sept. 15

ServiceTitan told affected customers the legacy integration would end on this date.

Partnership length

~9 years

The companies had integrated for nearly a decade.

Shared contractors

~1,000

Podium CEO Eric Rea's estimate; not independently confirmed by ServiceTitan.

ServiceTitan Q2 revenue

$292.8M

Fiscal Q2 2027, up 21% year over year.

ServiceTitan Q2 GTV

$26.8B

Gross transaction volume processed through the platform, up 17% year over year.

Podium migration claim

10–14 days

Podium's stated average for switching from ServiceTitan to its current FSM.

The risk is not that every Podium feature stops working at midnight. Podium's phones, inbox, reviews and other services are separate products. The failure point is the automation that needed ServiceTitan to provide context or receive data back.

Podium's historical ServiceTitan directory page describes contact sync plus payment, lead and conversation writeback. It also describes customer communications that use job, appointment and booking context from ServiceTitan. Independent contractor guidance published since the cutoff notice has highlighted the same operational dependencies: customer records can stop syncing, job-triggered texts can lose their ServiceTitan event source, automated review requests can lose the completion signal, and conversation history may stop appearing in the ServiceTitan record.

That distinction matters because a workflow can look healthy from one side. A CSR may still be able to send a text from Podium. A review-request template may still exist. But if the triggering job status never arrives from ServiceTitan, the automation has lost the event that made it useful.

The practical test is therefore not 'Can I log into both systems?' It is 'Does the same customer, job and status still move through the same operational path after the integration is removed?'

Audit these workflows before September 15

The product boundary changed.

Podium began as a customer-communication and reputation-management layer. Its current home-services site now markets a broader AI operating system with phones, reviews, payments, memberships, field-service management and AI employees. Its ServiceTitan comparison page explicitly pitches migration away from ServiceTitan and says most businesses switching to Podium are live in 10 to 14 days.

ServiceTitan is moving in the opposite direction from the system of record outward. The public company now describes itself as an agentic operating system for the trades. In its September 8 earnings release, CEO Ara Mahdessian said ServiceTitan's AI strategy helped drive 21% year-over-year revenue growth and more than $50 million of non-GAAP free cash flow in the quarter. The company expects to end its fiscal year with more than 700 locations enrolled in Max.

When both vendors want to own more of the same customer journey, the old relationship between 'platform' and 'app' becomes harder to preserve. Messaging can become CRM. AI call handling can become booking. Booking can become dispatch. Dispatch can become the system of record. The integration that once increased the value of both products can begin to help one product replace the other.

ServiceTitan's position: certification is the price of staying connected

ServiceTitan has said Podium's legacy agreement expired and that Podium chose not to move forward through its current certification program. In its statement to HomePros, ServiceTitan said the legacy Podium integration was not in compliance with its Marketplace standards and that it was supporting affected customers directly.

ServiceTitan's current integration documentation is clear about the paths it supports. Contractors can use a ServiceTitan Certified App from the Marketplace, or—on qualifying packages—build and maintain a Customer-Built App with their own App Keys. The company explicitly prohibits third parties from tunneling through a customer's App Key to gain access.

That has a practical implication for shops looking for a last-minute workaround: replacing one unsupported dependency with another can simply move the risk. If a new bridge depends on credentials, API access or behavior ServiceTitan does not approve, the contractor may be rebuilding the same fragility under a different name.

Podium's position: the rules changed as its product expanded

Podium's Eric Rea has framed the dispute differently. He has said the company was willing to discuss commercial terms but objected to restrictions it believed would limit Podium from continuing to build products that overlap with ServiceTitan. He also criticized the approximately 30-day transition window given to shared customers.

HomePros reported that ServiceTitan's newer Marketplace framework includes technical standards and an economic component such as connection-based fees or revenue sharing. It also reported a ServiceTitan policy statement that competitive products are welcome so long as the partner is not using the relationship to progressively displace more of ServiceTitan.

Those are competing commercial narratives, and Dispatch cannot adjudicate the private contract between the companies. What is public is the direction of Podium's product: it now competes directly for the field-service-management layer and markets migration from ServiceTitan as a supported path.

Contractors usually evaluate software one product at a time: Which CRM is best? Which phone system? Which reviews platform? Which AI agent?

The ServiceTitan–Podium split exposes a second layer of risk: the business process may depend on the relationship between two vendors even when the contractor has contracts with both. That relationship can change without the contractor having a vote.

This is especially important as AI makes software categories overlap faster. A reviews tool can become a communications suite. A communications suite can become an FSM. An FSM can add voice agents, marketing automation, payments and financing. The more products expand horizontally, the more likely yesterday's integration partner becomes tomorrow's competitor.

A mature technology stack therefore needs an integration inventory, not just an app inventory. Owners should know which automations are native, which rely on a certified partner, which use a customer-built integration, which system holds the authoritative record, what the notice period is if a connection disappears, and what manual process keeps revenue moving while the connection is down.

What to do before the September 15 cutover

• List every Podium workflow that depends on ServiceTitan data or job events. Do not use product names as the checklist; use actual business processes such as 'review request after completed job.'
• Run test records through customer creation, booking, dispatch, completion, payment and review request. Document which platform triggers each step today.
• Confirm the replacement path with both vendors in writing where possible, including the exact date and time your account's integration access changes.
• Export or preserve any customer-communication history your CSRs need to work efficiently. A searchable archive can matter even if the source platform remains active.
• Assign a human owner for each workflow that may need a temporary manual fallback. A broken automation with no named owner becomes an invisible revenue leak.
• Do not assume an unofficial API bridge is equivalent to a supported integration. Check ServiceTitan's current approved integration rules before connecting a third party through your credentials.
• Watch for duplicate messages. During migrations, the risk is not only that a reminder disappears; two systems can also fire the same reminder or review request.
• After cutoff, audit the first full day of leads, appointments, completed jobs, payments and reviews against the prior week. Confirm events still reconcile to the system of record.

What happens next matters more than who won the argument

The near-term test is operational: how many shared customers reach September 15 with a clean replacement workflow, how many experience broken automations, and whether either company announces a longer transition or alternate connection path.

The longer-term test is strategic. Podium is betting that AI can compress the switching costs that protected incumbent systems of record. ServiceTitan is betting that an agentic layer is most powerful when it is built on the contractor's operational database and transaction flow.

Both theses can be true for different contractors. The lesson from this cutoff is that interoperability itself has become a competitive asset—and a competitive weapon. Owners should price that risk before they make the next software decision, not after the integration email arrives.

ServiceTitan–Podium cutoff questions

Dispatch will update this story after the cutoff

Methodology

TradeVulcan Dispatch rechecked the ServiceTitan–Podium cutoff on September 14, 2026 against ServiceTitan's current approved-integration documentation and investor disclosures, Podium's current home-services and ServiceTitan-comparison pages, the companies' public executive statements, HomePros reporting and independent contractor transition guidance. The nearly 1,000 affected-customer figure is attributed to Podium CEO Eric Rea and is not presented as a ServiceTitan-confirmed count. ServiceTitan financial figures come from its September 8 fiscal Q2 2027 release. Podium's 10-to-14-day migration timing is a Podium marketing claim, not an independently benchmarked migration result. Dispatch found no public deadline extension as of publication, but account-specific cutover timing may vary and should be confirmed directly with the vendors.