Capability 01 / 04 · Assistants and agents

AI application design that plans for the wrong answer.

We design AI assistants, agents and voice interfaces for products your customers and staff use, and prototype them on a live model. Every screen has a designed state for slow, unsure and wrong answers.

Typical length
6–12 weeks to a working prototype
Surfaces
Chat · voice · vision · agents
Standard
Tested against a prompt set

Illustration: an assistant conversation. A user asks which enterprise contracts renew before March and whether pricing terms changed. The assistant shows a read-only plan of three tool calls and answers with three numbered citations. It notes that two scanned contracts could not be read, then proposes drafting reminders to three account owners and waits for the user to approve.

What we offer

Six parts of an AI product we design and test.

Each one decides what the AI does on its own, what it asks for and what it shows so people can judge whether to trust it.

  1. 01 / 06

    Conversation & prompt design

    The opening message, questions, refusals and recovery, written as a script and tested with users before any model is connected.

    Scripted · tested

  2. 02 / 06

    Agent plans and approvals

    How an agent’s plan is shown, paused, edited and approved, with a stop at every step and undo afterwards.

    Plan · approve · undo

  3. 03 / 06

    Voice and camera input

    Voice, camera, document and screen input designed as one, with a switch to typing in noise or poor light.

    Voice · vision · document

  4. 04 / 06

    Citations and confidence

    Citations, confidence, edit history and a plain record of what the AI used, so people check before they rely on it.

    Cited · checkable

  5. 05 / 06

    Delays, errors and fallbacks

    Streaming text, partial results and clear messages for the four-second wait and the wrong answer.

    Streaming · fallbacks

  6. 06 / 06

    Experience evaluation

    Task-based testing with users on a fixed set of prompts and edge cases, scored for completion, correction effort and trust.

    Task success · trust

How we work with you

From brief to specification in four stages.

A working prototype on a live model comes early, because a static mock-up cannot show how AI answers behave. Timings are typical, set per engagement.

  1. Wk 01–02

    Define

    We agree the users, their tasks, the data the AI may see and the actions it may take. Risks are listed before features.

    • Experience brief
    • Capability & risk map
    • Prompt set v1
  2. Wk 02–06

    Design

    Flows, conversation scripts and screens, built in the design system and prototyped on a live model.

    • Interaction design
    • Conversation scripts
    • Live prototype
  3. Wk 05–09

    Test

    Users work through tasks on the prompt set, including cases where the model is wrong; we change the design based on what they do.

    • Usability findings
    • Revised flows
    • Prompt set v2
  4. Wk 09–12

    Hand over

    Specifications, design tokens and components go to engineering with the prompt set and acceptance criteria attached.

    • Design specification
    • Components
    • Acceptance criteria

How it works

A failure-state catalogue, written and tested before launch.

For each failure we record what triggers it, what the person sees, how they recover and the test that checks it on the live model.

Failure states · Support assistant5 of 23 states
Failure states · Support assistant: illustrative sample
StateTriggerWhat the person seesRecoveryTested
No source found Search score too lowSays so, offers searchOne tap to a person41 / 41
Low confidence Quality score < 0.7Answer with caveat + sourcesAsk a follow-up38 / 40
Action needs approval Refund over limitPlan shown, approve or editNamed approver25 / 25
Prompt injection attempt Instruction in a documentIgnores it, flags the fileLogged for review18 / 20
Out of scope Legal or medical askDeclines, explains whyHand-off with context9 / 12
States designed
23All before launch
Prompt-set pass rate
94%Target 95% to launch
Hand-offs with context
100%No repeat questions

Illustrative Taken from a prototype. Yours is written for your own prompt set and policies.

What changes

Three measures of trust, taken on the prototype.

We take a baseline before design starts and measure again on the live-model prototype. Figures shown are typical; your targets are set per engagement.

01

Errors people can correct

People can spot a bad answer, correct it and carry on with their task.

Recovery after a wrong answer

  • Before35%
  • Target80%+

Measured by Moderated sessions on the prompt set

02

People stay in control

Plans are visible, consequential actions need approval and anything the AI did can be undone.

Agent actions approved first time

  • Before50%
  • Target85%+

Measured by Approval events in the prototype log

03

Evidence before engineering

Design decisions are tested with users on a live model, so the build starts from what worked.

Task success on the prompt set

  • Before58%
  • Target85%+

Measured by Tasks completed ÷ tasks attempted

What you get

The specification engineering builds to, in your repositories.

Conversation scripts, the failure-state catalogue, the prompt set and the tested prototype sit in your repositories and design files from week one.

A hand sketches a flow diagram on paper, the pen resting on a yes-or-no branch
Every branch drawnthe wrong answer included

