What we do · 05 · Product & Experience Design

App and website design tested with your users before you build.

Apps and online services that people find easy to use. We research, design and build them for founders and product teams. We agree how to measure success before we start.

Services
5
Process
Research → release
Built to
WCAG 2.2 AA

Illustration: a plan-change screen, half rough sketch and half finished design. Beside it are a customer quote and a test result: 5 of 6 people did the task alone.

What we make

5 services, bought alone or together.

Each one works on its own. Used together, strategy passes on its research and design passes on its test results.

01 / 05 · Consulting

Decide before you spend

Design Consulting & Solutioning

Expert advice on what to build, with options compared and costed.

  • Product and team assessment
  • Options compared
  • Design sprints
02 / 05 · Strategy

Plan based on evidence

Product Strategy & Vision

Decide what your product does next, and test a clickable draft with customers.

  • Product discovery
  • Opportunity mapping
  • Product vision & main measure
Typical length · 6–10 weeks Explore Strategy — Product Strategy & Vision
03 / 05 · Experience

Designed, tested, built

Experience Design & Development

App and website screens designed, tested with your users, then built.

  • User research & user testing
  • Menus, pages & journeys
  • Screen design
04 / 05 · AI Product

From idea to live feature

AI Product Strategy & Development

AI features designed into your product and tested before launch.

  • AI opportunity mapping
  • AI interaction patterns
  • AI prototype on live models
Typical length · 4-week concept · 12-week build Explore AI Product — AI Product Strategy & Development
05 / 05 · Systems

Made once, used everywhere

System Design

A shared kit of buttons, screens and brand styles your teams reuse.

  • Colours, fonts & spacing
  • Screen parts in code
  • Themes for brands & markets
Typical build · 8–16 weeks to v1 Explore Systems — System Design

Why now

Product decisions are cheapest to change before you build.

Each step from sketch to live app makes a decision harder to undo. So we test the riskiest assumptions first, in sketches and clickable drafts.

Relative cost to change one decisionLog scale · illustrative
1× 2× 4× 8× 30× 100× Where we work
Chart: the cost of changing a decision rises with each stage. It is 1× at research, about 2× at mapping and 4× at sketch. Then 8× at draft, 30× in build and 100× once live. Illustrative order of magnitude.
  • 01

    Plans built on opinion

    The loudest request wins months of engineering time. Nobody wrote down what would prove it wrong.

  • 02

    Research that arrives too late

    Findings come after the design is approved, so they only shape the next release.

  • 03

    Untested AI features

    A demo tested on 5 questions goes live. The first warning is a support ticket.

  • Our approach

    We name each assumption and test it with the simplest sketch or draft that can answer it. The result is kept with the decision.

Example project

One product idea, from customer interviews to release.

Follow one example idea through 5 stages. Customer quotes become a map of their steps, a sketch, a tested draft and a release. Each assumption moves from “untested” to “measured”.

Idea 014 · Self-serve plan changeRelease

The canvas shows the same six blocks at each stage. First interview quotes, then a map of the steps from noticing the need to changing plan. Then a sketch and a clickable draft of a plan-change screen with a “what changes” panel. Last, the released screen.

Stage 05 of 05 · Step-by-step release · usage data

Release and measure

Released to 10% of users, then to everyone. For 4 weeks, we compare plan-change contacts with before.

Confidence in the idea86%
Assumption tracker
AssumptionStateEvidence
A1People want to change plan without talking to anyone validated Self-serve completion 94% (illustrative)
A2Downgrades are mainly about price invalidated Closed
A3Fear of losing data blocks the switch validated Panel viewed in 71% of changes
A4Self-serve cuts plan-change contacts by 30% measuring −41% at week 4 · target −30%

Illustrative example. The numbers show what we measure. They are not client results.

How it works

6 stages, each with a check before the next.

Each stage ends with one question. We answer it with proof before you fund the next stage. You can start at any stage.

An engineer sketches a system diagram on a whiteboard during a working session
Design · costed with engineers

