Skip to content
Notifications
Clear all

Our results after cutting 3 tools and keeping 1 good one

3 Posts
3 Users
0 Reactions
1 Views
(@cloud_ops_learner_99)
Estimable Member
Joined: 1 month ago
Posts: 137
Topic starter   [#16491]

We run a B2B SaaS with ~50k monthly visits. Our martech stack was bloated and expensive. We were using separate tools for analytics, email, and user journeys. The cost was eating into our margins.

We decided to consolidate. After a painful audit, we cut three tools and kept **Segment** (now Twilio Segment). The main win? Having a single source of truth for customer data. Our engineers built a clean data model in Terraform. Here's a snippet of how we define sources now:

```hcl
resource "segment_source" "web_app" {
name = "production_web_app"
slug = "prod-web-app"
enabled = true

labels = {
environment = "production"
platform = "website"
}
}
```

This let us connect everything—website, app, backend events—to one place. Our email tool (Customer.io) and ads (Google Ads) pull from this. It's reduced our monthly martech bill by ~60% and cut down data discrepancies a lot. Has anyone else gone through a big consolidation? I'm nervous we might have over-consolidated, but the results so far are good.



   
Quote
(@ellaq)
Estimable Member
Joined: 1 week ago
Posts: 107
 

That 60% cost reduction is massive, and the Terraform approach is super interesting. I've seen teams try to do this kind of consolidation manually, and it becomes a maintenance nightmare within months. Defining sources as code is a game-changer for keeping that single source of truth clean.

My one caveat from experience is to watch out for the "Swiss Army knife" trap. Segment is fantastic as the central pipeline, but sometimes it tempts people to try and make it *do* everything (like complex attribution modeling) directly, when it's better to just pipe clean data to a dedicated tool for that job. As long as you're using it as the foundation to feed specialized tools like Customer.io, you're on the right track.

Has this consolidation changed how your sales or success teams build reports? I'm curious if having everything in one stream improved their forecasting accuracy or just made the data team's life easier.


Pipeline is king.


   
ReplyQuote
(@jasonb)
Estimable Member
Joined: 1 week ago
Posts: 115
 

Love seeing the Terraform integration, that's smart. It gives you version control for your data pipeline config, which most teams overlook.

We consolidated around Segment last year too. One surprise benefit: onboarding new hires got way faster. They learn one data model instead of three different tools.

Have you run into any issues with event volume spikes on your plan? We had to tweak our tracking once we centralised everything.


Let's build better workflows.


   
ReplyQuote