Blog
Pricing thinking, compliance deep dives, design decisions we've made along the way. No clickbait — most posts run 5-7 minutes.
Five shift schedulers compared to each other, by someone building a sixth. The useful part is not the feature list: they do not bill on the same axis, so “which is cheaper” has no answer until you know your headcount per site.
Posting an unfilled shift to the team and letting people claim it is the cheapest coverage tool there is. It also quietly rewards whoever refreshes their phone fastest. Here is how to run it so it does not.
Federal law requires none. A handful of cities and one state require up to 14 days plus a payment when you change it late. Which rule applies to you depends on your address, not your industry — here is the actual map.
Most scheduling APIs are a second implementation of the product's rules, which is why they drift. Ours is the same code path the buttons use — here is what that buys you, plus the webhook contract in full.
Both do it the same way — a one-way calendar feed URL you paste into Google. Here are the steps for each, why your changed shift still shows the old time, and the thing about that URL nobody reads until it matters.
In April we argued per-seat was the only honest model for scheduling software. We now charge per location. Here is the argument that changed our mind, and the numbers.
California is one of the few states with daily overtime in addition to weekly. Understanding the 8/12-hour thresholds — and the 7th-day premium — is the difference between compliant scheduling and a wage-and-hour claim.
A shift from 8pm to 4am crosses midnight. That sentence breaks more scheduling tools than any other. Here's what goes wrong, and what we do differently.
No credit card required. The product is the proof.
