Back to Details

growth-pulse

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Growth Pulse

Growth Pulse

One page that answers whether the growth engine is working, and what to do about it this week.
Owners describe pulling numbers from three dashboards and trying to find the story themselves. The story is the deliverable here — not the dashboards.
一页内容，回答增长引擎是否在运转，以及本周该做什么。
业主往往会从三个 dashboard 拉取数字，再自行寻找其中隐含的故事。这里交付的是故事，而不是 dashboard。

Step 1 — Pull everything in parallel

步骤 1 — 并行拉取所有数据

Dispatch all connector calls in a single batch. See 
reference/data_sources.md
for the metric-to-tool mapping. Serial pulls turn this into a wait nobody sits through twice.
  • HubSpot — deals by stage, new contacts, lead source, win rate, cycle time, stalled deals
  • PayPal, Stripe, Square — revenue trend, transaction counts, refunds
  • Shopify — orders, SKU-level revenue, repeat purchase rate
  • QuickBooks — realized revenue, the number the books agree with
  • TikTok Ads — last week's spend, impressions, clicks, results, and cost per result per campaign, from the native connector (
    report_integrated_get
    , last 7 days against the prior 7), so paid spend sits beside the sales it claims to drive
  • Mailchimp — campaign, e-commerce, and audience-growth analytics, with revenue attribution on campaigns
  • Gmail or Microsoft 365 — inbound inquiry volume and response times
  • Public reviews — recent ratings and review text, via web research
If a source errors or is missing, record it and move on. This skill is designed to say something useful on one connector and something excellent on six.
Zero connectors is a supported path. Ask for exports — a CRM deal export, a sales report, an ads performance CSV — and build the same pulse from files. Say it plainly rather than stalling.
将所有 connector 调用一次性批量派发。指标与工具的映射见 
reference/data_sources.md
。串行拉取会把流程拖成没人愿意再经历一次的长等待。
  • HubSpot — 各阶段商机、新增联系人、线索来源、赢单率、销售周期时长、停滞商机
  • PayPal、Stripe、Square — 收入趋势、交易笔数、退款
  • Shopify — 订单、SKU 级收入、复购率
  • QuickBooks — 已实现收入，也就是账簿确认的收入数字
  • TikTok Ads — 通过原生 connector 获取上周支出、展示次数、点击数、转化结果，以及每个营销活动的单次结果成本（
    report_integrated_get
    ，最近 7 天与此前 7 天对比），让付费投放支出与其声称带来的销售并列呈现
  • Mailchimp — 营销活动、电商和受众增长分析，以及营销活动的收入归因
  • Gmail 或 Microsoft 365 — 主动咨询量和响应时长
  • 公开评价 — 通过联网调研获取近期评分和评论文本
如果某个数据源报错或缺失，记录下来并继续执行。这个 skill 的设计目标是在只连接一个 connector 时也能提供有用信息，连接六个时则能提供出色洞察。
即使没有连接任何 connector，也支持完整执行。 可以请业主提供导出文件，例如 CRM 商机导出、销售报告或广告效果 CSV，然后基于这些文件构建同样的 pulse。应明确说明情况，而不是停滞不前。

Step 2 — Compute the five views

步骤 2 — 计算五个视图

Read 
reference/thresholds.md
for the cutoffs. Compute each view and assign it a status.
  1. Channel trend — revenue by channel this period versus last, and versus the same period last year where available
  2. Funnel conversion — leads in, qualified, opportunities, won; the conversion rate between each step and where the biggest drop-off sits
  3. Campaign return — spend versus attributed revenue per campaign, and cost per lead
  4. Product performance — top three and bottom three by revenue and by growth rate
  5. Customer sentiment — recent review scores, review themes, disputes, churn signals
A view with no data gets marked "n/a" and named in the appendix. It does not silently vanish.
读取 
reference/thresholds.md
以了解各项阈值。计算每个视图，并为其指定状态。
  1. 渠道趋势 — 本期各渠道收入与上期相比，并在数据可用时与去年同期相比
  2. 漏斗转化 — 进入的线索、合格线索、商机、赢单；各环节之间的转化率，以及最大流失发生在哪一环节
  3. 营销活动回报 — 每个营销活动的支出与归因收入，以及单条线索成本
  4. 产品表现 — 按收入和增长率分别列出前三名与后三名
  5. 客户情绪 — 近期评论评分、评论主题、纠纷和流失信号
