Define what to learn
Identify the intended users, the assumptions to test, and the evidence to look for. Choose the essential journey and agree on what can wait.
You can spend months building features before finding out whether customers value the core idea. We help identify the question your first release should answer, who will try it, and what evidence would guide the next decision.
The work involved
Identify the intended users, the assumptions to test, and the evidence to look for. Choose the essential journey and agree on what can wait.
Develop the agreed product features with appropriate testing, access controls, and maintainable foundations. A focused scope should still support reliable everyday use.
We review progress with you regularly and plan how to gather feedback from customers using the product. We look for where they find value, get stuck, or need something different.
Use what you learn to prioritize improvements, leave out low-value features, or reconsider the direction. Agree on releases, handover, and any further development rather than assuming the next step is always to build more.
Scope, pricing & delivery
Start with the product idea, the people you want to help, and the assumption you need to test. We help choose one essential user journey and the evidence that will guide your next decision.
If the first-release scope is still uncertain, we propose a separately priced discovery phase. You receive the prioritized release scope, key user flows, technical decisions, risks, and a delivery proposal. An MVP with clear requirements can move directly to a development quote.
Agree the features, acceptance criteria, delivery stages, and price or budget before development starts. Keep later ideas outside the first release unless you approve a change to scope, timing, and cost.
Review the core journey as it takes shape. Include appropriate testing, security, privacy, and reliability in the agreed scope so early users can use the product meaningfully.
Agree deployment, documentation, code access, ownership, and handover before delivery. Plan how to gather feedback, then decide whether to improve, expand, or pause. Further releases, hosting, and ongoing support are quoted separately.
Possible starting points
Interest in an idea doesn’t always translate into paying customers. Build the essential journey and test whether early users find enough value to use it, return, and pay.
Give a small audience a working way to discover and book a service. Learn from their experience before investing in a wider catalog, advanced reporting, or more automation.
Separate essential features from assumptions so the first version answers a specific business question.
What you take away
Deliverables depend on the scope we agree:
No finished specification is needed to start a conversation. Bring the idea, the people it should help, and what you know so far. We can help clarify the assumptions and define the first release.
A prototype explores an idea or interaction and may not be functional software. An MVP is a working product with a limited scope that real users can try. We help decide which level is appropriate for what you need to learn.
The core journey, user roles, integrations, data requirements, and launch needs determine the work involved. A single-user internal tool and a product handling payments or several user roles can both be MVPs, but require different budgets. We quote the defined first release individually rather than offering a standard package price.
Timing depends on the features needed for a useful test, external dependencies, and availability for reviews. We propose a realistic plan after defining the scope and discuss whether a smaller release could answer the product question sooner.
We build with maintainability and foreseeable needs in mind, while keeping the first release focused. Wider adoption or a change in direction may call for further architecture work; an MVP is not a promise that every future requirement is already covered.
We can help review user feedback and agree on improvements, further releases, and ongoing support. The next step may be expanding the product, changing part of the idea, or pausing development while you gather more evidence.
Explore the decisions behind the work
Plan your 2027 custom software budget using illustrative effort ranges, a €100 hourly assumption, 2026 rate references, and practical cost drivers.
Should you build custom software or choose SaaS? Compare costs, flexibility, ownership, integration, and long-term value to make the right business decision.
Let’s move your business forward
Share your product idea and what you need to learn. We’ll help define a usable first release with a focused scope.