I am an engineering manager and the thing I could never keep current was not the code, it was the shape of the org. Who sits where, what each team is carrying, what it costs. That lived across a spreadsheet, a wiki page and some Slack threads, and it was stale the moment I finished assembling it.
Squado is one canvas with alliances, tribes and squads and the people on them. Drag someone into another squad and pick whether they transfer or stay on both. Vacation, split allocations and open seats show on the faces. Set hourly rates by role once and cost rolls up per squad, tribe and alliance. OKRs attach to the squads that own them, and the ceremony calendar flags the overlaps.
The link goes straight into a fictional fintech org, 10 squads and the people on them, no signup and no account. It is read-only for visitors, so you can click into everything but not change it.
Stack is React, React Flow, Fastify, Prisma and Supabase. The canvas query is cached in Redis for 30 seconds, which is what keeps a 50KB payload feeling instant for everyone looking at the same org.
I built it alone and I am mostly curious where the model breaks for orgs that are not shaped like this. If you do not run anything resembling squads and tribes, I would like to hear what you do run.
There is a full demo with no signup: https://app.squado.io/demo
https://squado.io
Top comments (0)