LiveKit — Agent Observability
Challenge
[Placeholder] Brief project context to be added — what problem this work addressed.
Services
- Product design
- Interface design
Role
[Placeholder] Contribution details to be added.
The models are good. The experience is why users leave.
Ghost Pixel designs and ships the interface layer for agentic and voice AI — the states, cues, and recovery paths that make people trust an agent instead of quitting on it. Production code, not a deck.
Ten years shipping at
A Recipe App Where the Assistant Does Real Work
An AI that saves recipes, plans meals, builds your grocery list, and guides you through cooking — using the same tools as the app itself.
Launching soon
The parts of your product no component library was built for.
Agent behavior, voice conversations, latency, failure — the states your design system doesn't have components for yet. I've shipped these interfaces before and know exactly where they break.
Agentic interfaces
Most interfaces were built for someone clicking a button, not someone handing a task to an agent and waiting to see what it did. I make agent behavior visible and correctable from day one, so users stay in control instead of guessing.
Voice AI UX
Voice interfaces fail when a user talks over the agent and it keeps going, or waits through a silence without knowing if it heard them. I design what happens on interruption, latency, and a wrong answer, so voice feels usable instead of broken.
The full scope of what I cover
Design system updates Tokens, components, and docs that keep pace with your product — not lag behind it.
User research Interviews and usability tests that ground decisions in real behavior, not assumptions.
Wireframes & flows Every journey mapped before a pixel is placed, so scope stays clear and surprises stay small.
High-fidelity UI Production-ready screens with states, spacing, and motion all accounted for.
AI UX patterns The exact screens for when the agent is thinking, when it's unsure, and when it's wrong — so users know what's happening instead of staring at a spinner.
Interactive prototypes Built in code, not slides — so stakeholders react to something real, not something imagined.
Design engineering Specs, assets, and annotations engineers can implement without a single follow-up question. Shipped directly into your repo.
Content design The words inside the product — labels, errors, empty states, and onboarding — written to match how users actually think.
A continual obsession over the details.
Great experiences are built with a continuous loop of observing, reflecting and making. Understanding the now and envisioning the future.
Hey Pepper!
Challenge
[Placeholder] Brief project context to be added — what problem this work addressed.
Services
- Product design
- Agentic UX
Role
[Placeholder] Contribution details to be added.
Snowflake
Challenge
[Placeholder] Brief project context to be added — what problem this work addressed.
Services
- Product design
- Visual design
Role
[Placeholder] Contribution details to be added.
Start small, or hand me the whole problem.
In your sprints week-to-week, or scoped to one thing you need shipped. Both start at $6K. Not sure where to start? A $1,500 audit maps the problem first.
Start here
Design Audit
Map the problem before committing to the fix.
$1,500
I spend a week inside your product, using it like a real user and documenting every place it breaks trust. You get a specific, prioritized roadmap back. Most engagements start here.
- Full interface review: trust signals, error states, agent transparency, correction flows, latency handling
- 10–15 specific issues — what's broken, why it matters, and exactly what to do about it
- 30/60/90-day implementation roadmap
- Delivered in one week: written doc and recorded Loom walkthrough
Fixed-Scope Project
One thing, defined upfront and shipped.
$6,000
I scope it with you, then design and build it directly into your repo — the same person from kickoff to merge, so nothing gets lost along the way.
- Scope locked before work starts — no drift, no debate mid-project
- Design and code in one pass — nothing waits on another person
- Production-ready, merged into your repo when it's done
- If nothing ships, you don't pay for the work that didn't
Ghost Pixel takes on 2 - 3 clients at a time
How it works
- 01
Define exactly what ships.
I start inside the product, tracing agent behavior, latency, failure, and recovery. A focused scoping session turns the problem into one agreed outcome before design work begins.
- 02
Work in the same loop.
I join your Slack, Linear, and sprints. The work is async-first and Loom-heavy, with one working session each week when a decision is faster to make together.
- 03
Merge the finished interface.
Design and production code move together, then land directly in your repo with the decisions documented. What you approve is what ships — no interpretation gap in between.
Something delivered every week. If nothing is delivered in your first two weeks, that time is on us.
I started Ghost Pixel because the best design work I've ever done happened when I was closest to the problem.
Not in a review meeting. Not polishing slides. In the work — with the team, in the code, figuring it out in real time. I've done that for ten years at places like LiveKit, Snowflake, and IBM. Ghost Pixel is how I do it for you.
No pitch, no deck. Just a 25 minute conversation to see if it's a fit.