A plan for the bad day,
and the record after.
Coming: not built yet.
Coming: the incident plan written with you, the steps when something happens and the record afterwards; nothing is sold as working until it is built.
Risk & compliance · Respond · your team
Your team: five seats, one job.
The same five seats run every module, so every report reads the same way. You approve what goes out.
01 · Lead
Incident lead
Keeps the plan and who to call; runs each incident from its runbook
02 · Analyst
Impact analyst
Records what happened and the time to contain
03 · Makers
Runbook and notice writers
Draft the steps and the notices from templates
04 · Reviewer
Notice review
A person reviews every notice and sends it themselves
05 · Operator
Operator
Keeps the incident register and the after-action records
Across every module
- Chief of staff (Hue) Reads every Lead’s plan, settles conflicts between modules and writes the one-page 7 AM brief
- Head of analytics One attribution truth, to the paid invoice, that every Analyst reads
- Compliance officer Consent, anti-spam rules, claims and voice policy; can veto any Reviewer’s pass
What you get each month
Loops that close, counted every month.
One module includes its team and 500 tasks a month, pooled across everything you buy. A task is one finished item; heavier items count for more.
Incident to closed
- Counted
- incidents
- Judged on
- time to contain
Practice runs
- Counted
- practice runs
- Judged on
- the plan known before it is needed
Beyond the pool, packs of extra tasks under a monthly cap you set. We never promise a result: these are the measures we report against.
Risk & compliance · Respond · what’s inside
Seven features, one module.
7 live, 0 in early access, 0 coming. Open a card for what it does and what it connects to.
LiveThe incident plan
Who does what when something goes wrong, kept by your team, with the runbook for each likely incident.
Runs inside Humonix, nothing to connect.
LiveWho to call
The incident lead, the insurer’s incident line, IT, the bank and the lawyer, in order, with their numbers on one page.
Runs inside Humonix, nothing to connect.
LiveStep-by-step runbooks
The steps for the incidents you are most likely to face, checked off as they happen, with the decisions left to a person.
Runs inside Humonix, nothing to connect.
LivePractice runs
A practice run on a made-up incident, labelled as practice, so the team knows the plan before it is needed.
Runs inside Humonix, nothing to connect.
LiveIncident register
Every incident and its dates, whether personal information was involved and the risk-of-harm decision a person recorded.
Runs inside Humonix, nothing to connect.
LiveAfter-action record
What happened, what was done and what changes now, kept on the record.
Runs inside Humonix, nothing to connect.
LiveNotices drafted
Notices to an insurer, a client, the people affected or a regulator, drafted from templates for a person to review and send.
Runs inside Humonix, nothing to connect.
Live: works today. Early access: built, switched on for you after a setup step or a provider’s review. Coming: planned, never sold as working. Anything that goes out waits for your approval.
Good to know
- Respond is not built yet: every feature on this page is marked coming, and none is sold as working.
- Until it ships, Risk & compliance’s working module is Comply; the security side of an incident sits with Watch and Defend in IT & security.
- When it ships, every notice to a client, an insurer or a regulator is a draft a person reviews and sends; it is never legal advice.
One module (Respond) · $350/mo, the Risk & compliance department (both modules) · $600/mo, all of Business in a box · $3,000/mo, or with Head of Digital, agents · $5,000/mo.
See pricing