Works with the AI tools you already use
Claude Code
Cursor
Codex CLI
GitHub Copilot
Gemini CLI+20 moreClaude CodeCursorCodex CLIGitHub CopilotGemini CLI
OpenClaw
Manus
Grok+17 agentsPre-Launch Evidence Package for B2B SaaS
Organize customer evidence, validate assumptions, and get a launch readiness score before going public.
$11.11
Pre-Launch Evidence Package for B2B SaaS
Example session with this skill installed
Run the pre-launch evidence package for my B2B SaaS product.
Product: ContractFlow - AI-powered contract review for in-house legal teams
Target Vertical: In-house counsel at mid-market tech companies (50-500 employees)
Current Status
- Interviewed 12 in-house counsel and legal ops managers
- Landing page built; tested with 240 visitors; 6% conversion
- Pricing: Tested $199/month (75% positive) and $299/month (50% positive)
- 2 customers completed full sales cycle (4 weeks each)
- 0 paying customers yet
- Competitive landscape: Ironclad (enterprise); mostly manual process
What's Validated
- Problem: In-house counsel spend 15-20 hours/month on contract review
- Business impact: Legal delays, SLA misses, compliance risks
- Current solution: Manual (Word + email)
- Customer budget exists for this problem
What's NOT Validated
- Actual willingness to pay (only hypothetical "yes")
- Sales channel performance (planning outbound sales; untested)
- Product-market fit (idea validated; actual product untested)
- Landing page messaging (headline untested with customers)
Give me
- Evidence inventory (what's verified vs. speculative)
- Consistency checks across positioning, pricing, channel, and ICP
- Launch readiness score (percentage validated)
- Risk register (highest-risk assumptions)
- Go/no-go recommendation (public launch, beta, or keep iterating?)
- Prioritized 30-day validation roadmap
- Read your context and instructions
- Compiled the pre-launch evidence package
- Generated the document
LAUNCH READINESS REPORT
Product: ContractFlow
Generated: [date]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
OVERALL LAUNCH READINESS: 52% VALIDATED
✅ Evidence Confidence Breakdown:
- VERIFIED claims: 62% (backed by research or testing)
- INFERRED claims: 28% (reasonable but untested)
- UNVERIFIED claims: 10% (assumptions/guesses)
🎯 LAUNCH RECOMMENDATION: 🟡 READY FOR BETA
Launch to 5-15 early adopters (closed beta).
NOT ready for public launch yet.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
EVIDENCE INVENTORY
✅ VERIFIED
-
Problem: "In-house counsel spend 15-20 hours/month on contract review"
Evidence: 11 of 12 customers confirmed this range; 2 shared time-tracking data
Confidence: HIGH -
Market: "In-house counsel at 50-500 person tech companies exist"
Evidence: Job postings, LinkedIn search, customer interviews
Confidence: HIGH -
Current Solution: "Manual review process is status quo"
Evidence: 11 of 12 customers use Word + email workflow
Confidence: HIGH
🟡 INFERRED
-
Price Acceptance: "Customers will pay $199/month"
Evidence: 6 of 8 customers tested said "yes" to $199/month
Confidence: MEDIUM (only hypothetical; no paid customers yet) -
Sales Cycle: "Takes 4 weeks to close"
Evidence: 2 customers took 4 weeks; small sample size
Confidence: MEDIUM (only 2 data points)
❌ UNVERIFIED
-
Actual Customer Acquisition Cost (CAC)
Evidence: None; assuming $200-300 per customer based on sales time
Confidence: LOW (not tested) -
Product-Market Fit with actual product
Evidence: None; only tested workflow ideas with customers
Confidence: LOW (product not tested) -
Sales channel performance (outbound email + warm intros)
Evidence: None; assuming based on B2B SaaS best practices
Confidence: LOW (not tested)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CONSISTENCY CHECKS
✅ ICP ↔ PRICING ALIGNMENT
Your ICP: In-house counsel at mid-market tech companies (50-500 people)
Your Price: $199/month
Customer Budget: Tested at $199; 75% positive signal
Status: ALIGNED ✅
🟡 POSITIONING ↔ CUSTOMER EVIDENCE
Your positioning: "Save 15 hours/month with AI-powered review"
Customer focus: Accuracy/risk mitigation, NOT time savings
Customer quotes: "I need something that catches clauses we miss"
Status: NEEDS ADJUSTMENT 🟡
Action: Reposition around risk/accuracy; time savings is secondary benefit
🚨 CHANNEL ↔ CUSTOMER DISCOVERY
Your planned channel: Outbound sales + warm introductions
How customers found current vendor: Peer recommendations (70%), consultants (20%), search (10%)
Status: MISALIGNED 🚨
Action: Build referral program; test outbound in parallel; consider consultant partnerships
✅ FEATURES ↔ PROBLEMS
Core problems: (1) Slow review, (2) Missing clauses, (3) Manual redline process
Your features: (1) AI risk detection, (2) Auto-flag missing terms, (3) Redline suggestions
Status: ALIGNED ✅
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
RISK REGISTER
🔴 HIGH RISK
-
Pricing Not Validated at Purchase
Risk: You tested hypothetical willingness; no paying customers
Impact: High (pricing is revenue model)
Mitigation: Land 3-5 beta customers at $199/month; monitor churn -
Sales Channel Untested
Risk: Outbound sales has zero track record; CAC unknown
Impact: High (if CAC > $600/year, business doesn't work)
Mitigation: Run pilot with 20 cold emails + 10 warm intros; measure close rate
🟡 MEDIUM RISK
3. Positioning Misalignment
Risk: Emphasizing time savings; customers care about risk mitigation
Impact: Medium (converts fewer; messaging can be fixed)
Mitigation: A/B test landing page headlines; lead with risk mitigation
- Small Sales Sample
Risk: Only 2 customers through full cycle; sales cycle could be longer
Impact: Medium (affects cash flow projections)
Mitigation: Track close time carefully; adjust forecasts as sample grows
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
GO/NO-GO GATES
✅ Will customers actually pay?
Evidence: 75% positive at $199/month price test
Status: LIKELY (but not confirmed; no paying customers)
✅ Problem is frequent enough?
Evidence: Weekly task (15-20 hours/month)
Status: YES (sufficient for $200/month subscription)
✅ Your solution is 10x better?
Evidence: Customers said automation would be valuable
Status: LIKELY (but product not tested)
❌ Customers will actually convert?
Evidence: None yet; no paying customers
Status: UNVERIFIED (highest risk)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
LAUNCH RECOMMENDATION
→ 🟡 READY FOR BETA LAUNCH (not public)
Why
✅ Problem validated (92% customer consensus)
✅ Budget confirmed ($199-299/month is acceptable)
✅ Market confirmed (in-house counsel at mid-market tech exists)
🟡 Pricing tested but not purchased
🟡 Sales channel untested
❌ Product not tested by real customers
❌ No paying customers
Beta Launch Plan
- Contact 5-10 warm leads (customers who expressed interest)
- Offer free/discounted access in exchange for feedback
- Track: feature usage, time to value, product-market fit signals
- Monitor churn closely (target: <20% in first 30 days)
- Gather NPS and qualitative feedback
Public Launch Criteria (after beta):
- 3+ paying customers at $199/month
- Product feedback positive (NPS > 30)
- CAC validated (< $500 per customer)
- Churn rate < 10%
- Sales cycle confirmed (±1 week vs. 4-week assumption)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
NEXT 30 DAYS PRIORITY:
WEEK 1: Positioning
- A/B test landing page headlines (risk mitigation vs. time savings)
- Track which version converts better
- Iterate based on results
WEEK 2: Sales Channel
- Send 20 cold outreach emails to target customers
- Personal outreach to 10 warm leads
- Track: # contacted, # replied, # agreed to demo
WEEK 3: Product Testing
- Get 3 beta customers access to product
- Establish weekly feedback calls
- Document feature requests and pain points
WEEK 4: Pricing Validation
- Have pricing conversation with all beta customers
- Confirm $199/month or negotiate
- Document any price resistance
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
KEY METRICS TO TRACK
-
of beta customers who sign up
- Trial-to-paid conversion rate (target: 20%+)
- Actual sales cycle (vs. 4-week assumption)
- Customer acquisition cost by channel
- Churn rate (target: <10% in month 2)
- NPS (target: 40+)
- Feature usage (what's actually being used?)
RED FLAGS (stop and pivot if you see these):
- <10% trial-to-paid conversion (product-market fit issue)
- Churn >15% in month 1 (retention issue)
- NPS <20 (customer satisfaction problem)
- CAC >$1000 (profitability issue)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CONFIDENCE SUMMARY
You have STRONG problem validation and MEDIUM price validation.
You have ZERO product and channel proof.
This is normal for a pre-launch SaaS.
Launch to beta; use first 30 days to validate product and sales channel.
If after 30 days you have 3+ paying customers + positive feedback + validated CAC,
move to public launch.
Good luck. 🚀
pre-launch-evidence-package-for-b2b-saas.pdf
PDF · document
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
What you get
About this skill
This skill helps B2B SaaS founders determine if they're ready to launch by organizing customer research, validating assumptions, and checking for contradictions across their strategy.
WHAT IT DOES:
- Evidence Inventory: Categorize your claims as VERIFIED (backed by research), INFERRED (reasonable conclusion), or UNVERIFIED (guess)
- Gap Analysis: Identify what you haven't validated yet
- Consistency Checks: Flag contradictions (e.g., pricing $199/month but target customers say max budget is $50/month)
- Launch Readiness Score: Get a clear go/no-go recommendation (go public, launch to beta, or keep iterating)
- Risk Register: Identify highest-risk assumptions and mitigation plans
- 30-Day Validation Roadmap: Prioritized checklist of what to research before launch
WHY USE THIS: You've talked to customers. You've built a prototype. You're not sure if you're ready to launch. Instead of guessing, this skill organizes what you know, identifies gaps, and tells you whether to go public or test with beta customers first.
WHO IT'S FOR:
- Founders with customer interviews but no clear launch signal
- Teams disagreeing on positioning and pricing (need data to decide)
- Founders raising money (need to back up market/customer claims)
- Anyone deciding: public launch or beta launch?
EXAMPLE: Input: "I've talked to 12 accounting firms. They said they'd pay $199/month. I haven't tested messaging or sales channel yet." Output:
- Evidence Score: 45% validated
- Recommendation: Ready for beta launch (10-20 customers), not for public
- Gaps: Pricing (only hypothetical), messaging (untested), channel (untested)
- Next Steps: Land 3 beta customers, test sales channel, validate messaging
CORE PRINCIPLE: Do not launch without evidence. Every major claim should be backed by customer research, competitive analysis, or testing.
NOT INCLUDED:
- Full business plan generation (too broad)
- Financial modeling
- Product building
- Guaranteed launch success (skill reduces risk, doesn't eliminate it)
INCLUDES:
- 4 reusable templates (evidence inventory, interview script, consistency checker, launch checklist)
- Realistic example output
- Structured analysis framework
- Customer-facing, actionable outputs
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
30-day refund
Not a fit? Get your money back
Trust & safety
Security scanned
Verified clean 28 days ago
- Passed all security checks, Safe to install