sales-performance-review

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Sales Performance Review

销售业绩复盘

The all-up periodic report. Every other analytics composite looks at one slice — a single campaign's emails, or the pipeline's current state. This one answers the question a founder or sales leader asks in every team meeting: "What did we do this period, and did it move the needle?"
It inventories every sales initiative, measures each one's contribution to pipeline and revenue, compares them against each other, and produces a presentation-ready report that the team can review together.
What makes this different from
pipeline-review
and
sequence-performance
:
CompositeScopeQuestion It Answers
sequence-performance
One email campaign"Is this specific campaign working?"
pipeline-review
Pipeline state"What does our pipeline look like right now?"
sales-performance-review
ALL initiatives across the period"What did we do, what worked, and where should we invest next?"
This composite can call
sequence-performance
for deeper campaign-level diagnosis and
pipeline-review
for pipeline state — but its primary job is the cross-initiative view.
这是一份全面的定期报告。其他分析工具通常只聚焦单一维度——比如某一个营销活动的邮件数据,或是当前pipeline的状态。而本工具则能回答创始人或销售负责人在每次团队会议上都会提出的核心问题:“我们在这段时间做了什么?这些举措是否带来了实际成效?”
它会盘点所有销售举措,衡量每项举措对pipeline和收入的贡献,进行跨举措对比,并生成可直接用于团队复盘的演示报告。
本工具与
pipeline-review
sequence-performance
的区别:
工具组件覆盖范围解决的核心问题
sequence-performance
单一邮件营销活动“这个特定的营销活动是否有效?”
pipeline-review
pipeline当前状态“我们当前的pipeline情况如何?”
sales-performance-review
周期内所有销售举措“我们做了什么、哪些有效、未来该如何投入?”
本工具可调用
sequence-performance
进行更深入的活动级诊断,也可调用
pipeline-review
查看pipeline状态——但其核心价值在于跨举措的全局视角。

When to Auto-Load

何时自动加载

Load this composite when:
  • User says "sales review", "periodic review", "what did we do this month", "team performance report", "sales standup report"
  • User says "prepare for the weekly/monthly/quarterly sales meeting"
  • User asks "what's working", "where should we focus", "are our initiatives paying off"
  • End of period (weekly, biweekly, monthly, quarterly) review is due

当出现以下场景时,加载本工具:
  • 用户提及“销售复盘”、“定期回顾”、“我们这个月做了什么”、“团队业绩报告”、“销售站会报告”
  • 用户提及“准备周/月/季度销售会议材料”
  • 用户询问“哪些举措有效”、“我们该聚焦什么”、“我们的举措是否有回报”
  • 周/双周/月/季度等周期复盘节点到来

Step 0: Configuration (One-Time Setup)

步骤0:配置(一次性设置)

On first run, collect and store these preferences. Skip on subsequent runs.
首次运行时,收集并存储以下偏好设置,后续运行可跳过此步骤。

Data Sources

数据源

QuestionPurposeStored As
Where do you track deals/pipeline?Pipeline attribution
crm_tool
What outreach tools do you use?Campaign data pull
outreach_tools
(list)
Do you track initiatives anywhere? (spreadsheet, Notion, project tool)Initiative inventory
initiative_tracker
What other sales channels are active?Ensure complete coverage
active_channels
Common
active_channels
:
active_channels: [
  "outbound_email",        # Cold email campaigns
  "outbound_linkedin",     # LinkedIn outreach
  "inbound_content",       # Blog, SEO, content marketing
  "inbound_website",       # Website conversions, demo requests
  "events",                # Conferences, webinars, meetups
  "referrals",             # Partner/customer referrals
  "paid_ads",              # Google Ads, LinkedIn Ads, Meta Ads
  "social_organic",        # LinkedIn posts, Twitter, community
  "partnerships",          # Co-selling, integrations, channel
  "product_led",           # Free trial, freemium, PLG
  "warm_outbound"          # Re-engagement, nurture, expansion
]
问题目的存储字段
你在哪里跟踪客户成交和pipeline数据?Pipeline归因
crm_tool
你使用哪些外拓工具?营销活动数据提取
outreach_tools
(列表)
你是否在其他地方跟踪销售举措?(如电子表格、Notion、项目管理工具)举措盘点
initiative_tracker
还有哪些活跃的销售渠道?确保覆盖所有渠道
active_channels
常见
active_channels
active_channels: [
  "outbound_email",        # 冷邮件营销活动
  "outbound_linkedin",     # LinkedIn外拓
  "inbound_content",       # 博客、SEO、内容营销
  "inbound_website",       # 网站转化、演示请求
  "events",                # 行业会议、线上研讨会、线下聚会
  "referrals",             # 合作伙伴/客户推荐
  "paid_ads",              # Google Ads、LinkedIn Ads、Meta Ads
  "social_organic",        # LinkedIn帖子、Twitter、社区运营
  "partnerships",          # 联合销售、集成合作、渠道合作
  "product_led",           # 免费试用、免费增值、PLG
  "warm_outbound"          # 再触达、培育、拓展
]

Team & Goals

团队与目标

QuestionPurposeStored As
Who is on the sales team? (names + roles)Per-rep breakdown
team_members
What are the period targets?Gap analysis
targets
What is the review cadence?Default period length
review_cadence
Who is the audience for this report?Adjust depth/tone
report_audience
Targets structure:
targets: {
  meetings_booked: integer | null
  qualified_opportunities: integer | null
  pipeline_created: number | null       # Dollar value
  deals_closed: integer | null
  revenue_closed: number | null
  other: [                              # Custom KPIs
    { name: string, target: number }
  ]
}
Report audience options:
  • "team"
    — Sales team standup. Tactical, action-oriented. "What do we do next week?"
  • "leadership"
    — VP/Founder review. Strategic, trend-focused. "Are we on track? Where to invest?"
  • "board"
    — Board/investor update. High-level, metric-heavy. "Is the GTM motion working?"
问题目的存储字段
销售团队成员有哪些?(姓名+角色)按销售代表细分数据
team_members
本周期的目标是什么?差距分析
targets
复盘的频率是?默认周期长度
review_cadence
报告的受众是谁?调整报告深度与语气
report_audience
目标结构:
targets: {
  meetings_booked: integer | null
  qualified_opportunities: integer | null
  pipeline_created: number | null       # 金额
  deals_closed: integer | null
  revenue_closed: number | null
  other: [                              # 自定义KPI
    { name: string, target: number }
  ]
}
报告受众选项:
  • "team"
    — 销售团队站会。侧重战术、行动导向。聚焦“下周我们要做什么?”
  • "leadership"
    — 副总裁/创始人复盘。侧重战略、趋势分析。聚焦“我们是否在正轨上?该往哪里投?”
  • "board"
    — 董事会/投资人更新。侧重高层视角、数据驱动。聚焦“GTM策略是否有效?”

Initiative Categories

举措分类

