A starting point

Product Discovery Sprint

Test a product idea before you pay for the build. A tested scope, a clickable prototype and a build plan, in one written report.

  • Set with you at the start
  • 6 deliverables
  • Ends in a written report
Sample layout, not real findings Product Discovery Sprint report

Prepared for: yourbusiness.com

Summary
What we looked at
  1. A written problem statement and a definition of who the product is forFix first
  2. Research notes from talking to the people who would use itFix first
  3. A scoped first version: what is in, and what is left outPlan
  4. A clickable prototype you can put in front of usersPlan
  5. A recommended technical approach and build planFine
Next steps, in priority order
The report is short and written in plain words. Ratings above are placeholders to show the layout.

What you get

What you receive

Agreed before we start, so you know exactly what is covered. You choose the pace. We agree the schedule with you at the start.
product-discovery-sprint.deliverables6 items
  • A written problem statement and a definition of who the product is for
  • Research notes from talking to the people who would use it
  • A scoped first version: what is in, and what is left out
  • A clickable prototype you can put in front of users
  • A recommended technical approach and build plan
  • A short written report with the decision to build, change or stop
The report is yours to keep, whatever you decide next.

How it works

Three steps, then you decide

  1. Tell us what is worrying you

    Write a few lines or book a short call. Share the site, system, quote or idea you want looked at.

  2. We agree the scope with you

    A person on the team replies to agree what is covered. The work is fixed and written down before it starts, and you choose the pace.

  3. You get a short written report

    Plain words, fixes in priority order. It is yours to use with us or with anyone else.

Where it can lead

If you want to go further

The report often points to work in one of these disciplines. You decide whether, when and with whom.

Read more

The detail

The Product Discovery Sprint is for founders and product owners who have an idea and want to test it before building it, because the most expensive mistake in a new product is building the wrong thing well. You walk away with a tested scope, a clickable prototype and a build plan, written up in a short report.

What does the Product Discovery Sprint cover?

We begin with the problem: who has it, how they solve it today and what would make them change. We talk to people who would use the product, look at what already exists in the market and test the assumptions the idea depends on.

From there we decide what the first version should do and, just as important, what it should leave out. Leaving things out keeps a first build affordable and quick.

How does the sprint run?

The sprint is focused, and it follows the first steps of The Path: Understand, then Shape. We work with you on the brief, run the research, design the steps users will take and build a clickable prototype. You see the work as it forms, and you decide at each step whether to keep going. The price is fixed and agreed before we start.

What do you walk away with?

A short written report with the problem and audience, what we learned, the scope of a first version, the prototype and a build plan covering the technical approach. It ends with a plain recommendation: build, change direction or stop.

What happens after the sprint?

If the answer is to build, the plan leads straight into MVP development, or SaaS development for products with accounts, subscriptions and billing. App-first ideas move into Application Development and mobile app development. The Product Sprint and, for founders we choose to back, the Co-Build Partnership, both under Ways to Work, are other ways to start.

Is this right for you?

It suits first-time founders, teams adding a new product line and anyone about to spend heavily on a build. If you already have a tested scope and only need it built, skip the sprint and tell us what you need. If you have a stalled build, product rescue is the better start. Have an idea worth testing? Start with a discovery sprint.

FAQ

Questions we get asked

What if the sprint shows the idea will not work?

That is a useful result, and we will tell you plainly. It is far cheaper to learn it now than after a full build.

Do I need a finished idea?

No. You need a problem you believe is worth solving and some idea of who has it. The sprint turns that into a scope.

Do I own the prototype and the plan?

Yes. You get the prototype, the scope and the report, and you can take them to any team.

How is this different from a Product Sprint?

The Product Discovery Sprint is the small first step and ends in a plan. A Product Sprint is a wider way of working that can also deliver a first working version.

Let's Talk

Start with the Product Discovery Sprint

Tell us a little about your business and what you want looked at. A person on the team will reply to agree the scope and when to begin, and will tell you if a smaller step would do.
  • A reply from a person on the team
  • Or book a short call
  • We say so if another team suits you better

Write to us in plain words

We use your details only to reply to you. Privacy notice

contact@techsum.digital WhatsApp

Or book a short call

Pick a time that suits you. You will speak with the people who would do the work.

Loading the calendar.Open the booking page