Manifest · AI Apps7 items

AI Application Design deliverables and their formats
#DeliverableFormat
01AI experience brief & capability mapDoc · board
02Interaction design & flowsFigma
03Conversation & prompt scriptsDoc · prompt set
04Working prototype on a live modelPrototype · repo
05AI interface pattern libraryFigma · Storybook
06Experience evaluation reportReport · recordings
07Design specification & acceptance criteriaDoc · tickets

Where it sits

Design follows strategy and guides engineering.

AI Application Design covers what people see and use. Its acceptance criteria become the tests engineering builds against.

  1. AI Design AI Strategy & Consulting

    Which use case, and why this one first.

  2. AI Design · this page AI Application Design

    The conversation, controls and failure states, tested on a live model.

  3. Technology & Intelligence AI engineering

    Agents, document search and infrastructure, built to the specification.

  4. Both Production evaluation

    The same prompt set, re-run on every release.

The prompt set written in week one is used at all four stages.

Technologies we work with

The design tools and models we prototype with.

Design, model and prototyping tools, most used first. We choose models by testing them on your prompt set.

  • Figma
  • Anthropic
  • Google Gemini
  • Mistral AI
  • LangGraph
  • TypeScript
  • React
  • Next.js
  • Storybook
  • Vercel
  • PostHog

Also in use

  • OpenAI
  • LlamaIndex
  • Playwright

Frameworks we build to

Public frameworks your reviewers already know.

These frameworks shape the automatic checks, failure states and records we hand over. We build to them; we do not hold certifications for them.

  • WCAG 2.2 AAWeb Content Accessibility Guidelines

    Perceivable, operable, understandable and robust content, including 2.2 criteria such as focus not obscured, target size and accessible authentication.

  • EU AI ActArtificial Intelligence Act (EU) 2024/1689

    A risk-based regime: prohibited practices, obligations for high-risk systems, transparency duties and rules for general-purpose AI models.

  • NIST AI RMF 1.0AI Risk Management Framework

    Four functions for trustworthy AI: Govern, Map, Measure and Manage, with a companion profile for generative AI (NIST AI 600-1).

  • OWASP Top 10 for LLM ApplicationsSecurity risks in generative AI applications

    Risks specific to applications built on AI models, including prompt injection (LLM01), sensitive information disclosure (LLM02), excessive agency (LLM06) and vector and embedding weaknesses (LLM08).

  • GDPRGeneral Data Protection Regulation (EU) 2016/679

    Lawful basis, data-subject rights, data protection by design and by default, breach notification and DPIAs for high-risk processing.

  • DPDP Act 2023Digital Personal Data Protection Act, 2023

    Notice and consent, duties of data fiduciaries, rights of data principals, breach intimation and added duties for significant data fiduciaries, with the DPDP Rules.

Services & packages

AI application design services, bought alone or as one programme.

Buy the design of one assistant, agent or voice interface, or the whole experience from concept to a specification your engineers can build. Designs are prototyped on a live model and tested with users.

Categories
04
Services
14
Packages
04
Not sure what you need? Describe the problem

How to buy

  1. 01Pick services. Enquire about one, or add several to a brief.
  2. 02Choose a package. A sprint, a fixed project or an ongoing team.
  3. 03Send the brief. We reply within one working day.

Browse by category

Timelines are typical. Every quote follows a written scope.

01Discovery & concept

3 services
Typical timeline: 2–3 weeks

AI experience diagnostic

A review of an AI feature that is already live: where people give up on it, where they stop trusting it and what to fix first.

What’s included

  • Session and transcript review
  • Expert review against AI interface patterns
  • Interviews with people who stopped using it
  • Ranked list of fixes with effort
  • Entry point
  • Diagnostic
  • Ranked fixes

Best forTeams with a live AI feature whose usage is falling.

Typical timeline: 2 weeks

AI concept sprint

Two weeks to turn an idea into three concepts, each demoed on a live model, so the choice rests on how they behave.

What’s included

  • Framing session with your team
  • Three concepts designed and demoed
  • Feasibility, cost and risk notes on each
  • Recommendation and next steps
  • Sprint
  • Demos
  • Decision
  • OpenAI

Best forLeadership teams choosing between several AI ideas.

Typical timeline: 3–5 weeks

AI product definition & service blueprint

What the product does and refuses to do, where a person approves and how the work runs behind the interface.

What’s included

  • Users, tasks and failure modes
  • What it can and cannot do
  • Service blueprint including the human steps
  • Success measures and acceptance criteria
  • Definition
  • Blueprint
  • Boundaries

Best forTeams whose AI product scope changes in every meeting.

