ROQ CX
Start a prototype sprint →
Sprint 01 · Validate

Prototype Sprint.
Find out if the idea earns a build.

A fixed-fee fourteen-day sprint that turns a fuzzy idea into a hi-fi clickable prototype, validates it with five real-user interviews, and ends with a written go/no-go memo.

Duration
14 days
You walk away with
  • Hi-fi clickable prototype on a public URL
  • Five recorded user interviews with consent
  • Signed go/no-go memo with rationale
  • A clean backlog for the build sprint
Week by week

How the sprint runs.

Same shape every time: checkpoints you can plan around and artifacts you can hand to a board.

01 · Week 1 · Frame

Pressure-test the idea.

  • Day 1: kick-off, success metric agreed
  • Day 2: map the riskiest assumption
  • Day 3: lo-fi flows + content draft
  • Day 4: hi-fi prototype build starts
  • Day 5: internal review + interview script
02 · Week 2 · Validate

Put it in front of humans.

  • Day 6: interview recruiting + final prototype polish
  • Day 7-9: five real-user interviews, recorded
  • Day 10: synthesis: what actually happened vs. what we expected
  • Day 11-12: iterate on the prototype where signal was clear
  • Day 13: write the go/no-go memo
  • Day 14: readout, signed memo, handover
Inputs
  • One-page problem statement
  • Target segment + access to 5 candidates
  • One success metric you'd defend
  • A decision-maker on the call
Artifacts
  • Clickable prototype URL (Figma / coded)
  • Five interview recordings + transcripts
  • Sprint memo with decision rationale
  • Backlog for the build sprint (optional)
Decision
  • Ship: move into Build & Launch
  • Iterate: second short sprint
  • Kill: cleanly, with notes
  • Pivot: reframe and re-scope
Not for
  • Big-bang website redesigns
  • Pure design polish on an existing live product
  • Compliance-heavy enterprise procurement timelines
  • Anyone who can't get five users on a call in two weeks
Common questions

Quick answers.

What if we already have a prototype?

Then this sprint is about validating it, not building it. We'll skip ahead and spend more days on user interviews and iteration cycles.

Who runs the interviews?

We do. You're welcome on the calls but the script and the synthesis are owned by ROQ CX.

What does the memo cover?

What we built, what we expected, what actually happened, our recommendation (ship / iterate / kill / pivot), and the open risks.

What if we want to keep going on day 15?

Most do. We roll straight into a Build & Launch sprint using the memo as the scope. No new procurement cycle.

Ready when you are
Book a 30-minute kick-off call.

We'll pressure-test the idea, agree on the success metric, and decide if a sprint is the right shape.

Book the kick-off call Next stepBuild & Launch