Voice Brain Dump →
Structured Action Plan

The real problem

The differentiating cost of running several businesses is not any individual task — it is routing. A thought that surfaces at 10 PM can simultaneously touch one entity's payroll cycle, an advisory insight for another, and a personal scheduling conflict. The thinking happens regardless. The cost is the act of stopping, opening the right document, and placing the thought in its correct context.

That friction — multiplied across the fifty to a hundred daily threads that have operational consequence — is the invisible tax on the founder-led organisation. Most operators resolve it by not stopping: they lose the thought, or they dump it into one undifferentiated note, and the routing never happens.

What was built

A system that accepts a raw voice dump or stream-of-consciousness message — multi-topic, unstructured, mid-sentence shifts, half-thoughts, "wait, also" insertions — and resolves it. The critical step is routing: the system identifies which entity each thread belongs to and routes before it structures. Then it structures within each destination: actions with named owners, decisions, blockers, deferred items.

Output arrives in the format the downstream consumer needs — a memo for a delegated owner, an entry in the project register, a draft email, an update to the company knowledge base. The routing judgment comes from context the system already holds: current live projects, entity priorities, standing escalation policy.

What changed

Processing a dump went from roughly two hours of human sorting and drafting to about five minutes. More importantly, the thoughts stopped being lost: capture no longer competes with whatever the operator was doing when the thought arrived.

The human equivalent is a bilingual chief of staff with full cross-entity access — a role that genuinely works at the senior corporate level, but takes 12–18 months before the routing judgment is reliable, and takes the institutional context along when the person leaves. The system applies the organisation's accumulated context immediately, and that context persists.

What it required

A maintained, structured knowledge base — the routing is only as good as the context behind it. A working standard: if the recipient of the structured output has to come back for clarification, the routing or structuring failed. And one discipline held firmly: when a dump is genuinely ambiguous, the system surfaces the ambiguity as a question instead of absorbing it into a guess — because a wrongly-routed brief quietly teaches the downstream owner that the briefs cannot be trusted.

Honest limits

Genuinely ambiguous routing still needs the operator to confirm context. Voice transcripts are processed locally where possible, so raw founder-level commentary does not travel to third-party services unnecessarily.