Product designer who ships
I make AI for people who run real businesses and never wanted to run software, the kind that answers their customers over text, voice, and email, and I ship it to production myself in React. Talk to one on the right.
Designed and built end to end · React · Next.js · Claude
How I design AI people trust
AI is easy to demo and hard to trust. These are the principles I design to, and under each is where I have already proven it in production.
If it cannot ground an answer, it says so. Confident wrong answers are how trust dies.
Proof: Sophia declines rather than fabricate.
The output traces back to a real, scored source, so a professional can stand behind it.
Proof: the citation-trust layer.
Approval and handoff live inside the flow, before anything goes out, never as damage control after.
Proof: the approval gate, and the demo handing off to a person.
Under pressure, legibility beats decoration. I cut a tilde once because it read as a minus from across a room.
Proof: the live auction board.
Find the step that kills momentum and collapse it. Speed is a feeling, and the feeling is trust.
Proof: a new combination, three minutes on a spreadsheet, now seconds.
Not a pretty mock. A person who never wanted software, using the thing without thinking about it.
Proof: operators adopting it with real money on the line.
The Desk · company-wide AI
The Desk is my own idea, and the work I am proudest of. One workspace that unites every tool a company already uses and puts an AI inside it. It learns each person's comfort level and adapts: more guidance for someone who never wanted software, out of the way for a power user, and it grows with them as they get more confident. The point is to bring AI to everyone on day one, not just the technical few, and lift what each person can do.
React · Next.js · multi-tenant · role-aware · adaptive UI · Claude
At one company, the whole team runs on it, every department, every day.
Try it: switch Guided and Pro to watch the Desk meet a brand-new user, then a power user.
“Having the desk available is like working next to the most patient, knowledgeable, and experienced clerk-treasurers in the state.”City Clerk-Treasurer
Conversational AI · at scale
I designed and built Sophia, the AI concierge for a national true-crime event owned by a major media company. She answers thousands of attendees over chat in the event's own voice, drawing on 600+ event sessions and 400+ verified, fact-checked speaker profiles, and she gets sharper as new transcripts land. The hard part was never getting her to answer. It was making her refuse to invent a fact she could not ground, so a brand could put her in front of its whole audience without flinching.
Next.js · Claude · retrieval grounding · guardrails · self-improving · live in production
A brand put it in front of its whole audience without flinching.
Across the county, demand for infant care outpaces licensed capacity by a wide margin, with the sharpest gap in rural ZIP codes where the nearest provider can be over 20 minutes away.
AI trust · human in the loop
For a consulting firm whose reports get read by funders, I designed a citation-trust layer. Every claim the AI writes traces back to the client's own source, scored, and a human approves it inside the flow instead of after. Making AI feel controllable and accountable is the whole job, and it is the same job here.
Next.js · retrieval · source scoring · approval gate
Consultants put their name on what the AI produced.
Real-time · dense data, made calm
Farmland sells live, by the parcel, while bidders sit in the room. People bid on a single tract, a combination, or the whole farm, and the board recomputes the optimal combination in real time. A new combination bid used to take two to three minutes to work out on a spreadsheet, and the room would lose its energy. Now the room sees the new first, second, and third in seconds. I designed it to be read from across the room with real money on the line, down to dropping a tilde that read as a minus sign from the back.
React · Tailwind · real-time bid-combination engine (dynamic programming)

The Desk in production
The Desk above runs for operators who share almost nothing: a large farm-management company that put its whole team on it, a county office, a city clerk, and a consulting firm. One product and one AI, with row-level isolation, reshaped into a different job in every seat. That is the role-aware, many-organizations-on-one-product problem, solved and in daily use.
Four operators, one product, all live and used daily.
A large farm-management company put its entire team on the Desk: leadership, accounting, marketing, and farm managers. AI grounded in the firm's own knowledge, an email assistant, and live numbers from the back office.
A county official with zero prior AI experience ran a full 8-hour workday on it, drafting real policy, a contract review, and an RFQ, with no software staff in the building.
Council minutes, ordinances, and public-records requests on the same product, reshaped for a city clerk's job.
The citation-trust workflow above, lived in every day by a team that stakes its name on the output.
Eighteen years of building
I taught myself to code to launch the first true-crime podcast, then kept building whatever the work needed. A sampling, beyond the AI products above.
I built my own task system around how my brain actually works, because the off-the-shelf ones fought me.
A clean way for an audience to listen, built when the tools to host and play audio barely existed.
Brand, product, audience, and operations for an independent network, owned end to end.
The problem I want to work on
The hard part of letting an AI answer a business's customers is not the answering. It is trust: an AI that earns it from a stranger after hours, handles the conversation that goes sideways, knows the exact moment to hand a person the wheel, and sounds like the business instead of a bot. The owner is putting their name behind it. Get the trust right and the growth follows. That trust surface is the work I want to own.
How I work on a team
I own the problem, not just the screens. Discovery, the interaction model, the design system, the production code. Accountable for the outcome, end to end.
I work as a two, not a one. My co-founder runs discovery and the client relationship; I turn her real operator interviews into the shipped product, and every build is reviewed against her field notes.
I design from real use, not taste. After watching an operator's first session reach for an attach button that did not exist, I shipped in-chat upload, a clean copy, and document export next. The bar is the moment someone stops hesitating.
I make PMs and engineers faster. Working prototypes beat decks. I run critique, give and take feedback hard, and leave the codebase better than I found it.

Let's talk
If you are building AI that real people have to trust, that is the work I want to be doing.