About Plantime
Plantime exists because every restaurant manager and shift planner we talked to said the same thing: the tools they used had digitised the problem without solving it. They were still spending half a day a week dragging shifts around a grid.
01 - Background
Fitting people to shifts under constraints - availability, skills, hours, labor cost, fairness, compliance - has decades of mathematics behind it. And yet most of the scheduling software on the market still hands the manager a blank grid and asks them to solve it by hand.
So we built a scheduling tool around the algorithm, not the spreadsheet. The UI exists to express constraints and review what the engine produced. The hard part - assignment - runs underneath.
What we replaced
Drag-and-drop cells. Conflict warnings after the fact. Manual reshuffles every time someone calls in.
What we built
You describe the constraints once. Plantime searches for the best assignment - preferences honored, hours balanced, coverage met.
Research roots
Years of theory at FHNW and ETH Zürich before a single line of product code. Scheduling has been our problem since long before it was our product.
02 - The team
Co-founder · Product
Wrote his master's thesis on scheduling algorithms, then spent 11 years as CTO at iMusician, building software used by tens of thousands of musicians. Plantime is what happens when those two things meet.
Co-founder · ML
Master's degrees in Mathematics and Computer Science from ETH Zürich. Builds the optimization engine behind Plantime - the algorithms that actually generate schedules, not just store them.
Growth · Go-to-market
Makes sure the teams who need this find us. Helps shape product strategy and aligns what we build with real customer needs.
03 - Why the AI is free
Every other scheduling tool we've seen treats AI auto-scheduling as a premium upsell. We think that's backwards. Charging more for the part that actually saves you time means the people who'd benefit most never see it.
So auto-scheduling is on every plan, including the free one. Paid tiers exist for approvals, time tracking, compliance, and reporting - the things larger teams genuinely need on top.
We'd rather the engine be the reason you stay than the reason you upgrade.
04 - Where we are
Basel,
Switzerland
Infrastructure
Vercel & Supabase, Frankfurt. Data stays in the EU.
Customers today
Shift-based teams worldwide — from hospitality floors to factory lines.
How we build
The roadmap is shaped by what teams actually tell us - not what we imagine they want.
Get in touch
contact@plantime.ioQuestions, demos, or just to say hi.