Start with the decision the MVP must unlock
An MVP is not a smaller version of the dream product. It is the smallest release that lets you learn or sell something specific: a pilot customer, a fundraising proof point, or an operational bottleneck removed. Write that decision in one sentence before listing features.
Define boundaries and non-goals
- Who the first users are (and who they are not)
- The three to seven capabilities required for that decision
- Explicit non-goals: admin suites, every integration, multi-region, white-label
- Platforms in v1: iOS, Android, web, or a subset
Sequence milestones, not a wish list
Break work into slices that can ship and be tested. Prefer vertical slices (a user can complete a job) over horizontal layers (UI only, then API only). Note dependencies: payments, auth providers, app store accounts, legal copy.
Capture technical constraints early
- Data sensitivity and where systems must live
- Must-use vendors (payments, identity, messaging)
- Team that will operate the product after launch
- Budget and calendar you will not move
What to bring to a partner conversation
- One-page problem and user description
- v1 feature list with non-goals
- Rough success metric for the first release
- Known constraints and open questions
Gulf market constraints to capture early
If your first users are in Saudi Arabia, the UAE, Kuwait, Qatar, Bahrain, or Oman, lock these before you hire:
- Language and UX: Arabic-first, English-first, or bilingual — and which screens must be RTL in v1
- Payments and subscriptions: which rails and store accounts you already have (or will open)
- Identity and messaging providers that work for Gulf users
- App Store / Play listing ownership and who handles regional compliance copy
- How you will collaborate remotely across Gulf and Europe time zones
European / Nordics constraints to capture early
If your first users are in Estonia, Finland, Latvia, Lithuania, Sweden, or nearby EU markets, lock these before you hire:
- GDPR and privacy: what personal data v1 actually processes, and who is controller vs processor
- EU payments and subscriptions: which rails and store accounts you can open now
- App Store / Play EU account ownership and regional listing copy
- How you will collaborate with an Estonia-registered partner across Nordics/Baltics working hours
Related Zinova pages
- MVP guide for GCC startups
- How Zinova delivery typically looks
- MVP guide for European startups
- MVP Discovery & Roadmap if you want help locking this down
- MVP Development when you are ready to build
- Studio vs freelance vs offshore agency
FAQ
How detailed should an MVP brief be?
Enough that two engineers would estimate the same surfaces. User, problem, v1 features, non-goals, platforms, and constraints on budget and date.
Should we write technical specs ourselves?
Not always. You should own product intent and constraints. Architecture depth can come from discovery with a partner if you lack that skill in-house.
When is Zinova a fit after scoping?
When you want senior-led discovery or a bounded build with written scope. Start with a discovery call; there is no automatic purchase on the site.
Next step
Tell us what is breaking, what you want to ship, and any hard constraints. We’ll confirm fit and propose a clear next step.