Typical times for all 6 stages. They are shorter if you start at a later stage.

  1. Plan Week 1

    We name the decision at stake and the assumption most likely to break it. Then we agree how to measure success.

    • Decision note
    • Assumption map
    • Starting data

    Check · Is the question worth answering?

  2. Discover Weeks 1–4

    We study interviews, usage data, support tickets and what you have today. Every finding keeps its source.

    • Research notes
    • Opportunity map

    Check · Is there a problem worth solving, and for whom?

  3. Design Weeks 2–6

    For each option, we draw the steps, menus and page sketches in equal detail. The engineers who would build it estimate the effort.

    • Step maps
    • Page sketches
    • Effort & risk

    Check · Can we build it, and at what cost?

  4. Test Weeks 3–8

    Your users try clickable drafts. AI features are tested on your examples before anyone sees a demo.

    • Tested draft
    • Test videos
    • AI test results

    Check · Did people complete the task?

  5. Build Weeks 6–16

    We build the screens from your shared design kit. Every change is checked for accessibility and speed, and we release in stages.

    • Screen parts
    • Accessibility report
    • Release plan

    Check · Does it pass the checks we agreed?

  6. Measure Ongoing

    With your team, we compare results with week 1. What we learn starts the next round.

    • Results dashboard
    • Decision record

    Check · Keep, change or retire?

How we use AI

AI does the sorting. Named people decide.

AI gathers, sorts and checks research. It never approves its own work: a named person reviews every theme, instruction and release.

  • Sorting research

    AI groups interview notes into themes linked to quotes. A researcher approves, merges or rejects each.

  • Working AI drafts

    We build AI drafts on the model you will use, with realistic data. So tests show the answers users would get, wrong ones too.

  • Tests before demos

    Every AI feature gets its own test set: right answers, refusals and known failures. We rerun it after every change.

  • Design quality checks

    Automatic checks for contrast, button size and keyboard use run on every change. A person reviews what they cannot judge.

Illustration of AI sorting research. Personal data is removed from 24 interviews, then 312 quotes are tagged and 5 themes proposed. A researcher approves 3, rejects 1 and merges 1. The run is logged with the model, instructions and reviewer.

  • Personal data removed before any AI sees it
  • A named person approves every result
  • Every theme links to its quotes
  • Model, instructions and reviewer logged

Shared design kit

Build each part once, and one fix reaches every product.

Colours and fonts make buttons. Buttons make screens, and screens make each app. Automatic checks cover each step, so new work reuses tested parts.

01 · Styles

ColourNamed by purpose, contrast checked
Type & spaceOne scale, every screen size
MotionTiming and reduced motion
Contrast pairs ≥ 4.5 : 1

02 · Screen parts

Figma libraryEvery version and state
Code packageSame names as the design
DocsUsage, do and don’t
Keyboard & screen-reader tests

03 · Patterns

ScreensSign-up, checkout, plan change
AI statesLoading, low confidence, refusal
ContentVoice, errors, empty states
Screenshot checks on each change

04 · Channels

WebReact · Next.js
iOS & AndroidSwiftUI · Jetpack Compose
Email & in-appSame colours and fonts
Use tracked per team

Our service pages use this diagram for research, AI testing and team set-up too.

A wall of old wooden drawers, each showing the hooks, hinges or catches it holds on its front
One libraryevery part labelled by what it is

Tools we use

Your tools first, ours only where you have none.

We work in your tools and hand everything over in them. These are the ones we use most, from research to measuring results.

01

Research & strategy

Research, maps and decisions in one place.

  • Figma
  • Miro
  • Notion
  • Confluence
  • Jira
  • Linear
02

Design & build

One library in design and in code.

  • Storybook
  • React
  • Next.js
  • TypeScript
  • Tailwind CSS
  • Swift
  • Kotlin
  • GitHub
  • GitHub Actions
03

Test & measure

Ease of use, accessibility, speed and usage.

  • Playwright
  • Cypress
  • Jest
  • Lighthouse
  • PostHog
  • Mixpanel
  • Google Analytics
  • Looker
04

AI features

Models chosen per task by tests on your own examples.

  • Anthropic
  • OpenAI
  • Google Gemini
  • LangGraph
  • LlamaIndex
  • Python

How we check quality

The standards we build to, and where each is checked.

We build to these standards. They are checks we run and record, not certificates we hold.

Every product

  • WCAG 2.2 AAWeb Content Accessibility Guidelines

    The global standard for apps disabled people can use. We build to level AA: 4.5 : 1 text contrast, visible focus, buttons at least 24 px and no drag-only moves.

    Checked inAutomatic tests · manual screen-reader check

  • Core Web VitalsLoading, interactivity and visual stability

    Google’s speed scores: main content shows in 2.5 s, taps respond in 0.2 s and nothing jumps, on 3 in 4 visits.

    Checked inLighthouse tests · user visits

  • GDPRGeneral Data Protection Regulation (EU) 2016/679

    Europe’s data law: consent, purpose and a delete date for each recording and tracked event.

    Checked inConsent log · delete dates

  • DPDP Act 2023Digital Personal Data Protection Act, 2023

    India’s data law: notice, consent and people’s rights built into each step.

    Checked inConsent and notice screens

  • ISO 9001:2015Quality management systems

    Quality rules applied to our work: written stages, a check before each next stage and logged fixes.

    Checked inStage checks · decision records

