Back to Details

sales-proposal-analytics

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Interpret Qwilr Proposal Analytics

解读Qwilr提案分析数据

Help the user read Qwilr engagement signals and turn them into concrete next steps — follow-up messages, strategy adjustments, or deal actions.
帮助用户解读Qwilr互动信号，并将其转化为具体的后续步骤——跟进消息、策略调整或成交动作。

Step 1 — Gather context

步骤1 — 收集背景信息

Ask the user:
  1. What are the analytics showing?
    • A) Prospect viewed the proposal (single view)
    • B) Prospect viewed multiple times
    • C) Multiple people viewed it (committee/forwarded)
    • D) Prospect hasn't viewed it at all
    • E) Prospect viewed specific sections heavily (e.g., pricing)
    • F) Prospect partially accepted (selected some items, not all)
    • G) Prospect accepted the proposal
    • H) Other — describe the signals
  2. How long since you sent it?
    • A) Less than 24 hours
    • B) 1-3 days
    • C) 4-7 days
    • D) More than a week
    • E) More than 2 weeks
  3. Deal context:
    • What's the deal size and product/service?
    • Who's the buyer (title, decision-making authority)?
    • Is there a competitive situation?
    • What was the last conversation like before sending?
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) 潜在客户重点浏览了特定章节（如定价）
    • F) 潜在客户部分接受（选择了部分项目，而非全部）
    • G) 潜在客户接受了提案
    • H) 其他情况——请描述具体信号
  2. 提案发送至今已有多久？
    • A) 不到24小时
    • B) 1-3天
    • C) 4-7天
    • D) 超过一周
    • E) 超过两周
  3. 交易背景:
    • 交易规模和产品/服务是什么？
    • 买方是谁（职位、决策权限）？
    • 是否存在竞争情况？
    • 发送提案前的最后一次沟通情况如何？
如果用户的请求已提供大部分上述背景信息，可直接跳至相关步骤。 先基于合理假设（需明确说明）给出最佳答案，最后仅询问最关键的1-2个澄清问题——不要要求收集完整背景后再给出回复。

Step 2 — Signal interpretation

步骤2 — 信号解读

Interpret the engagement pattern using this framework:
使用以下框架解读互动模式：

View patterns and what they mean

浏览模式及其含义

SignalLikely MeaningUrgency
Viewed once, brieflySkimmed it, may return later — or may not be prioritizingMedium
Viewed once, spent time on pricingEvaluating cost, possibly comparing to alternativesHigh
Viewed multiple timesActively considering, possibly building internal caseHigh
Multiple unique viewersBeing circulated to buying committee — deal is progressingHigh
Pricing section revisited 3+ timesPrice sensitivity or building a budget justificationHigh
Executive summary skipped, jumped to pricingBuyer already understands the value, focused on costMedium
Not viewed after 24hEmail may not have landed, or not a priority right nowMedium
Not viewed after 3+ daysDelivery issue, lost priority, or buyer is going darkHigh
Viewed then went silentMay be discussing internally, or lost momentumMedium-High
Partial acceptanceWants some items but not others — negotiation opportunityHigh
信号可能的含义优先级
仅浏览过一次且时间短暂大致浏览了内容，可能之后会再回来查看——也可能未将其列为优先事项中等
仅浏览过一次，但在定价部分花费了时间正在评估成本，可能在对比其他方案高
多次浏览提案正在积极考虑，可能在内部构建支持理由高
多名独立浏览者提案正在采购委员会内传阅——交易正在推进高
定价章节被反复查看3次以上对价格敏感，或正在准备预算审批依据高
跳过执行摘要，直接查看定价买方已了解价值，重点关注成本中等
24小时后仍未查看邮件可能未送达，或当前非优先事项中等
3天以上仍未查看存在送达问题、已不再优先处理，或客户已失联高
查看后不再联系可能正在内部讨论，或已失去推进动力中高
部分接受想要部分项目但非全部——存在谈判机会高

Multiple-viewer analysis

多浏览者分析

When multiple people view the proposal:
  • 2-3 viewers: Normal buying committee circulation. The original contact is championing internally.
  • 4+ viewers: Larger committee than expected — deal may be more complex. Ask about procurement involvement.
  • New viewer after silence: The proposal was forwarded up — a good sign, but the new viewer may need different framing.
  • Same person, different times: They're returning to it — likely building a case or comparing options.
