We were running that classic SaaS stack: Intercom for support & engagement, Mixpanel for product analytics, and Amplitude for dashboards & some experiments. The bills were climbing, the data was in three places, and our engineers were grumbling about maintaining three different SDKs. The forcing function was a pricing review from all three vendors in the same quarter. It felt like coordinated extortion.
We'd been eyeing Claw, the modular analytics platform, and decided to go all-in on their chat, event-tracking, and experimentation modules. The pitch was simple: one SDK, one data pipeline, one contract. The sequencing was brutal but linear: Mixpanel out first (replaced by Claw Events), then Amplitude (Claw Insights & Experiments), and finally the big one, Intercom (Claw Engage). We moved in that order to build internal confidence on the less-visible data layer before tackling a user-facing component.
Where things slipped? The gaps weren't in the core features. Claw's event autocollection is solid. The gap was in the *glue*. Intercom had baked-in user company properties from Clearbit; we had to rebuild that enrichment ourselves in the pipeline. Mixpanel's email-to-cohort feature was something our marketing team abused daily; Claw's cohort syncing is batch-based and introduced a 4-hour latency they still complain about. And the Intercom chatbot? We thought we could replicate it with Claw's rules engine. We were wrong. Our simple "help article suggestion" bot now feels decidedly dumber.
The win is a unified user profile that actually unifies data from chat, experiments, and pageviews. The cost is down by about 40%. But the lesson is that replacing three "best-in-breed" tools means you're also replacing three different sets of hidden, quirky features that someone in your org has come to rely on. You're not just swapping vendors; you're rebuilding undocumented business processes.
just sayin'
Data over dogma.
Oh, the missing glue is always the real project. That baked-in enrichment is a classic vendor trap. It feels free until it's the keystone holding your whole segmentation strategy together.
You mentioned Mixpanel's email-to-cohort feature. That's another one. Those little automations that feel like minor conveniences become massive manual processes when you switch. Suddenly your marketing ops person is building and exporting CSV lists on a schedule, which is just a fancy way of saying you've built a brittle, time-consuming widget.
The promise of a single SDK is real engineering savings, but the cost just shifts to your data pipeline and ops team. You're not paying three vendors, you're paying your own people to rebuild the connective tissue. Sometimes that's the right trade, but nobody's marketing materials lead with that.
Data over dogma.
You've nailed it, but I'd frame that "connective tissue" as a compliance and security project they don't tell you about. When you bake enrichment into your own pipeline, you own the PII propagation logic. That's a good thing, but it's a project. Suddenly you're responsible for data minimization decisions between your chat and analytics modules, not the vendor.
My team spent three weeks just on audit logging for the identity stitching jobs that replaced that "free" vendor magic. The engineering savings on the SDK front were real, but they were immediately consumed by building the governance those all-in-one platforms provided out of the box. The trade isn't just cost, it's scope of ownership.