Eight industries where “did it land?” is the whole question.
Each page opens with a situation, shows the four screens that answer it, names the regulation or auditor who will ask, and says what the product does not do. Every organisation on these pages is fictional.
No customer stories yet. We are in early access and will not invent them.


The same record, eight situations.
The new protocol went to every ward on Tuesday. Here is who confirmed it.
Harbourside Medical Group · Durban, South Africa · 6 clinics, 1 day hospital, 214 staff · HQ plan. Fictional.
Read the use caseThe procedure changed on Friday. Here is who confirmed it before Monday.
Ridgeline Foods · Marysville and Findlay, Ohio, United States · 2 plants, 3 shifts, 380 staff · HQ plan. Fictional.
Read the use caseThe route changed on Friday. Here is every driver who confirmed it before Monday's run.
Kilimani Freight · Nairobi and Mombasa, Kenya · 3 depots, 160 drivers and pickers · Command plan. Fictional.
Read the use caseThe procedure changed on Friday. Here is every branch that confirmed it before Monday.
Northgate Credit Union · Fort Worth, Texas, United States · 11 branches, field agents, 240 staff · HQ plan. Fictional.
Read the use caseThe site instruction changed on Friday. Here is every officer who confirmed it before the shift.
Sentinel Guarding · Gauteng, South Africa · 42 client sites, 610 security officers · HQ plan. Fictional.
Read the use caseThe safeguarding policy changed on Friday. Here is every adult on campus who confirmed it.
Acacia Schools Group · Western Cape, South Africa · 4 campuses, 190 staff, coaches and aftercare · HQ plan. Fictional.
Read the use caseThe menu changed on Friday. Here is every store that confirmed it before Monday's open.
Copper Kettle Coffee · Colorado, United States · 14 stores, 320 staff · Command plan. Fictional.
Read the use caseThe spraying procedure changed on Friday. Here is every worker who confirmed it, in their own language.
Meru Highlands Tea · Meru County, Kenya · 2 estates, 1 packhouse, 900 workers, 3 languages · HQ plan. Fictional.
Read the use caseIf you run comms, or you are asked about it at the board.
The policy went out on Tuesday. Here is who has actually confirmed it.
One announcement, published once, with a named record of who confirmed it, who is pending and when. The number you take to Monday's meeting is the one finance would have asked for.
Read the pageMonday's leadership meeting runs on last week's acknowledgement rates, not on a feeling.
Three numbers about your own communication: who confirmed it, what people said when asked, and who was reached. On one screen, printed to PDF for the board pack.
Read the pageTeams of 5 to 1,000+ people who need the record, not the noise.
- You must show a policy was distributed and confirmed, by name and date.
- You are moving official communication off US-hosted tools.
- One comms owner publishes to everyone and reports upwards.
- You want a new chat tool. Chat is included, not the reason to buy.
- You need SOC 2 or ISO 27001 today. Neither is in scope.
- Over 1,000 people. Ask before assuming it fits.
Bring the situation you are in.
Early access is by invitation. Tell us about your organisation and we will be in touch.
