Solutions Page Generator
Draft or audit B2B solutions pages—industry, size, and outcome-led copy and structure—for solo builders who sell on measurable business value, not feature lists.
Overview
Solutions-page-generator is an agent skill most often used in Launch (also Validate, Grow) that produces outcome- and segment-led B2B solutions page structure, copy direction, and audits.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill solutions-page-generatorWhat is this skill?
- Industry-first B2B norm (Salesforce/HubSpot-style) vs pure feature or use-case pages
- Section map: outcome headline, segment proof, outcomes, social proof, and primary CTA (demo, signup, contact)
- Initial assessment: outcomes, segments (industry, size, team), hub vs single page, conversion goal
- Reads project-context for product, outcomes, and proof when `.claude` or `.cursor` context exists
- Routes sitewide IA to website-structure skill
- Solutions page structure table with 5+ core sections (headline through CTA)
- Industry-first positioning aligned with major B2B site patterns
Adoption & trust: 725 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your site explains features but buyers searching by industry or outcome cannot find a page that proves business value for their segment.
Who is it for?
Indie B2B SaaS founders shipping or refreshing /solutions hubs by industry, SMB vs enterprise, or business outcome.
Skip if: Pure D2C catalog sites, one-page portfolios with no segments, or full sitemap planning without page-level solutions focus.
When should I use this skill?
User wants to create, optimize, or audit solutions pages or mentions solutions, by industry, SMB, enterprise, business outcomes, or how we solve X.
What do I get? / Deliverables
You get a solutions page blueprint—sections, segment angles, proof placement, and CTAs—ready to implement or hand to website-structure for broader IA.
- Solutions page section outline and outcome-led messaging
- Segment-specific page recommendations (hub vs dedicated URLs)
- Audit notes when optimizing existing solutions content
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Solutions pages are canonical on Launch/seo as indexable conversion assets; they also support Validate (positioning) and Grow (segment expansion). SEO subphase fits outcome-led URLs, hub-and-spoke solutions architecture, and SERP-facing headlines tied to industry queries.
Where it fits
Draft a single industry solutions outline to test positioning before full site build.
Ship hub plus three industry URLs with outcome headlines and proof blocks for organic capture.
Add a company-size solutions page when moving upmarket from SMB.
How it compares
Page-type copy and structure skill, not sitewide website-structure planning.
Common Questions / FAQ
Who is solutions-page-generator for?
Solo B2B builders and small teams who need industry- or outcome-led solutions pages that convert demos, signups, or contact requests.
When should I use solutions-page-generator?
Use in Launch/SEO when building solutions URLs; in Validate when scoping segment messaging; in Grow when adding industries or company-size pages; when user says solutions page, by industry, SMB, enterprise, or business outcomes.
Is solutions-page-generator safe to install?
Check the Security Audits panel on this Prism page and review the skill files before the agent reads project-context or writes to your repo.
Workflow Chain
Then invoke: website structure
SKILL.md
READMESKILL.md - Solutions Page Generator
# Pages: Solutions Guides solutions pages focused on business outcomes. **Industry-first** is the B2B norm (Salesforce, HubSpot). Answer "what outcome do I get for my industry/team/size?" rather than "what does it do?" Distinct from features (capabilities) and use cases (scenarios); solutions emphasize measurable value by segment. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, outcomes, and proof points. Identify: 1. **Outcomes**: Revenue growth, cost savings, efficiency, compliance 2. **Segments**: Industry (primary), company size, team 3. **Format**: Hub + per-solution pages, or single solutions page 4. **Primary goal**: Demo, sign up, contact ## Solutions Page Structure | Section | Purpose | |---------|---------| | **Headline** | Outcome-led; "Achieve X with [Product]" | | **Challenge** | Business problem, context | | **Solution** | How product delivers the outcome | | **Proof** | Metrics, case study, ROI | | **Features used** | Link to relevant features | | **CTA** | Book demo, start trial, see case study | | **Related** | Other solutions, use cases (as sub-applications) | ## Best Practices ### Outcome-First - **Lead with result**: "Increase conversion by 30%" not "We have A/B testing" - **Measurable**: Time saved, revenue gained, cost reduced - **Specific**: Industry workflows, not generic claims - **Differentiate**: Each industry/segment gets unique content ### Organization (Primary → Secondary) | Dimension | Priority | Examples | |-----------|----------|----------| | **By Industry** | Primary | Healthcare, Retail, Manufacturing, Financial Services | | **By Company Size** | Secondary | SMB, Mid-Market, Enterprise | | **By Team** | Secondary | Marketing, Sales, Service, Operations | | **By Outcome** | Alternative | Scale support, Reduce churn, Accelerate sales | ### Common Industries (Reference) Automotive, Communications, Consumer Goods, Consumer Services, Construction & Real Estate, Education, Energy & Utilities, Financial Services, Government, Healthcare & Life Sciences, Manufacturing, Media, Nonprofit, Professional Services, Retail, Technology, Travel & Hospitality. ### Company Size Segments | Size | Typical | Focus | |------|---------|-------| | Startup | <50 | Speed, agility | | SMB | 50–500 | Ease of use, affordability | | Mid-Market | 500–5000 | Scalability | | Enterprise | 5000+ | Customization, compliance, integration | ### vs. Use Cases vs. Features | Page | Answers | Primary Organization | |------|---------|----------------------| | **Features** | What does it do? | Capabilities | | **Use cases** | When would I use it? | By scenario, persona, business goal | | **Solutions** | What outcome do I get? | By industry, company size, team | **Hierarchy**: Solutions (industry/segment) can contain Use Cases as sub-applications. Example: /solutions/healthcare → use cases: patient scheduling, telemedicine. ### When to Use Solutions vs Use Cases | Need | Use | |------|-----| | By industry (Healthcare, Retail) | Solutions | | By company size (SMB, Enterprise) | Solutions | | By team (Marketing, Sales) | Solutions | | By outcome (Scale support) | Solutions | | By scenario (Event marketing) | Use Cases | | By persona (For Realtors, For CMOs) | Use Cases | | By business goal (Acquisitio