Many startups spend months building an app before anyone has paid for the outcome it promises. A concierge MVP is a way to avoid that. You deliver the service by hand first, learn from real customers, and build software only for the steps that keep repeating. This guide shows how to run one and when to start replacing manual work with code.
What a concierge MVP is
A concierge MVP is the simplest version of a product where the customer receives the full result, but a person does the work behind it instead of a system. A laundry pick-up service can start with a WhatsApp number and a notebook. A tutoring match service can pair students and tutors by phone before any app exists. The customer experiences the promise, and you learn what they actually want, how often they want it, and what they will pay for.
This differs from a plain prototype. A prototype shows screens. A concierge MVP runs the real service, so the feedback is about behaviour and money, not opinions about a mockup.
When a concierge MVP makes sense
It fits best when the idea depends on a process you do not fully understand yet. Use it when:
- You have not yet confirmed that customers will pay for the outcome.
- The workflow has exceptions you cannot predict, such as custom pricing, delivery rules or approvals.
- Building the full system would take months and cost more than you can risk on a guess.
- You can reach a small group of target customers directly.
It fits less well when the product is a regulated payment flow or a feature that must be reliable from day one. In those cases you still need engineering early, but you can keep the first release narrow.
How to run a concierge MVP step by step
Define one outcome
Write the single result a customer pays for. "Book a verified plumber within two hours" is an outcome. "A marketplace for home services" is not. If you cannot state the outcome in one sentence, you are not ready to test it.
Deliver it by hand with simple tools
Use tools you already have: a WhatsApp Business number, a form, a shared spreadsheet, a calendar and a bank transfer or payment link. Keep a record of every request, what was asked, how long it took and whether the customer came back. The tools do not need to look professional. They need to show you what happens.
Sell before you automate
Charge from the first customer if you can, even a small amount. A payment is stronger evidence than a polite yes. Start with a short list of people you know are in the target group, then ask them to refer others. Be clear about turnaround times so you never promise what your manual process cannot deliver.
Track the repeats
Look at three numbers: how many people asked, how many paid, and how many paid again. Repeat purchases tell you more than sign-ups. If the same request arrives every week, it is a candidate for software. If every request is unique, you may need a clearer offer before you automate anything.
Which parts to build first
Once a step has repeated enough to be predictable, replace it with software. Common first builds include:
- A simple website with an order or booking form, so requests arrive in one place. Our website and web app development work covers this with Next.js.
- A mobile app for customers who need to order, track or rebook often. See our mobile app development service for Flutter and React Native builds.
- Back-office logic such as pricing rules, scheduling and notifications. This is usually the job of backend and API development.
Build only the step that removes the most manual work. Leave the rest on WhatsApp and spreadsheets until the numbers justify the cost.
Mistakes to avoid
- Serving too many customers at once. If you cannot deliver quality by hand, you will not learn what quality means to them.
- Hiding that the service is manual. You do not need to advertise it, but do not promise instant results you cannot deliver. Overpromising damages trust and distorts your data.
- Testing only with friends. Friends are polite. Ask strangers in the target group to pay or commit.
- Keeping the manual process forever. A concierge MVP is a learning stage. Decide in advance when you will either build or stop.
Frequently asked questions
What is a concierge MVP?
A concierge MVP is a version of a product where you deliver the full service by hand before building software. The customer gets the outcome, and you learn their needs, how often they need it and whether they will pay. It is a low-cost way to test a business idea first.
How is a concierge MVP different from a prototype?
A prototype shows what a product will look like, usually as clickable screens. A concierge MVP runs the real service, so feedback comes from actual use and real payments. That makes it stronger evidence that people want the outcome.
How many customers do I need to test an idea?
There is no fixed number. Aim for enough paying customers to see a pattern in requests and repeat purchases. If the same requests keep coming and customers return, you have a signal worth building on. If they do not, change the offer before writing code.
When should I replace the manual process with software?
Replace a step once it repeats often enough that manual work slows you down or causes errors. Start with the single step that takes the most time. A developer can then build exactly what the manual process has already proven.
If you have a service you already deliver by hand and want to turn it into software, tell us what the manual steps are. Share your brief through our project form or contact us directly, and we will help you decide what to build first.




