Section 06: Validation Experiments & Hypotheses
Defining testable hypotheses and lean experiments to validate PromptVault's critical assumptions before building. Focus on de-risking the core value proposition, pricing, and user workflow.
Executive Summary: Validation Approach
We will run a 6-week validation sprint to test 5 critical hypotheses with 7 targeted experiments. The primary focus is confirming that AI practitioners experience significant pain managing prompts and will pay for a dedicated solution. Total estimated validation budget: $2,500 + 80 person-hours.
CRITICAL HYPOTHESES
5
DESIGNED EXPERIMENTS
7
VALIDATION TIMELINE
6 Weeks
EST. BUDGET
$2.5K
1. Hypothesis Framework
Five structured hypotheses covering problem, solution, pricing, and workflow adoption.
2. Experiment Catalog
Seven targeted experiments designed to test hypotheses with minimal resource expenditure.
| Experiment | Hypothesis | Method | Success Criteria | Cost/Effort |
|---|---|---|---|---|
| #1: Prompt Chaos Interviews | #1 (Problem) | 15-20 semi-structured interviews with AI engineers. Show current prompt "workspace" screenshots. | 70%+ rate prompt management as top-3 productivity pain | $750 (incentives) 25 hours |
| #2: Landing Page Smoke Test | #1, #2 | 3 landing page variants driving to waitlist. Test messaging: "Git for Prompts" vs "Prompt Workspace" vs "AI Prompt Manager". | >7% conversion to waitlist Best variant identified |
$500 (ads) 10 hours |
| #3: Wizard of Oz MVP | #2, #4 | Manual service: Users submit prompts via form β we manage versions in Airtable β return tested outputs. Simulate full workflow. | 80% workflow completion 8/10 satisfaction |
$0 (tools) 40 hours |
| #4: Van Westendorp Pricing | #3 | Survey showing features at different price points. Identify "too cheap", "expensive", "too expensive" thresholds. | Clear price sensitivity curve Optimal price Β±20% of target |
$250 (survey platform) 15 hours |
| #5: Concierge Onboarding | #5 (Teams) | Manual onboarding for 3-5 small teams. Set up their prompt library, conduct training, observe collaboration. | Teams continue using after 2 weeks Identified collaboration friction points |
$0 30 hours |
| #6: Fake Door Feature Test | #4 | Add "Test on Multiple Models" button to prototype that records clicks but shows "coming soon". | >40% of users click the feature Identified most-wanted models |
$0 5 hours |
| #7: Channel CAC Test | Go-to-Market | $100 each on LinkedIn, Twitter, Reddit, Google Ads. Measure signup cost per qualified lead. | CAC < $30 for 2+ channels Best channel identified |
$400 (ads) 10 hours |
3. Experiment Prioritization Matrix
Impact vs. Effort Analysis
Impact: High
Effort: Low
Impact: High
Effort: High
Impact: Medium
Effort: Low
Impact: Medium
Effort: High
Priority Order
- Prompt Chaos Interviews
Critical path - must validate problem first - Landing Page Test
Quick signal on messaging & demand - Wizard of Oz MVP
Validate solution workflow - Pricing Survey
Optimize revenue before build - Channel CAC Test
Validate acquisition feasibility
4. 6-Week Validation Sprint Schedule
Problem
Problem
Solution
Solution
Business
Synthesis
(15-20)
($500)
($250)
Go/No-Go Decision
5. Minimum Success Criteria (Go/No-Go)
1 Problem Validation
2 Solution Validation
3 Business Validation
Go/No-Go Decision Matrix
All 3 critical criteria met
Proceed to MVP build
2/3 criteria met
Pivot & re-test specific area
β€1 criteria met
Stop or pivot significantly
6. Pivot Triggers & Contingency Plans
Trigger: Problem Not Severe Enough
Signal: <50% of practitioners rate prompt management as painful
- Interview users about actual top AI workflow pains
- Pivot to adjacent problem: "LLM API cost optimization" or "AI output quality monitoring"
- Target enterprise teams where governance is mandatory
Trigger: Price Sensitivity Too High
Signal: Optimal price point < $15/month, CAC > LTV
- Shift to freemium with paid team features
- Add LLM API passthrough revenue (margin on usage)
- Target larger enterprises with compliance budgets
- Consider open-source core with paid hosting
Trigger: Workflow Too Complex
Signal: <60% workflow completion, high support requests
- Simplify to single killer feature (e.g., just version control)
- Build browser extension that works within ChatGPT/Claude
- Focus on API-first for developers, not UI for everyone
- Partner with existing tools (Notion, VS Code) as plugin
Key Recommendation
Execute the 6-week validation sprint before writing any production code. The Wizard of Oz MVP (Experiment #3) is particularly crucialβit will reveal whether practitioners actually want a dedicated prompt management workflow or if they prefer to continue with their current ad-hoc solutions. Total investment of $2,500 and 80-100 hours will prevent wasting $350K+ on building the wrong product.