Per-seat BI pricing: what a bill that moves does to a team

The real cost of a per-seat BI bill isn’t on the invoice. It’s the person in support who never got a login.

Somebody sits down at rollout and asks who really needs access. A few seats feel fine, a few dozen feel like a line item someone will ask about. So the team buys seats for the analysts and the founders, and everyone else gets a screenshot.

What a variable bill does

Per-seat tools charge for each person. Some split people into creators and viewers, some charge everyone the same, and usage-priced tools charge for what runs. Either way the bill moves when headcount, viewers, editors or usage move. That has side effects:

• Two people share one login because the second seat “isn’t worth it yet”.
• Someone exports a dashboard to PNG every Monday and drops it in Slack. By Wednesday it’s stale and nobody says so.
• Ops, support and sales keep asking the one analyst for numbers, because they can’t look them up themselves.
• Every new hire raises the question of whether they get a license, and the answer turns into politics.
• Finance asks what next quarter’s bill will be, and the honest answer is “depends on how many people we add”.

The people who need the number most are usually the people closest to customers, and they’re the last to get a seat. A dashboard nobody can open is a report with extra steps.

None of this makes per-seat pricing a scam. Seats are how most vendors scale their revenue with your growth. But it moves a budget decision into a rollout decision, and those shouldn’t be the same decision.

What a fixed bill changes

With a fixed price, “should support have a login?” stops being a budget question. You add everyone who’d use it, share a link with anyone, and the Slack screenshots stop. Nobody tracks who is a viewer and who is an editor, and nobody forecasts headcount to guess next year’s invoice.

That’s what we built arcodash around: $59 a month on Team or $300 on Org, for the whole org, with unlimited seats and no usage billing. It’s hosted only and in early beta, with SQL dashboards plus scheduled data quality checks that alert to Slack, email or PagerDuty. You get 14 days free, no card. The price on the page is the bill. Fixed doesn’t have to mean big: Team is $59 a month for the whole team.

Fair warning: a fixed price means you pay the same with 2 people or 200. If your group is tiny and stays tiny, a per-seat tool may already fit you fine. AI features run on your own key, so that usage is billed by your provider, not on the arcodash bill.

Self-hosting is the other way out

Open source tools with unlimited users and no license fee are a fair answer to “how do I stop paying per seat”, and for a team with an engineer who likes running things it’s often the right one.

What you pay instead is time. Someone provisions it, upgrades it, backs up the metadata database, and gets paged when it falls over. If you have the person and the appetite, run it yourself. If you don’t, you’re choosing between a variable bill and a fixed one. arcodash is hosted only and can’t be self-hosted.

How to decide

Skip the spreadsheet. Ask these instead:

1. Does anyone share a login, or get a screenshot instead of access? Then the pricing model is shaping how your team works.
2. Do many people need to look while few build? Readers shouldn’t each need a purchase decision.
3. Do you want one number to budget, with no headcount forecast and no usage estimate?
4. Is the group small, fixed and already well served by a per-seat tool? Then keep it.

If the first three sound like you, a fixed bill is worth a trial. You can start the free trial and invite the whole company to see what changes. If you’re weighing specific tools, the Metabase, Power BI and Tableau comparisons go through the differences.