Service 01 of 05 · Decide before you spend

Design Consulting & Solutioning

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

We sketch 2 or 3 ways to build your new product or feature. Users test them and engineers estimate the cost. You get one clear recommendation.

Typical length
4–8 weeks
Format
Advice · options compared
Standard
One clear recommendation
Options map · Your companyIllustrative

An illustrative options map: 5 features placed on 3 plan phases for 3 options. Effort, running cost and risk are compared. The combine option is recommended.

Option 2 · CombineCombine ready-made services around your core: 9–13 weeks, lowest risk. Recommended.

What it covers · 6 parts

6 kinds of advice, from audit to ongoing help.

Start with any one. Each ends in a recommendation clear enough for finance and engineering to approve.

Sticky notes sorted into columns on a whiteboard during a planning workshop
01 / 06

Product and team assessment

We score your product, research, design kit, accessibility and measures against what your plans need.

Your starting score
02 / 06

Options compared

2 or 3 ways to reach one goal, sketched, costed and compared like for like.

Options · pros and cons
03 / 06

Design sprints

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

1–2 weeks
04 / 06

Build, buy or combine

Software compared on fit, cost to switch and what your team can run alone.

Chosen on evidence
05 / 06

Design team set-up

How design work is requested, reviewed and handed over, and how many designers you need.

Clear roles
06 / 06

Accessibility support

Ongoing help to make your product accessible: an audit, fixes, training and a public statement.

WCAG 2.2 AA

How it works

6 weeks from start to a costed plan.

No option is dropped without evidence. Each stage ends with a check: one question answered before the next begins.

  1. Plan Wk 01

    We agree the decision, the fixed limits, who is affected and what success looks like in 12 months.

    • Decision note
    • List of limits
    • Success measures

    Check · Is this the right decision to make?

  2. Explore Wk 01–03

    We review today’s steps, systems and data with their owners. Then we draw 2 or 3 options in equal detail.

    • How it works today
    • Option sketches
    • Risk log

    Check · Are all options drawn in equal detail?

  3. Test Wk 03–05

    Users and engineers test clickable drafts of the best options. The results set the effort, running cost and risk.

    • Tested drafts
    • Research findings
    • Effort & cost estimate

    Check · Did users and engineers back the best option?

  4. Recommend Wk 05–06

    We recommend one option and note why the others were dropped. You get a staged plan your team can run.

    • Recommendation
    • Staged plan
    • Decision record

    Check · Can finance and engineering both approve it?

Typical times. They are shorter if the evidence already exists.

Options compared · what you will see

3 options, scored on the same 5 questions.

The comparison your leaders approve. Each option is drawn in equal detail, so none is set up to lose.

Options compared · Your company · v4Illustrative
Options compared · Your company · v4
QuestionA · Extend the current portalB · New self-serve appC · Buy and configure
Time to first release10–12 weeks (Passes)16–20 weeks (Watch)8–10 weeks (Passes)
3-year cost rangeMedium (Passes)High (Watch)Medium, rising with seats (Watch)
Covers the top 5 user needs3 of 5 (Fails)5 of 5 (Passes)4 of 5 (Passes)
Riskiest assumptionOld system takes the load (Watch)Team can hire 2 engineers (Watch)Supplier’s plans fit (Fails)
Can undo if wrongYes (Passes)Partly (Watch)Costly (Fails)
Recommended: B, with A for the first 10 weeksAn illustrative example. Estimates are ranges agreed with your engineers, not quotes.

What you get

A decision you can defend, with the files behind it.

The decision record, research and files stay in your own workspace. The reasons stay when people move on.

Hand-drawn wireframes of a web page and its sections on a sketchbook, an orange pen beside it
The optionsdrawn in equal detail

/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/README

In every handover

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

Results

Fewer surprises after the decision, tracked with 3 measures.

Does the estimate hold? Were risky assumptions tested first? Do design requests come in the agreed way? We agree where you start, the target and the method in week 1.

  1. Outcome 01

    A plan you can budget for

    Every estimate is a range, with its assumptions written beside the numbers.

  2. Outcome 02

    Fewer U-turns later

    We test the costly assumptions in week 3. Changing course then costs a week, not months.

  3. Outcome 03

    A team that can run it

    Roles, meetings and handover written down, so your team can run the plan without us.

Outcome review · Your companyIllustrative
  • 01 Estimate range, chosen optionHow wide the estimate is, first vs final
    22%from 60%target 25%
  • 02 Assumptions tested before the decisionShare of high-risk assumptions with evidence
    82%from 15%target 75%
  • 03 Design requests made the agreed wayShare of work arriving the agreed way, week 12
    88%from 30%target 80%
Scale 0–100 on every row. Row numbers match the outcomes. Illustrative figures, not client results.

Tools we use

Workshops, maps and estimates in the tools you already use.

Every map, estimate and decision stays with your teams. Most used first. Technologies we work with. No partnership is implied.

  • Figma
  • Miro
  • Notion
  • Confluence
  • Jira
  • Linear
  • Storybook
  • Lighthouse
  • Google Analytics
  • PostHog
  • Mixpanel
  • Playwright

Standards we build to

What every option is scored against, including accessibility and privacy.