Define the categories of initiatives the team runs. This creates the taxonomy for the report.
initiative_categories: [
  {
    name: "Outbound Email Campaigns"
    data_source: "smartlead"           # or "instantly", "outreach", etc.
    metrics_available: ["sent", "opens", "replies", "meetings"]
  },
  {
    name: "LinkedIn Outreach"
    data_source: "manual_tracking"     # or "dripify", "expandi"
    metrics_available: ["connections_sent", "accepted", "replies", "meetings"]
  },
  {
    name: "Events & Webinars"
    data_source: "spreadsheet"
    metrics_available: ["attended", "leads_captured", "meetings", "pipeline"]
  },
  {
    name: "Inbound / Content"
    data_source: "hubspot"             # or "website_analytics"
    metrics_available: ["visitors", "leads", "mqls", "meetings"]
  },
  {
    name: "Referrals & Partnerships"
    data_source: "crm"
    metrics_available: ["intros", "meetings", "pipeline", "closed"]
  }
]
Store config in:
clients/<client-name>/config/sales-performance-review.json
or equivalent.

定义团队开展的销售举措类别,为报告创建分类体系。
initiative_categories: [
  {
    name: "Outbound Email Campaigns"
    data_source: "smartlead"           # 或"instantly", "outreach"等
    metrics_available: ["sent", "opens", "replies", "meetings"]
  },
  {
    name: "LinkedIn Outreach"
    data_source: "manual_tracking"     # 或"dripify", "expandi"
    metrics_available: ["connections_sent", "accepted", "replies", "meetings"]
  },
  {
    name: "Events & Webinars"
    data_source: "spreadsheet"
    metrics_available: ["attended", "leads_captured", "meetings", "pipeline"]
  },
  {
    name: "Inbound / Content"
    data_source: "hubspot"             # 或"website_analytics"
    metrics_available: ["visitors", "leads", "mqls", "meetings"]
  },
  {
    name: "Referrals & Partnerships"
    data_source: "crm"
    metrics_available: ["intros", "meetings", "pipeline", "closed"]
  }
]
配置存储路径:
clients/<client-name>/config/sales-performance-review.json
或等效位置。

Step 1: Inventory All Initiatives

步骤1:盘点所有销售举措

Purpose: Build a complete inventory of every sales initiative executed during the review period. Nothing should be missing from the report.
目的: 构建复盘周期内所有销售举措的完整清单,确保无遗漏。

Input Contract

输入约定

period: {
  type: "weekly" | "fortnightly" | "monthly" | "quarterly" | "custom"
  start_date: string
  end_date: string
  comparison_period: boolean          # Default: true
}
initiative_categories: [...]          # From config
data_sources: { ... }                 # From config
period: {
  type: "weekly" | "fortnightly" | "monthly" | "quarterly" | "custom"
  start_date: string
  end_date: string
  comparison_period: boolean          # 默认:true
}
initiative_categories: [...]          # 来自配置
data_sources: { ... }                 # 来自配置

Process

流程

For each initiative category, pull the list of specific initiatives run during the period:
针对每个举措类别,提取周期内开展的具体举措列表:

A) Outbound Email Campaigns

A) 外拓邮件营销活动

Pull from configured outreach tool:
ToolHow to List Campaigns
Smartlead
get_campaigns
→ filter by date range
InstantlyAPI or CSV export of campaigns active in period
OthersAPI, CSV, or user provides list
For each campaign, capture:
  • Campaign name
  • Launch date
  • Status (active / paused / completed)
  • Target audience description
  • Total leads loaded
  • Current metrics snapshot (sent, opens, replies — detailed analysis comes in Step 3)
从配置的外拓工具中提取:
工具如何列出活动
Smartlead
get_campaigns
→ 按日期范围筛选
InstantlyAPI或CSV导出周期内活跃的活动
其他工具API、CSV或用户提供列表
针对每个活动,收集:
  • 活动名称
  • 启动日期
  • 状态(活跃/暂停/已完成)
  • 目标受众描述
  • 加载的潜在客户总数
  • 当前指标快照(发送量、打开量、回复量——详细分析见步骤3)

B) LinkedIn Outreach

B) LinkedIn外拓

Pull from LinkedIn automation tool or manual tracking:
  • Campaign/sequence name
  • Connection requests sent
  • Messages sent
  • Period of activity
从LinkedIn自动化工具或手动追踪中提取:
  • 活动/序列名称
  • 发送的好友请求数
  • 发送的消息数
  • 活动周期

C) Events & Webinars

C) 线下活动与线上研讨会

Pull from tracking spreadsheet, CRM, or user provides:
  • Event name
  • Date
  • Type (conference, webinar, meetup, hosted event)
  • Attendees/leads captured
  • Follow-up status
从追踪电子表格、CRM或用户提供的信息中提取:
  • 活动名称
  • 日期
  • 类型(行业会议、线上研讨会、线下聚会、自有活动)
  • 捕获的参会者/潜在客户数
  • 跟进状态

D) Inbound / Content

D) 内拓/内容营销

Pull from website analytics, CRM, or marketing tool:
  • Content published (blog posts, case studies, whitepapers)
  • Website traffic / lead form submissions
  • Demo requests
  • MQL count
从网站分析工具、CRM或营销工具中提取:
  • 发布的内容(博客文章、案例研究、白皮书)
  • 网站流量/潜在客户表单提交量
  • 演示请求数
  • MQL数量

E) Referrals & Partnerships

E) 推荐与合作伙伴

Pull from CRM or manual tracking:
  • Referral sources (who referred)
  • Intro count
  • Meeting count
从CRM或手动追踪中提取:
  • 推荐来源(谁推荐的)
  • 引荐数
  • 会议数

F) Any Other Initiatives

F) 其他举措

Ask the user: "Were there any other sales initiatives this period not captured above?"
  • Ad campaigns launched
  • Product-led growth experiments
  • New channel tests
  • One-off outreach efforts (conference follow-up blast, etc.)
询问用户:“本周期是否还有上述未覆盖的其他销售举措?”
  • 启动的广告活动
  • 产品驱动增长实验
  • 新渠道测试
  • 一次性外拓工作(如会议跟进邮件群发等)

Output Contract

输出约定

initiative_inventory: [
  {
    id: string                         # Generated identifier
    name: string                       # Initiative name
    category: string                   # Which category it belongs to
    channel: string                    # "email", "linkedin", "event", "inbound", "referral", etc.
    launch_date: string
    status: "active" | "paused" | "completed"
    description: string                # 1-2 sentence summary of what this initiative was
    target_audience: string            # Who it was aimed at
    data_source: string                # Where the data came from
    raw_data_available: boolean        # Can we pull detailed metrics?
  }
]
initiative_inventory: [
  {
    id: string                         # 生成的唯一标识
    name: string                       # 举措名称
    category: string                   # 所属类别
    channel: string                    # "email", "linkedin", "event", "inbound", "referral"等
    launch_date: string
    status: "active" | "paused" | "completed"
    description: string                # 1-2句话总结举措内容
    target_audience: string            # 目标受众
    data_source: string                # 数据来源
    raw_data_available: boolean        # 是否可提取详细指标
  }
]

Human Checkpoint

人工校验点

undefined
undefined

Initiative Inventory — [Period]

举措盘点 — [周期]

Found X initiatives across Y categories:
#InitiativeCategoryChannelLaunchedStatus
1Q1 Series A OutboundOutbound EmailEmailJan 15Active
2LinkedIn ABM CampaignLinkedIn OutreachLinkedInJan 20Active
3SaaStr ConferenceEventIn-personFeb 5Completed
4Blog: "State of X" reportInbound ContentContentFeb 10Active
5Partner intro program w/ AcmeReferralPartnerJan 1Active
Missing anything? Any initiatives not captured here?