某个视图没有数据时，标记为“n/a”并在附录中注明，不能悄悄省略。

Step 3 — Find the actual story

步骤 3 — 找出真正的故事

This is where the skill earns its keep. Five views on their own are still a dashboard. The job is to connect them.
The connections that matter most:
  • Spend rising while cost per lead rises means the channel is saturating, not scaling
  • Strong lead volume with falling win rate points at lead quality or response speed, not at marketing
  • One product carrying the whole trend means the growth is more fragile than the total suggests
  • Sentiment dropping while revenue holds is the early warning that shows up in revenue two months later
  • A stage where the funnel drops off sharply is usually worth more than any new campaign
Look for the single sentence that explains the period. Lead with it.
这正是这个 skill 发挥价值的地方。五个视图单独来看仍然只是 dashboard，关键是把它们关联起来。
最重要的关联包括：
  • 支出上升，同时单条线索成本也在上升，意味着该渠道正在饱和，而不是在扩张
  • 线索量充足，但赢单率下降，说明问题更可能出在线索质量或响应速度，而不是营销本身
  • 某个产品撑起了整个趋势，意味着增长比总量所显示的更加脆弱
  • 客户情绪下降，但收入仍保持稳定，这是会在两个月后反映到收入上的早期预警
  • 漏斗在某个阶段急剧流失，通常比任何新营销活动都更值得优先处理
寻找能够解释这一时期的那一句话，并以它开篇。

Step 4 — Write the three actions

步骤 4 — 写出三项行动

Every pulse ends with exactly three actions. Not five, not a list of everything noticed.
Each action needs three things or it isn't an action:
  • What to do — specific enough to start today
  • Why — the number from this pulse that justifies it
  • What it's worth — the rough size of the opportunity or the risk
Rank them by size of impact, not by ease. Owners can decide what's easy; only this pulse can tell them what's big.
If the honest answer is that nothing needs to change, say that. A pulse that manufactures three actions every week trains the owner to ignore them.
每次 pulse 都必须以恰好三项行动结束。不是五项，也不是把所有发现都列出来。
每项行动都必须包含以下三项，否则就不算行动：
  • 具体做什么 — 细化到今天就能开始
  • 为什么做 — 使用本次 pulse 中能够证明该行动合理的数据
  • 价值有多大 — 估算机会或风险的大致规模
按影响规模排序，而不是按实施难度。什么容易做由业主决定；只有 pulse 能告诉业主哪些事项影响最大。
如果诚实的结论是什么都不需要改变，就直说。每周硬凑出三项行动，只会训练业主忽略它们。

Step 5 — Compose

步骤 5 — 组织内容

Use the exact structure in 
reference/output_template.md
. Include only sections with real data.
Writing rules:
  • Numbers lead, words follow. Not "paid social performed well" — "paid social drove 41 leads at USD 18 each, down from USD 31 last month."
  • Every number carries its comparison. A figure with no baseline is a missed insight.
  • Name the specific campaign, product, channel, or customer. "Some campaigns underperformed" is unusable.
  • No marketing vocabulary the owner doesn't use. Not "top of funnel velocity" — "how many new leads came in and how fast."
  • If a section has nothing worth saying, write "No material change" and move on.
使用 
reference/output_template.md
中的精确结构。只保留确实有数据的章节。
写作规则：
  • 数字在前，文字在后。不要写“付费社交表现良好”，而要写“付费社交带来了 41 条线索，每条成本 USD 18，较上月每条 USD 31 有所下降。”
  • 每个数字都要带上比较基准。没有基线的数字就等于漏掉了一个洞察。
  • 点明具体的营销活动、产品、渠道或客户。“某些营销活动表现不佳”无法使用。
  • 不要使用业主不会说的营销术语。不要写“漏斗顶部速度”，而要写“来了多少新线索，以及速度有多快”。
  • 如果某个章节没有值得说明的内容，写“无重大变化”并继续。

