sales-proposal-page

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Write a Qwilr Proposal Page

撰写Qwilr提案页面

Help the user write and structure a Qwilr proposal page — from section planning through copy and interactive element configuration. Qwilr replaces static PDF proposals with interactive web-based pages that include quote blocks, embedded content, and real-time engagement tracking.
帮助用户撰写并构建Qwilr提案页面——从板块规划到文案撰写,再到交互式元素配置。Qwilr以交互式网页版页面替代静态PDF提案,包含报价模块、嵌入内容和实时互动追踪功能。

Step 1 — Gather context

步骤1 — 收集背景信息

Ask the user:
  1. What are you proposing? (product/service, scope, price range)
  2. Who is the buyer? (title, company, industry, company size)
  3. Where is this deal?
    • A) Early — they're evaluating options
    • B) Mid — they've seen a demo, now need a formal proposal
    • C) Late — verbal yes, need the paperwork
    • D) Renewal or expansion of existing deal
  4. Which Qwilr features do you want to use?
    • A) Quote block with pricing table (interactive line items, optional add-ons)
    • B) Simple text-based proposal (no interactive pricing)
    • C) Full deal room with multiple pages (route to
      /sales-deal-room
      instead)
    • D) Not sure — recommend what fits
If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.
询问用户:
  1. 你要提案的内容是什么?(产品/服务、范围、价格区间)
  2. 目标买家是谁?(职位、公司、行业、公司规模)
  3. 当前交易处于哪个阶段?
    • A) 早期——买家正在评估多种选项
    • B) 中期——买家已观看演示,需要正式提案
    • C) 后期——已口头达成意向,需要完成文书工作
    • D) 现有交易的续约或拓展
  4. 你想使用Qwilr的哪些功能?
    • A) 带定价表格的报价模块(交互式行项目、可选附加项)
    • B) 纯文本提案(无交互式定价)
    • C) 包含多页面的完整交易空间(请跳转至
      /sales-deal-room
    • D) 不确定——推荐合适的功能
**如果用户的请求已提供大部分此类背景信息,可直接跳至对应步骤。**先基于合理假设(需明确说明)给出最佳答案,最后仅询问最关键的1-2个澄清问题——不要要求用户提供完整背景后才给出回应。

Step 2 — Generate page blueprint

步骤2 — 生成页面蓝图

Design a section-by-section page structure mapped to Qwilr block types. A strong Qwilr proposal typically follows this flow:
SectionQwilr Block TypePurpose
Cover / HeroSplash blockFirst impression, prospect's name/logo, one-line value prop
Executive SummaryText + Image blockWhy this matters to them specifically (2-3 paragraphs max)
Problem & SolutionText block or AccordionFrame the pain, present your solution mapped to their needs
Scope of WorkText block or AccordionWhat's included, deliverables, timeline
PricingQuote blockInteractive pricing table with line items
Timeline & MilestonesText blockKey dates, phases, dependencies
About Us / TeamText + Image blockCredibility — relevant team members, case study snippets
Next Steps / CTAAccept blockClear call to action — accept the proposal, sign, or book a call
Adapt this structure based on the deal context:
  • Early-stage deals: Lead heavier on problem/solution, lighter on detailed scope
  • Late-stage deals: Lead with scope and pricing, lighter on problem framing
  • Renewals/expansions: Lead with results achieved, then expansion scope and pricing
  • Technical buyers: Add a technical architecture or integration section
  • Executive buyers: Add an ROI/business case section
设计对应Qwilr模块类型的分板块页面结构。优质的Qwilr提案通常遵循以下流程:
板块Qwilr模块类型用途
封面/首屏Splash模块第一印象,展示潜在客户的名称/Logo,一句式价值主张
执行摘要文本+图片模块说明该提案对客户的重要性(最多2-3段)
问题与解决方案文本模块或折叠面板梳理痛点,展示与客户需求匹配的解决方案
工作范围文本模块或折叠面板包含的内容、交付成果、时间线
定价报价模块带行项目的交互式定价表格
时间线与里程碑文本模块关键日期、阶段、依赖项
关于我们/团队文本+图片模块建立可信度——展示相关团队成员、案例研究片段
下一步行动/号召性用语接受模块明确的行动号召——接受提案、签署协议或预约通话
根据交易背景调整结构:
  • 早期交易:侧重问题/解决方案,简化详细范围
  • 后期交易:以范围和定价为重点,减少痛点阐述
  • 续约/拓展交易:先展示已取得的成果,再介绍拓展范围和定价
  • 技术型买家:添加技术架构或集成板块
  • 高管型买家:添加投资回报率/商业案例板块

Step 3 — Write the copy

步骤3 — 撰写文案

