Users don't know what the agent can do, so they type "hi" and leave.
We design the first screen: starter prompts based on real tasks, example requests, and limits stated in plain words. A visitor understands within seconds what to bring to it.
We design the interface for agents (AI that takes actions on its own) and copilots (AI that works beside a person). Users see what the agent is doing, what happens when it fails, and how to reach a human.
Quote and schedule after your brief

We design the first screen: starter prompts based on real tasks, example requests, and limits stated in plain words. A visitor understands within seconds what to bring to it.
We map the agent's states: thinking, calling a tool, waiting for approval, done, failed. Irreversible actions get a confirmation step with a short summary and an undo.
We add sources to answers, a visible uncertainty signal and a fast way to report a bad reply. The error is made visible and fixable rather than hidden.
We design the handoff to a human: what the operator sees, how history carries over, what the customer reads at that moment. This ties the agent into your CRM and workflows.
Use a package to describe what you need. We agree on the quote and schedule after reviewing your brief and requirements.
You already have an AI chat or agent, but usage is low or users don't trust it
You are launching a first agent or copilot and need a prototype to show customers and developers
Your product has several agents or a copilot across multiple areas and needs consistent logic
You describe the task and current workflow. We clarify requirements, choose a first stage and prepare a quote.
We go through your real conversations or tickets. We write down what the agent does alone, what it only suggests, and what always goes to a person.
We design the screens and every agent state, including errors and refusals. Copy is written at the same time, not after the visuals.
We build a clickable prototype and walk 5–8 users through it. We note where they stall and fix it.
You get Figma files, components and behavior notes. All files and access sit in your accounts under the agreed terms. Payment is in stages.
AI replies are unpredictable, slow at times and sometimes wrong. Besides screens, we design waiting, errors, action confirmations and handoff to a human. Most of that doesn't exist in a conventional interface.
A description of the agent's job, examples of real conversations or tickets without personal data, a list of actions the agent can take, and API docs if you have them. If you have none of this, we start with the project brief and build the scenarios together.
The interface isn't tied to one model. For working prototypes we use common model provider APIs. You can swap the model without redesigning screens as long as it supports what you rely on, such as streaming responses.
The design packages end with mockups and components for your team. A working prototype with real model calls is included in the top package. Full product development can be ordered separately from our studio.
We run the prototype with 5–8 people from your target audience and watch where they get lost. This is qualitative testing, not a statistical study. A measurable result needs a pilot with real users.
We prepare a quote after reviewing your brief and requirements. A first stage can cover: review of real conversations (you supply logs without personal data); Prioritized problem list. Scope, payment and schedule are agreed before work starts.
Describe your business, the outcome you need and your current workflow. We will clarify the requirements and prepare a quote after your brief.