---
在Y个类别中发现X项举措:
序号举措类别渠道启动日期状态
1Q1 A轮外拓邮件外拓邮件Email1月15日活跃
2LinkedIn ABM营销活动LinkedIn外拓LinkedIn1月20日活跃
3SaaStr行业会议线下活动线下2月5日已完成
4博客:《X行业现状报告》内拓内容内容2月10日活跃
5与Acme的合作伙伴引荐计划推荐合作合作伙伴1月1日活跃
是否有遗漏?是否有未被捕获的其他举措?

---

Step 2: Pull Initiative-Level Metrics

步骤2:提取举措级指标

Purpose: For each initiative in the inventory, pull the detailed performance metrics. This is the data collection step — no analysis yet.
目的: 为盘点中的每项举措提取详细业绩指标,此步骤仅做数据收集,暂不分析。

Input Contract

输入约定

initiative_inventory: [...]           # From Step 1
period: { ... }
outreach_tools: [...]                 # From config
crm_tool: string                     # From config
initiative_inventory: [...]           # 来自步骤1
period: { ... }
outreach_tools: [...]                 # 来自配置
crm_tool: string                     # 来自配置

Process

流程

For each initiative, pull metrics appropriate to its channel:
针对每项举措,提取与其渠道匹配的指标:

Outbound Email Metrics

外拓邮件指标

MetricSource
Emails sentOutreach tool
Unique recipientsOutreach tool
Open rateOutreach tool
Reply rateOutreach tool
Positive reply rateOutreach tool (if categorized) or estimate from reply analysis
Bounce rateOutreach tool
Meetings bookedOutreach tool + CRM cross-reference
Pipeline created ($)CRM — deals sourced from this campaign
Deals won ($)CRM — closed deals sourced from this campaign
指标来源
发送邮件数外拓工具
唯一收件人数外拓工具
打开率外拓工具
回复率外拓工具
正向回复率外拓工具(若已分类)或通过回复分析估算
退信率外拓工具
预约会议数外拓工具 + CRM交叉验证
创建的pipeline金额CRM — 来自该活动的成交机会
赢单金额CRM — 来自该活动的已成交订单

LinkedIn Outreach Metrics

LinkedIn外拓指标

MetricSource
Connection requests sentLinkedIn tool or manual count
Connections acceptedLinkedIn tool
Accept rateCalculated
Messages sentLinkedIn tool
Replies receivedLinkedIn tool
Reply rateCalculated
Meetings bookedManual tracking or CRM
Pipeline created ($)CRM
指标来源
发送的好友请求数LinkedIn工具或手动统计
通过的好友请求数LinkedIn工具
通过率计算得出
发送的消息数LinkedIn工具
收到的回复数LinkedIn工具
回复率计算得出
预约会议数手动追踪或CRM
创建的pipeline金额CRM

Event Metrics

线下活动指标

MetricSource
Attendees / leads capturedEvent tool, badge scans, signup list
Follow-ups sentOutreach tool or manual
Meetings booked from eventCRM or manual
Pipeline created ($)CRM
Cost of eventFinance/budget tracking
Cost per meetingCalculated
指标来源
参会者/捕获的潜在客户数活动工具、胸牌扫描、报名列表
发送的跟进数外拓工具或手动统计
从活动中预约的会议数CRM或手动统计
创建的pipeline金额CRM
活动成本财务/预算追踪
每会议成本计算得出

Inbound / Content Metrics

内拓/内容营销指标

MetricSource
Content pieces publishedCMS or manual count
Website visitors (organic)Analytics tool
Lead form submissionsCRM or marketing tool
Demo requestsCRM
MQLs generatedCRM or marketing tool
Pipeline created ($)CRM
指标来源
发布的内容数量CMS或手动统计
网站访客(自然流量)分析工具
潜在客户表单提交量CRM或营销工具
演示请求数CRM
生成的MQL数量CRM或营销工具
创建的pipeline金额CRM

Referral / Partnership Metrics

推荐/合作伙伴指标

MetricSource
Intros receivedManual tracking or CRM
Meetings from introsCRM
Conversion rate (intro → meeting)Calculated
Pipeline created ($)CRM
Deals won ($)CRM
指标来源
收到的引荐数手动追踪或CRM
来自引荐的会议数CRM
转化率(引荐→会议)计算得出
创建的pipeline金额CRM
赢单金额CRM

Pipeline Attribution

Pipeline归因

Critical step: Connect initiatives to pipeline and revenue. For each deal in the CRM created during the period:
  • What initiative sourced it? (first touch attribution)
  • What initiative influenced it? (multi-touch, if trackable)
  • Current stage
  • Dollar value
This creates the bridge between "what we did" and "what it produced."
Attribution methods (use the best available):
MethodAccuracyWhen to Use
CRM source fieldHighIf reps consistently tag lead source
Campaign ID matchHighIf outreach tool logs campaign ID on the deal
Email/name matchMediumMatch deal contact email to campaign lead lists
Time-based proximityLowDeal created within 7 days of an initiative = attributed
Ask the userHighFor small volume, just ask "where did this deal come from?"
关键步骤: 将举措与pipeline和收入关联。针对周期内CRM中的每个成交机会:
  • 哪个举措是其来源?(首次触点归因)
  • 哪个举措影响了它?(多触点归因,若可追踪)
  • 当前阶段
  • 金额
这一步搭建了“我们做了什么”和“产生了什么结果”之间的桥梁。
归因方法(使用可用的最优方法):
方法准确性使用场景
CRM来源字段若销售代表持续标记潜在客户来源
活动ID匹配若外拓工具在成交机会上记录了活动ID
邮箱/姓名匹配将成交机会联系人邮箱与活动潜在客户列表匹配
时间 proximity成交机会在举措开展后7天内创建 = 归因于该举措
询问用户对于小体量业务,直接问“这个成交机会来自哪里?”

Output Contract

输出约定

initiative_metrics: [
  {
    id: string                         # Matches inventory
    name: string
    category: string
    channel: string
    metrics: {
      # Activity metrics (what we did)
      activity_volume: integer          # Emails sent, connections sent, leads captured, etc.
      activity_label: string            # "emails sent", "connections sent", etc.

      # Response metrics (what happened)
      responses: integer                # Replies, accepts, form fills, etc.
      response_rate: percentage
      response_label: string            # "replies", "accepted", "submitted", etc.

      # Meeting metrics (pipeline entry)
      meetings_booked: integer
      meeting_rate: percentage           # Meetings / activity_volume
      meetings_qualified: integer | null
      qualification_rate: percentage | null

      # Pipeline metrics (business impact)
      pipeline_created: number | null    # Dollar value
      deals_created: integer | null
      avg_deal_size: number | null

      # Revenue metrics (if deals closed)
      deals_won: integer | null
      revenue_closed: number | null

      # Efficiency metrics
      cost: number | null                # If cost data available
      cost_per_meeting: number | null
      cost_per_pipeline_dollar: number | null
      roi: number | null                 # Revenue / cost

      # Comparison period
      vs_prior: {
        activity_change: percentage
        response_rate_change: percentage
        meetings_change: percentage
        pipeline_change: percentage
      } | null
    }
  }
]
initiative_metrics: [
  {
    id: string                         # 与盘点中的ID匹配
    name: string
    category: string
    channel: string
    metrics: {
      # 活动指标(我们做了什么)
      activity_volume: integer          # 发送邮件数、好友请求数、捕获的潜在客户数等
      activity_label: string            # “发送邮件数”、“好友请求数”等

      # 响应指标(发生了什么)
      responses: integer                # 回复数、通过数、表单提交数等
      response_rate: percentage
      response_label: string            # “回复数”、“通过数”、“提交数”等

      # 会议指标(pipeline入口)
      meetings_booked: integer
      meeting_rate: percentage           # 会议数 / 活动量
      meetings_qualified: integer | null
      qualification_rate: percentage | null

      # Pipeline指标(业务影响)
      pipeline_created: number | null    # 金额
      deals_created: integer | null
      avg_deal_size: number | null

      # 收入指标(若有成交)
      deals_won: integer | null
      revenue_closed: number | null

      # 效率指标
      cost: number | null                # 若有成本数据
      cost_per_meeting: number | null
      cost_per_pipeline_dollar: number | null
      roi: number | null                 # 收入 / 成本

      # 对比周期
      vs_prior: {
        activity_change: percentage
        response_rate_change: percentage
        meetings_change: percentage
        pipeline_change: percentage
      } | null
    }
  }
]

