Available for AI engineer & automation roles

AI workflows for messy expert work.

I turn voice notes, documents and evidence into structured, reviewable, decision-ready systems — not chatbots.

3+ AI products designed & built
04 Evidence-heavy domains
UCL PhD-level research rigour
UK London · full right to work
01 Approach

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.

02 Selected work

Messy evidence in. Verifiable output out.

001 AI · Fintech
SlipMind

Pre-accounting memory for sole traders

In
Receipts, invoices, forwarded emails, CSVs
Out
Reviewed records, evidence flags, accountant-ready exports
Case study →
002 AI · Construction
Bildeasy

Compliance reports from site evidence

In
Voice notes, photos, site observations
Out
Compliance reports, findings, action plans
Case study →
003 AI · PropTech
Ledger & Lease

Private proof records for property compliance

In
Emails, screenshots, PDFs, notices
Out
Dated proof records, verification links
Case study →
004 Delivery · Ops
DOS Design Studio

Project delivery in complex built environments

In
Briefs, constraints, budgets, stakeholders
Out
Coordinated delivery, documentation, handovers
Case study →
03 How I work

Real workflow to working system.

01

Map the workflow

Actors, inputs, decisions, exceptions, handoffs — how the work really happens.

02

Define the output

Report, record, export or decision. AI is only useful when the output is clear.

03

Design the AI layer

Prompts, extraction rules, confidence signals, review points, escalation paths.

04

Build or brief

Prototypes and Codex/Claude implementation briefs engineering can execute.

05

Test for failure

Missing evidence, hallucination, weak confidence, polished-but-useless output.

04 Principles
  • /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.
05 Stack
Claude Codex Cursor Prompt architecture Workflow mapping Next.js / React Supabase / Vercel Stripe / Resend / Cloudflare Python (learning) FastAPI Figma
On the code

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.

06 Contact

Let's make a messy workflow useful.

For AI workflows in evidence-heavy, regulated or operationally messy environments.