How much money would you save if you knew your product was going to fail before you even wrote a single line of code? Many founders spend months building complex automation only to find out that nobody actually wants the service they've spent thousands of dollars to build.
A concierge mvp is a technique where you provide a highly personalized, manual service to a small group of customers to test your business assumptions. It's a way to prove that your value proposition works by doing the heavy lifting by hand before you ever try to automate the process.
This approach helps you avoid the common trap of building a "solution" for a problem that doesn't exist. By serving customers individually, you get a front-row seat to their frustrations and needs, which allows you to refine your product based on reality instead of a business plan.
In his book The Lean Startup, Eric Ries describes this technique as a way to start the process of learning as quickly as possible. Most startups assume they need a polished, automated software product to be credible in the eyes of a customer.
The concierge mvp flips this on its head by focusing on the customer experience rather than the technology. You act like a personal concierge, providing a high-touch service that mimics what the final automated product will eventually do.
This matters because it removes the technical risk of the project and focuses entirely on the market risk. If you can't get one person to pay for your service when you're doing it for them personally, no amount of automation will change that outcome.
Most founders are terrified of doing things that don't scale because it feels inefficient. They want to reach millions of people immediately, but they forget that you can't reach a million people if you can't even satisfy one.
By providing a manual service, you can test if your customers actually find value in your idea. If they're willing to pay for a clunky, manual version of your service, it's a strong signal that you've found a real pain point.
When you work with a single customer, you don't need a database, a server, or a slick user interface. You only need a person with a problem and your own willingness to solve it manually.
In the early days of Food on the Table, the founders didn't have any recipes in a database or any grocery store partnerships. They simply met their first customer in person to learn what her family liked to eat.
They provided this personalized service for a subscription fee of $9.95 per week. This small amount of revenue was less important than the validated learning they gained from her direct feedback.
Each manual interaction acts as a mini-experiment that proves or disproves your leaps of faith. You don't have to guess what features are important because your customers will tell you exactly what they're struggling with.
As you serve more people by hand, you'll start to see patterns in their behavior. Only when you're too busy to handle any more manual customers should you start to invest in software to automate those specific tasks.
This ensures that your development team is always scaling a process that's already working. It prevents the waste of building features that customers never use or don't understand.
Manuel Rosso and Steve Sanderson founded Food on the Table by visiting local grocery stores and moms' groups in Austin. They found their first customer and provided a manual concierge service by hand-delivering meal plans and shopping lists based on what was on sale at her favorite store.
They didn't build a website until they had to scale to more customers than they could handle in person. This manual approach allowed them to eventually scale to a nationwide service that supports thousands of grocery stores across the country.
Another example is Aardvark, a social search service that Google eventually acquired for a reported $50 million. Before they built their complex routing algorithms, they had eight employees manually sorting and answering user queries behind the scenes.
This "Wizard of Oz" style of concierge service allowed them to test if users liked the experience of social search. They didn't waste time on artificial intelligence until they knew that the human-driven version of the product was something people loved.
Find a person who has the specific problem you're trying to solve and offer to fix it for them personally. Don't worry about whether they're a typical mainstream user; you're looking for an early adopter who feels the pain acutely.
Ask for payment immediately to ensure you're testing a real value hypothesis. If someone isn't willing to pay you to solve their problem by hand, they're unlikely to pay for a software version of that same solution later.
Pay close attention to every manual step you take and write down which parts of the process are the most time-consuming or confusing for the customer. These documented pain points will become the blueprint for your first automated features when you're ready to scale.
One common criticism is that a concierge service doesn't accurately reflect the experience of using an automated product. Critics argue that a human's personal touch might mask flaws in the underlying business model that automation can't fix.
There's also a risk of the "concierge trap," where a startup becomes a low-margin service business instead of a high-growth technology company. If you don't have a plan to automate the manual steps, you'll eventually run out of capacity.
However, these limitations are minor compared to the risk of building a product that nobody wants. Using manual effort as a learning tool is a temporary phase designed to provide the data needed for long-term growth.
To apply this technique, find one person who has the problem you want to solve and offer to fix it for them manually. If they agree to pay for your help, you've found the foundation for a sustainable business. Start your first manual trial with a single paying customer this week.
A concierge mvp is transparently manual, where the customer knows a human is providing the service to learn about their needs. In a Wizard of Oz MVP, the front end looks like a finished automated product, but a human is secretly performing the tasks behind the scenes. Both methods are designed to test the value hypothesis without building complex back-end technology first.
Yes, it's often more effective in B2B settings where the value of a solution is high. You can act as an outsourced consultant or service provider for a single corporate client to learn their workflow. This allows you to understand their internal constraints and data requirements before you attempt to integrate a software solution into their existing enterprise systems.
You should start automating only when you have a clear understanding of the customer's needs and your manual workload has reached its limit. If you are consistently performing the same manual task for every customer and that task provides proven value, it is a prime candidate for automation. Automation should be used to scale a validated process, not to find one.
While the cost per customer is high, the total cost to the company is significantly lower than building the wrong software. You only serve a handful of customers during this phase, meaning your total expenditure is minimal. The goal isn't to be profitable on these early customers but to gain the validated learning needed to build a profitable automated product.
The Concierge MVP Why Doing Things That Don't Scale is the Secret to Success
Rigor vs. Ruthlessness The Secret to High-Performance Teams
Transcending the Curse of Competence Why 'Good at it' Isn't Enough
Why Sales and Marketing Are Your Foundation for Wealth
Why the 'Genius with a Thousand Helpers' Model Fails
Why Validated Learning is More Important Than Your Revenue
The 7 Ways We Get Money Wrong Identifying Entropic Choices
Hero Worship as a Tool How Role Models in Finance Can Skyrocket Your Wealth
The Reality of Breakthrough Why Success Has No Miracle Moments