Skip to content

Approach · Sheet 01

Four steps,
no surprises.

A clear process that keeps you in control, with working software to review every two weeks.

W1W2W3W4W5W6W7W8W9W10W11W1201  DISCOVER02  DESIGN03  BUILD04  LAUNCHBRIEF AGREEDPROTOTYPE TESTEDRELEASE CANDIDATESPRINT REVIEWSLIVE
PlannedDoneMilestoneSprint reviewToday

Fig. 1: Illustrative 12-week plan

Phases

Sheet 02 · Phases

Discover → Launch

  1. Step 01

    Typically 1–2 weeks

    Discover

    Agree what success looks like before anything is designed.

    Your role

    Share context, access and a decision-maker.

    What happens

    • Kick-off workshop
    • User & stakeholder interviews
    • Audit of existing systems & data
    • Success metrics & constraints

    You get

    • Project brief
    • Prioritised backlog
    • Estimate & delivery plan
  2. Step 02

    Typically 2–4 weeks

    Design

    Explore, prototype and test before committing to code.

    Your role

    Review options and join testing sessions.

    What happens

    • User flows & wireframes
    • Interactive prototype
    • Usability testing with real users
    • UI & design system

    You get

    • Tested prototype
    • Production-ready designs
    • Design system
  3. Step 03

    Typically 4–12 weeks

    Build

    Ship working software in short, visible increments.

    Your role

    Join sprint demos and prioritise the backlog.

    What happens

    • Two-week sprints
    • Demo at the end of every sprint
    • Code review & automated tests
    • Continuous deployment to staging

    You get

    • Working software every two weeks
    • Source code & documentation
    • Release notes
  4. Step 04

    Ongoing

    Launch & grow

    Go live, then keep improving based on real usage.

    Your role

    Tell us what users say, and we’ll act on it.

    What happens

    • Release & app store submission
    • Monitoring & analytics
    • Iteration roadmap
    • Support & maintenance

    You get

    • A live product
    • Handover & training
    • Improvement plan

How we work: principles

Sheet 03 · How we work

Principles

  • Work in the open

    A shared board, weekly check-ins and regular demos, so you always know where things stand.

  • Small, senior team

    The people you meet are the people who do the work.

  • Decisions in writing

    Every major decision documented with its trade-offs.

  • Quality built in

    Design QA, code review and automated tests on every change.

  • You own everything

    Code, designs and IP are handed over in full.

Rhythm: a typical cadence

Sheet 04 · Rhythm

A typical cadence

  • 30 min

    Weekly check-in

    Progress, blockers and next priorities.

  • Every 2 weeks

    Sprint demo

    See working software and steer what comes next.

  • Monthly

    Roadmap review

    Step back, measure results and re-plan together.

Sheet 05 · Next step

Start with a discovery call.

Tell us about your idea and we’ll outline how the four steps would work for your project.

Book a consultationhello@appcepted.com