Sponge Digital/Services/Strategy
Product discovery before you build
Check the assumptions that matter and define version one before development money is spent.
The short version
An idea for a product is not yet a list of things to build. Founders, staff and future users often picture different products under the same name. Discovery turns those pictures into something testable: who it is for, which problem it solves and which features must exist on day one. It is worth doing before a new service launches or before an existing one changes course.
Together we unpick the business goal, the audience, the limits and the riskiest assumptions. The main user journeys are written down and turned into a clickable prototype, so the conversation is about something concrete. We separate what the first release needs from what can wait, and list the questions that still need answering by users or engineers.
At the end you hold a specification, a prototype, a staged plan and a quote with its assumptions spelt out. Those are enough to decide whether, and how, to build. If you go ahead, the same team can carry on into design, development and launch. Start by telling us the idea and the decision in front of you.

What's included
What's included
Review of the problem and audience
Testing the riskiest product assumptions
Clickable prototype of core journeys
Specification for the development team
Staged plan with a quote
Also in Strategy