Human Checkpoint

人工校验点

undefined
undefined

Metrics Pulled

已提取的指标

InitiativeActivityResponsesMeetingsPipelineRevenue
Q1 Series A Outbound2,500 sent125 replies (5%)18$240K$0
LinkedIn ABM300 requests180 accepted (60%)8$120K$45K
SaaStr Conference150 leads45 follow-ups12$180K$0
Blog content5 posts28 leads4$50K$0
Partner intros15 intros12 meetings12$200K$80K
Pipeline attribution notes:
  • X deals could not be attributed to a specific initiative
  • Y deals have multi-touch attribution (counted in primary source)
Data look accurate? Any corrections?

---
举措活动量响应数会议数Pipeline收入
Q1 A轮外拓邮件2500封125次回复(5%)18次$240K$0
LinkedIn ABM活动300次请求180次通过(60%)8次$120K$45K
SaaStr行业会议150个潜在客户45次跟进12次$180K$0
博客内容5篇28个潜在客户4次$50K$0
合作伙伴引荐15次引荐12次会议12次$200K$80K
Pipeline归因说明:
  • X个成交机会无法归因到特定举措
  • Y个成交机会为多触点归因(计入主要来源)
数据是否准确?是否需要修正?

---

Step 3: Analyze Initiative Performance

步骤3:分析举措业绩

Purpose: Score each initiative, compare them against each other, and identify what's working, what's not, and where the gaps are. Pure LLM reasoning + computation.
目的: 为每项举措打分,进行跨举措对比,识别有效举措、无效举措及差距。纯LLM推理+计算。

Input Contract

输入约定

initiative_metrics: [...]             # From Step 2
targets: { ... }                      # From config
team_members: [...]                   # From config
period: { ... }
initiative_metrics: [...]             # 来自步骤2
targets: { ... }                      # 来自配置
team_members: [...]                   # 来自配置
period: { ... }

Analysis Sections

分析模块

A) Initiative Scorecards

A) 举措评分卡

For each initiative, produce a scorecard:
Initiative: [Name]
Category: [Category] | Channel: [Channel]
Status: [Active/Paused/Completed]

Activity:    [X sent/captured/etc.]    [+/-Y% vs prior]
Response:    [X replies/accepts]       [Z% rate] [above/at/below benchmark]
Meetings:    [X booked]               [Z% conversion]
Pipeline:    $[X]                     [+/-Y% vs prior]
Revenue:     $[X]                     [if applicable]
Efficiency:  $[X] cost per meeting    [if cost data available]

Grade: [A/B/C/D/F]
Verdict: [One sentence — "Strong performer, scale up" / "Underperforming, diagnose copy" / etc.]
Grading criteria:
GradeCriteria
AAbove benchmark on response rate AND meeting conversion AND pipeline creation. Clear ROI.
BAt or above benchmark on most metrics. Producing pipeline. Room to optimize.
CMixed results. Some metrics above, some below. Needs specific fixes.
DBelow benchmark on most metrics. Producing minimal pipeline. Needs overhaul or kill decision.
FFailing across all metrics. Negative ROI. Should be stopped or completely rebuilt.
为每项举措生成评分卡:
举措:[名称]
类别:[类别] | 渠道:[渠道]
状态:[活跃/暂停/已完成]

活动量:    [X 发送/捕获等]    [较上一周期 +/-Y%]
响应:    [X 回复/通过等]       [Z% 转化率] [高于/等于/低于基准]
会议:    [X 次预约]               [Z% 转化率]
Pipeline:    $[X]                     [较上一周期 +/-Y%]
收入:     $[X]                     [若适用]
效率:  $[X] 每会议成本    [若有成本数据]

评分:[A/B/C/D/F]
结论:[一句话总结 — “表现优异,应扩大规模” / “表现不佳,需优化文案” 等]
评分标准:
评分标准
A响应率、会议转化率、pipeline创建量均高于基准。ROI清晰。
B多数指标达到或高于基准。持续产生pipeline。有优化空间。
C结果参差不齐。部分指标高于基准,部分低于。需要针对性修复。
D多数指标低于基准。产生的pipeline极少。需要全面整改或考虑终止。
F所有指标均不达标。ROI为负。应立即停止或彻底重构。

B) Cross-Initiative Comparison

B) 跨举措对比

Rank all initiatives on consistent metrics:
Ranking DimensionWhy It Matters
Meetings per dollar (if cost data available)Which channel gives most meetings for the spend
Meetings per activity unitEmail sends vs. LinkedIn requests vs. event attendance — what converts best
Pipeline per meetingWhich channels produce bigger deals once meetings happen
Speed to pipelineTime from initiative start to first pipeline dollar
Win rate by sourceWhich channels produce deals that actually close
基于统一指标对所有举措排名:
排名维度重要性
每美元会议数(若有成本数据)哪个渠道的投入产出比最高
每活动单位会议数邮件发送、LinkedIn请求、活动参会等,哪个转化效果最好
每会议pipeline金额哪些渠道在预约会议后能产生更大的成交机会
pipeline生成速度从举措启动到首次产生pipeline的时间
按来源划分的赢单率哪些渠道产生的成交机会最终能成交

C) Funnel Analysis (Full Funnel View)

C) 漏斗分析(全局漏斗视图)

Map the complete funnel across ALL initiatives combined:
Total activity → Total responses → Total meetings → Qualified → Pipeline → Won
[X emails+      [Y replies+       [Z meetings]    [W qual]    [$P]      [$R]
 connections+    accepts+
 leads+etc.]     leads]

Conversion rates at each stage:
Activity → Response: X%
Response → Meeting: X%
Meeting → Qualified: X%
Qualified → Pipeline: X%
Pipeline → Won: X%
绘制所有举措合并后的完整漏斗:
总活动量 → 总响应数 → 总会议数 → 合格机会 → Pipeline → 赢单
[X 邮件+      [Y 回复+       [Z 会议]    [W 合格]    [$P]      [$R]
 好友请求+    通过+
 潜在客户+等]    潜在客户]

各阶段转化率:
活动量 → 响应:X%
响应 → 会议:X%
会议 → 合格机会:X%
合格机会 → Pipeline:X%
Pipeline → 赢单:X%

