Systems shipped
End-to-end
From messy input to a product people can operate on a normal Tuesday.
Applied AI · Workflow systems · Product engineering
Practical AI
Systems for
Messy Manual
Workflows.
I design and build AI-powered products, knowledge systems and automation that make complex work simpler.
Focus
AI + workflow
Products that organise dense information and make the next decision obvious.
Stack depth
Full build
Product design, AI-assisted flows, Next.js / Astro, Supabase, CMS architecture.
Selected systems
Work that shows how I think and ship.
Three products that organise dense information and prove I can take a messy problem all the way to a usable system.
Libertrade LOOP
Designing a process-first trading journal for discretionary futures traders.
- Next.js
- Supabase
- Chart.js
- ChatGPT
Trading Knowledge Wiki
A structured trading reference wiki for Market Profile and auction-market concepts — built for session prep, not scattered PDFs.
- Markdown
- Vercel
Real Estate Marketing & Listings Platform
CMS-backed real estate platform with dynamic property pages, i18n, SEO, and contact/newsletter flows.
- Next.js
- Sanity CMS
- TypeScript
About
I make complicated work easier to operate.
I work between product design, engineering and operations — usually where the problem is still ambiguous and the workflow has not been properly defined yet.
I build AI workflows and systems for people who have too much input and not enough structure. I like messy problems — half-broken processes, too many tabs, scattered notes, and the sense there must be a better way. That is usually where I come in.
Capabilities
What I bring to an AI team.
Not slide decks — shipped systems. Comfortable across product, AI workflow design and the engineering needed to make them real.
Product
- Product design
- Information architecture
- Decision-centred UX
AI systems
- AI-assisted workflows
- Knowledge systems
- Retrieval & notes ops
Engineering
- Next.js & Astro
- Supabase
- Automation & CMS
How I work
Refinement is the work.
I rarely start with a clean specification. I start with scattered information, repeated friction and a problem that has not been properly framed yet.
- 01
Observe
Map the real workflow — including the awkward workarounds people have learned to ignore.
- 02
Simplify
Cut the problem down to the decisions, information and hand-offs that actually matter.
- 03
Build
Ship a usable product or operating layer people can run without constant explanation.
- 04
Iterate
Watch it in use, find the friction, and refine until the structure feels inevitable.