5.5Concierge Test

A concierge behind a desk with a service bell welcoming an approaching customer

At a Glance

~1 month~1 month Concierge tests can be the most time-consuming method as they require manually solving the customer problem. For a complex B2B IT solution, a concierge test can be a complete consulting engagement lasting many months. For a consumer, it might be as simple as personally going shopping with a customer. AI tools can help with note-taking and pattern recognition across customer interactions, but the manual delivery itself cannot be shortcut.
~$1K~$1K Similarly, the method can require substantial resources or nothing but a pen and paper. In the case of a B2B concierge service, it is often possible to charge for the solution up-front, which eliminates resource constraints.

In Brief

A concierge test is a product research method where you manually deliver your product’s value as a hands-on service to a small number of real customers. You perform every step by hand — solving their problem personally — and gather direct feedback on what works, what does not, and what features are essential. The output is detailed qualitative insight into the minimum viable feature set needed before you invest in building an automated product.

Common Use Case

You believe your product idea will save customers time or effort, but you haven’t tested the actual workflow yet. Instead of building anything, you personally deliver the service by hand for a handful of customers, learning exactly which steps matter, what they actually need, and whether they would pay — all before you write any code.

Helps Answer

  • Does this solution actually solve a real customer problem?
  • How can the problem be solved in practice?
  • What is the minimum feature set needed to deliver the solution?
  • What are the biggest obstacles to delivering this solution?

Description

In a concierge test, the value proposition is delivered as a service. Like a hotel concierge, the focus is on a highly customized, customer-facing service. For this method you need to perform the tasks manually, usually for only a few customers as it is not cost-efficient to scale. That said, the heavy customer touch gives you quality feedback from the targeted segment, allowing you to adjust services instantly at a very low cost. Hence iterations based on insights from customer feedback are easily accomplished.

To conduct a successful concierge test, you need a clear and well-formulated value proposition. As an evolution of problem-solution interview techniques, the goal is to test the solution and figure out if it matches your customer’s expectations. Design your value proposition as a service with the leap-of-faith assumptions in mind. When using the service, your customers should go through the same steps as they would later with your actual product.

Deliver your service manually in a customized and personal way. To avoid being overwhelmed, start with just a small batch of customers. At this point, you do not need a single line of code or automation. Even though it is inefficient and time-consuming, keep in mind that the direct customer touch is a valuable learning tool. While delivering your service, keep collecting customer feedback and adjust your service accordingly.

After some time, you learn about your customers’ expectations and what is really valuable to them. Gradually automate the parts of your service that work. Be careful not to run your concierge test forever! Keep automating and expanding your service until you are not getting new major insights.

How to

Prep

  1. Write down the value proposition you are testing. Be specific: “We help [customer] do [task] so they get [outcome].” This is the claim your concierge test will validate or invalidate. If you cannot finish that sentence, you are not ready to run a concierge test — you are still in problem discovery, and a Customer Discovery Interview is the better next step.
  2. Pick the segment. Concierge tests do not scale, so the segment you pick determines what you can learn. Choose a tightly-scoped early-adopter group: people who already feel the pain acutely, can describe their current workaround, and are reachable without a marketing budget. The wrong segment produces friendly-sounding feedback that does not generalize.
  3. Map the manual flow. List every step the customer will go through — the same steps they would go through with your eventual product. For each step, decide how you will deliver it manually: email, spreadsheet, phone call, in-person meeting, Google Doc. The flow you draft here is the spec for what gets automated later, so write it as if a junior teammate would have to follow it.
  4. Identify which steps to automate first. Tag each step on the manual flow as must stay human (the part where the value proposition lives), automate first (high-volume, low-judgment, easily templated), or automate later (judgment-heavy but eventually scriptable). The automate-first list is what you watch the test against.
  5. Recruit 3–5 early adopters. Find people who already have the problem and are willing to try your service. Ask for payment (even a small amount) — paying customers give more honest feedback than free users.
  6. Set expectations. Tell customers this is an early, hands-on version of the service. You will be personally involved, things may be rough, and you want their honest feedback.