D) Gap Analysis

D) 差距分析

Compare actuals to targets:
TargetActualGapStatus
Meetings booked: XY+/-ZOn track / Behind / Ahead
Pipeline created: $X$Y+/-$ZOn track / Behind / Ahead
Revenue closed: $X$Y+/-$ZOn track / Behind / Ahead
If behind on any target:
  • Which initiatives need to increase output?
  • How much incremental activity is needed to close the gap?
  • At current conversion rates, how many more [emails/events/intros] to hit the target?
将实际结果与目标对比:
目标实际差距状态
预约会议数:XY+/-Z达标 / 落后 / 超额
创建的pipeline金额:$X$Y+/-$Z达标 / 落后 / 超额
成交收入:$X$Y+/-$Z达标 / 落后 / 超额
若任何目标未达标:
  • 哪些举措需要增加产出?
  • 需要多少增量活动才能填补差距?
  • 按当前转化率,需要多做多少[邮件/活动/引荐]才能达成目标?

E) Effort vs. Impact Matrix

E) 投入-产出矩阵

Classify each initiative into a 2x2:
                    HIGH IMPACT
    SCALE UP            │           OPTIMIZE
    (High impact,       │       (High impact,
     low effort)        │        high effort)
────────────────────────┼─────────────────────
    MAINTAIN            │           QUESTION
    (Low impact,        │       (Low impact,
     low effort)        │        high effort)
                    LOW IMPACT
  • Scale Up: High pipeline/meetings relative to effort. Pour fuel on this fire.
  • Optimize: Producing results but resource-intensive. Find ways to make it more efficient.
  • Maintain: Low effort, modest results. Keep running, don't invest more.
  • Question: High effort, low results. Diagnose why or shut it down.
将每项举措归入2x2矩阵:
                    高产出
    扩大规模            │           优化
    (高产出,       │       (高产出,
     低投入)        │        高投入)
────────────────────────┼─────────────────────
    维持现状            │           重新评估
    (低产出,        │       (低产出,
     低投入)        │        高投入)
                    低产出
  • 扩大规模: 相对于投入,pipeline/会议产出高。加大资源投入。
  • 优化: 有产出但资源消耗大。寻找更高效的方式。
  • 维持现状: 投入低,结果一般。继续运行,但不增加投入。
  • 重新评估: 投入高,产出低。诊断原因或终止。

F) Trend Analysis (If Comparison Period Available)

F) 趋势分析(若有对比周期)

MetricPrior PeriodCurrent PeriodTrendCommentary
Total meetingsXY+/-Z%[Accelerating/Decelerating]
Pipeline created$X$Y+/-Z%[context]
Best channel[channel][channel][Same/Shifted][context]
Qualification rateX%Y%+/-Z pts[context]
指标上一周期当前周期趋势说明
总会议数XY+/-Z%[加速/减速]
创建的pipeline金额$X$Y+/-Z%[背景说明]
最佳渠道[渠道][渠道][相同/变化][背景说明]
合格转化率X%Y%+/-Z个百分点[背景说明]

Output Contract

输出约定

analysis: {
  initiative_scorecards: [
    {
      id: string
      name: string
      category: string
      grade: "A" | "B" | "C" | "D" | "F"
      verdict: string
      key_metrics_summary: string
    }
  ]

  cross_initiative_ranking: {
    by_meetings_per_dollar: [ { name: string, value: number } ] | null
    by_meeting_conversion: [ { name: string, value: percentage } ]
    by_pipeline_per_meeting: [ { name: string, value: number } ] | null
    by_win_rate: [ { name: string, value: percentage } ] | null
    overall_best_performer: string
    overall_worst_performer: string
  }

  funnel: {
    total_activity: integer
    total_responses: integer
    total_meetings: integer
    total_qualified: integer | null
    total_pipeline: number | null
    total_won: number | null
    stage_conversions: [ { from: string, to: string, rate: percentage } ]
    biggest_drop_off: string          # Which stage loses the most
  }

  gap_analysis: {
    targets_summary: [ { metric: string, target: number, actual: number, gap: number, status: string } ]
    behind_on: string[]               # Which targets are behind
    incremental_needed: string        # "Need X more meetings from Y channel to close the gap"
  } | null

  effort_impact_matrix: {
    scale_up: [ { name: string, reason: string } ]
    optimize: [ { name: string, reason: string } ]
    maintain: [ { name: string, reason: string } ]
    question: [ { name: string, reason: string } ]
  }

  trends: {
    overall_direction: "improving" | "stable" | "declining"
    notable_shifts: string[]
  } | null
}

analysis: {
  initiative_scorecards: [
    {
      id: string
      name: string
      category: string
      grade: "A" | "B" | "C" | "D" | "F"
      verdict: string
      key_metrics_summary: string
    }
  ]

  cross_initiative_ranking: {
    by_meetings_per_dollar: [ { name: string, value: number } ] | null
    by_meeting_conversion: [ { name: string, value: percentage } ]
    by_pipeline_per_meeting: [ { name: string, value: number } ] | null
    by_win_rate: [ { name: string, value: percentage } ] | null
    overall_best_performer: string
    overall_worst_performer: string
  }

  funnel: {
    total_activity: integer
    total_responses: integer
    total_meetings: integer
    total_qualified: integer | null
    total_pipeline: number | null
    total_won: number | null
    stage_conversions: [ { from: string, to: string, rate: percentage } ]
    biggest_drop_off: string          # 流失最多的阶段
  }

  gap_analysis: {
    targets_summary: [ { metric: string, target: number, actual: number, gap: number, status: string } ]
    behind_on: string[]               # 未达标的目标
    incremental_needed: string        # “需要从Y渠道多获取X个会议来填补差距”
  } | null

  effort_impact_matrix: {
    scale_up: [ { name: string, reason: string } ]
    optimize: [ { name: string, reason: string } ]
    maintain: [ { name: string, reason: string } ]
    question: [ { name: string, reason: string } ]
  }

  trends: {
    overall_direction: "improving" | "stable" | "declining"
    notable_shifts: string[]
  } | null
}

Step 4: Generate Insights & Recommendations

步骤4:生成洞见与建议

Purpose: Distill the analysis into actionable insights — what to double down on, what to fix, what to kill, and what to start. Pure LLM reasoning.
目的: 将分析提炼为可执行的洞见——要加倍投入什么、要修复或终止什么、要启动什么。纯LLM推理。

Process

流程

A) What's Working (Double Down)

A) 有效举措(加倍投入)

Identify initiatives or patterns that are clearly producing results:
SignalRecommendation
Initiative has A/B grade + above-benchmark metrics"Scale [initiative]: increase volume by X%. It's converting at Y% — the highest across all channels."
One channel produces 50%+ of qualified meetings"Double down on [channel]. It accounts for X% of qualified meetings at Y cost per meeting."
Specific audience segment responding well"The [segment] audience converts at 2x the overall rate. Build a dedicated campaign for this segment."
Referral/partner channel has highest win rate"Invest in the referral program. Win rate is X% vs. Y% for cold outbound. Each intro is worth $Z in expected pipeline."
识别明显产生结果的举措或模式:
信号建议
举措评分为A/B且指标高于基准“扩大[举措]规模:将量提升X%。其转化率为Y%——是所有渠道中最高的。”
某一渠道贡献了50%+的合格会议“加倍投入[渠道]。它贡献了X%的合格会议,每会议成本为Y。”
特定受众群体响应良好“[细分群体]的转化率是整体的2倍。为该群体打造专属营销活动。”
推荐/合作伙伴渠道赢单率最高“投入到推荐计划。赢单率为X%,而冷外拓为Y%。每个引荐的预期pipeline为$Z。”

