Glossary term
MVP (Minimum Viable Product)
The simplest version of a product that still delivers real value and can be tested with users. Hackathon teams aim for an MVP, not a finished product.
Why it matters
MVP (Minimum Viable Product) is part of the practical craft of shipping something real in 48 hours instead of only talking about ideas. In the Global South, where access to compute, devices and training is uneven, getting this vocabulary right is not academic — it is the difference between watching the AI shift and taking part in it.
In context
We use MVP (Minimum Viable Product) in the hackathons & building part of our work. Students meet the concept in workshops, mentors reference it while reviewing projects, and partners see it in the reporting we send after every programme. Keeping the definition plain means a first-year student and a ministry official can hold the same conversation.
How Tembi Labs uses it
MVP (Minimum Viable Product) is not left on a slide. Our AI hackathons put concepts to work within hours: teams pick a local problem, use AI tools to prototype, and present something running by Sunday. It is exactly the kind of skill a 48-hour build teaches faster than a semester of lectures.
At a Tembi Labs hackathon, understanding MVP (Minimum Viable Product) means a student can move from asking "what is this?" to shipping a working prototype in a weekend — and walk away with a portfolio piece, a mentor network and a credible path into tech work.
Want to see MVP (Minimum Viable Product) applied on campus?
Book a call and we will walk you through how a Tembi Labs AI hackathon or computer room works at your university.