When AI is in the product

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

    Europe’s AI law. People are told when they are using AI, and we set the risk level at the sketch stage.

    Checked inAI notices · risk note

  • NIST AI RMF 1.0AI Risk Management Framework

    A US guide to AI risk. We apply its 4 steps (govern, map, measure, manage) from research to after launch.

    Checked inAI test set · monitoring plan

  • ISO/IEC 42001:2023Artificial intelligence management systems

    The AI management standard. We keep its records: intended use, oversight and change history.

    Checked inDesign records

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

    The top security risks for AI apps. We guard against hidden instructions (LLM01) and AI acting alone (LLM06): a person confirms big actions.

    Checked inAttack tests in the AI test set

What you get

Working files, handed over in your tools.

Each project ends with a handover of research, decisions and files. 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.

/handover/01-consulting/

Design Consulting & Solutioning

  • Product and team scorecardDeck · Sheet
  • Map of how it works todayFigma
  • Options with pros and consDocument · Figma
  • Clickable draft used in testsFigma · coded
  • Effort, cost & risk estimateSheet
  • Ways of working & team set-up planDocument
  • Staged plan & decision recordPlan · record

/handover/02-strategy/

Product Strategy & Vision

  • Product visionOne page · Deck
  • Opportunity map & evidence packBoard · Sheet
  • Main measure & driversSheet · Dashboard
  • Business case per ideaModel · Sheet
  • Ranked product planPlan · Board
  • Vision demoFigma · film
  • List of assumptions to testSheet

/handover/03-experience/

Experience Design & Development

  • Research plan, findings & video clipsReport · clips
  • Maps of steps, pages and menusFigma
  • Screen designs in every stateFigma
  • Screen words & writing guideDoc · Figma
  • Clickable draftFigma · coded
  • Working code & screen partsYour accounts · Storybook
  • Accessibility report & fixesWCAG 2.2 AA
  • Ease-of-use scoreSheet · Dashboard

/handover/04-ai-product/

AI Product Strategy & Development

  • AI opportunity map, task by taskBoard · Figma
  • AI interaction pattern setFigma · Storybook
  • AI prototype on live modelsCoded draft
  • Test set & resultsData · report
  • Trust & AI label guidelinesDocument
  • Live AI featureCode · your cloud
  • Use & quality dashboardDashboard

/handover/05-systems/

System Design

  • Screen inventory & auditSheet · Figma
  • Design tokensJSON · web & app files
  • Figma libraryFigma
  • Screen parts in codeYour accounts · code
  • Documentation siteStorybook
  • Accessibility checks to passPer part
  • Version & contribution rulesDocs
  • Usage dashboardDashboard

/handover/README

In every handover

  • Decision record, with sourcesDoc
  • Assumption tracker, with resultsSheet
  • Research consent & deletion logSheet
  • Walkthrough session, recordedVideo

Results

Ease of use and take-up, measured before and after.

Before design starts, we measure where you are and agree a target. We measure again the same way, so the comparison is fair.

  1. Measure firstWe measure your current product in week 1.
  2. Same methodThe same tasks, survey or events after release.
  3. Reviewed at each stageWith your team, in your analytics tools.
A printed report of bar and pie charts on a desk beside a pen pot and a red ring binder
The same methodbefore and after
Outcome review · Your productIllustrative
  • Key tasks completedRemote test, same tasks before and after
    90%from 64%target 85%
  • Rated ease of use (UMUX-Lite)2-question survey after the task, 0–100
    79from 58target 75
  • WCAG 2.2 AA criteria metAutomated checks plus a manual audit
    100%from 71%target 100%
  • AI answers kept as writtenLogged accept, edit and reject events
    82%from 55%target 80%
  • Screens built from the shared kitCode scan of shared parts used
    85%from 20%target 80%
  • New-feature users active in week 4Usage data by start week
    41%from 18%target 35%
Scale 0–100 on every row. Illustrative figures, not client results.

Offers & plans

What we offer, from audits to embedded teams.

