The 3‑Week Concierge MVP Playbook for Validating Network Effects Without Building a Marketplace

A concierge MVP — delivering the product manually and visibly — surfaces the exact mechanisms that create network value. When your hypothesis depends on users deriving more value as other users join (two‑sided interactions, referrals, or matchmaking), manual delivery reveals which parts of the flow actually produce the multiplier and which are noise. Pretotyping and concierge approaches prioritize learning over early engineering and prevent building the wrong marketplace at scale.

This approach is especially effective when the core value is complex, involves human judgment (curation, trust, fit), or when you don’t yet know which side will drive growth. It reduces cost and time-to-learning by turning product features into conversation points and operational steps you can observe and measure in real time.

Objective (Days 1–7): collect 30–75 qualified leads, but only onboard 8–15 that meet gating criteria. Replace broad sign‑ups with a short, structured intake that screens for fit and willingness to pay. Use a landing page + intake form (fake‑door copy is fine) and route applicants into a 15–20 minute discovery call. The aim is not vanity signups — it’s high‑quality candidates who are likely to engage in repeated matched interactions.

Scripts and intake fields should prioritize outcomes and commitment signals. Ask about the exact problem, current workaround, measurable outcome they want, and budget. Offer a single paid path (preorder or deposit) for first access — charging upfront filters serious users and validates monetization early.

Objective (Days 8–14): run 2–3 matching cycles with the gated cohort and measure whether matches produce net lift in the target outcome. As the operator, curate matches, introduce participants via scheduled calls or message threads, and track specific behavioral metrics: response rate, conversion to the target outcome, repeat engagement, and invite/referral attempts.

Collect structured qualitative feedback at three touchpoints: immediately after the match, one week later, and after a second interaction. Document edge cases and special handling required — these notes are the exact product requirements for later automation. Track time-per‑match to estimate engineering and operational costs for scaling.

Objective (Days 15–21): convert engaged users into paid commitments and apply objective thresholds to decide whether to build. Use preorder pricing, limited slots, and clear deliverables (e.g., “3 curated matches in 30 days”). The pricing test must be real money — even a small commitment changes behavior and reveals true willingness to pay.

Set go/no‑go thresholds before the experiment. For two‑sided or matchmaking networks, example thresholds: 1) match activation rate ≥ 40% (matched users complete the target action), 2) repeat engagement ≥ 25% after first match, 3) willingness‑to‑pay conversion ≥ 20% of qualified cohort, and 4) time-per‑match low enough to justify an initial automation investment. If you miss thresholds, iterate on onboarding, matching criteria, or unit economics rather than building full marketplace features.

Practical templates save time and make the experiment repeatable. Use a 6‑question intake form focused on outcomes; a 10‑minute discovery script to confirm fit; an intro email template that frames the match and next steps; and a short post‑match survey with 5 metricized questions (activation, satisfaction, improvement, likelihood to pay, referral intent). Keep each template lean so it’s easy to A/B adjust between cohorts.

Operational hygiene: centralize notes in a simple spreadsheet or Notion board with status flags (applied, qualified, matched, paid, churned) and timestamps. Track time spent on each match and categorize manual steps (data collection, curation, communication) — these categories map directly to automation priorities.