A minimum viable product (MVP) is the first, bare-bones version of your software product that only includes its most essential features.

A V1 product is the first version of the software product that fully deliver the value in production on a small scope - typically 1 sub-scope, 1 power-users with 3 customers with validation for at scale deployment and payment.

A prototype is a piece of MVP developed to validate a specific technical parts of the full software experience.

The Prototyping Strategy is our ability to get fast and gradually significant market validation with minimal effort through prototyping, MVP and product development.

The Prototyping Strategy usually start when we close Co-builder Agreements on a Product Vision being:

• Promise: Hypothesis of Value - “we aim to 10x the accuracy and development time of BOM”
• Problem or Roadblock to overcome - “scattered BOM data with no data intelligence”
• Product capabilities loosely defined to do so - “Data Relationships & Automation in a nice UX”

The Prototyping Strategy aims thus to move from a dream product vision to a tangible product and impact through successive deliberate product development efforts.