Write actual copy for each section, not just placeholders. Follow these principles:
  • Executive Summary: 2-3 paragraphs max. Lead with their problem, not your product. Reference specific things from their situation (company name, goals they mentioned, pain points from discovery).
  • Problem & Solution: Mirror their language back to them. Map each pain point to a specific capability.
  • Scope: Use clear deliverables with enough detail that both sides know what "done" looks like, but not so much that it reads like a contract.
  • Pricing copy: Write the framing text above the quote block — this is where you anchor value before they see numbers.
  • CTA: Be specific about what happens after they accept (kickoff call within 48 hours, implementation begins week of X, etc.).
Use
{{token}}
syntax for any fields the user might want to auto-populate via the Qwilr API later (e.g.,
{{company_name}}
,
{{contact_first_name}}
,
{{deal_amount}}
).
为每个板块撰写实际文案,而非仅使用占位符。遵循以下原则:
  • 执行摘要:最多2-3段。从客户的痛点切入,而非你的产品。引用客户的具体情况(公司名称、他们提及的目标、发现阶段的痛点)。
  • 问题与解决方案:呼应客户的表述。将每个痛点与具体功能匹配。
  • 工作范围:使用清晰的交付成果,足够详细到双方都明确“完成”的标准,但不要繁琐到像合同。
  • 定价文案:在报价模块上方撰写框架性文本——这是让客户在看到数字前建立价值认知的关键。
  • 号召性用语:明确说明客户接受后的后续安排(如48小时内启动项目会议、X周开始实施等)。
使用
{{token}}
语法标记日后可能通过Qwilr API自动填充的字段(例如
{{company_name}}
{{contact_first_name}}
{{deal_amount}}
)。

Step 4 — Configure interactive elements

步骤4 — 配置交互式元素

If the proposal includes a quote block, design the pricing structure:
如果提案包含报价模块,设计定价结构:

Quote block configuration

报价模块配置

  • Sections: Group line items logically (e.g., "Platform License", "Implementation", "Add-Ons")
  • Line items: Each item needs a name, description, and price
    • Use
      fixedCost
      type for most items
    • Mark add-ons as
      isOptional: true
      so the buyer can select/deselect
    • Set
      quantity
      ranges where buyers should choose volume (seats, units)
    • Apply discounts where appropriate (percentage or fixed amount)
  • Billing: Specify
    oneOff
    or
    recurring
    (monthly/quarterly/annual) per item
  • Tax: Include tax configuration if applicable
  • 板块:将行项目按逻辑分组(例如“平台许可证”、“实施服务”、“附加项”)
  • 行项目:每个项目需要名称、描述和价格
    • 大多数项目使用
      fixedCost
      类型
    • 将附加项标记为
      isOptional: true
      ,以便买家可以选择/取消选择
    • 为买家需要选择数量的项目(席位、单位)设置
      quantity
      范围
    • 酌情应用折扣(百分比或固定金额)
  • 计费方式:为每个项目指定
    oneOff
    (一次性)或
    recurring
    (月度/季度/年度)
  • 税费:如有需要,包含税费配置

Interactive features to consider

可考虑的交互式功能

  • Optional line items: Let buyers self-select add-ons — this increases deal size while giving them control
  • Quantity selectors: For per-seat or per-unit pricing, let buyers adjust quantity
  • Discount display: Show the discount visibly to reinforce the deal they're getting
  • Section subtotals: Help buyers understand cost breakdown by category
  • Features lists: Add feature descriptions to line items for context
  • 可选行项目:让买家自行选择附加项——这既能提升交易规模,又能给予客户控制权
  • 数量选择器:对于按席位或按单位定价的项目,允许买家调整数量
  • 折扣展示:显眼地展示折扣,强化客户获得的优惠
  • 板块小计:帮助买家了解按类别划分的成本明细
  • 功能列表:为行项目添加功能描述以提供上下文

Step 5 — Generate API payload (optional)

步骤5 — 生成API负载(可选)

If the user wants to create the page programmatically via the Qwilr API, generate the
POST /pages
JSON payload:
json
{
  "name": "Proposal for {{company_name}}",
  "isPublished": false,
  "tags": ["proposal", "{{deal_stage}}"],
  "blocks": [
    {
      "savedBlockId": "<from GET /blocks/saved>",
      "tokens": {
        "company_name": "Acme Corp",
        "contact_first_name": "Jane"
      }
    }
  ],
  "quoteSections": [
    {
      "title": "Platform License",
      "items": [
        {
          "title": "Annual Platform License",
          "description": "Full access to all features",
          "type": "fixedCost",
          "fixedCost": { "amount": 24000, "currency": "USD" },
          "isOptional": false,
          "billing": { "type": "recurring", "frequency": "annual" }
        }
      ]
    }
  ]
}
Notes for the user:
  • Run
    GET /blocks/saved
    first to discover available block IDs
  • Set
    isPublished: false
    to review before sending
  • Use
    tokens
    to substitute CRM data into the template
  • Auth:
    Authorization: Bearer <your-jwt-token>
  • Base URL:
    https://api.qwilr.com/v1
