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:
- Outcomes: Revenue growth, cost savings, efficiency, compliance
- Segments: Industry (primary), company size, team
- Format: Hub + per-solution pages, or single solutions page
- 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 (Acquisition, Retention) |
Use Cases |
| Industry-specific application |
Use Cases (as Solutions sub-page) |
Output Format
- Solutions list (industries/segments)
- Per-page structure (sections, messaging)
- Headline options
- Proof integration (case studies, metrics)
- Internal linking (features, use cases, pricing)
- SEO metadata
Related Skills
- use-cases-page-generator: Use cases as sub-applications under solutions; link between
- features-page-generator: Solutions reference features; link to feature pages
- customer-stories-page-generator: Case studies as proof on solutions pages
- pricing-page-generator: Solutions pages link to pricing
- landing-page-generator: Solutions pages apply LP principles
1---2name: solutions-page-generator3description: When the user wants to create, optimize, or audit solutions pages. Also use when the user mentions "solutions," "solutions page," "by industry," "industry solutions," "by company size," "SMB," "enterprise," "by outcome," "business outcomes," or "how we solve X." For sitewide page planning, use website-structure.4---5
6# Pages: Solutions
7
8Guides 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.
9
10**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.
11
12## Initial Assessment
13
14**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, outcomes, and proof points.
15
16Identify:
171. **Outcomes**: Revenue growth, cost savings, efficiency, compliance
182. **Segments**: Industry (primary), company size, team
193. **Format**: Hub + per-solution pages, or single solutions page
204. **Primary goal**: Demo, sign up, contact
21
22## Solutions Page Structure
23
24| Section | Purpose |
25|---------|---------|
26| **Headline** | Outcome-led; "Achieve X with [Product]" |
27| **Challenge** | Business problem, context |
28| **Solution** | How product delivers the outcome |
29| **Proof** | Metrics, case study, ROI |
30| **Features used** | Link to relevant features |
31| **CTA** | Book demo, start trial, see case study |
32| **Related** | Other solutions, use cases (as sub-applications) |
33
34## Best Practices
35
36### Outcome-First
37
38- **Lead with result**: "Increase conversion by 30%" not "We have A/B testing"
39- **Measurable**: Time saved, revenue gained, cost reduced
40- **Specific**: Industry workflows, not generic claims
41- **Differentiate**: Each industry/segment gets unique content
42
43### Organization (Primary → Secondary)
44
45| Dimension | Priority | Examples |
46|-----------|----------|----------|
47| **By Industry** | Primary | Healthcare, Retail, Manufacturing, Financial Services |
48| **By Company Size** | Secondary | SMB, Mid-Market, Enterprise |
49| **By Team** | Secondary | Marketing, Sales, Service, Operations |
50| **By Outcome** | Alternative | Scale support, Reduce churn, Accelerate sales |
51
52### Common Industries (Reference)
53
54Automotive, 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.
55
56### Company Size Segments
57
58| Size | Typical | Focus |
59|------|---------|-------|
60| Startup | <50 | Speed, agility |
61| SMB | 50–500 | Ease of use, affordability |
62| Mid-Market | 500–5000 | Scalability |
63| Enterprise | 5000+ | Customization, compliance, integration |
64
65### vs. Use Cases vs. Features
66
67| Page | Answers | Primary Organization |
68|------|---------|----------------------|
69| **Features** | What does it do? | Capabilities |
70| **Use cases** | When would I use it? | By scenario, persona, business goal |
71| **Solutions** | What outcome do I get? | By industry, company size, team |
72
73**Hierarchy**: Solutions (industry/segment) can contain Use Cases as sub-applications. Example: /solutions/healthcare → use cases: patient scheduling, telemedicine.
74
75### When to Use Solutions vs Use Cases
76
77| Need | Use |
78|------|-----|
79| By industry (Healthcare, Retail) | Solutions |
80| By company size (SMB, Enterprise) | Solutions |
81| By team (Marketing, Sales) | Solutions |
82| By outcome (Scale support) | Solutions |
83| By scenario (Event marketing) | Use Cases |
84| By persona (For Realtors, For CMOs) | Use Cases |
85| By business goal (Acquisition, Retention) | Use Cases |
86| Industry-specific application | Use Cases (as Solutions sub-page) |
87
88## Output Format
89
90- **Solutions list** (industries/segments)
91- **Per-page structure** (sections, messaging)
92- **Headline** options
93- **Proof** integration (case studies, metrics)
94- **Internal linking** (features, use cases, pricing)
95- **SEO** metadata
96
97## Related Skills
98
99- **use-cases-page-generator**: Use cases as sub-applications under solutions; link between
100- **features-page-generator**: Solutions reference features; link to feature pages
101- **customer-stories-page-generator**: Case studies as proof on solutions pages
102- **pricing-page-generator**: Solutions pages link to pricing
103- **landing-page-generator**: Solutions pages apply LP principles
gabrielmoreira