Biskilati — Validating the MVP Specifications Before Development
Testing the business processes with the first customers to validate and refine the MVP requirements
As the Biskilati MVP specifications and Cahier des Charges approach completion, the team has undertaken an important pre-development step: testing the project's main operating processes in real-life conditions.
At this stage, the Biskilati platform has not yet been developed. The objective of the experiment was therefore not to test the digital platform itself, but to verify whether the processes, services, and user journey defined for the future platform accurately reflect real customer needs.
Testing Before Coding
The team experimented with the Biskilati process with its first two customers, reproducing several stages of the experience that the future platform is expected to support.
This allowed the team to observe the process from the customer's perspective and identify practical points that may need to be added, simplified, modified, or removed from the current MVP specifications.
The experiment focused in particular on:
Understanding the customer's actual needs.
Identifying the information required at each stage.
Testing the process of finding and proposing suitable bicycles.
Understanding the interaction between the customer and the seller.
Identifying possible difficulties in the transaction process.
Determining which operations should be handled by the platform.
Identifying which services should remain outside the initial MVP.
From Field Experience to the Cahier des Charges
This phase is particularly important because the team is currently finalizing the Cahier des Charges before starting the technical development of Biskilati.
The feedback and observations collected from the first two customer experiences will therefore be used to review the current specifications.
The objective is to ensure that every major feature included in the MVP has a clear purpose and responds to an identified need.
The process can be summarized as:
Initial Concept → Process Testing → Customer Feedback → Requirements Validation → Final Cahier des Charges → Development
This approach allows the team to make important adjustments before coding begins, when changes are significantly easier and less costly to implement.
A Final Check Before Development
The purpose of this stage is not to prove that Biskilati is already a finished product.
Instead, it represents a final validation step before development.
By testing the operating model with real users, the team aims to enter the technical development phase with a clearer understanding of:
What the MVP must do.
What it should not do at this stage.
What information users need.
Which processes should be automated.
Which features can be postponed to later versions.
The experience gained from the first two customers will therefore contribute directly to the final version of the MVP Cahier des Charges.
Once the specifications are validated and finalized, Biskilati will be ready to move from process validation to product development.