如果用户希望通过Qwilr API以编程方式创建页面,生成
POST /pages
的JSON负载:
json
{
  "name": "Proposal for {{company_name}}",
  "isPublished": false,
  "tags": ["proposal", "{{deal_stage}}"],
  "blocks": [
    {
      "savedBlockId": "<from GET /blocks/saved>",
      "tokens": {
        "company_name": "Acme Corp",
        "contact_first_name": "Jane"
      }
    }
  ],
  "quoteSections": [
    {
      "title": "Platform License",
      "items": [
        {
          "title": "Annual Platform License",
          "description": "Full access to all features",
          "type": "fixedCost",
          "fixedCost": { "amount": 24000, "currency": "USD" },
          "isOptional": false,
          "billing": { "type": "recurring", "frequency": "annual" }
        }
      ]
    }
  ]
}
给用户的提示:
  • 先调用
    GET /blocks/saved
    获取可用的模块ID
  • 设置
    isPublished: false
    以便在发送前审核
  • 使用
    tokens
    将CRM数据替换到模板中
  • 认证方式:
    Authorization: Bearer <your-jwt-token>
  • 基础URL:
    https://api.qwilr.com/v1

Gotchas

注意事项

  • Don't generate walls of text. Qwilr is a visual, web-based platform — not a Word doc. Use Qwilr block types (Splash, Accordion, Quote blocks) to break up content. If a section runs longer than 3 paragraphs, restructure it into an Accordion or split it into sub-sections.
  • Don't forget the interactive pricing/quote block. Claude defaults to writing pricing as plain text. Qwilr's quote block is the product's key differentiator — use it for any proposal that includes pricing. Configure line items, optional add-ons, and quantity selectors.
  • Don't skip the CTA. Every proposal needs a clear call to action using Qwilr's Accept block. Don't end with "let us know your thoughts" — end with "Accept this proposal" or "Book your kickoff call."
  • Don't make the proposal too long. Web proposals are not PDFs. Buyers skim. A strong Qwilr proposal is 5-8 sections. If it's longer, consider moving detailed content to a deal room (
    /sales-deal-room
    ) instead.
  • Don't forget
    {{token}}
    placeholders.
    If the proposal might be auto-generated via API later, use
    {{company_name}}
    ,
    {{contact_first_name}}
    , etc. throughout — not hardcoded values.
  • 不要生成大段文字。Qwilr是可视化的网页平台——不是Word文档。使用Qwilr模块类型(Splash、折叠面板、报价模块)拆分内容。如果某个板块超过3段,将其重构为折叠面板或拆分为子板块。
  • 不要忘记交互式定价/报价模块。Claude默认会将定价写成纯文本。Qwilr的报价模块是产品的核心差异化优势——任何包含定价的提案都应使用它。配置行项目、可选附加项和数量选择器。
  • 不要跳过号召性用语。每个提案都需要使用Qwilr的接受模块设置明确的行动号召。不要以“请告知你的想法”结尾——要以“接受此提案”或“预约启动会议”结尾。
  • 不要让提案过长。网页提案不是PDF。买家会快速浏览。优质的Qwilr提案包含5-8个板块。如果更长,考虑将详细内容移至交易空间(
    /sales-deal-room
    )。
  • 不要忘记
    {{token}}
    占位符
    。如果提案日后可能通过API自动生成,请全程使用
    {{company_name}}
    {{contact_first_name}}
    等占位符——不要使用硬编码值。

Related skills

相关技能

  • /sales-proposal-analytics
    — Track engagement after sending (who viewed, which sections, when to follow up)
  • /sales-qwilr-automation
    — Automate proposal creation from CRM data via the Qwilr API
  • /sales-deal-room
    — For complex multi-stakeholder deals that need multiple pages
  • /sales-proposal-template
    — Design reusable templates for your whole team
  • /sales-proposal
    — For general (non-Qwilr) proposal strategy and pricing
  • /sales-do
    — Not sure which skill to use? The router matches any sales objective to the right skill. Install:
    npx skills add sales-skills/sales --skills sales-do
  • /sales-proposal-analytics
    — 发送后追踪互动情况(谁查看了、查看了哪些板块、何时跟进)
  • /sales-qwilr-automation
    — 通过Qwilr API从CRM数据自动生成提案
  • /sales-deal-room
    — 适用于需要多页面的复杂多利益相关方交易
  • /sales-proposal-template
    — 为整个团队设计可复用的模板
  • /sales-proposal
    — 适用于通用(非Qwilr)提案策略和定价
  • /sales-do
    — 不确定使用哪个技能?该路由会将任何销售目标匹配到合适的技能。安装方式:
    npx skills add sales-skills/sales --skills sales-do