How to Validate an Expansion Before Building: The Minimum Proof You Need

The fastest way to waste a quarter is to ‘validate’ expansion by building most of it.

Thesis: You need proof of pain, proof of usage intent, and proof of willingness-to-pay—before full build.

Proof 1: Pain is real and costly

Get 10 customer quotes that include one of:

• time wasted
• revenue lost
• risk/compliance exposure
• missed opportunities

If it’s just ‘nice to have,’ expansion will stall.

Proof 2: Intent shows up in behavior

Look for:

• repeated exports
• manual workarounds
• customers building internal tools
• users chaining features in a hacky way

Behavior beats opinions.

Proof 3: WTP or ROI signal

You don’t need perfect pricing research. You need a signal:

• customers agree to pay for early access
• they commit resources (implementation)
• sales can attach it to renewals/expansions

The cheapest validation artifacts

• clickable prototype + 5 usability sessions
• concierge workflow (manual behind the scenes)
• pricing page test (fake door)
• partner LOIs for integrations

Kill criteria

Write down what failure looks like. If you won’t write it down, you’re not validating—you’re hoping.

Key takeaways

• Validate pain, intent behavior, and WTP—before building big.
• Use cheap artifacts: prototype, concierge, fake door, LOIs.
• Behavior signals matter more than stakeholder excitement.
• Kill criteria is the discipline that protects your roadmap.