Pre-accounting memory for sole traders
AI workflows for messy expert work.
I turn voice notes, documents and evidence into structured, reviewable, decision-ready systems — not chatbots.
I turn operational mess into usable AI workflows.
Expert work rarely starts clean. I map the mess — inputs, decisions, exceptions, handoffs — into systems that know what to extract, what to draft, where they're unsure, and where a human must decide.
Messy evidence in. Verifiable output out.
Compliance reports from site evidence
Private proof records for property compliance
Project delivery in complex built environments
Real workflow to working system.
Map the workflow
Actors, inputs, decisions, exceptions, handoffs — how the work really happens.
Define the output
Report, record, export or decision. AI is only useful when the output is clear.
Design the AI layer
Prompts, extraction rules, confidence signals, review points, escalation paths.
Build or brief
Prototypes and Codex/Claude implementation briefs engineering can execute.
Test for failure
Missing evidence, hallucination, weak confidence, polished-but-useless output.
- /01 AI should structure messy work, not hide uncertainty.
- /02 The useful unit is a record or decision — not a conversation.
- /03 Human review is designed in, not added later as an apology.
- /04 The best AI products feel boring once they work.
The SlipMind demo is public on GitHub → Other repos are private — commercial workflows and compliance logic — but I share walkthroughs, architecture notes and redacted examples during interview.
Let's make a messy workflow useful.
For AI workflows in evidence-heavy, regulated or operationally messy environments.