Having spent the last week analyzing the updated Twilio Segment pricing documentation for a client migration plan, I believe the structural changes represent a significant strategic shift towards consolidating revenue from higher-volume, established customers. The move from a primarily event-volume-based model to a more complex hybrid model with feature-gated tiers will disproportionately impact mid-market companies with sophisticated but not yet massive data pipelines.
The core of the change is the introduction of two new paid plan tiers, **Teams** and **Business**, which sit above the legacy **Free** and **Pro** plans. Critical functionality previously available in Pro, such as SQL-based Reverse ETL and multiple sandboxes, has been moved into these higher tiers. Furthermore, the pricing metrics have expanded.
**Key Pricing Dimension Changes:**
* **Monthly Tracked Users (MTU):** Now a primary cost driver across all paid plans, calculated as the sum of daily distinct `userId`s across all `track` calls. This penalizes user-centric applications with high daily active user counts.
* **Performance Tiers:** Within the **Business** plan, you must now select a volume tier (e.g., Business 1, Business 2) based on your MTU and event volume, locking in a higher commit.
* **Feature Gates:** Advanced tooling is now tier-exclusive. For example:
* **Protocols (Sources/Destinations):** Free (2), Pro (10), Teams (Unlimited), Business (Unlimited).
* **Workspace Roles:** Pro (Admin, Developer, Analyst), Teams/Business (adds Billing Admin, Read-only).
* **Reverse ETL:** Now exclusively in Teams and Business plans.
A simplified cost comparison for a hypothetical scenario illustrates the impact. Assume: 5M events/month, 100,000 MTUs, needing 15 destinations and Reverse ETL.
**Under a legacy Pro model estimate:**
```
5M events * ~$0.0025 per event (estimated blended rate) = ~$12,500
```
Destinations and features like Reverse ETL were typically included.
**Under new model (Business 1 Tier estimate):**
```
Base Plan Fee (Business 1): $1,200/month
100,000 MTUs * $0.03 per MTU = $3,000/month
5M events * $0.0025 per event = $12,500/month
----------------------------------------------
Estimated Total: ~$16,700/month
```
This represents a **~33% increase** for the same volume, solely due to the MTU charge and base plan fee, before accounting for the value of the now-included additional features. The push is clear: to maintain previous functionality levels, most Pro users will be forced into Teams or Business, incurring the MTU tax and higher commit tiers. The analysis suggests that companies with lower MTU counts but very high event volumes (e.g., IoT data streams) may see a less severe impact, while B2C SaaS companies with large, active user bases will face the steepest climbs. It necessitates a re-evaluation of tracking strategies, potentially pushing more logic server-side to minimize MTU counts, and a rigorous cost-benefit analysis of the newly gated features.
Spreadsheets or it didn't happen.
Oh, that MTU shift you mentioned is such a big red flag for anyone doing heavy user analytics. It completely reframes the cost for product-led growth companies where daily active user counts are high but maybe event volume per user isn't. I ran a quick comparison for our e-commerce client, and just flipping from their old volume-based plan to the new Teams plan with MTU doubled their projected cost, even before adding the features they lost from the old Pro tier.
It feels like they're betting that the pain of switching pipelines is greater than the pain of the price hike, especially for those mid-market teams you described who've built everything around those now-gated features like Reverse ETL. Makes me wonder if this will push more people to explore the open-source alternatives like RudderStack a bit more seriously.