The Segment price hike isn't surprising; it's the inevitable outcome of the "land-and-expand via venture capital" model finally meeting its balance sheet. For anyone not at enterprise scale with a seven-figure martech budget, the new pricing is a sledgehammer. They've shifted from a model that scaled with your usage to one that scales with your *potential*, based on "Monthly Tracked Users" (MTUs). This is a classic post-acquisition pivot to profitability.
If you're on the receiving end of this, your next move depends entirely on your business model and data volume.
**For low-to-mid volume B2B SaaS (sub 500k MTUs):**
Segment is now likely cost-prohibitive. Your alternatives aren't about feature parity; they're about core pipeline reliability and audit trails. Look at:
- **Freshpaint** (if you need HIPAA/GDPR compliance baked in)
- **RudderStack** (self-hosted or cloud, but mind the ops overhead)
- A simplified, event-driven architecture built around something like **PostHog** or **Clicktracker** for the core funnel events, feeding a data warehouse directly.
**For high-volume B2C/e-commerce:**
You're likely already in the enterprise tier, feeling the pain but with less room to move. Your leverage is your contract. Start a vendor risk assessment *now*. Audit your actual MTU count versus what they're billing. Challenge their attribution model. This is where you renegotiate with a migration plan in your back pocket (RudderStack Cloud or a home-built pipeline on GTM/Tealium are your only real alternatives at this scale).
The technical takeaway is the same for everyone: you must decouple collection from destinations. Your code should emit events to a single, owned pipeline. That pipeline then fans out to analytics, CRMs, and warehouses. Segment was that pipeline. Now you need to own it.
```javascript
// Instead of this (tightly coupled to vendor):
analytics.track('Order Completed', { ... });
// Your code does this (owns the event):
import { ownTheEvent } from '@/lib/pipeline';
ownTheEvent('order.completed', { ... });
```
Then, inside your `pipeline` library, you handle the routing, batching, and retries to whatever system you're using this year. This is the only way to insulate yourself from the next 30% price increase. The cost isn't just in dollars; it's in the existential lock-in risk.
Trust but verify – and audit