solutions-page-generator
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChinesePages: Solutions
页面：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.
指导制作以业务成果为核心的Solutions页面。行业优先是B2B领域的通用规范（Salesforce、HubSpot均采用该模式）。要回答“我所在的行业/团队/公司规模能获得什么成果？”，而非“这个产品有什么功能？”。Solutions页面和功能页（介绍产品能力）、用例页（介绍使用场景）有明显区别：Solutions页面强调针对不同细分群体的可衡量价值。
调用规则：首次调用时，如果合适，可以先用1-2句话介绍本技能覆盖的范围和价值，再给出核心输出。如果是后续调用或者用户要求跳过说明，直接给出核心输出即可。
Initial Assessment
初步评估
Check for product marketing context first: If or exists, read it for product, outcomes, and proof points.
.claude/product-marketing-context.md.cursor/product-marketing-context.mdIdentify:
- 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
优先检查产品营销上下文：如果存在或文件，先读取文件中的产品信息、成果指标和佐证内容。
.claude/product-marketing-context.md.cursor/product-marketing-context.md确认以下信息：
- 成果：收入增长、成本节约、效率提升、合规性
- 细分群体：行业（首要维度）、公司规模、团队
- 呈现形式：汇总页+单解决方案详情页，或者单个解决方案聚合页
- 核心目标：申请演示、注册、联系销售
Solutions Page Structure
Solutions页面结构
| 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) |
| 模块 | 用途 |
|---|---|
| 标题 | 以成果为导向，比如“使用[产品名]实现X目标” |
| 挑战 | 业务痛点、背景信息 |
| 解决方案 | 产品如何交付对应成果 |
| 佐证 | 数据指标、案例研究、ROI |
| 用到的功能 | 跳转至对应功能页的链接 |
| CTA | 预约演示、开启试用、查看案例 |
| 相关内容 | 其他解决方案、用例（作为子应用） |
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
- 以结果开篇：比如“转化率提升30%”，而非“我们支持A/B测试”
- 可衡量：节省的时间、增长的收入、降低的成本
- 具体：贴合行业工作流，而非泛泛而谈
- 差异化：每个行业/细分群体都有专属内容
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 |
| 维度 | 优先级 | 示例 |
|---|---|---|
| 按行业 | 最高 | 医疗、零售、制造、金融服务 |
| 按公司规模 | 次高 | SMB、中端市场、Enterprise |
| 按团队 | 次高 | 营销、销售、服务、运营 |
| 按成果 | 替代维度 | 扩容支持、降低流失率、加速销售流程 |
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 |
| 规模 | 典型人数 | 关注重点 |
|---|---|---|
| 初创公司 | <50 | 速度、灵活性 |
| SMB | 50–500 | 易用性、性价比 |
| 中端市场 | 500–5000 | 可扩展性 |
| Enterprise | 5000+ | 定制化、合规性、集成能力 |
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.
| 页面类型 | 回答的问题 | 核心组织逻辑 |
|---|---|---|
| 功能页 | 这个产品是做什么的？ | 按产品能力组织 |
| 用例页 | 我什么时候可以用它？ | 按场景、用户角色、业务目标组织 |
| Solutions页 | 我能获得什么成果？ | 按行业、公司规模、团队组织 |
层级关系：Solutions（按行业/细分群体）可以包含用例作为子应用。示例：/solutions/healthcare → 下属用例：患者预约、远程医疗。
When to Use Solutions vs Use Cases
什么时候用Solutions页，什么时候用用例页
| 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) |
| 需求 | 选用页面类型 |
|---|---|
| 按行业划分（医疗、零售） | Solutions |
| 按公司规模划分（SMB、Enterprise） | Solutions |
| 按团队划分（营销、销售） | Solutions |
| 按成果划分（扩容支持） | Solutions |
| 按场景划分（活动营销） | 用例页 |
| 按用户角色划分（面向房产经纪人、面向CMO） | 用例页 |
| 按业务目标划分（获客、留存） | 用例页 |
| 行业专属应用场景 | 用例页（作为Solutions的子页面） |
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
- Solutions列表（行业/细分群体）
- 单页结构（模块、信息传达要点）
- 标题备选方案
- 佐证内容整合（案例研究、数据指标）
- 内部链接（功能、用例、定价）
- SEO元数据
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
- use-cases-page-generator：用例作为Solutions的子应用，两者之间互相链接
- features-page-generator：Solutions页面引用功能，跳转至功能页
- customer-stories-page-generator：案例研究作为Solutions页面的佐证内容
- pricing-page-generator：Solutions页面跳转至定价页
- landing-page-generator：Solutions页面适用落地页设计原则