Per-Seat Pricing Is Why Your Ops Manager Doesn’t Have a Login

The seat count is a decision nobody makes on purpose

No one sits down and decides that the dispatcher shouldn’t see the numbers. It happens in smaller steps. The tool gets bought for a handful of people. A year later the renewal comes up and someone asks whether all those seats are still being used. A few get cut. A manager wants to add a team lead and is told to share a login instead. Someone starts screenshotting charts into a Slack channel because that’s easier than asking for a seat.

Each step is reasonable. The sum of them is a company where the analytics tool is a place a few people go, and everybody else gets the numbers secondhand, late, and without the ability to ask a follow-up question.

Who ends up on the outside

Look at who typically has a seat in a per-seat BI deployment and who doesn’t. The analysts have one. The executives have one. Finance has a couple. Then the list runs out, and the people without a login are the ones who could have done something with the number that morning.

• The office manager who decides which estimates get a follow-up call.
• The dispatcher who could rebalance the day if they knew a crew was behind.
• The crew lead whose callbacks are the thing that’s trending.
• The bookkeeper chasing the overdue invoices, who never sees the aging.
• The regional manager who gets a PDF on Monday about a week that already happened.

This is the quiet failure of self-service analytics. The tool works fine. The access model just keeps it away from the people who’d change a decision based on it.

What the pricing model does to the question

Under per-seat pricing, “should this person see this number” is a budget question. Under flat pricing it’s only ever a relevance question. That’s the whole argument, and a chart makes it plain.

We’re not claiming flat is always cheaper. At five people it obviously isn’t. We’re claiming the bars change behavior. Somewhere between the second and third bar, most companies stop adding people, and the stopping point has nothing to do with who would benefit.

Why we price flat, and what we meter instead

Dashfeed is built around a feed that pushes insights to people, and a brief that tells them what changed before they ask. That design only works if the right person is a member of the workspace. A morning brief about cold estimates is worth a lot to the person who makes the follow-up calls, and almost nothing to a VP who forwards it. If we charged per seat, we’d be charging the most for exactly the people the product is for.

So the plans are flat. Dashfeed AI is $1,500 a month, Pro is $2,500, and Platform is $3,500, each with unlimited users. What we meter is AI credits, because AI usage is the thing that costs us money as it grows, and it’s also the thing that grows with value rather than with headcount. An organization that invites forty people and generates the same number of insights pays the same. One that runs a lot more analysis pays more. That feels like the honest version of usage-based pricing to us.

Flat pricing is a bet, and we should say so. We’re betting that the value of a workspace scales with how many people act on its numbers, and that companies that can invite everyone will. If we’re wrong about that, our pricing is wrong. So far the bet looks right.

A short audit for this quarter

Whatever tool you use, three questions will tell you whether seat rationing is costing you decisions.

If those three lists are short, per-seat pricing is fine for you. If they’re long, the pricing model is shaping who gets to know what, and it was never supposed to.