We build rota and training software for shift-based teams, hospitality, care, retail, logistics. It started as a tool for our own sites.
Most rotas are still a printed sheet and a group chat. That works until someone swaps a shift, or leaves, or turns out not to be signed off for the station you put them on.
Built on Postgres with row-level security, so every organisation’s data is isolated in the database itself rather than by application code remembering to filter. Hosted in London. It runs a two-site restaurant group today and is built to run a great deal more.
Every table carries its organisation and checks it on every read and write. The isolation is a database rule, not a line of application code someone can forget.
Indexed for the queries a rota actually runs, and hosted in London next to the database rather than a continent away.
Transparent holiday accrual, auditable time logs, and equal access to shift opportunities.
A small team. Brigadeur came out of running actual sites, not out of a product workshop, which is why it argues with you about training records instead of just drawing a grid.
Runs multi-site hospitality in Birmingham and built the first version of this to solve his own rota. Still writes the specs.
Works on the scheduling engine and the rules underneath it, working time, accrual, clearance, and the maths that has to be right every time.
Takes what happens on the floor and turns it into something the software can enforce. Runs onboarding for new sites.
We are three people and not hiring yet. If you run sites and think we have got something wrong, we would rather hear that.