Choose one and your enquiry reaches the right team. Start with a Sprint, such as a product review, or a Project, such as an app design.

Categories
05
Offers
21
Plans
06
Not sure what you need? Tell us the problem

How to buy

  1. 01Pick offers. Ask about one, or add several to one enquiry.
  2. 02Choose a plan. A small job, a fixed project or ongoing help.
  3. 03Send your enquiry. We reply within one working day.

Browse by category

Timelines are typical. We write the scope before we quote.

01Assess & advise

4 offers
Typical timeline: 2–4 weeks

Product review

An outside review that shows where people get stuck, and what to fix first.

What’s included

  • Expert review of the main tasks
  • Usage data and support-ticket review
  • Accessibility and speed spot checks
  • Fixes ranked by effort and impact
  • Diagnostic
  • Ranked fix list

Best forTeams who know something is wrong but not where.

Explore Design Consulting & Solutioning
Typical timeline: 3–5 weeks

Options compared & costed

2 or 3 ways to reach one goal, each sketched and costed with your engineers.

What’s included

  • Map of how things work today
  • 2–3 options in equal detail
  • Effort, cost and risk for each
  • One recommendation, with reasons recorded
  • Options
  • Decision-ready

Best forLeaders about to spend on a large build.

Explore Design Consulting & Solutioning
Typical timeline: 1–2 weeks

Design sprint

1 or 2 weeks from rough idea to a clickable draft your customers have tried.

What’s included

  • Planning session with decision makers
  • Ideas and a clickable draft
  • 5 to 8 customer tests
  • A go, adjust or stop recommendation
  • 1–2 weeks
  • Tested with users

Best forTeams stuck between ideas, with little proof either way.

Explore Design Consulting & Solutioning
Typical timeline: 2–5 weeks

Accessibility audit (WCAG 2.2 AA)

Can disabled people use your app or website? Tested by tool and by hand.

What’s included

  • Automatic scan of key pages
  • Manual keyboard and screen-reader checks
  • Issues matched to WCAG 2.2 rules
  • Ranked fix list and a retest
  • WCAG 2.2 AA
  • Manual testing
  • Playwright

Best forOrganisations that must meet a tender or policy rule.

Explore Design Consulting & Solutioning

02Strategy & vision

4 offers
Typical timeline: 4–6 weeks

Product discovery

Research with your customers and data to find what is worth building next.

What’s included

  • Customer and lost-customer interviews
  • Usage, support and sales data together
  • Opportunity map, sorted by size
  • Shortlist of ideas, with evidence
  • Research-led
  • Opportunity map

Best forProduct teams with more ideas than evidence.

Explore Product Strategy & Vision
Typical timeline: 3–5 weeks

Product vision & main measure

Where your product is going, its one main measure and what moves it.

What’s included

  • Vision on one page
  • Main measure and what drives it
  • Sessions to agree it with leaders
  • A story for board and team
  • Vision
  • Main measure

Best forProducts where each team has a different idea of the goal.

Explore Product Strategy & Vision
Typical timeline: 3–5 weeks

Ranked product plan

A now, next and later plan, ordered by evidence, with each item’s assumption noted.

What’s included

  • Opportunities scored and put in order
  • Dependencies and skill gaps
  • Measures and owners per item
  • List of assumptions to test
  • Now · next · later
  • Owners & measures

Best forTeams whose plan has become a wish list.

Explore Product Strategy & Vision
Typical timeline: 4–8 weeks

Vision demo

A polished clickable draft or film of your product in 2 years, tested with customers.

What’s included

  • Concept work with your leaders
  • Polished clickable draft or film
  • Customer reaction sessions
  • Story and presentation pack
  • Concept
  • Agreement

Best forLeaders raising money, changing direction or entering a new market.

Explore Product Strategy & Vision

03Design & research

5 offers
Typical timeline: 8–16 weeks

Complete UX & UI design

A product or main task fully designed, tested with users as we go.

What’s included

  • How pages and menus are organised
  • Every screen, including error states
  • Clear words for labels and errors
  • User tests throughout the project
  • Developer handover with clear checks
  • UX · UI
  • Tested
  • Handover-ready

Best forTeams building a new product or fixing a failing part.

Explore Experience Design & Development
Typical timeline: 10–20 weeks

Product or app redesign

A redesign of your current product, released in stages you can switch on and off.

What’s included

  • Ease-of-use score at the start
  • Redesign plan, task by task
  • Designs and drafts for each stage
  • Plan for moving users over
  • Same test repeated after release
  • Released in stages
  • Measured
  • Playwright

