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#

SectionPurposeHeadlineOutcome-led; "Achieve X with [Product]"ChallengeBusiness problem, contextSolutionHow product delivers the outcomeProofMetrics, case study, ROIFeatures usedLink to relevant featuresCTABook demo, start trial, see case studyRelatedOther 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)#

DimensionPriorityExamplesBy IndustryPrimaryHealthcare, Retail, Manufacturing, Financial ServicesBy Company SizeSecondarySMB, Mid-Market, EnterpriseBy TeamSecondaryMarketing, Sales, Service, OperationsBy OutcomeAlternativeScale 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#

SizeTypicalFocusStartup<50Speed, agilitySMB50–500Ease of use, affordabilityMid-Market500–5000ScalabilityEnterprise5000+Customization, compliance, integration

vs. Use Cases vs. Features#

PageAnswersPrimary OrganizationFeaturesWhat does it do?CapabilitiesUse casesWhen would I use it?By scenario, persona, business goalSolutionsWhat 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#

NeedUseBy industry (Healthcare, Retail)SolutionsBy company size (SMB, Enterprise)SolutionsBy team (Marketing, Sales)SolutionsBy outcome (Scale support)SolutionsBy scenario (Event marketing)Use CasesBy persona (For Realtors, For CMOs)Use CasesBy business goal (Acquisition, Retention)Use CasesIndustry-specific applicationUse 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