02Interaction design

4 services
Typical timeline: 3–6 weeks

Conversation & prompt design

The assistant’s opening, questions, refusals and recovery, written as a script and tested before a model is connected.

What’s included

  • Conversation scripts for the main journeys
  • System prompt and tone specification
  • Refusal, repair and escalation wording
  • Script testing with users
  • Scripts
  • Tone
  • Refusals
  • OpenAI

Best forAssistants and chat products where the writing is the interface.

Typical timeline: 4–8 weeks

Agent interaction design

How a plan is shown, paused, edited and approved, so people can see what the software intends before it acts and undo it afterwards.

What’s included

  • Plan preview and step-through design
  • Approval, permission and spend-limit patterns
  • Interruption, retry and undo states
  • Audit view of what the agent did
  • Agents
  • Approval
  • Undo

Best forProducts where software acts on a customer’s or colleague’s behalf.

Typical timeline: 4–8 weeks

Multimodal & voice interface design

Speech, camera and document input designed alongside typing, with steps to confirm or correct input that was misheard or misread.

What’s included

  • Voice and camera interaction design
  • Confirmation, interruption and correction flows
  • Typed equivalent for every spoken step
  • Noise, lighting and low-quality input states
  • Voice
  • Camera
  • Corrections
  • OpenAI

Best forProducts used hands-free, in the field or on a phone camera.

Typical timeline: 3–5 weeks

Trust, citation & control design

Interface parts that let someone judge an answer: sources, what the AI used, what it is unsure of and how to correct it.

What’s included

  • Citation and source-inspection patterns
  • Uncertainty and confidence presentation
  • Correction, feedback and override flows
  • AI disclosure on each screen
  • Citations
  • Uncertainty
  • Override

Best forProducts used for decisions where a wrong answer has consequences.

03Systems & build

3 services
Typical timeline: 6–10 weeks

AI interface design system

Reusable parts of an AI interface, such as streaming text, citations, plan steps, approvals and empty and error states, designed once and documented in code.

What’s included

  • Component set with design tokens
  • Streaming, loading and partial-result states
  • Accessibility behaviour per component
  • Documentation in Storybook
  • Design system
  • Components
  • Documented

Best forOrganisations adding AI to several products and repeating the same work.

Typical timeline: 4–8 weeks

Working prototype build

A prototype on a live model with your own content, ready to test with users or show to a board or investors.

What’s included

  • Prototype on your data or a safe sample
  • Document search or tool calls where needed
  • A fixed prompt set covering the awkward cases
  • Test sessions and a findings report
  • Prototype
  • Live model
  • Testable
  • LlamaIndex

Best forTeams that need evidence before committing an engineering budget.

Typical timeline: Ongoing, by sprint

Design support through the build

Designers work with your engineers through delivery, answer what the specification cannot and check each release against what was agreed.

What’s included

  • Designer in your sprints and reviews
  • Specification updates as model behaviour changes
  • Design QA against acceptance criteria
  • Accessibility checks before release
  • Embedded
  • Design QA
  • Your cadence

Best forEngineering teams building an AI product without an AI interface designer.

04Evaluate & operate

4 services
Typical timeline: 3–5 weeks

Experience evaluation with real users

Task-based sessions on a fixed prompt set, wrong answers included, scored for completion, correction effort and trust.

What’s included

  • Prompt set covering the awkward cases
  • Moderated user sessions
  • Scoring for completion, effort and trust
  • Ranked findings with design changes
  • Usability
  • Task success
  • Trust

Best forTeams about to launch or to invest more in an unproven feature.

Typical timeline: 2–4 weeks

Prompt & response quality review

A review of what your assistant says, covering tone, accuracy, refusals and answers that damage trust, with the prompts rewritten.

What’s included

  • Sampled transcript review against your tone rules
  • System prompt rewrite and versioning
  • Refusal and safety wording review
  • Before-and-after comparison on a fixed set
  • Transcripts
  • Tone
  • Rewrite
  • OpenAI

Best forLive assistants whose answers no longer sound like the brand.

Typical timeline: 2–4 weeks

Accessibility review for AI interfaces

A WCAG 2.2 AA review of what generic audits miss: streaming output, agent actions, voice input and content that changes as people read.

What’s included

  • Screen-reader testing of streaming output
  • Keyboard control of every agent action
  • Voice input with a typed equivalent
  • Findings with fixes and retest
  • WCAG 2.2 AA
  • Screen readers
  • Keyboard
  • Playwright

Best forPublic-sector, regulated and enterprise products with conformance duties.

Typical timeline: Monthly, ongoing

Post-launch experience monitoring

A monthly review of how the experience is holding up: abandoned conversations, corrections, escalations and rejected answers.

