Browse skills

Designs a SaaS pricing model - the value metric, three-tier packaging with feature gates, list prices, annual discount, and a built-in expansion path targeting net revenue retention - delivered as a pricing page spec. Use when a founder asks "how should we price our SaaS", "per seat or usage-based", "what features go in each tier", or is building or overhauling a pricing page. Do NOT use for pricing strategy outside SaaS packaging - use pricing-strategy instead; for the upsell motion after pricing exists, use expansion-revenue.

Use when turning a positioning statement into actual copy - building the value proposition, message pillars, proof points, and per-channel messaging that keep the website, ads, and sales deck all saying the same thing. Triggers on "write our value proposition", "message pillars", "messaging framework", "messaging house", "key messages", "proof points", "our website and sales say different things", "per-channel messaging", "on-message copy", "get everyone on the same message". Takes the positioning-statement as input and feeds landing-page-copy. Do NOT use when you have not yet fixed positioning (audience, category, differentiator) - use positioning-statement first. Do NOT use when you need the actual hero/landing page words - use landing-page-copy with this framework as the brief. Do NOT use to schedule or sequence the launch phases (pre-launch, launch, post-launch) - use launch-plan-sequencer. Do NOT use to plan the hour-by-hour go-live - use launch-day-runbook. Do NOT use to build the sales deck, one-pager, or talk track - use sales-enablement-kit (it consumes this house). Do NOT use to design the in-product / free-trial activation flow - use plg-motion-designer (it pulls its language from this house).

Build a sequenced go-to-market plan - beachhead ICP, positioning, one or two channels, and dated milestones - instead of a scattershot launch. Use when someone asks "how do I take this to market", "what's my GTM strategy", "which channel should I start with", "who should I sell to first", or is planning a new product or a new market entry. Do NOT use for the dated launch-week timeline and asset checklist - use launch-plan-sequencer instead; for Product Hunt copy and day-of tactics use product-hunt-launch; for deep persona research use icp-persona-builder.

Audit technical SEO health - crawlability, indexing, Core Web Vitals, robots.txt, sitemaps, canonicals, redirects, HTTPS, and structured data - with scored results and a prioritized fix roadmap.

Stands up product analytics from decision questions backward - a north-star metric with an input-metric tree, an object-action event taxonomy with a governed tracking plan, and the priority analyses to build first: activation funnels, cohort retention curves, and feature adoption correlated with retention. Use when someone asks "what events should we track", "set up our analytics taxonomy", "where do users drop off before first value", or "what's our activation moment". Do NOT use for growth-accounting decompositions of MAU changes - use growth-accounting instead - or for deep funnel diagnosis on existing data - use funnel-analysis instead.

Build a competitor-relative coverage map - missing topics, keyword gaps, and format gaps - bucketed into Quick Wins, Strategic Builds, and Long-term, with a dated content-calendar entry per quick win.

Use when planning a product launch end-to-end and you need the full dated timeline. Triggers on "plan my launch", "launch plan", "how do I sequence a launch", "pre-launch checklist", "what happens before launch day", "launch timeline", "GTM launch plan", "coordinate a launch across channels", "who owns what for launch". Builds the pre-launch → launch-day → post-launch arc with a channel & asset checklist, owners, and dates. Do NOT use when you need the minute-by-minute run-of-show for the day itself - use launch-day-runbook instead. Do NOT use to write the core message - use positioning-statement for the one-line claim and messaging-hierarchy for the laddered copy. Do NOT use to design the self-serve adoption motion - use plg-motion-designer. Do NOT use to build the sales deck, battlecard, or demo script - use sales-enablement-kit.

Turn product ideas into structured Product Requirements Documents for teams and stakeholders.

Set or revise pricing for any product by triangulating value, competition, and cost floor into a recommended structure, price points, and a test plan. Use when someone asks "what should I charge", "how do I price my product", "are we priced too low", "should we go usage-based or flat", or is preparing a repricing or a new-product launch. Do NOT use for designing SaaS tier ladders, value metrics, and expansion packaging in detail - use saas-pricing instead; for gym front-end offers and guarantees use gym-pricing-and-guarantees; for checking whether the resulting price produces healthy CAC payback use unit-economics.

Analyze a backlink profile - referring domains, anchor-text mix, toxic-link share, profile health, and competitor link gaps - then recommend concrete link-building or disavow actions.

Use when designing a product-led, self-serve activation motion for signups. Triggers on "design our PLG motion", "self-serve onboarding", "what is our aha moment", "define activation", "activation rate", "time-to-value", "onboarding funnel", "in-product nudges", "set activation milestones", "signup to value", "free-to-paid", "PQL". Defines the aha moment, the activation milestones to it, and the in-product nudges and metric gates between each step. Do NOT use for outbound/sales-led launch sequencing - use launch-plan-sequencer instead; for arming a human sales team with collateral, use sales-enablement-kit instead; for the page that captures the signup, use landing-page-copy; for pricing tiers and the paywall, use saas-pricing and pricing-strategy.

Build the batch visual-asset production system for an automated social operation — a locked format set with exact dimensions, brand constants as declared inputs, a one-deliberate-risk composition rule, programmatic SVG-to-PNG rendering, and a staged-media-first rule that checks the scheduler before generating anything new. Use when someone asks "set up our social image pipeline", "produce this week's post images", "batch-generate assets for the queue", or "systematize our social visuals". Do NOT use for one-off OG images or quote cards — use social-image-designer; for captions and copy, use caption/thread skills; for defining the brand palette and type itself, use brand-guidelines or color/typography system skills.