Talk it through
Talk through my project
Talk to an expert firstContact

A process built to remove surprises.

Seven stages, each with a clear purpose, a clear output and a clear decision for you to make. Here is exactly what happens in each one.

Talk through my project

  1. Discover

    Understand the business before the product.

    We learn how your business works, who the product is for and what success would actually look like.

    What happens

    • Conversations with the people who own the problem
    • A review of existing systems, data and constraints
    • A clear picture of users and what they are trying to do
    • Agreement on what success means and how to measure it

    Who is involved

    • Product people
    • Project leads
    • Designers
    • Engineers

    Deliverables

    • Project brief
    • Goals and success criteria
    • Risks and assumptions

    Your involvement

    High. Nobody knows your business better than you do, and this stage depends on it.

    The decision that is yours
    Is this the right problem, and is now the right time to solve it?
    Handoff
    A shared brief that product, design and engineering all work from.
    You leave with
    A shared understanding of the problem.

  2. Define

    Turn understanding into a plan.

    We set the scope, choose the technical direction and decide what belongs in the first release.

    What happens

    • Features prioritised against the goals from Discover
    • Architecture and technology direction chosen, with reasons
    • A roadmap broken into releases
    • The right team assembled for the work

    Who is involved

    • Product people
    • Engineers
    • Project leads
    • AI specialists

    Deliverables

    • Scope and roadmap
    • Technical approach
    • Estimate and team plan

    Your involvement

    Decisive. You choose the priorities; we show you what each choice costs and unlocks.

    The decision that is yours
    What goes into the first release, and what waits?
    Handoff
    A prioritised scope that design can start drawing against.
    You leave with
    A plan everyone can commit to.

  3. Design

    Make it real enough to react to.

    Flows, interfaces and a clickable prototype, so decisions are tested before they are built.

    What happens

    • User flows mapped for the core tasks
    • Wireframes, then full interface design
    • A clickable prototype you can put in front of people
    • Design system foundations for consistent building

    Who is involved

    • Designers
    • Product people
    • Engineers
    • Mobile developers

    Deliverables

    • UX flows
    • Interface designs
    • Clickable prototype
    • Design system

    Your involvement

    Hands-on. You react to real screens and prototypes, not descriptions of them.

    The decision that is yours
    Does this solve the problem for the people who will use it?
    Handoff
    Designs and components engineers can build from directly.
    You leave with
    A tested design, ready to build.

  4. Build

    Engineer it in working increments.

    The product is built in short iterations, and you see working software at the end of each one.

    What happens

    • Development in short, planned iterations
    • A demo of working software at the end of each one
    • Code reviewed before it is merged
    • Designers stay involved as details are resolved

    Who is involved

    • Engineers
    • Mobile developers
    • AI specialists
    • Computer Vision engineers
    • Designers
    • Project leads

    Deliverables

    • Working software each iteration
    • Source code and documentation
    • Progress demos

    Your involvement

    Regular. You review working software, not status reports, and steer what comes next.

    The decision that is yours
    After each iteration: continue, adjust or re-prioritise?
    Handoff
    Completed features pass to QA continuously, not in one batch at the end.
    You leave with
    A working product that grows every iteration.

  5. Test

    Prove it works before anyone depends on it.

    The product is tested the way it will be used: across devices, under load and by real people.

    What happens

    • Functional testing of every flow
    • Checks across the devices and browsers your users have
    • Performance and security review
    • Acceptance testing with your team

    Who is involved

    • QA
    • Engineers
    • Product people

    Deliverables

    • Test reports
    • Resolved issue log
    • Release candidate

    Your involvement

    Hands-on. Your team tries the product against real scenarios and signs it off.

    The decision that is yours
    Is it ready for real users?
    Handoff
    A signed-off release candidate and a launch checklist.
    You leave with
    A release you can trust.

  6. Launch

    Release with a plan, not a leap.

    Deployment, store submission, monitoring and handover, planned in advance and done carefully.

    What happens

    • Production deployment and app store submission
    • Monitoring and alerting switched on
    • Documentation and training for your team
    • Close support through the first days live

    Who is involved

    • Engineers
    • Project leads
    • QA
    • Mobile developers

    Deliverables

    • Production release
    • Monitoring setup
    • Documentation and handover

    Your involvement

    Coordinated. We agree the launch plan and timing together, then run it.

    The decision that is yours
    Go live.
    Handoff
    Access, documentation and ownership transferred to your team.
    You leave with
    A product in the hands of real users.

  7. Evolve

    Keep improving what is live.

    We look at how the product is really used, then maintain, improve and extend it.

    What happens

    • Usage and feedback reviewed against the original goals
    • The next improvements prioritised
    • Maintenance, updates and scaling
    • New features designed and released

    Who is involved

    • Product people
    • Engineers
    • Designers
    • AI specialists
    • QA

    Deliverables

    • Improvement roadmap
    • Regular releases
    • Support and maintenance

    Your involvement

    Ongoing. A regular rhythm of review and planning, at the pace your product needs.

    The decision that is yours
    Based on what we have learned, what should we build next?
    Handoff
    Each round of learning feeds the next cycle of Discover and Define.
    You leave with
    A product that keeps getting better.

Three things that never change.

  • You see working software

    From the Build stage on, progress is shown in demos of the real product, not in status reports.

  • The decisions are yours

    Every stage ends with a clear decision. We lay out the options and what each one costs; you choose.

  • Nothing is thrown over a wall

    The same team carries the product from stage to stage, so context is never lost in a handover.