Digital consulting, custom software, automation and AI. We choose the direction based on your business processes and goals.
All solutions ↗Digital product definition and validation
Define your users, their problem and a focused first release. Test the experience with a prototype and prepare requirements for an informed development decision.
Explore the solution01 / Who it is for
Product discussions quickly collect accounts, messaging, payments and reports. It becomes difficult to explain which need the first release addresses and which features can wait. For a founder, we start with the intended user and the alternative they use today. Within an established company, we also identify who sponsors the project, who will run it and how it fits existing services. We turn these perspectives into a shared scope, with explicit assumptions and questions that can be tested before development begins.
02 / What the project can include
We speak with people in the intended audience about real situations, existing alternatives and recurring difficulties. We separate observed needs from feature ideas and state the assumptions that need checking before the team decides what to build.
We map the journey through which a user solves the problem and connect conceptual screens into a prototype. We also consider missing information, declined requests and moments when someone needs help, so the journey covers more than an ideal outcome.
We identify what the main journey requires, what can wait and which evidence the test should produce. Observations become requirements and priorities, giving the team a shared basis for deciding whether and how to proceed with development.
03 / Illustrative example
Imagine a platform connecting businesses with service providers. The initial idea includes subscriptions, recommendations, chat and ratings. We first explore whether businesses can describe a request clearly and providers can give a useful response. We prepare a prototype covering request submission, responses and status tracking. During testing, we observe where people hesitate and what information they need. We then revise the journey and define the first release. The remaining features stay as options, with clear reasons for considering them later rather than adding them automatically.
04 / How we work
We gather the idea, intended audience and existing examples. Conversations with relevant people help identify the real problem and the questions worth exploring before drawing screens.
We choose a main journey, explain the roles and sketch the screens. Essential features are separated from extensions, then checked against the problem the product should address.
People from the intended audience work through concrete tasks using the prototype. We observe behaviour, difficulties and questions without treating polite feedback as evidence of commercial demand.
We summarise findings and revise the scope. First-release requirements accompany a recommendation to proceed, adjust or test further, keeping unresolved assumptions visible to the team.
05 / What you receive
What the project can include
Where we start
Describe the idea, who would use the product and how that person solves the problem today. If you have sketches or conversations with potential users, we can use them as a starting point.
Let's define your product idea
