saas-go-to-market/SKILL.md
Use when planning a go-to-market strategy for a SaaS product, defining positioning and messaging, choosing channels, planning a launch, or building a 90-day marketing plan. Produces a structured GTM document with positioning, channels, launch phases, and metrics.
npx skillsauth add paulund/skills saas-go-to-marketInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
references/gtm-checklist.md for templates and definitions.Positioning defines who the product is for, what it does, and why it is better than the alternative. Everything else flows from it.
Positioning statement format:
For [target audience] who [have this problem], [product name] is a [category] that [provides this benefit]. Unlike [current alternative], [product name] [key differentiator].
Questions to answer before writing any marketing:
Every marketing channel is one of three types. A good GTM strategy uses all three, weighted by stage.
Best for: Long-term compounding growth. Slow to start, hard to lose.
Best for: Distribution and reach. Fast to start, algorithmic and subject to platform changes.
Best for: Credibility and reaching new audiences. Requires relationship-building.
Early-stage recommendation: Start with 1-2 rented channels (where your audience already is), build 1 owned channel (usually email), and pursue 1-2 borrowed channel opportunities per quarter.
Most successful SaaS launches are not a single event — they are a series of increasingly public launches.
| Phase | Who it targets | Goal | | --- | --- | --- | | 1. Internal | Team and advisors | Find obvious gaps before anyone sees it | | 2. Alpha | Trusted friends, existing network | Get real usage feedback, not just opinions | | 3. Beta | Targeted waitlist or community invite | Validate core value proposition with strangers | | 4. Early access | Broader waitlist, specific communities | Generate early social proof and case studies | | 5. Full launch | Public — all channels | Maximum distribution with social proof ready |
Do not skip to phase 5. Each phase builds the evidence and confidence needed for the next.
| Phase | Primary metric | Secondary metrics | | --- | --- | --- | | Pre-launch | Waitlist signups | Email open rate, community engagement | | Launch | Signups (day 1 and week 1) | Traffic, conversion rate from landing page | | First 30 days | Activation rate (users reaching core value milestone) | Trial-to-paid conversion | | First 60 days | MRR growth | Churn rate, NPS | | First 90 days | CAC by channel | LTV, payback period |
| Topic | Reference | Load When |
| ----- | --------- | --------- |
| GTM Checklist | references/gtm-checklist.md | Always |
development
Use when the user wants to run the project's lint + types + build sequence as a gate before pushing, opening a PR, or merging. Invoked by chained dev skills between phases. Trigger phrases - "/quality-gate", "run the quality gate", "check it builds".
tools
Use when the user wants to verify a PR's feature works at runtime by booting the dev server, exercising the affected UI via Chrome DevTools MCP, and posting a screenshot summary back to the PR. Idempotent — skips if `verified` or `verify-failed` is already on the PR. Trigger phrases - "/pr-verify", "verify this PR", "runtime check the pr".
testing
Use when the user wants a security-focused review pass on a PR with findings actioned as commits on the same branch. Trigger phrases - "/pr-security-review", "security review and fix".
testing
Use when the user wants to open a pull request for an already-pushed branch that implements a specific issue. Idempotent — returns the existing PR if one is already open for the branch. Trigger phrases - "/pr-open", "open the pr", "create pr for this branch".