Outbound resource

An outbound campaign report template with clear funnel definitions

Make the report explain what changed and what to do next. Track unique prospects through separate reply and meeting stages, state every denominator and keep a send cohort separate from a calendar activity report.

Editorial update:

Use the template ↓Discuss your outbound plan →

Copyable weekly report brief

Use the activity and cohort worksheets as separate views. Fill their fields from your own records. The example arithmetic on this page is fictional, not a LeadFlow result or performance benchmark.

  1. Scope and freshness

    Campaign: [name] Segment and ICP version: [value] Views included: [weekly activity / send cohort / both, shown separately] Period start (inclusive), end (exclusive) and time zone: [details] Observed through: [date] Data owner and source: [details]

  2. Send cohort conversion worksheet

    Cohort first-contact interval: [start inclusive / end exclusive] Observed through: [timestamp] All following counts refer only to members of this cohort. Unique contacted prospects: [count] Human replies / contacted: [counts and rate] Positive replies / contacted: [counts and rate] Booked / contacted: [counts and rate] Held / booked: [counts and rate] Sales accepted / held: [counts and rate] Allocated cohort cost / accepted: [amount or not applicable] Cost inclusions and allocation rule: [details]

  3. Weekly activity worksheet

    Event interval and time zone: [start inclusive / end exclusive] Newly contacted unique prospects: [count] Human reply events / unique people replying: [counts] First-meeting booking events / unique prospects booked: [counts] Held meeting events / unique prospects attending: [counts] Reschedules and cancellations: [separate counts] Earlier-cohort activity included: [count and definition] Unmatched records awaiting review: [count] These activity counts are not cohort conversion rates. Do not divide weekly meetings by weekly new prospects.

  4. Interpretation and next test

    Observed change: [specific measure and comparison] Evidence from replies or meeting notes: [summary] What we still cannot conclude: [uncertainty] Next test and owner: [one change] Review date and success measure: [details]

Funnel measures
7
Example arithmetic
Illustrative
Suggested review
Weekly

Illustrative cohort: definitions and arithmetic

Scroll the table sideways to compare all columns.

Illustrative cohort: definitions and arithmetic
MeasureDefinition used hereFictional example
Contacted prospectsUnique people first contacted in the cohort200
Human repliesUnique people with a human reply; exclude automatic replies20 / 200 = 10%
Positive repliesUnique people expressing relevant interest under agreed rules8 / 200 = 4%
BookedUnique prospects with a first meeting scheduled5 / 200 = 2.5%
HeldUnique prospects whose first meeting occurred4 / 5 booked = 80%
Sales acceptedUnique prospects accepted against agreed criteria2 / 4 held = 50%
Cohort cost per accepted prospectAllocated cohort cost divided by sales-accepted prospects$1,000 / 2 = $500

Choose the reporting unit first

For the cohort convention below, a contacted prospect is a unique person first contacted during the selected period. Follow-up messages to that person do not create additional prospects. Track channel and campaign separately, and define how cross-channel contacts are deduplicated before adding totals. If that join is unavailable, show the channel totals separately rather than claiming a unique combined total.

Distinguish a send cohort from weekly activity

A send cohort follows the people first contacted in a period, including their later replies and meetings as of a stated date. A weekly activity report counts events that happened that week, even when the original outreach was earlier. Both views are useful, but dividing this week's meetings by this week's new prospects mixes populations. Label the view and observation date on every report.

Turn the report into one decision

Add the main constraint, the evidence and one next test. Few human replies may call for investigation of delivery, targeting or message relevance; that number alone does not identify the cause. A large gap between booked and held calls needs different investigation from a gap between held and accepted meetings. Segment the affected records before changing the whole campaign.

Reconcile the exports before calculating rates