B) What's Not Working (Fix or Kill)

B) 无效举措(修复或终止)

SignalRecommendation
Initiative has D/F grade"Consider killing [initiative]. It's consumed [resources] and produced [minimal results]. Reallocate to [better performer]."
Channel has high activity but no pipeline"Diagnose [channel]. High volume (X sent) but near-zero pipeline. Either targeting, copy, or the channel itself isn't working."
Large gap between meetings and qualified meetings"Meeting quality issue. X meetings booked but only Y qualified (Z%). Review ICP targeting and qualification criteria."
High effort, low impact quadrant"[Initiative] is in the 'Question' quadrant. It's consuming [effort] for [minimal return]. Fix within 2 weeks or shut down."
信号建议
举措评分为D/F“考虑终止[举措]。它消耗了[资源]但仅产生了[极少结果]。将资源重新分配给[表现更好的举措]。”
渠道活动量高但无pipeline产出“诊断[渠道]。活动量高(X次发送)但pipeline产出近乎为零。可能是目标受众、文案或渠道本身的问题。”
会议数与合格机会数差距大“会议质量问题。预约了X次会议但仅Y次合格(Z%)。重新审视ICP定位和合格标准。”
高投入低产出象限“[举措]属于‘重新评估’象限。它消耗了[大量投入]但仅产生了[极少回报]。2周内完成诊断或终止。”

C) What's Missing (Start)

C) 缺失的举措(启动)

SignalRecommendation
Only 1-2 channels active"Channel concentration risk. X% of pipeline comes from one channel. Test [suggested new channel] as a hedge."
No inbound or content effort"100% outbound. Consider starting a lightweight inbound play (blog, LinkedIn content) to build a compounding pipeline source."
No referral program"Referrals typically convert at 3-5x cold outbound. Start a structured referral ask to existing customers and partners."
Strong outbound but no event presence"Consider attending [industry event]. Events produce higher-ACV pipeline for [segment]."
信号建议
仅1-2个活跃渠道“渠道集中风险。X%的pipeline来自单一渠道。测试[建议的新渠道]作为对冲。”
无内拓或内容营销投入“100%依赖外拓。考虑启动轻量级内拓策略(博客、LinkedIn内容)来构建复利式pipeline来源。”
无推荐计划“推荐的转化率通常是冷外拓的3-5倍。向现有客户和合作伙伴发起结构化的推荐请求。”
外拓表现良好但无活动参与“考虑参加[行业活动]。活动能为[细分群体]带来更高ACV的pipeline。”

D) Resource Allocation Recommendation

D) 资源分配建议

Based on the effort-impact analysis, recommend how to allocate the team's time next period:
Recommended time allocation (next period):
- [Channel A]: Increase from X% → Y% of team time (reason)
- [Channel B]: Maintain at X% (reason)
- [Channel C]: Reduce from X% → Y% or eliminate (reason)
- [New Channel]: Allocate Z% for testing (reason)
基于投入-产出分析,建议下周期团队时间分配:
建议下周期时间分配:
- [渠道A]:从X% → Y% 团队时间(原因)
- [渠道B]:维持X%(原因)
- [渠道C]:从X% → Y% 或完全取消(原因)
- [新渠道]:分配Z%时间用于测试(原因)

Output Contract

输出约定

insights: {
  double_down: [
    { initiative: string, recommendation: string, expected_impact: string, data_point: string }
  ]
  fix_or_kill: [
    { initiative: string, recommendation: string, deadline: string, data_point: string }
  ]
  start: [
    { recommendation: string, rationale: string, effort_estimate: string }
  ]
  resource_allocation: {
    current: [ { channel: string, effort_percentage: percentage } ]
    recommended: [ { channel: string, effort_percentage: percentage, change: string, reason: string } ]
  }
  key_risks: string[]                 # Top 3 risks to next period's targets
}

insights: {
  double_down: [
    { initiative: string, recommendation: string, expected_impact: string, data_point: string }
  ]
  fix_or_kill: [
    { initiative: string, recommendation: string, deadline: string, data_point: string }
  ]
  start: [
    { recommendation: string, rationale: string, effort_estimate: string }
  ]
  resource_allocation: {
    current: [ { channel: string, effort_percentage: percentage } ]
    recommended: [ { channel: string, effort_percentage: percentage, change: string, reason: string } ]
  }
  key_risks: string[]                 # 下周期目标的前3大风险
}

Step 5: Generate Report

步骤5:生成报告

Purpose: Produce a presentation-ready report that the team can review together. Two formats: the full detailed report and a slide-ready summary.
目的: 生成可直接用于团队复盘的演示报告。提供两种格式:完整详细报告和幻灯片摘要。

Input Contract

输入约定

initiative_inventory: [...]           # From Step 1
initiative_metrics: [...]             # From Step 2
analysis: { ... }                     # From Step 3
insights: { ... }                     # From Step 4
targets: { ... }                      # From config
report_audience: string               # From config
period: { ... }
initiative_inventory: [...]           # 来自步骤1
initiative_metrics: [...]             # 来自步骤2
analysis: { ... }                     # 来自步骤3
insights: { ... }                     # 来自步骤4
targets: { ... }                      # 来自配置
report_audience: string               # 来自配置
period: { ... }

Report Structure

报告结构

Adapt depth and tone based on
report_audience
:
SectionTeamLeadershipBoard
Executive summaryBriefDetailedConcise + metrics
Initiative scorecardsFull detailSummaryTop/bottom only
Cross-initiative comparisonFull tablesRankingsTop 3 chart
Funnel analysisDetailed with actionsStage conversion focusHigh-level conversion
Stuck/problem areasDetailed with fix plansSummary with ownersMention only
RecommendationsTactical, this-week actionsStrategic, this-quarterInvestment themes
undefined
根据
report_audience
调整深度与语气:
模块销售团队管理层董事会
执行摘要简洁详细简洁+数据驱动
举措评分卡完整细节摘要仅展示Top/Bottom举措
跨举措对比完整表格排名Top3图表
漏斗分析详细+行动项聚焦阶段转化高层转化视图
问题区域详细+修复计划摘要+负责人仅提及
建议战术性、本周行动战略性、本季度规划投资主题
undefined

Sales Performance Review — [Period Type]: [Start Date] to [End Date]

销售业绩复盘 — [周期类型]: [开始日期]至[结束日期]

Executive Summary

执行摘要

Period overview: [2-3 sentences: what happened, headline result]
周期概览: [2-3句话:发生了什么,核心结果]

Scorecard

评分卡

MetricTargetActualStatusTrend
Meetings bookedXY[ahead/behind][+/-Z% vs prior]
Qualified meetingsXY[ahead/behind][+/-Z%]
Pipeline created$X$Y[ahead/behind][+/-Z%]
Revenue closed$X$Y[ahead/behind][+/-Z%]
指标目标实际状态趋势
预约会议数XY[超额/落后][较上一周期 +/-Z%]
合格会议数XY[超额/落后][较上一周期 +/-Z%]
创建的pipeline金额$X$Y[超额/落后][较上一周期 +/-Z%]
成交收入$X$Y[超额/落后][较上一周期 +/-Z%]

