End Three-Month CRM Implementations

Diving deeper into

Thomas Schiavone, co-founder and CEO of Calixa, on the PLG data pipeline

Interview
There’s something fundamentally broken with the fact that people are okay with a three-month implementation window
Analyzed 6 sources

Long CRM implementation cycles are a tax from an older sales model, and PLG software exposed how unnatural that tax really is. In a bottoms up motion, the key job is not building months of custom objects and admin rules, it is pulling product usage data into a usable workflow fast enough that sales and success teams can act on live customer behavior. Calixa was built around direct warehouse connectivity and lightweight mapping for exactly that reason.

  • Calixa’s core argument was that SaaS companies should start from product events and warehouse data, then layer outreach and account workflows on top. The setup is meant to look more like connecting Snowflake and mapping fields than a classic CRM rollout with long admin work.
  • A clear split existed in the market. Calixa and similar products argued for a new operating surface for PLG teams, while Arrows argued most teams still preferred staying inside HubSpot or Salesforce because reps already lived there. The real fight was speed and focus versus consolidation in one familiar system.
  • Incumbents still had distribution gravity. HubSpot ended 2024 with 247,939 customers, and Salesforce leans heavily on consulting partners for deployments, with the company stating that 70% of Salesforce implementations are led by consulting partners. That scale helps explain why long setups became normalized.

The direction of travel is toward CRM layers that ingest warehouse and product data with far less ceremony, then either replace parts of the incumbent workflow or feed those incumbents in the background. As product signals become the trigger for sales, onboarding, and expansion, the winners will be the systems that turn setup from a quarter long project into a same week workflow.