← Blog

MAU pricing is a tax on adoption

Here's a pricing model working exactly as designed: your internal rollout succeeds, usage doubles — and your analytics vendor sends a bigger invoice. You are literally billed for the outcome you were hoping to achieve.

July 21, 2026 · 4 min read

The perverse incentive nobody talks about

Per-MAU and per-event pricing made sense in the world it was invented for: one revenue-generating product, where more users meant more revenue, and the analytics bill was a rounding error against growth. Aim the same model at an enterprise's internal estate and every assumption flips:

• Your "MAU ceiling" is your whole workforce — and you already pay them.
• There is no revenue line to absorb the bill; it's pure cost center.
• You don't have one product. You have forty. Or three hundred.

So a rational team does the rational thing: it instruments the two or three apps that can justify the spend, and leaves the rest dark. The pricing model designed to monetize visibility ends up rationing it. That's the tax — paid not in dollars but in blindness.

Watch what the tax changes

Pricing isn't just a bill; it's an incentive system that quietly redesigns your measurement program:

1. Coverage shrinks to the defensible. "Should we instrument the procurement tool?" becomes a budget question instead of an obviously-yes question. The long tail — where the zombie apps and quiet failures live — stays unmeasured, which is precisely backwards. (See the shadow portfolio.)
2. Teams sample and truncate. Event caps teach engineers to track less, strip properties, and drop "unimportant" events — decisions made to manage a bill, not to answer questions.
3. Success gets renegotiated. Every good rollout triggers a procurement conversation. Some vendors' true-up emails arrive faster than their release notes.

What flat portfolio pricing changes

When the price is flat per portfolio — never per user, never per event — the marginal cost of instrumenting the next app is zero, and behavior flips accordingly. Instrument everything becomes the default. The 40th app costs what the 4th did: nothing. Rollout success is unambiguously good news. And the political question "which apps deserve analytics?" simply stops existing — the same way nobody debates which teams deserve version control.

The objection, answered

"But usage-based pricing aligns cost with value!" For a customer product, sometimes. For portfolio intelligence, the value is the completeness of the picture — the ability to compare every app on one dashboard and retire the losers. A pricing model that penalizes completeness attacks the product's own value proposition. Charging per event for portfolio visibility is like charging a mapmaker per tree.