sales-deal-room

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Design a Qwilr Deal Room

设计Qwilr交易室

Help the user architect a Qwilr deal room — a multi-page digital sales room for complex B2B deals with multiple stakeholders, long sales cycles, and lots of moving parts.
帮助用户构建Qwilr交易室——这是一个多页面的数字化销售空间,专为涉及多方利益相关者、销售周期长且环节复杂的B2B交易打造。

When to use a deal room vs. a single proposal

何时使用交易室而非单一提案

ScenarioUse
Simple deal, single decision-maker, straightforward pricingSingle proposal page (
/sales-proposal-page
)
Multiple stakeholders, complex evaluation, needs ongoing updatesDeal room (this skill)
Enterprise deal with procurement, legal, technical reviewDeal room
Partner/channel deal with shared materialsDeal room
Expansion deal with existing customer needing executive buy-inDeal room
场景适用方案
简单交易、单一决策者、定价清晰单一提案页面(
/sales-proposal-page
多方利益相关者、评估流程复杂、需持续更新交易室(本技能)
涉及采购、法务、技术评审的企业级交易交易室
包含共享材料的合作伙伴/渠道交易交易室
需要高管认可的现有客户拓展交易交易室

Step 1 — Gather context

步骤1 — 收集背景信息

Ask the user:
  1. What type of deal is this?
    • A) New logo — first time selling to this company
    • B) Expansion — upselling/cross-selling existing customer
    • C) Renewal — contract renewal with potential changes
    • D) Partner/channel deal — working through a partner
    • E) Other — describe it
  2. Who are the stakeholders? (select all that apply)
    • A) Executive sponsor (C-suite / VP)
    • B) Economic buyer (budget holder)
    • C) Technical evaluator (engineering/IT)
    • D) End users / champions
    • E) Procurement / legal
    • F) External consultant or advisor
    • G) Other — describe
  3. What materials do you already have?
    • A) Nothing yet — starting from scratch
    • B) We have a proposal/quote
    • C) We have a pitch deck
    • D) We have case studies and technical docs
    • E) We have most things, need to organize them
  4. What's the deal timeline?
    • A) Trying to close this month
    • B) 1-3 month sales cycle
    • C) 3-6 month enterprise cycle
    • D) 6+ months
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. 本次交易类型是什么?
    • A) 新客户交易 — 首次向该公司销售
    • B) 拓展交易 — 向现有客户进行向上销售/交叉销售
    • C) 续约交易 — 合同续约并可能包含变更内容
    • D) 合作伙伴/渠道交易 — 与合作伙伴协作开展
    • E) 其他 — 请描述
  2. 利益相关者有哪些?(可多选)
    • A) 高管发起人(C级高管/副总裁)
    • B) 经济决策者(预算负责人)
    • C) 技术评估人员(工程/IT部门)
    • D) 终端用户/内部支持者
    • E) 采购/法务部门
    • F) 外部顾问或咨询师
    • G) 其他 — 请描述
  3. 已准备好哪些材料?
    • A) 尚未准备 — 从零开始
    • B) 已有提案/报价
    • C) 已有演示文稿
    • D) 已有案例研究和技术文档
    • E) 大部分材料已备齐,仅需整理
  4. 交易时间线是怎样的?
    • A) 计划本月内完成签约
    • B) 1-3个月的销售周期
    • C) 3-6个月的企业级销售周期
    • D) 6个月以上
如果用户的请求已提供大部分此类背景信息,可直接跳至相关步骤。先基于合理假设(需明确说明)给出最佳方案,最后仅询问1-2个最关键的澄清问题——不要因需要收集完整背景信息而延迟提供回复。

Step 2 — Deal room architecture

步骤2 — 交易室架构设计

Design the page-by-page structure. A deal room is a collection of Qwilr pages organized as a hub with linked sub-pages. The hub page is the "front door" that each stakeholder visits.
设计页面-by-页面的结构。交易室是一组Qwilr页面的集合,以一个中心枢纽页面为核心,链接各个子页面。枢纽页面是所有利益相关者的入口。

Recommended structure

推荐结构