当多人查看提案时：
  • 2-3名浏览者：正常的采购委员会传阅，最初对接人正在内部推进。
  • 4名及以上浏览者：委员会规模超出预期——交易可能更复杂。询问是否涉及采购部门。
  • 失联后出现新浏览者：提案被转发给上级——是好信号，但新浏览者可能需要不同的内容框架。
  • 同一人多次浏览：对方反复查看——可能正在构建支持理由或对比其他选项。

Step 3 — Action plan

步骤3 — 行动计划

Based on the signals, provide concrete next steps:
基于信号提供具体后续步骤：

If viewed and engaged (positive signals)

若客户已查看并互动（积极信号）

  1. Don't jump in immediately — let them finish evaluating (unless they've viewed 3+ times with no action)
  2. Send a value-add follow-up — share a relevant case study, ROI data, or answer a question they didn't ask yet
  3. Offer to walk through it — "I saw you've had a chance to review — want to jump on a quick call to walk through the pricing options?"
  1. 不要立即跟进——让对方完成评估（除非已查看3次以上但未采取行动）
  2. 发送增值跟进消息——分享相关案例研究、ROI数据，或解答对方未提出的问题
  3. 主动提出讲解——“我看到您已经查看过提案了——要不要开个短会讲解一下定价选项？”

If not viewed

若客户未查看提案

  1. Check delivery — confirm the email landed (check spam, verify address)
  2. Re-send with a different subject line — the original email may not have cut through
  3. Try a different channel — LinkedIn message, text, or phone call
  4. Reduce friction — "Here's the one-page summary" with a link back to the full proposal
  1. 检查送达情况——确认邮件是否送达（检查垃圾邮件、验证地址）
  2. 更换主题行重新发送——原邮件可能未引起注意
  3. 尝试其他渠道——LinkedIn消息、短信或电话
  4. 降低决策门槛——“这是一页摘要”，附带完整提案的链接

If pricing section is getting heavy attention

若定价章节被重点关注

  1. Proactively address value — send an ROI breakdown or case study showing cost justification
  2. Offer flexibility — "I noticed you're reviewing the pricing — happy to discuss options that fit your budget"
  3. Don't discount preemptively — let them raise the concern first
  1. 主动强调价值——发送ROI分析或案例研究，说明成本合理性
  2. 提供灵活性——“我注意到您正在查看定价部分——很乐意讨论符合您预算的方案”
  3. 不要主动降价——等对方提出价格顾虑后再回应

If multiple stakeholders are viewing

若多名利益相关者查看提案

  1. Ask your champion — "It looks like a few people on your team are reviewing — should I put together a summary for the broader group?"
  2. Create stakeholder-specific content — technical details for engineering, ROI for finance, timeline for ops
  3. Offer a group walkthrough — bring all stakeholders into one call
  1. 询问对接人——“看起来您团队的几位成员正在查看提案——要不要我为 broader团队准备一份摘要？”
  2. 创建针对不同利益相关者的内容——给技术部门的技术细节、给财务部门的ROI分析、给运营部门的时间规划
  3. 提议集体讲解——邀请所有利益相关者参加同一会议

If buyer went dark

若客户失联

  1. Day 3-5: Light touch — share something useful (article, case study), don't ask "did you see my proposal?"
  2. Day 7-10: Direct but empathetic — "I know things get busy. Is this still a priority for Q2, or should we revisit later?"
  3. Day 14+: Break-up email — "I don't want to keep following up if the timing isn't right. Should I close this out for now?"
  1. 第3-5天：轻触式跟进——分享有用内容（文章、案例研究），不要问“您看到我的提案了吗？”
  2. 第7-10天：直接但共情的跟进——“我知道您很忙。这个项目在Q2还是优先事项吗？或者我们之后再谈？”
  3. 第14天以上：收尾邮件——“如果时机不合适，我不想再继续跟进了。要不要先结束这个项目？”

Step 4 — Draft follow-up messages

步骤4 — 起草跟进消息

Write 1-2 follow-up messages tailored to the specific engagement pattern. Messages should:
  • Reference the engagement signal indirectly (don't say "I see you viewed it 5 times" — that's creepy)
  • Add value, not just ask for status
  • Include a specific, low-friction CTA
  • Match the tone of the deal stage (casual for early, professional for enterprise)
针对特定互动模式撰写1-2条跟进消息。消息需满足：
  • 间接提及互动信号（不要说“我看到您查看了5次”——这会让对方感到不适）
  • 提供价值，而非仅询问状态
  • 包含具体、低门槛的行动号召（CTA）
  • 匹配交易阶段的语气（早期阶段可随意些，企业级交易需专业）

Step 5 — Webhook setup guidance

步骤5 — Webhook配置指南