What’s included

  • Tracking for AI-specific events
  • Monthly review of abandonment and corrections
  • Prompt set refreshed from live traffic
  • Prioritised design backlog
  • Monthly
  • Tracked
  • Backlog

Best forProducts where the AI feature is now a main part of the service.

Your brief

Tick “Add to brief” on any service, choose a package, then continue. Or enquire about one service directly.

How we work with you

Ways to engage, from a question to an RFQ.

Ask a quick question, send a project brief or issue a formal RFQ. The lead for the work reads each one in full, and any services already in your brief go with it.

Or book a thirty-minute call

What are you sending?

  1. 01

    About 2 minutes4 required answers

    For a first conversation, a press request or anything that does not need a scope yet.

    You get A reply from a named lead

  2. 02Recommended

    About 8 minutes5 short steps

    Goals, audiences, a budget band and timing, so our first reply can outline the work.

    You get Options and a first scope after one call

  3. 03

    About 15 minutesYour documents attached

    Your documents, deadlines and the procurement and security rules the work must meet.

    You get Receipt confirmed and a named bid lead

How it is priced

Each package shows its pricing model. Work starts once a written scope and quote are agreed.

  • Typical length
    1–3 weeks
    Pricing
    Fixed fee
  • Typical length
    4–12 weeks
    Pricing
    Fixed price
  • Typical length
    3–9 months
    Pricing
    Fixed price per milestone
  • Typical length
    Ongoing · 6-month minimum
    Pricing
    Monthly fee
Compare what each package includes
What each package includes and who it suits
PackageEvery engagement includesBest for
SprintA short, fixed-scope engagement that answers one defined question.
  • Scope and outcome agreed before day one
  • A senior lead plus the specialists needed
  • A working review every week
  • A decision-ready answer or prototype
Discovery, a diagnostic, a prototype or a decision you need to make soon
ProjectA defined scope, delivered for a fixed price.
  • Statement of work with deliverables and acceptance criteria
  • A named project lead and a fixed team
  • A shared plan with dated checkpoints
  • Source files, yours once paid for
Work you can describe up front: an identity, a platform or a set of tools
MilestoneA larger build in phases you approve and pay for one at a time.
  • Phases with their own scope, output and sign-off
  • A go or no-go review at every gate
  • Re-planning between phases as you learn
  • Payment tied to accepted milestones
Programmes too large for one contract, where you want control at each step
RetainerReserved monthly capacity to run, improve and extend what we built.
  • A reserved block of team time every month
  • Agreed response times for requests and fixes
  • A monthly review and a rolling backlog
  • Planned improvements as well as upkeep
Live brands and products that need a steady team without hiring one

Questions

Your questions on AI application design.

What buyers ask before AI Application Design work starts.

Book a call
How is this different from the AI work in Technology & Intelligence?

We design the experience; Technology & Intelligence builds the software behind it. That covers the agents, document search, infrastructure and production testing. We design the conversation, the controls and what the screen shows so people can judge an answer. On larger programmes the two run together.

Do you design for one model or several?

Several; the interface does not depend on one model. We prototype on the models that suit the task, including Gemini, OpenAI, Anthropic, Mistral and open-weight models. You can change model later without a redesign.

How do you design for wrong answers?

We treat a wrong answer as a normal state of the product. Sources and confidence are shown, a correction is one action away, consequential steps need approval and there is always a route to a person. Failure states are designed in the same sprint as the main journey.

Can our engineers build it from your designs?

Yes. You get a specification, components and a prompt set for your engineers to build against. What we make for you is yours once it is paid for. Tools we already had stay ours, and you get a free, permanent licence to use them. If you need more engineers, ours can join the build through Technology & Intelligence.

Can an AI interface be accessible?

Yes; we design to WCAG 2.2 AA. Streaming text is announced to screen readers and every agent action works from the keyboard. No meaning relies on motion alone, and every voice step has a typed equivalent.

Also in AI Design

The strategy and content an assistant needs to work.

Each shares the models, evaluation sets and approval rules built here.

All of AI Design

04 / 04 · Measured AI adoption

AI Strategy & Consulting

AI use policy, pilots, roadmaps and training for brand and marketing teams.

03 / 04 · AI Design

Brand AI Tools

Image and copy models tuned to your brand, scored on a brand-fidelity test set.

02 / 04 · Generative media

AI Content Studio

AI-made films, images and edits, with creative direction and a rights log.

Tell us what you need built.

You will speak to a lead who would run the work, and get a straight answer on fit.

Book a call

Three ways to start

Every engagement starts with a written scope and a quote agreed before work begins.

Choose one of the three ways above