We build to these standards. We hold no certificate for them.

  • WCAG 2.2 AAWeb Content Accessibility Guidelines

    Rules that make websites usable by people with disabilities. Version 2.2 adds visible focus, tap size and easier log-ins.

    How we apply itWe check contrast, focus order and button size in the design file. Then we test key tasks by keyboard and screen reader before approval.

  • Core Web VitalsLoading, interactivity and visual stability

    For 3 in 4 visits, pages show in 2.5 s, respond in 0.2 s and do not jump around.

    How we apply itWe set limits for load time, response and layout shifts per page type. After release, we check them on 3 in 4 visits.

  • ISO 9001:2015Quality management systems

    Rules for managing quality: clear processes, attention to risk and steady improvement.

    How we apply itEvery stage ends with a written check that has an owner. Nothing is done until it matches the approved design.

  • GDPRGeneral Data Protection Regulation (EU) 2016/679

    Europe's data law: a legal reason to use data, people's rights, privacy by design, breach reports and risk checks.

    How we apply itResearch participants give recorded, specific consent. Recordings and notes have a delete date, and we keep to it.

  • DPDP Act 2023Digital Personal Data Protection Act, 2023

    India's data law and its Rules: notice and consent, people's rights, breach reports and extra duties for significant firms.

    How we apply itConsent notices for people in India. Requests about their data can be answered from the research log.

Offers & plans

Consulting services, scoped up front.

Choose a short review, costed options, new ways of working or ongoing advice.

Categories
04
Offers
14
Plans
04
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

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

  • 3 to 5 key tasks reviewed
  • Usage data, searches and support tickets
  • Problems rated by severity, with evidence
  • Fixes ranked by effort and impact
  • Diagnostic
  • Ranked fix list

Best forTeams who know something is wrong but not where.

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
  • Retest of fixed issues
  • WCAG 2.2 AA
  • Manual testing
  • Retest
  • Playwright

Best forOrganisations that must meet a tender or policy rule.

Typical timeline: 3–5 weeks

Design & research health check

How your design and research team works today, scored against what you need next year.

What’s included

  • Interviews with design, product and engineering
  • Scores for research, design and accessibility
  • Compared with your plans ahead
  • 12-month plan to close gaps
  • Starting score
  • Plan to improve

Best forDesign leaders making the case for more budget.

Typical timeline: 2–4 weeks

Drop-off review

Where people give up, at which step and on which device, from your usage data.

What’s included

  • Drop-off measured at every step
  • Screen recordings and heat maps
  • Tracking gaps that skew the picture
  • Shortlist of tests worth running
  • Usage data
  • Drop-off
  • Tests

Best forTeams with many visitors but too few customers.

02Compare options

4 offers
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.

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.

Typical timeline: 3–6 weeks

Concept check & costing

Your idea designed in enough detail to estimate its screens, systems, data and running cost.

What’s included

  • Designs detailed enough to estimate
  • Systems, data and links checked
  • Effort range, with assumptions listed
  • Advice: build, buy or wait
  • Can it be built?
  • Cost range

Best forTeams asked for a cost before anything is designed.

Typical timeline: 3–6 weeks

Software & tool selection

Build, buy or combine, chosen by fit and by what your team can run alone.

What’s included

  • Needs written as user tasks
  • Shortlist with a scored comparison
  • Hands-on trials or guided supplier demos
  • Advice, with the cost to switch
  • Build · buy · combine
  • Scored

Best forTeams choosing a website editor, shop software or portal.

03Ways of working

3 offers
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
  • Tools and access tidied up
  • Team set-up
  • Ways of working

Best forDesign teams too big to coordinate in one conversation.

Typical timeline: 3–5 weeks

Design team & roles

The design team your plans need: roles, levels, hiring order and where designers sit.

What’s included

  • Review of today’s team and workload
  • Future team, with role profiles
  • Hiring order and interview guide
  • Career paths for each role
  • Team design
  • Role profiles

Best forLeaders building or reshaping an in-house design team.

Typical timeline: 4–8 weeks

Research routine set-up

A research routine your team can keep: a test panel, consent rules and a schedule.

What’s included

  • Panel of people to test with
  • Consent, payment and deletion rules
  • Shared library of findings
  • Templates, training and a regular schedule
  • Ongoing research
  • Shared library

Best forTeams who research in bursts and lose what they learned.

04Advice

3 offers
Typical timeline: Ongoing · quarterly

Accessibility support

Ongoing help to make your product accessible and keep it that way.

What’s included

  • Audit, fix plan and first fixes
  • Checks built into design and build
  • Training for designers, writers and engineers
  • Accessibility statement drafted for you
  • Re-check and report every quarter
  • WCAG 2.2 AA
  • Ongoing
  • Training
  • Playwright

Best forOrganisations that must be accessible, with no expert on staff.

Typical timeline: Ongoing · monthly

Design advisory retainer

A senior design and product advisor for your leaders, each month, for reviews and decisions.

What’s included

  • Named senior advisor
  • Monthly review of work in progress
  • Feedback and decision help on request
  • Written review of your team, quarterly
  • Retainer
  • Senior advisor

Best forIn-house design leaders who need an experienced outside view.

Typical timeline: 1–2 weeks including preparation

Customer workshop for leaders

A guided day where your leaders see what customers go through and agree 3 changes.

What’s included

  • Customer evidence and clips, sent beforehand
  • Guided session with your leaders
  • Ranked change list, with owners
  • Follow-up note and a check-in
  • Workshop
  • One day

Best forLeaders who no longer see what their customers go through.

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
    Ongoing · 6-month minimum
    Pricing
    Monthly fee
  • Typical length
    6–18 months
    Pricing
    Priced per written scope
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
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

Questions

Consulting questions, answered up front.

Anything else goes to the people who would do the work.

Enquire
Q01How 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.

Q02Can you work with our existing design team?

Yes. We work next to your designers, researchers and product managers. They keep the way of working after we leave.

Q03How do you estimate cost without full details?

We give a range, set with the engineers who would build it. It draws on similar past work and written assumptions, and we update it as each is tested.

Q04Do you run accessibility audits?

Yes, to WCAG 2.2 AA. We run automatic checks and test by keyboard and screen reader. You get a ranked fix list and a statement to publish.

Q05What if the answer is to do nothing?

Then the report says so and explains why. It also lists what would change our advice.

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