A concierge MVP delivers the product's value proposition manually instead of through software. You personally perform the service for each customer, learning exactly what they need before automating anything. It is the fastest way to validate demand and understand the job-to-be-done when you are not yet sure what to build.
How It Works
Instead of building a feature, you deliver the outcome by hand. If you are building an automated reporting tool, you manually create reports for 10 customers each week. If you are building a recommendation engine, you personally curate recommendations based on each user's data.
The customer gets the value they need. You get deep insight into what the product must do, what edge cases exist, and whether people will pay for it. No code required.
When to Use It
Validating a new product. Before building anything, serve 5-10 customers manually. If you cannot deliver value by hand, you certainly cannot deliver it at scale. The concierge phase reveals whether the value proposition is real.
Testing a complex feature. If a feature requires significant engineering investment (3+ sprints), concierge it first. Manually processing requests for a few weeks costs far less than building the wrong thing.
Understanding the workflow. When you do not fully understand the customer's process, doing it manually teaches you faster than any research method. You experience every friction point, every edge case, and every moment of value firsthand.
Use the assumption mapper to identify which product assumptions a concierge MVP can validate.
The Process
Step 1: Define the value proposition in one sentence. "We will create a weekly competitive analysis report for your top 5 competitors."
Step 2: Recruit 5-10 customers. Offer the service for free or at a discount. Be transparent: "We are building this capability and want to serve you personally while we develop it."
Step 3: Deliver manually for 4-6 weeks. Document every step, every request, and every piece of feedback. Track how long each delivery takes.
Step 4: Analyze patterns. What steps are repeated? What varies per customer? What is time-consuming but predictable (automate this first)? What requires judgment (automate this last)?
Step 5: Build the product based on what you learned. Your spec is now grounded in real experience, not assumptions. Score the build using the RICE Calculator with high confidence because you have validated demand.
Concierge vs Wizard of Oz MVP
In a concierge MVP, the customer knows a human is doing the work. In a Wizard of Oz MVP, the customer thinks software is doing it, but a human is actually behind the scenes. Both validate demand. The concierge approach is more honest and generates richer feedback because customers share their needs openly.
Scaling Past Concierge
The concierge phase ends when you have clear patterns for what to automate. Build the product in order of "most repetitive manual task first." The roadmap building guide covers how to transition from validation to delivery planning.
Track adoption as you automate each piece. Use the feature adoption calculator to ensure the automated version performs as well as the manual one.