Skip to content
All posts

The real cost of per-seat scheduling software

Per-seat pricing bills provisioned accounts, and hourly teams do not have stable accounts — they have turnover. How to compare what you will actually pay.

Blog

5 min read

pricing
Blog

The sticker price of scheduling software is rarely what you pay. Not because anyone is lying, but because the unit being billed is almost never the unit you actually use.

Seats are not workers

Per-seat pricing bills provisioned accounts. Hourly teams do not have a stable number of accounts — they have turnover.

Hospitality and retail routinely run annual turnover well above the whole-economy average. The practical consequence is that at any moment, some share of your seats belong to people who no longer work for you. They stay provisioned because deprovisioning is an admin task nobody owns, and because the cost of forgetting is invisible: a slightly larger invoice that looks like every other invoice.

The multiplier is real and it compounds quietly. It is also entirely avoidable, because the number you actually care about is who worked this month — and that number is already in your time clock.

The add-on stack

The second gap is feature gating. The base plan schedules. Then:

  • forecasting is on the tier above,
  • compliance reporting is a module,
  • the mobile app for staff is an add-on,
  • payroll export is per-export or per-integration.

Each is individually defensible. Together they mean the advertised per-seat price describes a configuration nobody actually runs. The number you should compare is the price of the setup that does what you need — which is usually discovered after signing.

Forecasting is the one worth arguing about. It answers "how many people should I schedule" — the question the schedule exists to answer. Selling it separately means selling the product without the thing that makes the product work.

What to actually compare

Ignore the headline. Work out:

Billable units × unit price × add-ons you will actually need.

Then ask the question that decides it: what happens when someone leaves? If the answer involves you remembering to do something, that is a recurring cost with your name on it.

Where Sofia sits

We bill $200 per store per month — one number, unlimited staff, Tanda or native roster. Turnover does not change the bill. Forecasting, compliance guardrails and the fair-workweek ledger are included, not a module on the tier above.

There is a real competitor to that model, and it is worth naming: tools that are free because they make money elsewhere — typically by supplying you with staff and taking a percentage. That can be a fine deal. It is worth understanding the incentive, though. A platform that earns on placements has a reason to prefer that you fill gaps with its supply rather than with the part-timer already on your team who wanted the hours.

We would rather charge you for the software and have no opinion about who works the shift.

The uncomfortable question for us

The obvious objection to a per-store price is that a quiet month costs the same as a busy one. That is the trade: the bill is a number you can write down in August, not a function of who you remembered to deprovision.

What we will not do is make the bill hard to predict. The price is published, the unit is the store, and the calculator on the pricing page uses the same arithmetic we bill on.

If a vendor cannot tell you what you will pay next month without a call, that is information too.

Related features

She answers the phone$200

Get a store number, or let us show you around.

$200 a store. The line is boarding. Or open a workspace and run the roster today.