A readable scope before any promise is made.
These ranges provide an order of magnitude. Price, schedule and acceptance criteria only become contractual in an accepted quote.
Describe my needProduct diagnosis
Decide what to build, fix or stop before committing to a delivery project.
- Indicative duration
- 1 to 2 weeks
- Indicative budget
- From €1,500 excl. tax
Prerequisite
A product, prototype or sufficiently concrete problem to examine.
Included deliverables
- Journey, code or architecture audit based on the need
- Risks, assumptions and dependencies made explicit
- Prioritized plan with options and decision criteria
- Readout and handover material
Product MVP
Design and deliver a first scope that can be tested with real usage.
- Indicative duration
- 6 to 12 weeks depending on scope
- Indicative budget
- Budget defined after diagnosis
Prerequisite
An available decision-maker, identified users and an adjustable scope.
Included deliverables
- Priority journeys and a product-specific design system
- Responsive, accessible React / Next.js application
- Real data, integrations and error states
- Essential tests, preview, production release and documentation
Reliability sprint
Address the blockers making a product hard to ship or take over.
- Indicative duration
- 2 to 4 weeks
- Indicative budget
- From €4,000 excl. tax
Prerequisite
Access to the repository, a reproducible environment and observed errors.
Included deliverables
- Risk reproduction and classification
- Fixes within the agreed scope
- Regression tests and deployment checks
- Remaining debt and rollback procedure documented
In every engagement
Simple rules that remove grey areas
Ownership and access
Ownership of code, accounts and deliverables is defined in the quote.
Visible changes
An out-of-scope request is priced or exchanged for a planned item.
Traceable validation
Acceptance criteria and reservations are written, not assumed.
Planned handover
Access, decisions and procedures needed for takeover are part of the exit.
Frequently asked questions
Next step
Start with context, not a prepackaged solution.
Describe the problem, existing product and deadline. Yodev replies with the questions to resolve and a suitable engagement format.