Hub Page (the main deal room page — everyone starts here)
SectionBlock TypeContent
Welcome headerSplashPersonalized greeting, company logos, deal room title
NavigationText + buttonsLinks to each sub-page, organized by topic
Key contactsText + ImageYour team's contacts with photos and roles
Timeline snapshotTextHigh-level mutual action plan with key dates
Latest updatesTextWhat's new since last visit (keep this updated)
Sub-pages (linked from the hub — create based on what the deal needs):
PageWho it's forContent
Executive SummaryExecutive sponsorBusiness case, ROI, strategic alignment
Technical OverviewTechnical evaluatorArchitecture, integrations, security, compliance
Proposal & PricingEconomic buyerInteractive quote block, pricing options, terms
Case StudiesAll stakeholdersRelevant customer stories, metrics, testimonials
Implementation PlanTechnical + OpsTimeline, phases, resource requirements, dependencies
Security & ComplianceIT / Legal / ProcurementCertifications, data handling, SLAs, DPA
Mutual Action PlanAll stakeholdersShared timeline with milestones, owners, and status
FAQ & Objection HandlingChampionsAnswers to common questions champions get asked internally
枢纽页面(交易室主页面——所有用户从此处开始访问)
板块模块类型内容
欢迎标题醒目展示模块个性化问候语、双方公司标志、交易室标题
导航栏文本+按钮按主题分类的各子页面链接
关键联系人文本+图片我方团队联系人的照片、职位及联系方式
时间线快照文本包含关键日期的高层级共同行动计划
最新更新文本自上次访问以来的新增内容(需持续更新)
子页面(从枢纽页面链接——根据交易需求创建)
页面目标受众内容
执行摘要高管发起人商业案例、投资回报率、战略契合度
技术概览技术评估人员架构、集成方案、安全措施、合规性
提案与定价经济决策者交互式报价模块、定价选项、条款说明
案例研究所有利益相关者相关客户案例、数据指标、客户证言
实施计划技术+运营人员时间线、阶段划分、资源需求、依赖关系
安全与合规IT/法务/采购部门认证资质、数据处理方式、服务水平协议(SLA)、数据处理协议(DPA)
共同行动计划所有利益相关者包含里程碑、负责人及状态的共享时间线
常见问题与异议处理内部支持者支持者在内部常被问到的问题及解答

Adapting for deal type

根据交易类型调整结构

  • New logo: Heavier on Executive Summary, Case Studies, and Security. Include a "Why Us" page if competitive.
  • Expansion: Lead with "Results So Far" page showing value delivered, then expansion scope.
  • Renewal: Lead with partnership recap, then changes/additions for the new term.
  • Partner deal: Include a partner-facing page with co-selling materials and margin details.
  • 新客户交易:重点突出执行摘要、案例研究和安全合规板块。若存在竞争,可添加“为何选择我们”页面。
  • 拓展交易:以“现有成果”页面开头,展示已交付的价值,再介绍拓展范围。
  • 续约交易:以合作回顾页面开头,再介绍新合同期的变更与新增内容。
  • 合作伙伴交易:添加面向合作伙伴的页面,包含联合销售材料和利润分成细节。

Step 3 — Content briefs and hub page copy

步骤3 — 内容简报与枢纽页面文案

Hub page draft copy

枢纽页面文案草稿

Write the actual content for the hub/navigation page:
Welcome section: "Welcome to the [Company] + [Your Company] Deal Room. This is your central hub for everything related to our partnership. Below you'll find the key materials organized by topic — click into any section to dive deeper."
Navigation section: Create a card-style layout linking to each sub-page with a one-line description:
  • Executive Summary — The business case for [solution]: ROI, strategic fit, and expected outcomes
  • Technical Overview — Architecture, integrations, security posture, and compliance details
  • Proposal & Pricing — Interactive pricing with options to customize your package
  • Case Studies — How companies like yours achieved [specific outcome]
  • Implementation Plan — Timeline, phases, and what we need from each team
  • Mutual Action Plan — Our shared roadmap to getting this live by [target date]