Step 6 — Deliver the pulse page

步骤 6 — 交付 pulse 页面

Alongside the chat pulse — additive, never a replacement — deliver the full pulse per the owner's stored output preference — never default to a markdown file. Check the 
## Business context
block's 
Output preference
(shared style guide rule, 
../../shared/artifact-style.md
):
  • Visual artifact (the default): render the pulse as an HTML page in the house style. Each of the five views gets a panel; revenue trend, cost per lead, and win rate are stat tiles with their comparison as the context line; campaign return and product performance are tables with tabular-nums spend and revenue columns; each view's status becomes a status pill (good, warn, critical, or n/a in plain text); the three actions close the page in their own panel, ranked.
  • docx / md / notion / canva preference: deliver the same content in that form — a DOCX or markdown file, a Notion page created via the connector (named destination, never overwriting), or a Canva Doc created via the Canva connector (a new design each run, named with the date; tables become lists); fall back to the visual artifact if Notion or Canva is not connected — and say that is why.
  • Best for skill: use the visual artifact — five views compare best side by side on one screen.
除聊天中的 pulse 外——它是补充，绝非替代——还要按照业主保存的输出偏好交付完整 pulse，绝不能默认输出为 markdown 文件。检查 
## Business context
区块中的 
Output preference
（共享样式指南规则，见 
../../shared/artifact-style.md
）：
  • 可视化 artifact（默认）： 按统一的内部风格将 pulse 渲染为 HTML 页面。五个视图各使用一个面板；收入趋势、单条线索成本和赢单率采用 stat tile，并将比较值放在 context line 中；营销活动回报和产品表现使用表格，支出和收入列采用 tabular-nums；每个视图的状态变为 status pill（以纯文本显示 good、warn、critical 或 n/a）；三项行动在页面末尾的独立面板中按影响排序。
  • docx / md / notion / canva 偏好： 以对应形式交付相同内容——DOCX 或 markdown 文件、通过 connector 创建的 Notion 页面（指定目标位置，绝不覆盖），或通过 Canva connector 创建的 Canva Doc（每次运行都创建新设计，并以日期命名；表格转为列表）；如果未连接 Notion 或 Canva，则回退到可视化 artifact，并说明回退原因。
  • 此 skill 的最佳形式： 使用可视化 artifact——五个视图可在同一屏幕中并排比较。

Step 7 — Offer to save, once

步骤 7 — 提供一次保存选项

After presenting, offer once to save the pulse as a file or post it to Slack. Posting to Slack is an outward write, so it only happens on that explicit yes — the offer is the approval gate. If yes, do it. If no or no response, move on. Do not ask twice.
Then close with what the pulse found in one line, plus the single most relevant next step and at most two others nearby:
  • If the actions point at content or promotion: "what should I promote" runs 
    content-strategy
    .
  • If the funnel is the problem: "fill my funnel" runs 
    /grow-pipeline
    .
  • For the finance-side twin: "how's the business doing" runs 
    business-pulse
    .
Max three offers. Never repeat an offer the owner declined this session.
展示结果后，只提供一次将 pulse 保存为文件或发布到 Slack 的选项。向 Slack 发布属于对外写入，因此只有在获得明确同意后才会执行——该选项需经明确同意方可执行。如果同意，就执行；如果拒绝或没有回应，则继续。不要询问第二次。
然后用一行总结 pulse 的发现，并给出唯一最相关的下一步，以及最多两个相邻选项：
  • 如果行动指向内容或推广：“我应该推广什么”会运行 
    content-strategy
    。
  • 如果问题是漏斗：“填补我的漏斗”会运行 
    /grow-pipeline
    。
  • 对于财务侧对应 skill：“我的业务表现如何”会运行 
    business-pulse
    。
最多提供三个选项。绝不重复业主在本次会话中拒绝过的选项。

Scope variants

范围变体

Owners often want a slice rather than the whole pulse:
  • "How did the campaign do" — campaign return only, plus the sentiment check
  • "How's the pipeline" — funnel conversion and stalled deals only
  • "What's selling" — product performance only
  • "Are we getting reviews" — sentiment only
  • "Where should I spend next month" — channel trend and campaign return, with the three actions weighted toward budget