Execution

  1. Deliver the service manually. Perform every task yourself. Track how long each step takes, where customers get confused, what they ask for that you didn’t anticipate, and what they don’t use.
  2. Collect feedback after each interaction. Ask: “What was most valuable? What was frustrating? Would you pay for this again?” Record responses immediately.
  3. Adjust and repeat. After each batch of interactions, update your service based on what you learned. Change pricing, add steps, remove steps. The concierge test is iterative — you are designing the product through direct delivery.
  4. Know when to stop. When you stop hearing new feedback and can predict what customers will say, you’ve learned what you can from manual delivery. Begin automating the parts that work.

Analysis

  • You will collect mostly qualitative data as you are delivering a manual service. You need to aggregate the data from all your current customers for the various aspects of your service. Use the insights to adjust your service accordingly.
  • The main benefit of this method is the ability to generate ideas around the potential solution/product and identify obstacles to implementing that solution.
Biases & Tips
  • False positive bias This method does not serve to validate the solution, as the manual component provides an extra value proposition of trust and responsiveness. Entrepreneurs can therefore mistake positive feedback on the service as validation of the product concept. When moving to an automated solution, the extra “human” value proposition is removed and the customer can reject the solution.

  • Sampling bias As the concierge test is manually performed, you have to find a balance. On the one hand, having too many customers can be overwhelming — you find yourself or your team busy delivering the promised service, which leaves very little time to analyze the data and use the insights to make adjustments. On the other hand, you have to make sure that your customer batch is not too small. Insights you get from just one or two customers might not be enough. You risk that the collected feedback is not representative of the customer segment you are targeting.

  • A concierge test is an experience, not a product. - @poornima

Next Steps

  • Iterate on the service based on direct customer feedback from concierge delivery.
  • Identify which manual steps are highest-value and should be automated first.
  • Run a Pre-Sales Test to validate willingness to pay among concierge customers.
  • Once the concierge version consistently delivers value, build a Single-Feature MVP that automates the highest-value manual step first.
  • Use a Wizard of Oz test to evaluate customer reactions when the manual service is hidden behind an automated-looking interface.
  • Run a Product-Market Fit Survey once you have enough concierge customers to measure whether they would be disappointed without the service.
Learn more

Case Studies

Airbnb: Air mattresses in a San Francisco loft

Brian Chesky and Joe Gebbia photographed their San Francisco apartment, posted it for design-conference attendees, and hosted three paying guests to test whether people would pay to stay in a stranger’s home.

Read more

Amazing Airfare: $8 manual deal alerts

Zachary Cohn validated his flight-deal alerts concept by collecting $8 each from five subscribers via PayPal and emailing them deals from a spreadsheet before building any software.

Read more

GE Healthcare: Concierge-style infant monitoring trial

GE Healthcare tested a new infant monitoring concept in emerging markets by deploying trained nurses with portable tools to deliver the experience by hand, validating workflow fit and perceived value before investing in complex diagnostic equipment.

Read more

Food on the Table: Concierge meal-planning

Manuel Rosso recruited Food on the Table’s first customers by accompanying Austin grocery shoppers on their trips and emailing personalized meal plans, learning the workflow by hand before any software was written.

Read more

Wealthfront: Pencil-and-paper discovery

Andy Rachleff describes Wealthfront’s early use of low-fidelity prototypes to learn faster from customers than finished software allowed.

Read more

Wizard of Oz vs Concierge MVP: When to pick which

A practitioner walkthrough comparing Wizard-of-Oz and Concierge MVPs, using Airbnb’s early air-mattress hosting as the canonical concierge example of founders delivering the service manually before any software exists.

Read more

Virgin Atlantic & OpenTable: From manual to AI concierge

A roundup documenting how hospitality and restaurant brands moved from human concierge tests into automated AI concierge services, with the digital-concierge market projected at $509M in 2025.

Read more

Nucamp: Concierge MVP for solo AI founders

A practitioner guide recommending solo AI founders simulate AI features by hand to measure user interest and willingness to pay before investing in complex systems.

Read more

DoorDash: PaloAltoDelivery.com pilot

Four Stanford students launched PaloAltoDelivery.com in January 2013 to test demand for local restaurant delivery before raising $120K from Y Combinator and incorporating as DoorDash that June.

Read more

Zappos: Photograph, then buy at retail

Founder Nick Swinmurn photographed shoes at local stores, posted them online, and bought and shipped pairs from retail when an order came in — testing demand for online shoe sales without holding inventory.

Read more

Got something to add? Share with the community.