Headline Insights

核心洞见

  1. Best performer: [Initiative] — [one-line result with key number]
  2. Biggest concern: [Issue] — [one-line description]
  3. Biggest opportunity: [What to do next] — [expected impact]

  1. 最佳表现: [举措] — [带关键数据的一句话结果]
  2. 最大问题: [问题] — [一句话描述]
  3. 最大机会: [下一步行动] — [预期影响]

Initiative Performance

举措业绩

Overview

概览

#InitiativeChannelGradeMeetingsPipelineVerdict
1[name]EmailA18$240KScale up
2[name]LinkedInB8$120KOptimize
3[name]EventB+12$180KRepeat
4[name]ContentC4$50KNeeds time
5[name]ReferralA12$200KInvest more
序号举措渠道评分会议数Pipeline结论
1[名称]EmailA18$240K扩大规模
2[名称]LinkedInB8$120K优化
3[名称]活动B+12$180K重复开展
4[名称]内容C4$50K需要时间培育
5[名称]推荐A12$200K增加投入

Detailed Scorecards

详细评分卡

[Initiative 1 Name] — Grade: [X]

[举措1名称] — 评分:[X]

What it is: [1-sentence description] Target audience: [Who]
MetricValueBenchmarkStatus
[Activity]X
Response rateX%Y%[above/below]
Meetings bookedX
Meeting conversionX%Y%[above/below]
Pipeline created$X
Cost per meeting$X[if available]
What worked: [Specific things that performed well] What didn't: [Specific issues] Recommendation: [Scale / Optimize / Fix / Kill]
[Repeat for each initiative]

举措说明: [1句话描述] 目标受众: [群体]
指标数值基准状态
[活动量]X
响应率X%Y%[高于/低于]
预约会议数X
会议转化率X%Y%[高于/低于]
创建的pipeline金额$X
每会议成本$X[若有数据]
有效点: [具体表现好的地方] 问题点: [具体问题] 建议: [扩大规模/优化/修复/终止]
[为每个举措重复上述内容]

Cross-Initiative Comparison

跨举措对比

Efficiency Rankings

效率排名

RankInitiativeMeetings BookedMeeting ConversionPipeline per MeetingCost per Meeting
1[name]XY%$Z$W
2[name]XY%$Z$W
...
排名举措预约会议数会议转化率每会议Pipeline金额每会议成本
[名称]XY%$Z$W
[名称]XY%$Z$W
...

Effort vs. Impact Matrix

投入-产出矩阵

SCALE UP (high impact, efficient):
  • [Initiative] — [why]
  • [Initiative] — [why]

OPTIMIZE (high impact, resource-heavy):
  • [Initiative] — [why]

MAINTAIN (low effort, moderate results):
  • [Initiative] — [why]

QUESTION (high effort, low results):
  • [Initiative] — [why]

扩大规模(高产出、高效):
  • [举措] — [原因]
  • [举措] — [原因]

优化(高产出、资源密集):
  • [举措] — [原因]

维持现状(低投入、中等结果):
  • [举措] — [原因]

重新评估(高投入、低产出):
  • [举措] — [原因]

Full Funnel Analysis

全局漏斗分析

Aggregate Funnel

汇总漏斗

[Total Activity] → [Responses] → [Meetings] → [Qualified] → [Pipeline] → [Won]
    X,XXX             XXX            XX           XX          $XXX K      $XX K
              X.X%          X.X%          XX%          XX%          XX%
[总活动量] → [响应数] → [会议数] → [合格机会] → [Pipeline] → [赢单]
    X,XXX             XXX            XX           XX          $XXX K      $XX K
              X.X%          X.X%          XX%          XX%          XX%

Funnel by Channel

按渠道划分的漏斗

ChannelActivity→ Response→ Meeting→ Qualified→ Pipeline→ Won
EmailXY%Z%W%$V$U
LinkedInXY%Z%W%$V$U
EventsXY%Z%W%$V$U
InboundXY%Z%W%$V$U
ReferralXY%Z%W%$V$U
Biggest drop-off: [Stage] — [X% of pipeline is lost here. Why and what to do.]

渠道活动量→ 响应→ 会议→ 合格机会→ Pipeline→ 赢单
EmailXY%Z%W%$V$U
LinkedInXY%Z%W%$V$U
活动XY%Z%W%$V$U
内拓XY%Z%W%$V$U
推荐XY%Z%W%$V$U
最大流失点: [阶段] — [X%的pipeline在此流失。原因及解决方案。]

Gap Analysis (vs. Targets)

差距分析(与目标对比)

TargetGoalActualGapTo Close the Gap
MeetingsXY-ZNeed Z more from [best-converting channel]
Pipeline$X$Y-$ZAt avg deal size of $W, need Z more qualified meetings
Revenue$X$Y-$ZNeed to close X more deals from current pipeline
Path to target: [Specific plan — "If we increase [channel] volume by X% and maintain current conversion, we close the gap in Y weeks."]

目标目标值实际值差距填补差距的方法
会议数XY-Z需要从[转化最好的渠道]多获取Z个会议
Pipeline$X$Y-$Z按平均成交规模$W计算,需要多获取Z个合格会议
收入$X$Y-$Z需要从当前pipeline中多成交X个订单
达标路径: [具体计划 — “如果我们将[渠道]的活动量提升X%并维持当前转化率,可在Y周内填补差距。”]

Trends (vs. Prior Period)

趋势(与上一周期对比)

MetricPrior PeriodCurrent PeriodChangeSignal
Total meetingsXY+/-Z%[Improving/Declining]
Qualification rateX%Y%+/-Z pts[context]
Pipeline created$X$Y+/-Z%[context]
Best channel[channel][channel][Shifted?][context]
Avg deal size$X$Y+/-Z%[context]
[Commentary on what the trends mean]

指标上一周期当前周期变化信号
总会议数XY+/-Z%[改善/下滑]
合格转化率X%Y%+/-Z个百分点[背景说明]
创建的pipeline金额$X$Y+/-Z%[背景说明]
最佳渠道[渠道][渠道][是否变化][背景说明]
平均成交规模$X$Y+/-Z%[背景说明]
[趋势意义的评论]

What's Working (Double Down)

有效举措(加倍投入)

  1. [Initiative/Channel] — [Evidence with numbers]. Recommendation: [Specific action + expected impact].
  2. [Initiative/Channel] — [Evidence]. Recommendation: [Action].
  3. [Pattern] — [Evidence]. Recommendation: [Action].
  1. [举措/渠道] — [带数据的证据]。建议:[具体行动 + 预期影响]。
  2. [举措/渠道] — [证据]。建议:[行动]。
  3. [模式] — [证据]。建议:[行动]。

What's Not Working (Fix or Kill)

无效举措(修复或终止)

  1. [Initiative/Channel] — [Evidence]. Recommendation: [Fix plan with deadline OR kill decision].
  2. [Initiative/Channel] — [Evidence]. Recommendation: [Action].
  1. [举措/渠道] — [证据]。建议:[带截止日期的修复计划或终止决定]。
  2. [举措/渠道] — [证据]。建议:[行动]。