Give them the slice they asked for. Don't force the full pulse on a narrow question.
业主通常只想要完整 pulse 的一个切片：
  • “营销活动表现如何” — 仅查看营销活动回报，并附加客户情绪检查
  • “销售管道情况如何” — 仅查看漏斗转化和停滞商机
  • “哪些产品卖得好” — 仅查看产品表现
  • “我们有收到评论吗” — 仅查看客户情绪
  • “下个月应该把预算花在哪里” — 查看渠道趋势和营销活动回报，三项行动侧重预算分配
按业主所求提供对应切片，不要在范围狭窄的问题上强推完整 pulse。

What not to do

禁止事项

  • Do not ask permission before pulling data. The skill was invoked. Run it.
  • Do not invent attribution. If a campaign's revenue can't be traced, say the attribution is unavailable rather than assigning revenue on a guess. Fake attribution has moved real budgets.
  • Do not report CRM forecast value as revenue. Deal values are hopes; invoices are facts. Label which is which.
  • Do not double-count across sources. A Shopify order settled in Stripe is one sale. Pick one revenue source and name it.
  • Do not double-count inside one source. The sales-by-customer summary returns both a parent summary row and a separate total row for the same customer. Filter rows marked as totals before you rank customers or compute concentration, or the same customer lands in the list twice and the concentration figure comes out too high.
  • Do not manufacture urgency. If growth is steady, the pulse should read as steady.
  • Do not read expenses or margin from the QuickBooks P&L summary. Total the rows (
    ../../shared/quickbooks-report-traps.md
    , Trap 2).
  • 拉取数据前不要请求许可。 该 skill 已被调用，直接运行。
  • 不要编造归因。 如果无法追踪某个营销活动的收入，就说明无法归因，而不是凭猜测分配收入。虚假归因已经导致真实预算被错误调整。
  • 不要把 CRM 预测值当作收入报告。 商机金额只是期望，发票才是事实。必须明确标注所报数字属于哪一种。
  • 不要跨数据源重复计数。 在 Stripe 中结算的 Shopify 订单是一笔销售。选择一个收入数据源并明确说明。
  • 不要在同一数据源内部重复计数。 按客户汇总的销售数据会同时返回父级汇总行和同一客户的独立总计行。对客户进行排名或计算集中度前，应过滤标记为 totals 的行，否则同一客户会在列表中出现两次，导致集中度数值偏高。
  • 不要制造紧迫感。 如果增长平稳，pulse 就应如实呈现增长平稳。
  • 不要从 QuickBooks P&L 汇总中读取支出或利润率。 应汇总各行（
    ../../shared/quickbooks-report-traps.md
    ，Trap 2）。

Reference files

参考文件

  • reference/data_sources.md
    — connector to metric mapping, with fallbacks
  • reference/thresholds.md
    — status cutoffs for each of the five views
  • reference/output_template.md
    — exact output structure
  • reference/gotchas.md
    — the failure modes that produce confidently wrong growth advice
  • reference/data_sources.md
    — connector 与指标的映射，以及回退方案
  • reference/thresholds.md
    — 五个视图各自的状态阈值
  • reference/output_template.md
    — 精确的输出结构
  • reference/gotchas.md
    — 导致自信地给出错误增长建议的失败模式

Using a tool that isn't listed

使用未列出的工具

The connectors named in this skill are the tested paths, not a wall. If the owner wants this flow to use a tool that isn't connected or listed, offer 
build-connector
— it checks the connector directory first and connects through Zapier otherwise, never hand-building against a raw API. Once the connection exists, the tool joins this skill like any other optional connector, under the same approval gates.
此 skill 中列出的 connector 是经过测试的路径，并不是硬性限制。如果业主希望此流程使用尚未连接或未列出的工具，可以提供 
build-connector
——它会先检查 connector 目录；如果没有匹配项，则通过 Zapier 建立连接，绝不直接针对原始 API 手工构建。连接建立后，该工具会像其他可选 connector 一样加入此 skill，并遵循相同的审批门控。