Populate Template with Validated Discovery Inputs
Fill every section of the pilot problem definition template using empirical customer evidence, direct quotes, and verified operational data. Replace placeholders and subjective estimates with hard facts gathered during customer discovery and initial validation interviews.
Completing this action transforms a structural template into a rigorous, evidence-backed strategic asset. It ensures that every pilot commitment is anchored in demonstrated customer behaviour rather than optimistic founder speculation.
The founder must produce a fully populated Pilot Problem Definition document backed by referenced customer quotes, historical baseline data, and verified metrics. Every claim regarding customer readiness, timeline feasibility, and conversion terms must link directly to documented proof.
Five questions an expert would ask when reviewing your output
Use these to challenge assumptions, pressure-test your logic, and check the quality of this action's output in the context of the parent task and wider venture development.
- 1
What direct empirical evidence supports your target timeline for client onboarding and pilot execution?
- 2
Where is the documentation proving that the customer's technical team has agreed to your integration scope?
- 3
How have you validated that the proposed metrics reflect the buyer's internal definition of success rather than your own?
- 4
What actual historical baseline data from the client proves that the targeted problem is urgent enough to justify this pilot?
- 5
Why do you believe the stated decision-maker has the budget authority to execute the conversion path outlined?