Keep an unchanged export snapshot and record its extraction time, source and filters. Join a prospect register to an event ledger using a stable person ID; keep campaign and channel alongside that ID. A CRM contact creation date is not necessarily the first outbound contact date. Preserve source event IDs, occurred-at timestamps, event types and meeting IDs; distinguish event time from the time a sync imported it. Review ambiguous identity matches rather than merging people by company name.

  • Deduplicate repeated event IDs before counting. Link reschedules to the original meeting so they do not become new first bookings.
  • Classify automatic responses separately. Keep unmatched records in an exception list with a reason and owner, rather than silently dropping them or assigning them to a cohort.
  • For activity, filter by event time. For cohort conversion, select people by first-contact time, then join their later outcomes through the observation timestamp. Do not filter those outcomes to the original send week.
  • Check a sample of source records against each total and retain an exception count. If timestamps or identity joins are missing, label the affected measure unavailable instead of inferring historical events from a current status.

Worked reconciliation: six rows, two cohort prospects

Fictional example: the 200-person cohort in the table was first contacted from September 1 up to, but not including, September 8. In the September 8-15 activity interval, an export contains six booking-related rows: A is a new booking for a cohort member; B repeats A's event ID; C reschedules that same meeting; D is a new booking for a person first contacted in August; E is a new booking for another September cohort member; F has no match to the prospect register. After review, the weekly view has three matched first-booking events (A, D and E), one reschedule, one duplicate excluded and one unmatched row awaiting resolution. Only A and E contribute two newly booked prospects to the September cohort. If three other members were already booked, its observed total is five of 200, or 2.5%. Dividing the three weekly bookings by that week's newly contacted people would not describe this cohort's conversion rate.

Check what your CRM date filter selects

HubSpot's legacy funnel documentation distinguishes All and Any stage inclusion, with different date-filter behavior. Inspect the specific report builder and filters you use rather than assuming every CRM chart is a send cohort. Save those settings with the export and reconcile a few known records before using the chart in an agency or SDR review.

Action checklist

Check the report before sharing

  • Compare equally mature cohorts

    A new cohort has had less time to reply or attend a meeting. Show the observation window rather than presenting the difference as a campaign improvement.

  • Document status changes

    A cancelled meeting or a later sales rejection can change the funnel. State whether the report is a snapshot or a live view.

  • Show counts alongside rates

    Small counts can move percentages sharply. A rate without the denominator conceals how much evidence supports it.

Who this helps

  • Founders reviewing agency or SDR activity
  • RevOps teams defining consistent funnel measures
  • Campaign owners choosing the next experiment

Work through the process

  1. 01

    Set the reporting window

    Record cohort start and end, observation date, time zone and whether the view is cohort-based or event-based.

  2. 02

    Reconcile records

    Deduplicate contacts and reschedules, exclude automatic replies from human replies, and retain source records for each status.

  3. 03

    Calculate named rates

    Show numerator and denominator next to each percentage. A zero denominator produces not applicable, not a zero or infinite performance claim.

  4. 04

    Assign the next action

    Write the observation, its possible explanations, the test owner and the date to review the result.

Questions and answers

Are these percentages target benchmarks?
No. The numbers are deliberately fictional to demonstrate arithmetic. Set targets using your own economics, audience and agreed definitions.
What should happen when no meetings are accepted?
Report the count as zero and cost per accepted prospect as not applicable because the denominator is zero. Keep the actual cost visible.
Can I add email and LinkedIn reply rates together?
No. Combine underlying deduplicated counts only when the populations and definitions are compatible, then calculate a new rate. Otherwise report each channel separately.
What costs belong in the example calculation?
State the allocation rule for agency fees, internal labor, data and tools. The fictional $1,000 is an example total, not an estimate of what your campaign should cost.

Sources and editorial notes

Original AI-assisted editorial templates and planning conventions prepared for LeadFlow. Examples are illustrative; they are not independently tested results, customer evidence or performance benchmarks. Check facts and adapt the material to your own workflow before use.

Keep reading