The model is good. The interface is why users leave.

Ghost Pixel turns ambitious agent behavior into products people can understand, steer, and trust—from the first flow through production code.

Designed at

Drag in any direction to explore the infinite work canvas. Use the arrow keys to move the canvas. Open any item to view it fullscreen.

Selected work

Agent products become credible in the details: how users delegate work, inspect progress, correct mistakes, and recover when the model is uncertain. Here are two examples of those decisions carried into working interfaces.

Slide 1 of 4: Hey Pepper — interactive voice states shown in the hands-free kitchen companion

An agent-native cooking companion

Hey Pepper turns recipe discovery, meal planning, and guided cooking into one agent-native experience. People can find, save, and customize recipes, build menus and weekly meal plans, and use voice-activated controls while they cook.

Slide 1 of 3: LiveKit agent observability — dynamic panel system exploration to customize your view

LiveKit — Agent Observability

A unified workspace for reviewing and debugging voice agent sessions through transcripts, traces, logs, audio, and performance metrics.

Design the product around what the agent can actually do.

When agents take the first pass, users need to see what happened, steer what happens next, and recover when something goes wrong. We design that operating layer—and carry it into production code.

01

Agent-native product design

We shape the whole experience around what the agent can do and what the user needs to understand. Product structure, journeys, interaction patterns, interface states, and the moments where people delegate, review, redirect, or take back control.

02

Design engineering

We prototype in code and carry the final interface into production, so behavior, motion, responsiveness, and edge cases survive the trip from an idea to a shipped product. No translation layer between the design and the build.

The full scope of what we cover

  • 01

    Product strategy. User needs, model capabilities, and technical constraints turned into a product direction your team can act on.

  • 02

    Product flows & IA. End-to-end journeys mapped before pixels are placed, so scope stays clear and surprises stay small.

How it works

We stay close from the first product decision through the final merge, so the interaction you approve is the interaction users get.

  1. Define exactly what ships.

    01

    We start inside the product, mapping user goals, journeys, system behavior, and technical constraints. A focused scoping session turns the problem into one agreed outcome before design work begins.

    Scope locked before the work starts

  2. Work in the same loop.

    02

    We 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.

    Daily context, one weekly working session

  3. Merge the finished interface.

    03

    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.

    Receive code, not a design file.

Start with the problem. Shape the work around what it needs.

A one-week audit identifies the highest-priority problems across your product experience and turns them into a clear, sequenced plan for what to fix next.

Start here

Design audit

$1,500

We spend a week inside your product, reviewing the experience from core journeys to agent behavior. You get a specific, prioritized roadmap back. Most engagements start here.

Journeys, flows, UI, and agent behavior
10–15 prioritized issues with exact fixes
30/60/90-day action plan
Written report + Loom in one week

Fixed-scope project

$6,000

We scope it with you, then design and build it directly in your repo — founder-led from kickoff to merge, so nothing gets lost along the way.

Scope locked before work starts
Design and code in one pass
Production-ready and merged into your repo
Pay only for work that ships

Bring the product problem blocking your team.

In 25 minutes, we'll decide whether an audit, a focused project, or ongoing work is the right next step.

Dylan DotoloFounder & design engineer