> For the complete documentation index, see [llms.txt](https://milaforge.gitbook.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://milaforge.gitbook.io/home/founding/what-is-a-software-mvp.md).

# What Is a Software MVP?

Learn what an MVP in software development is, why startups build one, and how it helps test a business idea before investing in a full product.

An **MVP (Minimum Viable Product)** is the simplest version of a software product that can be released to real users to test whether the idea is worth pursuing.

For example, imagine you want to build an app that connects homeowners with local cleaners. You do not need to build a complete platform with automated payments, ratings, notifications, and dozens of features.

An MVP might simply let users:

* Create a request for cleaning
* See available cleaners
* Contact a cleaner
* Arrange the service manually

The goal is **not to build a low-quality product**. The goal is to build only what is necessary to test the core idea.

### Why build an MVP?

Building software is expensive and time-consuming. An MVP helps answer important questions before making a large investment:

* Do people actually want this product?
* Will they use it?
* Are they willing to pay for it?
* Which features actually matter?

Instead of spending months building a complete product based on assumptions, you can release a smaller version, learn from real users, and decide what to build next.

### MVP vs. prototype

An **MVP is usable software released to real users**.

A [**prototype**](#mvp-vs.-prototype) is usually created to explore or demonstrate an idea. It may not be a functioning product and may never be released publicly.

For example, a clickable design in Figma can be a prototype. A working web application that allows your first customers to use the core service is an MVP.

### Who builds an MVP?

A founder can build an MVP with a full-stack software developer, a small development team, or a **technical co-founder**.

If you are deciding whether you need a technical co-founder, see [How to Find a Technical Co-Founder: What to Look For](/home/founding/how-to-find-a-technical-co-founder-what-to-look-for.md).

The important question is not *"How many features can we build?"* but:

> **What is the smallest product we can build that lets us test our most important assumption?**

That is the purpose of an MVP.

Learn more about [How to Build an MVP](/home/founding/how-to-build-an-mvp.md).

Further read what to do [After Building an MVP](/home/founding/after-building-an-mvp.md).