What's Missing (Start)

缺失的举措(启动)

  1. [New initiative] — [Rationale]. Expected effort: [X]. Expected impact: [Y].

  1. [新举措] — [理由]。预期投入:[X]。预期影响:[Y]。

Recommended Resource Allocation (Next Period)

建议下周期资源分配

ChannelCurrent EffortRecommendedChangeReason
Outbound emailX%Y%[+/-Z%][reason]
LinkedInX%Y%[+/-Z%][reason]
EventsX%Y%[+/-Z%][reason]
Content/InboundX%Y%[+/-Z%][reason]
ReferralsX%Y%[+/-Z%][reason]

渠道当前投入建议投入变化原因
外拓邮件X%Y%[+/-Z%][原因]
LinkedInX%Y%[+/-Z%][原因]
活动X%Y%[+/-Z%][原因]
内容/内拓X%Y%[+/-Z%][原因]
推荐X%Y%[+/-Z%][原因]

Action Items

行动项

This Week

本周

#ActionOwnerDeadlineExpected Impact
1[action][name][date][impact]
2[action][name][date][impact]
序号行动负责人截止日期预期影响
[行动][姓名][日期][影响]
[行动][姓名][日期][影响]

This Month

本月

#ActionOwnerExpected Impact
1[action][name][impact]
序号行动负责人预期影响
[行动][姓名][影响]

Key Risks

核心风险

  1. [Risk with mitigation plan]
  2. [Risk with mitigation plan]

---
  1. [风险及缓解计划]
  2. [风险及缓解计划]

---

Step 6: Export & Distribute

步骤6:导出与分发

Purpose: Save and optionally distribute the report.
目的: 保存并按需分发报告。

Output Options

输出选项

DestinationFormatUse Case
Markdown file
.md
Default — save to
clients/<client>/reports/
Google SlidesPresentationTeam meeting — one slide per section
Notion pageDatabase entryRunning log of periodic reviews
Google SheetsData tablesSupplement to the report — raw data for filtering
EmailSummarySend executive summary to leadership
stdoutDisplayQuick review in terminal

目的地格式使用场景
Markdown文件
.md
默认 — 保存至
clients/<client>/reports/
Google Slides演示文稿团队会议 — 每个模块一页幻灯片
Notion页面数据库条目定期复盘的运行日志
Google Sheets数据表报告补充 — 用于筛选的原始数据
邮件摘要向管理层发送执行摘要
标准输出显示在终端快速查看

Execution Summary

执行摘要

StepTool DependencyHuman CheckpointTypical Time
0. ConfigNoneFirst run only5-10 min (once)
1. InventoryConfigurable (CRM, outreach tools)Confirm all initiatives captured3-5 min
2. Pull MetricsConfigurable (CRM, outreach tools)Verify metrics accuracy3-5 min
3. AnalyzeNone (computation + LLM reasoning)None — feeds into reportAutomatic
4. InsightsNone (LLM reasoning)None — feeds into reportAutomatic
5. Generate ReportNone (LLM reasoning)Review final report5-10 min
6. ExportConfigurable (file, Slides, Notion)Optional1-2 min
Total human review time: ~15-25 minutes for a report that would take 2-4 hours of manual data gathering, spreadsheet building, and analysis.

步骤工具依赖人工校验点典型耗时
0. 配置仅首次运行5-10分钟(一次性)
1. 盘点可配置(CRM、外拓工具)确认所有举措已捕获3-5分钟
2. 提取指标可配置(CRM、外拓工具)验证指标准确性3-5分钟
3. 分析无(计算 + LLM推理)无 — 直接输入报告自动
4. 洞见无(LLM推理)无 — 直接输入报告自动
5. 生成报告无(LLM推理)审核最终报告5-10分钟
6. 导出可配置(文件、Slides、Notion)可选1-2分钟
总人工校验时间:~15-25分钟,而手动完成数据收集、表格制作和分析通常需要2-4小时。

Cadence Guide

频率指南

Review TypePeriodBest ForFocus
Weekly standup7 daysSales teamActivity metrics, stuck items, this week's priorities
Fortnightly review14 daysSales managerInitiative performance, early trend detection
Monthly review30 daysVP Sales / FounderFull diagnostic, cross-initiative comparison, resource allocation
Quarterly business review90 daysLeadership / BoardStrategic assessment, channel ROI, next quarter planning
The report depth scales with period length. A weekly review focuses on activity and blockers. A quarterly review focuses on trends, ROI, and strategic allocation.

复盘类型周期适用对象聚焦点
每周站会7天销售团队活动指标、卡点、本周优先级
双周复盘14天销售经理举措业绩、早期趋势检测
月度复盘30天销售副总裁 / 创始人全面诊断、跨举措对比、资源分配
季度业务复盘90天管理层 / 董事会战略评估、渠道ROI、下季度规划
报告深度随周期长度调整。每周复盘聚焦活动和卡点。季度复盘聚焦趋势、ROI和战略分配。

Tips

小贴士

  • Attribution is the hardest part. Don't let perfect be the enemy of good. If you can't do multi-touch attribution, first-touch is fine. If CRM source fields are empty, use email/name matching. Some attribution is infinitely better than none.
  • Compare channels on the same metric. "We sent 2,500 emails and attended 1 conference" is meaningless. "Email produced 18 meetings at $0.50/meeting. The conference produced 12 meetings at $400/meeting" is actionable.
  • The effort-impact matrix drives resource allocation. This is the most important visual in the report. It turns a complex multi-channel discussion into four simple quadrants.
  • Include cost data when possible. Revenue numbers without cost data tell half the story. A $200K pipeline from referrals (free) is very different from $200K from events ($50K cost).
  • Trend direction matters more than absolute numbers. A 3% reply rate that was 1.5% last month is great. A 5% reply rate that was 8% last month is concerning. Always show the trajectory.
  • End every report with specific action items and owners. A beautiful report with no actions is a waste. Every insight should map to "who does what by when."
  • Save historical reports. The real power comes from comparing Q1 review to Q2 to Q3. Trends across review periods reveal strategic shifts that no single report can show.
  • 归因是最难的部分。 不要追求完美。如果无法做多触点归因,首次触点归因也可以。如果CRM来源字段为空,使用邮箱/姓名匹配。有归因比没有好得多。
  • 用同一指标对比渠道。 “我们发送了2500封邮件并参加了1个会议”没有意义。“邮件渠道产生了18次会议,每会议成本$0.50。会议渠道产生了12次会议,每会议成本$400”才是可行动的。
  • 投入-产出矩阵驱动资源分配。 这是报告中最重要的可视化。它将复杂的多渠道讨论简化为四个简单的象限。
  • 尽可能包含成本数据。 没有成本数据的收入数据只说了一半故事。推荐渠道带来的$200K pipeline(免费)和活动带来的$200K pipeline(成本$50K)有天壤之别。
  • 趋势方向比绝对数字更重要。 回复率从1.5%提升到3%很棒。回复率从8%降到5%则需要关注。始终展示趋势。
  • 每份报告结尾都要有具体的行动项和负责人。 一份没有行动的漂亮报告是浪费。每个洞见都要对应“谁在什么时候做什么”。
  • 保存历史报告。 真正的价值来自对比Q1、Q2、Q3的复盘报告。跨周期的趋势揭示了单一报告无法展现的战略变化。