One workspace for the whole business.
Your subdomain, your blocks, your rules. Scheduling comes first. Anything not built yet is labelled that way.
Request a demoToday the roster lives in a group chat.
Someone is sick, someone wants Friday off, someone forgot Saturday. The manager answers each one by hand, then fixes the spreadsheet.
Sample messages, fictional
Liis
Woke up with a fever, can't do the morning shift. Sorry.
Mari
Who can take Friday morning? Dentist at 10.
Karl
Do I work Saturday or not?
Anna
Can I swap Thursday with Karl?
Kristjan
Let me check, I'll get back to you tonight.
- Swaps go to the manager
- Anna proposes the swap from her phone. The manager approves in one tap. The roster updates itself and both people are notified.
- Open shifts find their people
- Friday morning is posted as an open shift. Eligible colleagues see it on their phone and claim it, pending approval.
- Nobody has to ask
- Karl opens a link and sees Saturday. Every person sees their own shifts, with status, without messaging anyone.
Sunday 19:40. Publish. Everyone has next week on their phone, and nobody has to text you.
Scheduling is the first module.
A roster has to obey labour law. Eleven hours between shifts, forty-eight hours weekly rest, hour caps per accounting period. A spreadsheet checks none of it.
11h
- Rest across locations
- One person, two cafés, one rest clock. The check spans every location they work.
- Hours over the whole period
- Weekly limits are counted across the full accounting period, not only the draft in front of you.
- Minors and leave
- Night-work limits by age and approved leave are hard boundaries, not reminders.
Configure. Generate. Review. Publish.
Four steps. None automatic. The generator fills a draft. You decide what goes out.
Configure the period
Any date range. No fixed week or month.
Generate a draft
Each shift goes to the eligible person with the fewest hours so far, once every rule passes.
Review the difference
New, changed and removed shifts side by side. Unfilled shifts are shown, never hidden. Edits you made by hand last time are carried over and locked.
Publish
A published schedule is never edited in place. Staff are notified and calendars updated from the difference only.
Built from blocks, in one place.
Your own subdomain and colour. A grid of blocks, built to be rearranged and resized. On a phone it reads top to bottom.
| Mon | Tue | Wed | Thu | Fri | Sat | Sun | |
|---|---|---|---|---|---|---|---|
| Liis | 06:00 14:00 | 06:00 14:00 | 06:00 14:00 | 06:00 14:00 | |||
| Marten | 10:00 18:00 | 10:00 18:00 | 10:00 18:00 | 09:00 17:00 | |||
| Kadri | 13:00 21:00 | Open | 13:00 21:00 | 13:00 21:00 | |||
| Jaan | 13:00 21:00 | 13:00 21:00 | 13:00 21:00 | 09:00 17:00 | |||
| Anu | 10:00 18:00 | 10:00 18:00 | 09:00 17:00 | 09:00 17:00 |
Requests
2 waiting
Open shifts
1 unfilled
Hours this period
142 of 160
Inventory
Not built yet
Wholesale orders
Not built yet
Your staff open a link, not an app.
Mobile web. No Google account needed. Next shift first, status always visible.
Next shift
Wednesday
13:00 21:00
Café, Telliskivi
Telegram, Platvorm
Your schedule for next week is published. One change: Wednesday 13:00 to 21:00.
- Telegram, where they already are
- Published schedules, changes and cancellations arrive as Telegram messages. There is an in-app bell too.
- Requests without the group chat
- Time off, swaps and open-shift claims from the phone. Nothing is final until a manager approves.
- Google Calendar, if you want it
- One team calendar per location. Staff with a Google address get their own shifts as invites.
One set of rules for people and agents.
Every screen calls the same validated operations. Later, your own AI agents will call them too, with the same permissions and nothing more.
- Same operations, whoever asks
A person or an agent proposes the change. Deterministic code checks it. Neither route gets extra authority.
- Inspectable, editable, never bypassed
Agent-made work is plain configuration a person can read and change. Permission checks run at execution, not at the button.
- Erasure that leaves a trace
GDPR erasure anonymises personal data and keeps the record. Every request is logged and flagged before the 30-day deadline.
Agent access is direction, not a shipped feature. Scheduling and the workspace come first.
Where we are today
Platvorm is early. It is built by someone who runs a small production business and needed this to exist.
We are onboarding a small number of first partners in Estonia. You get direct access to the builder and a say in what comes next.
No customer logos, no usage numbers. When there is something to show, it will be here.
Talk to the person who built it.
One email. The founder replies, not a funnel.
Request a demoTell us what you run and roughly how many people are on the roster.