Key contacts section: List 2-3 people from your team with name, title, photo placeholder, email, and one line about their role in this deal.
撰写枢纽/导航页面的实际内容:
欢迎板块:“欢迎来到[客户公司] + [我方公司]交易室。这是我们合作相关所有内容的中央枢纽。下方是按主题分类的关键材料——点击任意板块即可深入查看。”
导航板块:创建卡片式布局,链接至各子页面并附上一行描述:
  • 执行摘要 — [解决方案]的商业案例:投资回报率、战略契合度及预期成果
  • 技术概览 — 架构、集成方案、安全态势及合规细节
  • 提案与定价 — 可自定义套餐的交互式定价
  • 案例研究 — 类似企业如何实现[具体成果]
  • 实施计划 — 时间线、阶段划分及双方团队所需配合的内容
  • 共同行动计划 — 我们共同推进至[目标日期]的路线图
关键联系人板块:列出我方团队2-3名成员,包含姓名、职位、照片占位符、邮箱及该成员在本次交易中的职责说明。

Content briefs for sub-pages

子页面内容简报

For each sub-page, provide:
  • Audience: Who this page is for and what they care about
  • Key message: The one thing this page should communicate
  • Structure: Section-by-section outline with recommended block types
  • Tone: How formal/technical/executive the language should be
  • CTA: What action the reader should take after this page
为每个子页面提供:
  • 受众:页面的目标人群及其关注重点
  • 核心信息:页面需传递的核心内容
  • 结构:分板块的大纲及推荐使用的模块类型
  • 语气:语言的正式/技术/高管导向程度
  • 行动号召(CTA):读者浏览页面后应采取的行动

Step 4 — Mutual action plan

步骤4 — 共同行动计划

Design the timeline page with milestones and owners:
MilestoneOwnerTarget DateStatus
Discovery & scoping completeBoth[date]Done
Technical evaluationBuyer's IT team[date]In progress
Security reviewBuyer's security[date]Not started
Proposal & pricing reviewEconomic buyer[date]Not started
Legal / contract reviewBoth legal teams[date]Not started
Executive sign-offExecutive sponsor[date]Not started
Contract signedBoth[date]Not started
Kickoff & implementation beginsBoth[date]Not started
Customize milestones based on the deal type and timeline. For faster deals, collapse steps. For enterprise deals, add procurement and compliance milestones.
设计包含里程碑和负责人的时间线页面:
里程碑负责人目标日期状态
发现与范围界定完成双方[日期]已完成
技术评估买方IT团队[日期]进行中
安全审核买方安全团队[日期]未开始
提案与定价审核经济决策者[日期]未开始
法务/合同审核双方法务团队[日期]未开始
高管签字确认高管发起人[日期]未开始
合同签署双方[日期]未开始
项目启动与实施开始双方[日期]未开始
根据交易类型和时间线自定义里程碑。对于周期较短的交易,可合并步骤;对于企业级交易,需添加采购和合规相关的里程碑。

Step 5 — Analytics strategy

步骤5 — 分析策略

Set up engagement tracking per stakeholder by configuring webhooks for the deal room pages:
通过为交易室页面配置webhook,按利益相关者设置参与度追踪:

Which events to watch per stakeholder

各利益相关者需关注的事件

StakeholderWatch forWhat it means
Executive sponsorViews Executive Summary pageThey're engaged — or their EA is screening
Technical evaluatorViews Technical Overview, time on security pageDoing due diligence — prepare for technical questions
Economic buyerViews Pricing page repeatedlyEvaluating cost — may need ROI reinforcement
Procurement/LegalViews Security & Compliance pageDeal is in procurement — prepare for contract negotiation
New/unknown viewerViews any pageChampion is sharing internally — the deal is expanding
利益相关者关注事件事件含义
高管发起人浏览执行摘要页面他们正在关注——或其助理正在筛选内容
技术评估人员浏览技术概览页面、在安全页面停留的时间正在进行尽职调查——需准备技术问题的解答
经济决策者反复浏览定价页面正在评估成本——可能需要强化投资回报率的说明
采购/法务浏览安全与合规页面交易进入采购环节——需准备合同谈判
新/未知访问者浏览任意页面内部支持者正在分享内容——交易影响范围在扩大

Webhook setup for deal room

交易室Webhook配置

