A shift planning system for Danish businesses, one you own
A shift planning system built around the way you already hand out shifts. Staff bid on the open shifts themselves, the person in charge approves, and you pay for the system once instead of every month.
The trouble with spreadsheets and a noticeboard
In a smaller business the shift plan usually lives in three places at once: a spreadsheet, a sheet of paper in the staff room, and a run of text messages. None of the three is necessarily wrong. They just do not agree.
Then come the questions. Who is on Saturday? The spreadsheet says one thing, but a swap happened on Friday and it only exists in a message. Who swapped with whom, and did the manager even hear about it? Sometimes two people turn up for the same shift, and sometimes nobody does.
The worst part is usually not the mistakes but the uncertainty. A member of staff asks whether she can have a particular shift, and then hears nothing. Was the message seen? Did the shift go to someone else? Should she count on the evening off? It is written down nowhere, and all she can do is ask again.
For whoever makes the plan, it is working time disappearing. Not on the planning itself, but on chasing replies, tracking who asked for what, and rebuilding the picture every time something moves. That is the time a shift planning system gives back.
Why buy rather than subscribe
Shift planning systems on subscription exist, and for some businesses they are fine. They typically cost a couple of hundred kroner a month, and they keep costing it. In return you work the system's way instead of your own.
| Subscription | Tarnix | |
|---|---|---|
| Payment | Every month, forever | Once |
| After 5 years | Around 18,000 DKK and rising | 15,000 DKK |
| Fitted to how you work | No | Yes |
| Price increases | Yes | No |
| You are handed the system and the code | No | Yes |
The example assumes a system at 15,000 DKK, that is between Basic and Plus, and a subscription at 300 DKK a month.
The arithmetic is not the only argument, and for the first couple of years the subscription is cheaper. What matters is what you are left holding afterwards. With a subscription you stop having a system the day you stop paying. Here it sits on your own accounts, the code is handed to you, and you can take it to any developer.
What you get
- One current shift plan that everyone sees the same version of, updated live
- Access from staff phones in the browser, with no app to install
- A calendar overview marking open shifts, your own bids and your own shifts
- Bids on open shifts from staff, approved by the person in charge
- A stand-down flow where the shift is only released once cover has been approved
- Notifications, so people are told instead of having to ask again
- A panel for the person in charge with unfilled shifts and bids awaiting a reply
- Staff and roles, export to Excel, and setup on your own accounts
- In Plus also absence and holiday, an hours overview, email notifications and two adjustments
Rules are enforced on the server, not just in the interface. If a member of staff cannot hold two shifts on the same day, it is not because the button is hidden, it is because the system refuses. Work differently and the rule is changed for everyone.
If you want to see it work before writing to us, you can click around the demo with test data. The system is in production at a restaurant today, and the whole story is written up in the case.
Pricing
Basic costs 12,000 DKK and Plus 18,000 DKK, both as a one-off payment and excluding VAT. Under normal use there are no ongoing costs, because the system runs on your own accounts. Changes after handover cost 850 DKK per hour, or 4,500 DKK for a block of five hours. See exactly what each package includes.
How a project runs
- Conversation. Half an hour on how the plan is made today and where it breaks. No charge.
- Quote. You get a fixed price and a written description of what the system has to do, so both sides are looking at the same thing.
- Agreement. The price is fixed from here. Change your mind along the way and we agree it as an addition, not as a surprise on the invoice.
- Development, 4 to 6 weeks. You see the system as it goes and can speak up while changing it is still easy.
- Handover. The system is set up on your own accounts with Netlify and Supabase, and you are handed the code and the credentials.
- Walkthrough. We show you how to use it and how to adjust what needs adjusting day to day.
Frequently asked questions
Do staff have to install an app?
No. The plan opens in the browser on their own phone, and the page can be added to the home screen so it looks like an app. There is no app store and no installation, which is why the whole team is usually up and running the same day.
What happens when someone stands down the day before?
The shift is still theirs until someone else has bid and been approved. That way a shift cannot end up unassigned without anyone noticing. Standing down can be undone along the way.
Can we create and edit shifts ourselves afterwards?
Yes. The manager has a panel for creating and editing shifts, approving bids and seeing unfilled shifts for the next seven days. That is the daily running of it, and it does not need us.
Do you reuse the code from our shift plan elsewhere?
We reuse our own foundation, meaning login, user management and the calendar mechanics, across projects. That is why you are not paying to have it built from scratch. Your system, your rules and your data are yours, and we do not resell your solution to anyone.
Shall we find out whether it makes sense?
A half hour conversation, no charge. We look at how you work and say honestly whether there is something to build.