We got tired of watching good teams get buried by bad spreadsheets.
So we built the resource capacity platform we wished existed — back when it was still three browser tabs and a Slack thread called “who’s actually free this sprint.”
How we ended up here.
PlanWerk started the way most tools do: out of spite for the tool we were already using. Three tabs, two consultants, and a shared spreadsheet named FINAL_v3_capacity_ACTUAL.xlsx that nobody was allowed to touch on a Friday.
We spent a year watching great teams get quietly buried — not by too much work, but by nobody knowing who had room for more of it. So we built the thing that tells you, in one glance, before the retro turns into a confession.
What we believe (this week).
Our values are load-bearing, occasionally contradictory, and subject to change at the next offsite.
Radical transparency about who’s overbooked.
Bias for shipping — the roadmap, not the features.
Customer obsessed. Once we have customers.
Default to allocated.
The team (so far).
Fully distributed. Mostly across jurisdictions with favorable withholding tax treaties.
Previously scaled three roadmaps to zero.
Built the allocation engine over one long weekend. Still fixing it.
Has a PhD in something adjacent to this.
Wrote the buzzword ticker. Not sorry.
Made the loading spinner spin clockwise, on principle.
Knows exactly which office is real.
Want to help us find out if this works?
Early access opens in waves. Get in before we figure out pricing.