From bopen-tools
Validates SaaS launch readiness across 10 critical areas with a repeatable PASS/FAIL checklist and actionable next steps.
How this skill is triggered — by the user, by Claude, or both
Slash command
/bopen-tools:saas-launch-auditThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
A comprehensive, repeatable audit workflow for SaaS products approaching launch. Provides clear PASS/FAIL states with single actionable next steps.
A comprehensive, repeatable audit workflow for SaaS products approaching launch. Provides clear PASS/FAIL states with single actionable next steps.
Validate launch readiness across 10 critical areas: validation, pricing, payments, AI economics, discovery, competitors, social presence, legal, trust infrastructure, and launch day operations.
Before running the checklist, gather project context:
Questions to ask:
Platform recommendations by product type:
| Item | Verification Method |
|---|---|
| 50+ discovery calls completed | Ask user |
| Pre-payment secured from 3+ customers | Ask user |
| Problem validated (not just interest) | Ask user for evidence |
| Manual service delivery tested | Ask user |
| Item | Verification Method |
|---|---|
| Pricing model selected (outcome/usage/hybrid) | Ask user, verify NOT per-seat only |
| Value metric identified | Ask user what outcome they charge for |
| 3-4 tiers with clear differentiation | Browser: check pricing page |
| Annual contract incentives configured | Browser: verify discount shown |
| Pricing page live and scannable | Browser: visual check |
| Item | Verification Method |
|---|---|
| Stripe account activated (live keys) | Ask user to confirm |
| Test transactions successful | Ask user |
| Webhook endpoints configured | Ask about endpoint URL |
| Billing portal accessible | Browser: test billing portal link |
| Tax/KYC requirements met | Ask user |
| Item | Verification Method |
|---|---|
| Inference costs calculated per action | Ask user for cost breakdown |
| AI costs < 30% of revenue | Calculate: inference cost / revenue per user |
| Gross margin > 50% (AI-adjusted) | Verify: traditional SaaS 80-90%, AI-first 50-65% |
| Margin protection strategy exists | Ask about usage caps, tiering |
| Cost monitoring/alerts configured | Ask user |
| Item | Verification Method |
|---|---|
| AI visibility audit completed | WebSearch: query ChatGPT/Perplexity for brand |
| Structured data/FAQ schema | Browser: check page source |
| Content uses authoritative language | Browser: check for excessive hedging |
| SSR/pre-rendering for LLM crawlers | Ask about rendering strategy |
| Server response time < 200ms | Run scripts/tech-audit.sh |
| Core Web Vitals passing | Check PageSpeed Insights |
2026 Fact: AI agents account for ~33% of organic search activity. Only 12% of companies appear across ChatGPT, Perplexity, and Claude.
| Item | Verification Method |
|---|---|
| 3+ direct competitors identified | Ask user to list |
| Competitor pricing documented | WebSearch: research each competitor |
| Differentiation statement written | Ask user for positioning |
| AI visibility comparison done | WebSearch: query "[category] tools" |
| Citation sentiment analyzed | Review AI responses for tone |
| Item | Verification Method |
|---|---|
| Primary platform profiles created | Browser: check each platform |
| LinkedIn founder profile optimized | Browser: review profile |
| X/Twitter presence established | Browser: check account |
| Product Hunt profile ready | Browser: check PH profile |
| 400+ PH supporters lined up | Ask user about DM outreach |
| Launch email sequence drafted | Ask user |
| Content calendar for 30 days | Ask user |
| "Magic Triangle" ready | Ask about founder content + outreach + retargeting |
| Item | Verification Method |
|---|---|
| Privacy Policy live | Browser: check /privacy or footer link |
| Terms of Service live | Browser: check /terms or footer link |
| Cookie consent banner | Browser: verify banner appears |
| DPA template ready (if B2B) | Ask user |
| Item | Verification Method |
|---|---|
| Auth system production-ready | Ask user about auth provider |
| Audit logging enabled | Ask user |
| Error tracking configured | Ask about Sentry or similar |
| Uptime monitoring active | Ask user |
| Security headers configured | Run scripts/tech-audit.sh |
| Item | Verification Method |
|---|---|
| Support channels operational | Browser: check support links |
| FAQ/Knowledge base published | Browser: check /help or /docs |
| Analytics tracking verified | Ask about GA4, PostHog setup |
| Team roles assigned | Ask user |
| Rollback plan documented | Ask user |
Report each item as:
[PASS] Item description
or
[FAIL] Item description
→ Next step: Single actionable instruction
Use mcp__claude-in-chrome__* tools to:
Use WebSearch to:
Use provided scripts:
scripts/tech-audit.sh - Core Web Vitals, SSL, security headersscripts/competitor-visibility.sh - AI visibility comparisonFor detailed guidance, see the references directory:
references/pricing-2026.md - Outcome/usage-based pricing strategies, 2026 trends, tier design principlesreferences/payment-verification.md - Stripe go-live checklistreferences/geo-visibility.md - GEO/AI discovery optimization, technical requirements, content strategiesreferences/launch-tactics.md - Product Hunt and social strategies, "Magic Triangle" approachreferences/trust-infrastructure.md - Trust-as-a-Product requirementsreferences/metrics-2026.md - AI-first SaaS metrics (gross margins, cost optimization)references/platform-guides.md - Platform-specific launch guidesThe audit is complete when:
Re-run the audit after implementing fixes until all critical items pass.
npx claudepluginhub b-open-io/claude-plugins --plugin bopen-toolsGuides launching micro-SaaS: idea validation via landing pages/pre-sales, 2-week MVP with Next.js/Supabase/Stripe/Vercel stack, pricing, launch playbooks, early growth.
Pre-launch checklist for shipping websites: analytics, legal, security headers, SEO/GEO, accessibility, performance audits, and weekly SEO agent setup.
Provides a go/no-go pre-launch checklist checking showstoppers (core flow, payments, auth, HTTPS, secrets), UX (mobile, errors, speed), operations (Sentry, analytics, monitoring, backups), and polish before live deployment.