I define, design, and ship AI products people can understand, use, and verify.

Case Studies

Three fixed-scope systems, live and fully functional. Bring your own problem — this is how I'd approach it.

SIGNAL01
WHY

Research synthesis usually strips away its own evidence trail. A summary states something confidently, but checking where that claim actually came from means re-reading everything from scratch.

WHAT

Drop in a set of documents and SIGNAL extracts entities, clusters related material into themes, and produces a brief where every claim links back to the source text it came from.

HOW

A TF-IDF and clustering pipeline groups documents by topic, a rule-based extractor tags named entities, and the brief-generation step is checked against the original source sentences before anything is shown — nothing in the output exists that isn't traceable.

View live project
LENS02
WHY

Customer feedback piles up faster than anyone can read it, and by the time someone sits down to summarize it, the specific quotes that actually mattered are already lost.

WHAT

Upload reviews, interview notes, or support tickets and LENS tags each one — problem, feature request, objection, or praise — clusters similar feedback into themes, and ranks the resulting opportunities by volume and sentiment.

HOW

Rule-based category cues and sentiment scoring run on every item; TF-IDF vectors with clustering group related feedback into themes; and each ranked opportunity keeps its original quotes attached, so the priority list can be checked, not just trusted.

View live project
AUTOMATA03
WHY

Lead intake is usually a black box. A form gets submitted, and what happens between that and a sales rep's inbox is invisible, unauditable, and nearly impossible to improve.

WHAT

A lead comes in and AUTOMATA validates it, enriches what it can actually infer from the email domain, classifies intent, scores the opportunity, and drafts a response — logging every stage along the way.

HOW

Each pipeline stage is a small, independently tested function. A rejected lead stops with a visible reason instead of silently disappearing, and the scoring breakdown lists exactly which signals earned which points — the number is never a mystery.

PROCESS

AUTOMATA's real use case is triage on the go, so before any finished screens, a mobile companion concept started as six low-fidelity wireframes mapping the onboarding and lead-response flow — then went to a clickable hi-fi prototype once the flow held up.

Connect Source wireframe
Connect a source first — the score means nothing without real data behind it.
Set Scoring Threshold wireframe
Let the user set their own bar for "hot" instead of guessing at a universal one.
Notification Preferences wireframe
Push and hot-lead-only are on by default; summaries and quiet hours are opt-in.
Empty State Dashboard wireframe
An empty state that explains itself, so day one doesn't feel broken.
Notification and Lead Card wireframe
The notification and the decision live on one screen — no extra tap to act.
Score Breakdown wireframe
One tap deeper for anyone who doesn't want to just trust the number.
View the full flow Try the interactive prototype
View live project

About

My background is UX design and content strategy, most of it inside AI and blockchain products — writing, structuring, and shaping how people understand complex systems.

That's where the instinct comes from: a concept isn't finished until someone who's never seen it can use it without confusion. Everything below started as a plain question — what does this actually need to do — before it became code.

I use AI across the build, from prompt architecture and backend logic to front end design, data handling and deployment. I define the scope, shape the system, and determine how its parts work together.

Each project here is a deployed system that accepts real inputs, produces usable outputs, and exposes the evidence or logic behind its results.

Thoughts

Notes on building with AI, and the occasional argument.

The parts of a system you should never let AI decide

Practice

What actually happens when you have AI build a real backend

Systems

Productized service, or freelance labor with extra steps?

Business