Skip to main content

Now onboarding Q3 projects

Stage 01

Discovery & Requirements

Evidence before estimates - a paid, credited truth.

Approach stage 01: Discovery & RequirementsApproach stage 01: Discovery & Requirements

Why it matters

Why this stage earns its keep.

  • fewer change orders

    scope agreed on evidence, not optimism

  • aligned stakeholders

    one problem statement, one success metric

  • budgets based on reality

    fixed quote after prototype, not before

  • bad ideas killed early

    the cheapest place to be wrong

Step by step

How it runs.

  1. Stakeholder interviews

    8-12 sessions, recorded + synthesized

  2. Problem framing

    problem statement + success metrics

  3. Research + opportunity mapping

    analytics + competitor review

  4. Prototype in Figma

    riskiest flow first, up to 8 screens

  5. Architecture + estimate

    stack recommendation + fixed quote

  6. Roadmap handoff

    90-day plan + readout deck

Deliverables

What you walk away with.

  • PRD
  • prioritized user stories
  • clickable prototype
  • architecture sketch
  • risk register
  • fixed build estimate
  • 90-day roadmap
  • readout deck

Who's involved

The people on the stage.

  • PM1
  • BA1
  • Architect1
  • Designer1

Controls

Quality & risk.

  • sign-off gate per artifact
  • no-build recommendation allowed
  • NDA before material
  • estimate includes assumptions list
  • prototype tested with 5+ users (add-on)

FAQ

Questions, answered.

How long?

2-4 weeks depending on stakeholder availability.

Is it paid?

Yes - and credited to build if we ship it.

What do we own?

All artifacts, unconditionally.

Do you talk to users?

With permission, up to 5 sessions in the testing add-on.

What if we already have specs?

We audit them first; discovery shrinks to validation + estimate.

Discovery & Requirements applied to your project.

Tell us where you are — we'll run the stage that gets you unstuck.