Who this is for
- Founders validating an idea and deciding what belongs in v1
- Startups preparing an MVP budget, timeline, or investor narrative
- Teams that need technical clarity before hiring or locking vendors
- Companies rebuilding or pivoting a product and needing a grounded reset
For founders across the Gulf and Europe
Useful when you are validating a Gulf or European market idea — including Estonia and Nordics/Baltics founders — aligning stakeholders, or need a written plan before hiring locally or locking a vendor.
What’s included
- Product scope — MVP boundaries, phased milestones, and explicit non-goals
- Roadmap — sequencing against constraints, not a feature wish list
- Technical recommendations — stack direction, integrations, trade-offs stated plainly
- Architecture direction — mobile, web, backend, APIs, auth, and data at the right depth
- Feature prioritization — what validates assumptions early vs. what can wait
- Launch planning — what ships first, readiness, and risk areas
How we work
- Align — goals, users, constraints, and success criteria.
- Shape — scope, flows, architecture sketches, dependencies.
- Commit — written recommendations, timeline ranges, open risks.
- Hand off — outputs your team or ours can execute against.
What is out of scope
- Writing production application code (that is MVP Development)
- Marketing strategy, branding systems, or paid acquisition plans
- Unlimited workshops without a written deliverable
- Deciding your business model for you
Related reading
- MVP guide for GCC startups
- How Zinova delivery typically looks
- MVP guide for European startups
- How to scope an MVP before you hire
- MVP Development for startups
- Product studio vs freelance vs offshore agency
FAQ
When should we run discovery instead of starting to build?
Run discovery when scope is still fluid, stakeholders disagree on v1, architecture choices are unresolved, or you need a written plan before hiring or locking a vendor. Building first often wastes budget on the wrong surface.
What do we walk away with?
A scoped MVP boundary, phased milestones, architecture direction, technical recommendations, and launch planning you can hand to your team or to Zinova for build.
Does discovery include writing production code?
No. Discovery produces decisions and a plan. Implementation starts only after a separate written proposal for MVP development or another engagement.
Next step
Send a short brief. We’ll confirm fit and outline how discovery should run for your stage.