How to validate a customer portal or marketplace before development

01 · The direct answer

How to validate a customer portal or marketplace before development

Validate a portal or marketplace by testing the riskiest assumptions with the lightest credible experience. Prototype the customer journey, manually deliver the service behind it, recruit representative users, and measure whether they complete the valuable behavior—not whether they say the idea sounds useful.

Marketplaces add a second adoption problem because both sides need sufficient value and liquidity. Portals must earn a place in a customer's workflow rather than becoming another destination they are asked to remember.

For two useful external lenses, compare Product discovery from Silicon Valley Product Group with UX prototypes: low fidelity vs. high fidelity from Nielsen Norman Group. A practitioner perspective on addressing value, usability, feasibility, and business viability risks before delivery. How different prototype fidelities support different questions and stages of validation.

The useful decision is the one your team can carry into daily work. Define the outcome, make ownership explicit, and choose the smallest next move that produces trustworthy evidence.

02 · A practical framework

Work through the decision in four parts.

The framework is strengthened by How the discovery phase works and What is story mapping?. A public service standard for understanding users, constraints, existing services, and whether a project should proceed. A practical method for organizing work around the journey a user takes to complete a goal.

Write down the answers and the evidence behind them. A visible decision is easier to challenge, improve, and hand to the people responsible for delivery.

03 · Failure modes

Watch for the shortcuts that move risk downstream.

• 01

  Using positive interview reactions as proof that customers will adopt a new workflow.

• 02

  Building both sides of a marketplace before proving a narrow transaction can happen manually.

• 03

  Validating screens while ignoring the operational work required behind them.

The failure patterns are worth testing against Product discovery, product strategy, and empowered product teams and Build versus buy. A long-form conversation with Marty Cagan about discovery, strategy, and empowered product teams. A strategic framework for comparing third-party products with the total cost and responsibilities of building.

These problems rarely remain technical. They surface later as stalled adoption, operating workarounds, fragile ownership, or investment that cannot be tied to a business result.

04 · Decision checklist

Questions to take into the next working session.

• 01

  What is the single valuable behavior to prove?

• 02

  Which assumption could make the whole product fail?

• 03

  Can the experience be simulated manually?

• 04

  Are participants representative of the real market?

• 05

  What evidence justifies the next investment?

Before committing, use What is a product brief? and Using outcomes to guide product work to challenge the answers. An outcome-oriented artifact for aligning the problem, audience, goals, evidence, and early scope. A useful distinction between shipping outputs and creating measurable business and product outcomes.