Help the user set up real-time alerts for future proposals using Qwilr webhooks:
帮助用户使用Qwilr Webhook设置未来提案的实时提醒：

Recommended webhook subscriptions

推荐订阅的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-events",
    "events": ["pageFirstViewed", "pageViewed", "pageAccepted", "pagePartiallyAccepted"]
  }'
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-events",
    "events": ["pageFirstViewed", "pageViewed", "pageAccepted", "pagePartiallyAccepted"]
  }'

Event-to-action mapping

事件与行动映射

Webhook EventRecommended Action
pageFirstViewed
Alert rep in Slack/email — prospect opened the proposal
pageViewed
(repeat)		Log in CRM — track view count and timing
pageAccepted
Update CRM deal stage, notify rep, trigger onboarding
pagePartiallyAccepted
Alert rep — buyer selected some items, follow up on the rest
pagePreviewAccepted
Internal preview was accepted — ready for client review
For full automation setup (CRM sync, Slack notifications, etc.), use 
/sales-qwilr-automation
.
Webhook事件推荐行动
pageFirstViewed
在Slack/邮件中提醒销售代表——潜在客户已打开提案
pageViewed
（重复）		记录到CRM中——跟踪浏览次数和时间
pageAccepted
更新CRM交易阶段，通知销售代表，触发入职流程
pagePartiallyAccepted
提醒销售代表——买方已选择部分项目，跟进剩余部分
pagePreviewAccepted
内部预览已通过——可提交给客户查看
如需完整自动化设置（CRM同步、Slack通知等），请使用
/sales-qwilr-automation
。

Gotchas

注意事项

  • Don't over-interpret a single page view. One view could be the prospect, their EA, or an automated CRM preview. A single brief view doesn't mean "they're interested" — it means "someone opened the link." Wait for patterns (repeat views, time spent, multiple viewers) before drawing conclusions.
  • Don't treat all engagement signals equally. Pricing section views are much higher signal than a quick skim of the cover page. Weight your interpretation toward the sections that indicate evaluation behavior (pricing, scope, case studies).
  • Don't recommend aggressive follow-up on automated CRM views. Some CRMs and email tools auto-preview links, generating false "viewed" signals. If a view happens within seconds of sending with zero time on page, it's likely automated.
  • Don't tell the prospect you can see their views. Saying "I noticed you looked at the pricing 3 times" is creepy and breaks trust. Reference engagement signals indirectly — "I wanted to see if you had questions about the pricing options."
  • Don't ignore time-of-day context. A prospect reviewing a proposal at 10pm on a Sunday suggests they're doing personal due diligence, possibly building a case. A 30-second view during business hours is likely a quick skim between meetings.
  • 不要过度解读单次浏览。单次浏览可能来自潜在客户、其助理，或CRM的自动预览。单次短暂浏览不代表“对方感兴趣”——仅代表“有人打开了链接”。在得出结论前，需等待出现模式（重复浏览、停留时间、多名浏览者）。
  • 不要同等对待所有互动信号。定价章节的浏览比快速浏览封面页的信号强度高得多。解读时重点关注显示评估行为的章节（定价、范围、案例研究）。
  • 不要针对CRM自动浏览推荐激进跟进。部分CRM和邮件工具会自动预览链接，产生虚假的“已查看”信号。如果发送后几秒内就出现浏览且页面停留时间为0，很可能是自动浏览。
  • 不要告诉客户你能看到他们的浏览记录。说“我注意到您查看了定价3次”会让对方感到不适并破坏信任。需间接提及互动信号——比如“我想了解您对定价选项是否有疑问。”
  • 不要忽略时间背景。潜在客户在周日晚上10点查看提案，表明他们在做个人尽职调查，可能在构建支持理由。工作日期间30秒的浏览可能只是会议间隙的快速浏览。

Related skills

相关技能

  • /sales-proposal-page
    — Write or restructure the proposal itself
  • /sales-qwilr-automation
    — Set up automated CRM sync and webhook workflows
  • /sales-follow-up
    — General follow-up strategies (non-Qwilr-specific)
  • /sales-deal-room
    — For complex deals that need a multi-page deal room
  • /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-qwilr-automation
    — 设置自动化CRM同步和Webhook工作流
  • /sales-follow-up
    — 通用跟进策略（非Qwilr专属）
  • /sales-deal-room
    — 适用于需要多页面交易室的复杂交易
  • /sales-do
    — 不确定使用哪个技能？该工具会将任何销售目标匹配到合适的技能。安装：
    npx skills add sales-skills/sales --skills sales-do