Per-seat pricing is the only honest model for scheduling SaaS

Most scheduling tools price per location. Some price per employee. Weekwright prices per seat — the count of active managers and employees on your roster. The choice isn't cosmetic; it determines whether your bill scales with the value the product delivers, or with something orthogonal.

Per-location billing punishes growth in the wrong direction

A 3-store retailer pays 3× the per-location fee. A 30-store chain pays 30×. The bill scales with footprint, not workforce density. That works fine if your locations are uniformly staffed — every store has 8 employees. It breaks badly when one store has 20 and another has 4: you pay the same fee for both, despite getting 2.5× the value at the bigger store.

Worse: per-location pricing creates a perverse incentive. Open a smaller satellite location and your scheduling bill jumps even though headcount only crept. The cleanest businesses to scale are the ones the pricing model penalizes.

Per-employee billing taxes hiring

Per-employee pricing fixes the location problem but introduces a new one: every hire raises your software cost. That's directionally correct — more employees = more value — but it prices the wrong unit. A back-of-house employee who works 2 shifts a week consumes the same scheduler license as a manager who edits the schedule every day. Both pay full freight.

And per-employee billing tends to count anyone you've ever added, including ex-employees you forgot to deactivate. The user experience: surprise charges every quarter when someone notices.

Per-seat is the closest proxy for value

A "seat" in our model is an active member — managers and employees who are currently on the schedule. Inactive, suspended, and terminated members don't count. Move someone to inactive and your seat count drops at the next billing cycle.

This maps to value reasonably well: each active person uses the scheduler (gets shifts, requests time-off, accepts swaps, clocks-in / out). The bill scales with the team that actually consumes the product. Open another location with the same total headcount? Same bill. Hire 5 more people? Bill rises by 5 seats.

What about the manager / employee asymmetry?

Fair point — managers do more "scheduling work" than employees, so a flat per-seat rate slightly under-charges power users and slightly over-charges casual users. We accept the imprecision because the alternative — tier-based pricing per role — fragments the bill into something nobody understands. Simple beats accurate-but-confusing every time.

The annual discount is real

Annual pricing saves roughly 20% off monthly. Cash-flow trade-off on your end (one bigger payment vs twelve smaller); operational boost on ours (predictable revenue funds product investment). Switch back and forth from the Customer Portal whenever your accounting prefers the change.

Why this matters for choosing a tool

When you're comparing scheduling software, ignore the sticker price and compute your projected annual spend at three growth scenarios:

• One year from now: more locations, same headcount per location.
• Two years from now: same locations, double headcount.
• Three years from now: 3× locations, 2× headcount per location.

The right pricing model is the one whose growth curve matches yours. For most operators, that's per-seat — which is why we picked it.