ServiceTitan Ends Podium Integration After Certification Split; CEOs Clash Over Timeline

Material update: both CEOs have now spoken

What is now established

Key points for contractors

• ServiceTitan says Podium’s legacy partnership ran its course and Podium chose not to complete marketplace certification.
• ServiceTitan says it cannot continue the integration without a legacy or certified partnership.
• Podium says ServiceTitan went silent for three months and then gave nearly 1,000 shared customers less than 30 days to transition.
• Podium argues that its expanding AI operating system now competes with ServiceTitan; ServiceTitan says competing products have been allowed to certify under the same standards.
• Both companies acknowledge customer disruption, but they disagree sharply about who created the compressed timeline and whether more time should be granted.
• Contractors should now treat the shutdown as an active migration event, not simply a missing marketplace listing.

Mahdessian framed the decision as an enforcement of ServiceTitan’s Certified Marketplace rules rather than an attempt to remove a competitor.

In his statement, Mahdessian said the Podium relationship existed under a legacy partnership that had reached its end. He said ServiceTitan offered Podium a path to continue through certification on the same standards applied to other marketplace partners, including companies that compete with ServiceTitan capabilities. According to Mahdessian, Podium chose not to certify, leaving no partnership structure under which ServiceTitan could continue the integration.

Mahdessian acknowledged that contractors wanted a longer transition window and said he wished there had been more room. He also said ServiceTitan would work with affected customers and that he had personally contacted founders of certified partners to support the transition.

Rea’s response focused less on the certification decision itself and more on ServiceTitan’s conduct and the short runway for contractors.

Rea said Podium had tried to work through the issue with ServiceTitan for months and received no response for three months. He said the first renewed contact was notice that the integration would be shut off. Rea characterized the transition as less than 30 days for nearly 1,000 shared customers and asked Mahdessian to extend the deadline.

Rea also argued that Podium’s AI Operating System increasingly competes with ServiceTitan and suggested that competition changed the relationship. That is Rea’s stated interpretation. Mahdessian said ServiceTitan has certified other companies that compete with its own capabilities and did not identify competition as the reason for the decision.

Rea said Podium remained ready to work with ServiceTitan on a longer transition. His statement did not explain why Podium did not enter the certification program described by Mahdessian.

TradeVulcan Dispatch first documented that Podium was no longer discoverable in ServiceTitan’s public App Marketplace even though Podium’s own ServiceTitan integration page remained live.

The two CEO statements materially clarify that mismatch. ServiceTitan’s position is that the legacy agreement ended and Podium did not move into the Certified Marketplace. Podium’s position is that ServiceTitan failed to engage for months and imposed an unnecessarily abrupt cutoff.

Podium’s public integration page still describes setup steps, contact synchronization, payment writeback, lead writeback, conversation writeback, automated reminders, dispatch notifications, review requests, and customer-note workflows. Contractors should not interpret the continued existence of that page as proof that the integration will remain available after ServiceTitan’s stated shutdown.

The integration-status timeline

ServiceTitan’s current guidance presents two approved integration paths.

A ServiceTitan Certified App is developed and managed by a third party, reviewed by ServiceTitan, and listed in the marketplace. A Customer-Built App is created, hosted, controlled, and maintained by the ServiceTitan customer using that customer’s own app keys.

ServiceTitan separately prohibits “tunneling,” where a third party uses a customer’s app key to access the account. The company says customers may be asked to disconnect an integration that violates that rule.

Mahdessian’s statement places Podium outside the Certified App path after the legacy partnership ends. It does not indicate that Podium will continue as a customer-built integration, and a third-party vendor cannot simply recreate the same connection by asking customers to share app keys unless the arrangement satisfies ServiceTitan’s customer-built requirements.

ServiceTitan’s current approved integration paths

Rea says the shutdown affects nearly 1,000 shared customers during a major revenue season. Mahdessian says ServiceTitan will work alongside each customer and has asked certified partner founders to support the transition.

Those statements point to the same operational reality: contractors may need to replace more than a single software connection. Podium workflows can touch contact sync, appointment reminders, dispatch messages, review requests, calls, conversations, lead writeback, payments, customer notes, webchat, AI lead handling, and reporting.

A rushed replacement can create duplicate messages, missing reviews, broken consent records, lost attribution, double-created customers, incomplete transcripts, or an apparent “successful” automation that never produced a verified CRM outcome. Migration should therefore be managed as a revenue and data-continuity project, not a simple app swap.

Workflows that should be tested before any migration

Operator checklist

• Get the effective shutdown date and tenant-specific transition requirements in writing from ServiceTitan and Podium.
• Ask whether ServiceTitan will extend the cutoff or provide any account-specific exception, migration assistance, export, or support window.
• Inventory every workflow that depends on Podium, including contacts, appointments, dispatch texts, reminders, review requests, payments, leads, notes, conversations, calls, webchat, and AI booking.
• Export configuration, templates, consent records, message history, automation rules, reporting data, phone-number ownership, and suppression lists before access changes.
• Record the current triggers, mappings, filters, business units, postal codes, user permissions, fallback routing, and expected ServiceTitan writeback for every workflow.
• Select replacement products by verified workflow coverage and approved ServiceTitan access—not by a high-level feature checklist alone.
• Run controlled end-to-end tests using safe records and document what enters ServiceTitan, what leaves it, what writes back, and what fails.
• Prevent duplicate automations by assigning one system of record and one active sender for each customer event during the transition.
• Do not disconnect the current stack until the replacement has passed acceptance testing and the team has a rollback plan.
• Require the replacement vendor to document its ServiceTitan certification or customer-built access model, support owner, failure handling, data retention, security controls, and migration responsibilities.

ServiceTitan’s marketplace is becoming a stronger governance layer, not merely a directory. Certification, annual recertification, commercial participation, user-experience expectations, and approved access models now shape which third-party products can remain connected and visible inside the ecosystem.

This dispute also shows the concentration risk created when a contractor’s customer communication layer depends on a platform-controlled integration. Even a long-running partnership can end, and the business using both products may have very little influence over the timeline.

The right migration question is not simply “Which app has the same features?” It is “Which stack has a durable and approved access path, preserves the data we need, reproduces the workflows that make money, and gives us a tested fallback when a platform relationship changes?”

What Dispatch is still watching

Disclosure

Methodology

TradeVulcan Dispatch reviewed the full text of LinkedIn statements attributed to ServiceTitan co-founder and CEO Ara Mahdessian and Podium co-founder and CEO Eric Rea, ServiceTitan’s current marketplace and integration-policy materials, Podium’s current ServiceTitan integration page, and official company information. Statements about three months of nonresponse, less than 30 days’ notice, nearly 1,000 shared customers, and competitive motivation are attributed to Rea and were not independently verified. Statements about the legacy partnership, certification offer, Podium’s decision not to certify, and ServiceTitan’s reason for ending the integration are attributed to Mahdessian.