…

Why Is Employee Scheduling Software So Expensive? (The Model Explains It)

You open the pricing page. You're not against paying — you've been doing the schedule in a spreadsheet for two years and you're tired. You scroll down, find the tier that has the time clock and the SMS notifications, and then you start counting.

Twelve staff. Four-fifty a head. Plus the time-clock add-on, which is another two bucks each. You do the multiplication twice because the first answer felt wrong.

Then you remember you're hiring two more for the holidays.

That gut-drop feeling isn't you being cheap. It's a structural mismatch between the way the software is priced and the way your business actually works. And once you see it, you can't un-see it.

Where the per-seat model came from

Per-seat pricing wasn't invented for retail. It was invented for enterprise software — Salesforce, Workday, Microsoft 365. In those companies, the buyer is a procurement officer with a 400-person headcount and a budget that gets amortised across an entire department. Charging $30 per user per month feels fair to that buyer, because each user generates many times that in revenue or productivity.

When I Work, Deputy, Homebase — these tools inherited the model. Not because it fits a 12-person bookshop, but because that's how workforce software gets priced once it grows up and starts chasing the mid-market and enterprise tier. The board wants expansion revenue. Expansion revenue means the bill grows when the customer grows.

So a 200-store regional chain pays a lot, and the unit economics work. A single independent store inherits the same pricing logic and pays a price that was never really designed with them in mind. The model isn't evil. It's just architecturally pointed at someone else.

The real math on a 12-person team

Let's stop being vague and put real numbers on it. As of writing, When I Work's Essentials sits around $2.50 per user per month, and the tier that includes the time clock and shift swaps runs closer to $6. Deputy's Premium plan is about $4.90 per user per month. Homebase's Essentials is around $24.95 per location per month — but the moment you want the time clock with biometrics, swap management, or any real reporting, you're on Plus or All-in-One at $59.95 or $99.95 per location per month, and still capped by features.

Take a 12-person retail team on Deputy Premium: 12 × $4.90 = $58.80 per month. That's $705 a year. Add a time-attendance module where it's broken out separately, or move up a tier for advanced reporting, and you're easily at $1,000–$1,200 a year before you've published a single shift.

Now hire your 13th employee in November because Christmas is coming. The bill goes up the same day. Hire two more for January sales. Bill goes up again. You're being charged for the act of staffing your business.

The seasonality trap

This is the part that quietly stings the most. Independent retail and experience venues don't have flat headcounts. You run lean in February and you staff up in November. You bring on three casuals for school holidays. You hire a weekend-only person because Saturdays are murder.

In a per-seat model, every one of those decisions has a line item attached. A Sunday-morning casual who works six hours a week costs you the same monthly seat as your full-time assistant manager. The tool punishes the exact behaviour your business depends on: flexing labour to match demand.

If you've ever hesitated to add someone to the roster because "I don't want to pay for another seat" — congratulations, the pricing model has started running your hiring decisions. That's the tail wagging the dog.

Add-on creep and the free-tier bait

Here's the other thing that catches people. The base tier almost never includes what you actually need.

Time clock? Higher tier, or a per-user add-on. SMS notifications instead of just push? Often metered or gated. Decent reporting? Pro tier. Integration with your POS or payroll? Pro or above. Multi-manager permissions? Same story.

The reason is straightforward: the vendor's revenue model depends on expansion, both in seats and in tier. So the features a real operator needs on day one — clock-in that ties to the roster, text messages staff actually read, the ability to export hours — get distributed across the price ladder on purpose.

The free tier is the cleanest version of this. Homebase, Sling, and a few others advertise free plans that look generous until you try to use them. Strip out the time clock, integrations, multi-role permissions, and reporting, and what you're left with is a pretty calendar. So you upgrade. And the moment you upgrade, you're in the per-seat machine.

There's a different model

Per-seat pricing isn't the only way to price scheduling software. It's just the dominant one because the dominant vendors are chasing enterprise.

The other model is per-location. One flat price for the site, regardless of how many people work there. Hire a casual for the weekend — bill doesn't move. Bring on a second full-timer — bill doesn't move. Staff up for Christmas with three extras — bill doesn't move. You pay for the store, not for the act of employing people in it.

That's how Schedaddle prices. One predictable number per location, every feature included — the visual schedule builder, SMS and push notifications, shift swaps, the callout flow, and a real geofenced time clock that ties clock-ins back to the roster. No higher tier to unlock the basics. No add-on for the time clock. No surcharge for hiring your 13th person.

If you want the full breakdown of how that math works against a per-seat plan, we wrote it up on the per-location pricing page. The short version: for most independent operators with 8 to 30 staff, the savings show up in the first month and compound every time you hire.

One question to ask any vendor before you sign

Before you put a card down anywhere — including with us — ask the sales page or the support chat one thing:

"Does my monthly bill go up when I hire someone?"

If the answer is yes, you're in the per-seat model. That's not inherently wrong — for a 200-person chain with stable headcount, it can work fine. But for a 12-person store that flexes up and down with the seasons, it's a structural mismatch. And now you know why the number on the pricing page felt off when you did the math.

What's your current headcount, and how much does it swing between your quietest month and your busiest? That's the number that tells you which model you actually belong in.