Best forProducts that have grown past their original design.

Explore Experience Design & Development
Typical timeline: 2–5 weeks per round

User research & usability testing

Sessions with the people who use your product, planned to settle an open decision.

What’s included

  • Research plan tied to open decisions
  • We find and pay participants
  • Live or self-guided sessions
  • Findings, clips and ranked fixes
  • Live
  • Self-guided
  • Clips

Best forTeams making a decision that nobody can settle from the data alone.

Explore Experience Design & Development
Typical timeline: 6–16 weeks

Front-end build

The designed screens built as fast, accessible code, with checks on every change.

What’s included

  • Screens coded in React and TypeScript
  • Automatic accessibility and screenshot tests
  • Speed limits checked on every change
  • Design check before release
  • React
  • WCAG 2.2 AA
  • Core Web Vitals
  • Playwright

Best forTeams with finished designs and nobody to build them.

Explore Experience Design & Development
Typical timeline: 3–6 weeks

UX writing & content design

We rewrite your product’s labels, help text and errors so people understand them first time.

What’s included

  • Review of words in main tasks
  • New screen wording in the designs
  • Error and rare-case messages
  • Writing guide for your team
  • Screen words
  • Guidelines

Best forProducts where support keeps answering the same question.

Explore Experience Design & Development

04AI in the product

4 offers
Typical timeline: 2–4 weeks

AI opportunity mapping

Where AI helps your product and where it gets in the way, task by task.

What’s included

  • Review of tasks where AI helps
  • Value, effort and risk per idea
  • Check that your data is ready
  • Shortlist and first idea to test
  • Task by task
  • Scored

Best forProduct teams under pressure to add AI without a clear reason yet.

Explore AI Product Strategy & Development
Typical timeline: 3–6 weeks

AI prototype on live models

A working AI draft on your own content, judged on the answers it gives.

What’s included

  • Screens designed for the task
  • Draft on AI models, your content
  • Tests with its future users
  • Findings, costs, build or stop advice
  • Live models
  • Tested with users
  • OpenAI

Best forTeams deciding if an AI feature is worth months of work.

Explore AI Product Strategy & Development
Typical timeline: 8–14 weeks

AI feature design & build

An AI feature designed and launched, with sources shown and a person approving big actions.

What’s included

  • Screens, including when the AI fails
  • Connection to your documents and systems
  • Test set and pass marks
  • Feedback capture and a quality dashboard
  • Released
  • Tested
  • Human review
  • OpenAI
  • LlamaIndex

Best forProducts ready to put an AI feature in front of customers.

Explore AI Product Strategy & Development
Typical timeline: 4–8 weeks

AI interaction pattern set

Reusable designs for AI features: live answers, sources, undo and handing over to a person.

What’s included

  • Design set with how-to guide
  • Rules for showing it is AI
  • Parts added to your design kit
  • Review checklist for new AI features
  • Design kit
  • Reusable

Best forOrganisations where several teams are building AI features at once.

Explore AI Product Strategy & Development

05Systems & teams

4 offers
Typical timeline: 10–20 weeks

Design system build

Styles, screen parts and guides built once in Figma and code, so teams reuse them.

What’s included

  • List of every screen part today
  • Styles as code, web and apps
  • Accessible screen parts in every state
  • Guide site and update process
  • Figma + code
  • Versioned
  • Documented

Best forOrganisations where teams keep rebuilding the same parts.

Explore System Design
Typical timeline: 4–10 weeks

Design tokens & theming

One set of colours, fonts and spacing, styled for several brands on the same parts.

What’s included

  • Style names and structure
  • Themes per brand, product or market
  • Exports for web, iOS and Android
  • Light, dark and high-contrast modes
  • Styles
  • Multi-brand
  • Multi-platform

Best forGroups running several brands or products on shared parts.

Explore System Design
Typical timeline: 4–8 weeks

Design process set-up

Clear steps to request, review and hand over design work, so quality stays steady.

What’s included

  • Requests, priorities and design reviews
  • Design checks and handover rules
  • File, library and naming structure
  • Research library and recruiting process
  • Team set-up
  • Ways of working

Best forDesign teams too large to coordinate in one conversation.

Explore Design Consulting & Solutioning
Typical timeline: Ongoing · monthly

Embedded product design team

Designers, researchers and engineers who join your team and work on your priorities.

