What is an MVP? The smallest version of your idea that's worth launching
An MVP (minimum viable product) is the smallest version of your idea that real people can use and that tells you whether it's worth building more. It isn't a sloppy version. It's a version with fewer things, done well.
An MVP (minimum viable product) is the smallest version of your idea that real people can use and that tells you whether it's worth putting more money in. It isn't a sketch and it isn't a sloppy version. It has fewer features, but the few it has work properly.
When a business owner tells me about an app or software idea, they almost always bring a long list. My first question is a different one: out of all that, what's the one thing that would change your day if it worked? That's where the MVP starts.
Why launching small first makes sense
Because the list you write before launch is built on guesses. You're guessing customers will want to book from their phone, that they'll use the color filter, that they'll care about order history. Some of those guesses will be right and some won't, and the only way to find out is to put something in front of real people.
If you build everything at once, you also pay for the features nobody ends up using, and you find out late. If you launch small, you quickly learn what people use, where they get stuck and what they ask for. Your second phase is then built on what you saw, not on what you assumed.
There's a quieter benefit too: the MVP starts solving a problem while you're still thinking about the rest. If your biggest headache is answering the same quote requests by hand, an MVP that only does that already gives you hours back from day one.
How to decide what goes into the MVP
Run every item on your list through these questions. If the answer is no, it waits for the next phase:
- Can the idea be tested without it? A booking system without a calendar proves nothing. One without a second payment method still proves plenty.
- Will anyone use it in the first week? Year-end reports can wait until there's a year of data.
- Can it be handled by hand for now? If only a few orders come in at first, a manual text message is fine. Automate it when the volume asks for it.
- Is it for the customer or for me? What your customer sees usually goes first, because that's what you're testing. Back-office tidiness can come later.
- Is it a “nice to have”? Nice to have is almost never minimum.
Examples: the full idea and a sensible MVP
| Full idea | A sensible MVP |
|---|---|
| Ordering app with catalog, payments, delivery tracking, coupons and loyalty points | Catalog where the order lands in WhatsApp; payments and points come later |
| Business software with inventory, purchasing, sales, cash register, reports and multiple locations | Inventory and sales for one location; the rest gets added once that's used daily |
| 3D configurator for the whole product line with every option | One product, the one people ask about most, with the most requested options |
| Wholesale portal where customers see prices, order and download invoices | Ordering with each customer's price list; invoices stay the way they are now |
These show the reasoning. What counts as minimum is different for every business.
Minimum doesn't mean poorly made
This is the fear I hear most, and it's a fair one. A rushed MVP that crashes, looks broken on a phone or loses data teaches you nothing. People drop it, and you can't tell whether they rejected the idea or the bad experience.
So when I build an MVP, whatever goes in is finished: it looks right, loads fast and is easy to understand. What I cut is the number of features, not the quality of each one. I also build it with the next phases in mind, so phase two sits on top of it instead of replacing it. I explain how that's organized in building software in phases.
How to tell if the MVP worked
Before launch, decide what would need to happen for you to say “keep going.” It doesn't have to be an exact number; it just has to be something you can see. For example: your regular customers place orders there instead of sending voice notes, your sales reps use the configurator in meetings, or inquiries arrive with all the details filled in.
Then watch three things: whether people use it without being reminded, where they get stuck (they'll tell you, or you'll notice it in the questions they ask) and what they ask for that isn't there yet. Whatever comes up most is your next phase. If you're one step earlier, still deciding whether the idea holds up, read how to validate an app idea.
Seeing it before building it: the Estructuras 3D demo
When a metal building or horse stall manufacturer isn't sure a 3D configurator is right for them, I don't ask them to imagine it. I show them Estructuras 3D, my own demo where you can design sheds, carports, steel buildings, horse stalls and modular homes. In a few minutes they see what theirs could look like and decide with something real in front of them.
That's the MVP mindset: test the core with something real before investing in everything. And if they move forward, the sensible start is their most requested product, with the rest added in phases.
See the Estructuras 3D caseHow I work on an MVP
We start with a video call about your idea and your business. From there I propose what goes into the MVP and what waits, with the reason behind each call, and we adjust it together. While I build, you follow progress through a link and test it on your own phone.
I work remotely from Buenos Aires, Argentina, and I answer in English and Spanish. You can see the kind of projects I take on in services.
Frequently asked questions
Is an MVP the same as a prototype?
No. A prototype shows what something could look like, and often it doesn't really work. An MVP is used by real people to do something real: order, book, get a quote or enter data. That's why it gives you answers a prototype can't.
Does the MVP get thrown away later?
It shouldn't. I build the MVP as the foundation for what comes next, so later phases are added on top and nothing starts from scratch. What may change is the layout of a screen, if users show that something else was needed.
Is it only for startups, or for established businesses too?
Both. A business that's been around for years can also test a new idea small: an ordering system just for regular customers, or a configurator with a single product, before rolling it out to the whole catalog.
How much does an MVP cost?
It depends on what it has to do, so I quote each project individually. What I can say is that with fewer features it always costs less than the full version and gets to your customers sooner.
If you have an idea and aren't sure where to start, tell me about it. I'll tell you what I'd build first and what I'd leave for later. Message me on WhatsApp at +54 9 11 6193-3176 or email contacto@facundocampo.com.ar.