bash
curl -X POST https://api.qwilr.com/v1/webhooks \
  -H "Authorization: Bearer $QWILR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://your-endpoint.com/qwilr-deal-room",
    "events": ["pageFirstViewed", "pageViewed", "pageAccepted", "pagePartiallyAccepted"]
  }'
Use view data to:
  1. Identify which stakeholders are engaged and which aren't
  2. Spot new stakeholders entering the evaluation
  3. Time your follow-ups to when people are actively reviewing
  4. Update your champion on who's looked at what
For full webhook and CRM automation setup, use
/sales-qwilr-automation
.
bash
curl -X POST https://api.qwilr.com/v1/webhooks \
  -H "Authorization: Bearer $QWILR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://your-endpoint.com/qwilr-deal-room",
    "events": ["pageFirstViewed", "pageViewed", "pageAccepted", "pagePartiallyAccepted"]
  }'
利用浏览数据:
  1. 识别哪些利益相关者积极参与,哪些没有
  2. 发现参与评估的新利益相关者
  3. 在用户积极浏览时安排跟进
  4. 向内部支持者反馈谁查看了哪些内容
如需完整的Webhook和CRM自动化设置,请使用
/sales-qwilr-automation

Gotchas

注意事项

  • Don't create too many pages for simple deals. A deal room with 8 sub-pages for a $15k deal is overkill. Match complexity to deal size — small deals need 2-3 pages max (proposal + case study). Reserve the full structure for enterprise deals with multiple stakeholders.
  • Don't use the same content for every stakeholder. The whole point of a deal room is tailored content per role. An executive summary page full of technical specs fails the executive; a pricing page with no ROI context fails the CFO. Write for each audience.
  • Don't skip the mutual action plan. Claude often builds deal rooms with great content but no shared timeline. The MAP is what turns a deal room from a content dump into a collaboration tool. Always include one.
  • Don't forget the executive summary page. Even in a deal room with detailed sub-pages, the hub page needs a concise "why this matters" section. Executives won't click into sub-pages — they'll read the hub and decide if this is worth their time.
  • Don't treat the deal room as "set and forget." A good deal room is updated throughout the sales cycle — latest updates section, MAP status changes, new materials added. Mention this to the user.
  • 不要为简单交易创建过多页面。针对1.5万美元的交易创建包含8个子页面的交易室属于过度设计。页面复杂度需与交易规模匹配——小型交易最多需要2-3个页面(提案+案例研究)。仅为涉及多方利益相关者的企业级交易使用完整结构。
  • 不要为所有利益相关者使用相同内容。交易室的核心价值是为不同角色提供定制化内容。充满技术规格的执行摘要页面无法满足高管需求;缺乏投资回报率背景的定价页面无法打动CFO。需针对每个受众撰写内容。
  • 不要忽略共同行动计划。Claude常创建内容丰富但缺少共享时间线的交易室。共同行动计划是将交易室从内容集合转变为协作工具的关键。务必包含该板块。
  • 不要忘记执行摘要页面。即使交易室包含详细的子页面,枢纽页面也需要一个简洁的“核心价值”板块。高管不会点击进入子页面——他们只会浏览枢纽页面并决定是否值得投入时间。
  • 不要将交易室视为“一劳永逸”的工具。优秀的交易室需在整个销售周期中持续更新——包括最新更新板块、共同行动计划状态变更、新增材料等。请向用户强调这一点。

Related skills

相关技能

  • /sales-proposal-page
    — Write a single proposal page (for simpler deals)
  • /sales-proposal-analytics
    — Interpret engagement signals from deal room pages
  • /sales-qwilr-automation
    — Automate deal room creation and CRM sync
  • /sales-proposal-template
    — Create reusable deal room templates
  • /sales-close
    — Closing strategies and mutual action plan tactics
  • /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-page
    — 撰写单一提案页面(适用于简单交易)
  • /sales-proposal-analytics
    — 解读交易室页面的参与信号
  • /sales-qwilr-automation
    — 自动化创建交易室并同步CRM
  • /sales-proposal-template
    — 创建可复用的交易室模板
  • /sales-close
    — 成交策略与共同行动计划技巧
  • /sales-do
    — 不确定使用哪个技能?该路由器可将任意销售目标匹配至合适的技能。安装:
    npx skills add sales-skills/sales --skills sales-do