What’s included

  • Named experts matched to your plan
  • Your tools, meetings and code
  • Team grows or shrinks monthly
  • Your team trained from week 1
  • Squad
  • Pay for time used

Best forProduct teams with a clear plan and too few senior people.

Explore Experience Design & Development

Your enquiry

Tick “Add to enquiry” on any offer, choose a plan, then continue. Or enquire about one offer.

How we work with you

Ways to start, from a question to a quote.

Ask a quick question, send your project details or request a quote. The person who will lead the work reads each one in full. Services in your enquiry go with it.

Or book a 30-minute call

What are you sending?

  1. 01

    About 2 minutes3 short answers

    For a first chat, a press request or anything not ready to plan yet.

    You get A reply from a named lead

  2. 02Recommended

    About 8 minutes5 short steps

    Goals, who it is for, budget and timing, so our first reply can outline the work.

    You get Options and prices after one call

  3. 03

    About 15 minutesYour documents attached

    Your documents, deadlines and the purchasing and security rules to meet.

    You get Confirmation and a named lead

How it is priced

Each plan shows how it is priced. Work starts once we agree a written scope and price.

  • 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 stage
  • Typical length
    Ongoing · 6-month minimum
    Pricing
    Monthly fee
  • Typical length
    6–18 months
    Pricing
    Priced per written scope
  • Typical length
    Ongoing · 3-month minimum
    Pricing
    Paid by time used
Compare what each plan includes
What each plan includes and who it suits
PlanWhat you getBest for
SprintA short, fixed job that answers one clear question.
  • Scope and result agreed before we start
  • A senior lead and the right specialists
  • A weekly review with you
  • A clear answer or a test version
An audit, a brand check or a test version of an app
ProjectOne clear job for one fixed price.
  • A written scope: what you get and how we agree it is done
  • A named project lead and a fixed team
  • A shared plan with checkpoint dates
  • Source files, yours once paid for
A brand identity, a website, a simple app or a set of tools
MilestoneA bigger build in stages you approve and pay for one at a time.
  • Stages, each with its own scope and approval
  • A go or stop review at each stage
  • Re-plan between stages as you learn
  • Pay for each stage you approve
Work too big for one contract, such as a large app
RetainerA monthly team that runs and improves what we built.
  • Team time set aside for you every month
  • Agreed response times for requests and fixes
  • A monthly review and a to-do list
  • Planned improvements, not only fixes
Monthly social media and ads, or care for live sites and apps
EnterpriseA large, long project with its own team and agreed response times.
  • A project director and a decision group
  • A team for each part of the work
  • Response times, reports and a list of risks
  • Security, legal and purchasing checks in the plan
Large companies making changes across markets, brands or business units
SquadOur specialists join your team and work in your tools.
  • Named specialists matched to your plan
  • Works in your own tools and meetings
  • Grow or shrink the team each month
  • We teach your team from week one
Teams with a clear plan that need senior people fast

Questions

Asked before the first workshop.

Anything else goes to the team that would do the work.

Enquire
Two colleagues talk through a wall of sticky notes and printed pages
The working wallquestions answered in front of the evidence
Q01Do we have to start with research?

No. Start wherever your product is: a strategy question, a design to test, screens to build or a design kit to tidy up. We only test what matters to your next decision.

Q02Will you work with our designers and engineers?

Yes. We work in your Figma, code and task tools, next to your people. At handover your team gets the files and decision record, so it can carry on without us.

Q03How is consulting different from a discovery project?

Consulting starts from a choice you face and ends in a decision. Discovery starts from a problem and ends in a build plan. We keep them separate, so our advice stays independent of the build.

Design Consulting & Solutioning
Q04How is strategy different from a roadmap?

A roadmap says what and when. A strategy says why: why these ideas beat the others and what you will stop doing. We write both.

Product Strategy & Vision
Q05How many users do you need to test with?

5 to 8 people per round, on one journey. That finds most problems, so we run several small rounds. Tests that give a score need more people.

Experience Design & Development
Q06How is this different from Technology & Intelligence?

We design the feature. Technology & Intelligence builds the AI underneath. We decide where AI goes and what people see. Most AI products need both, and our teams work as one.

AI Product Strategy & Development
Q07How is this different from Brand Systems in Brand Design?

Brand Systems sets how your brand looks and sounds everywhere. System Design builds that into your product’s styles and parts, in Figma and code.

System Design

Tell us what you need built.

You will talk to the lead who would run your work.

Book a call

Three ways to start

We always agree a written scope and price before work begins.

Choose one of the three ways above