Why this exists
Rehearsal is priced for organizations that already have a security team.
A facilitated tabletop exercise from a consultancy costs somewhere in the tens of thousands and takes weeks to schedule. The organizations most likely to lose donor money to a fake invoice, or expose a case file by emailing the wrong list, are the ones that will never buy that. This is the same exercise structure, run by your own operations manager, for the price of a phone line.
Four decisions that shaped it.
- 01
The clock is not negotiable
Updates fire on a timer, and there is no button to bring the next one early. Every tabletop exercise that advances when the room finishes talking turns into a meeting about a hypothetical. Real incidents arrive while you are still mid-sentence, and that pressure is the thing being rehearsed.
- 02
Scenarios are written, not generated
Every scenario in the library was written by hand and reviewed. A language model helps word an update for your organization, but it cannot write a scenario or state a deadline — the part of the system that talks to a model has no ability to author either. A drill that invents a notification deadline is worse than no drill, because a room will act on it.
- 03
Nobody is named
Decisions are recorded against a role, never against a person. It costs some precision in the report and buys the only thing that matters more: people volunteering the gap they are embarrassed about, which is where the value is.
- 04
The report is the product
The hour is worth something on its own, but what survives is the document. If an executive director would not forward the After-Action Report to a funder unedited, nothing else about this product matters — and that is the bar it is held to before anything new gets built.
Where it is up to
Early, and saying so.
The drill runs, the report drafts and exports, and the scenario library is written. Corrective-action reminders and the funder roll-up are not built yet. There are no customer logos on this site because there are not yet customers to name, and inventing them on a product about trust would be a strange way to begin.
What that means in practice: if you run an early drill, the things you find irritating are the things that get fixed next.
Who is behind it
Practice Makes Ready is built by Impaque, a small studio building software for organizations that are under-served by enterprise tooling.
If you want to talk before running anything — about a cohort, about whether this fits your organization, or about something in the data handling you would want changed — write to us.