Applications / product strategy MVP
Product strategy and MVP
We clarify the public, the problem, the flows and the essential functionalities before design and code.
Background
When this service makes sense
We define the first release for a digital product so you can validate without waste.
- Main needproduct strategy MVP
- Role in the projectWeb and mobile applications, SaaS platforms and portals connected to company data and processes.
- Result pursuedWe clarify the public, the problem, the flows and the essential functionalities before design and code.
Deliverables
What usually comes into the project
The exact list shall be adjusted after the audit, but these modules frequently appear in product strategy and mvp projects.
01Product analysis
02Usage streams
03Functions for the first version
04Development plan
05Validation criteria
Connection
Service works better when it's connected to the rest of the project
Any service works better when connected to the rest of the ecosystem: content, SEO, data, operation, hosting and maintenance.
- Web applications
- Mobile applications
- SaaS platforms
- Portals and internal systems
Recommended pages
Pages related to this type of service: technologies, fields of activity, guides and complementary services.
Frequently Asked Questions
Before we begin the project
Choice, stages and support for Product Strategy and MVP.
01 / Choice
What's useful to know
MVP means incomplete product?
No. Means the first version clear enough to validate the value without unnecessary functionality.
What information are we preparing for the first discussion?
The problem you want to solve, users, current processes and existing systems. Concrete examples and time or budget constraints are useful, even if you do not yet have a technical specification.
02 / Planning
Purpose, budget and stages
What can the project include?
For Product Strategy and MVP, starting points are: Product Analysis; Usage Flows; Functions for First Version; Development Plan; Validation Criteria. In the offer we specify deliverables, limits and responsibilities; the list adapts to your situation.
How do we set the budget and the timetable?
We estimate analysis and planning by the number of processes, roles and systems to evaluate. Further development shall be budgeted separately on the basis of agreed priorities and delivery.
03 / Continuity
Verification and support
How do you verify the result before handover?
We review together the flows, priorities, dependencies and success criteria. We document the assumptions that still need to be validated so that the plan can guide an implementation decision.
What happens after handover?
You can use the analysis with your team or with a supplier chosen by you. If we continue together, we shall set out separately the first stage of implementation, responsibilities and validation points.