How to Build an MVP Without Starting With Every Feature
Salim Akil · · 2 min read
When I asked how Clara built its technology, the useful answer was not a technology stack. It was a decision about scope: start super narrow. That is the part I want founders in the UAE and KSA to hear before they commission an ambitious platform.
Complex Does Not Mean Build Everything
The speaker acknowledges that Clara had a complex problem to digitise. There was a lot to bring online, and the team spent a long time in development and closed beta. This is not a story about shipping an entire company-management system in a weekend.
The initial feature set included company formation, startup contracts such as SAFEs, and a data room that investors could use for diligence, comments and review. Even that starting point was broad. The speaker says not all those features survived.
Treat the First Feature Set as a Decision, Not a Promise
My takeaway is that the first version does not have to become the permanent product map. A feature can make sense at the beginning and still fail to earn a place later. Building it is not proof that customers need it.
If I were reviewing an early product plan, I would ask which customer task must work first and which features can wait. Clara's short does not give us a full prioritisation method or a delivery budget, so I would not pretend it does. It gives us something more focused: start narrow, acknowledge the complexity, and accept that some early features will not survive.
Bottom Line
Related reading
- how to validate the idea before expanding the feature set
- Clara's business-model lessons on digitising a traditional service
- how to earn the first customer once the MVP exists
Salim Akil — Venture Building Consultant, BE Venture Partners · Host, B Model Podcast. LinkedIn