GTM Engineering skill 13 of 13
GTM Reporting SKILL.md
The GTM Reporting skill makes Claude Code or another AI agent report GTM and outbound results from source to revenue. It agrees funnel definitions, stamps records for attribution by workflow, segment, signal, play and copy version, classifies replies, adds health and unit-cost metrics and builds dashboards and weekly and monthly reports that end with decisions.
gtm-reporting/SKILL.md, version 1.0.0, 1,486 words.
By Afeez Adebayo, Marketing, SEO & Growth Expert with 10+ years of experience.
Created 10 October 2026. Updated 10 October 2026. Free to use under CC BY 4.0.
Outbound and GTM automation are often judged on the wrong numbers: emails sent, open rates (unreliable since mail privacy features began loading images automatically) and total replies, including "unsubscribe" and "not interested". These numbers rise while pipeline stays flat. Leaders need to see whether the system produces qualified meetings, opportunities and revenue, at what cost, and which segments, signals, plays and copy drive the results.
This skill builds GTM reporting from source to revenue: a full funnel with clear definitions, attribution of meetings and pipeline to workflows, segments, signals, plays and prompt versions, data quality and deliverability health metrics, unit costs, dashboards for different audiences, a weekly and monthly reporting rhythm and experiments to improve weak stages.
Operating principles
- Pipeline over activity. Meetings, opportunities and revenue are the outcome metrics.
- Define every metric. "Positive reply" and "meeting held" mean the same thing to everyone.
- Attribute to the cause. Results by segment, signal, play, sequence and copy version.
- Health and cost alongside results. Deliverability and unit costs explain changes.
- Reports drive decisions. Every report ends with what to keep, change or stop.
The GTM funnel
| Stage | Definition | Typical owner |
|---|---|---|
| Accounts sourced | Accounts added to a workflow | GTM engineer |
| Accounts qualified | Accounts in tiers A or B | GTM engineer |
| Contacts ready | Contacts with verified email and QA pass | GTM engineer |
| Contacted | Contacts who received at least one step | SDR or automation |
| Delivered | Sent minus bounces | Automation |
| Replies | Any human reply | SDR |
| Positive replies | Interested, asked a question or referred | SDR |
| Meetings booked | Meeting scheduled | SDR |
| Meetings held | Meeting happened with a qualified person | AE |
| Opportunities | Qualified opportunity created in CRM | AE |
| Closed won | Revenue | AE |
Core metrics
| Metric | Formula |
|---|---|
| Qualification rate | Qualified accounts / sourced accounts |
| Match rate | Contacts with valid email / contacts sought |
| Bounce rate | Bounces / sent |
| Positive reply rate | Positive replies / delivered |
| Meeting rate | Meetings held / delivered (or per 1,000 contacted) |
| Show rate | Meetings held / meetings booked |
| Opportunity rate | Opportunities / meetings held |
| Win rate | Closed won / opportunities |
| Pipeline created | Value of opportunities from the workflow |
| Cost per meeting and opportunity | Total spend / meetings or opportunities |
| Time to meeting | Days from first touch to meeting |
When to use, and when not to
Use it to set up GTM dashboards, run weekly and monthly reviews, report to leadership, compare workflows and decide where to invest.
Don't use it for full marketing attribution across all channels (the Growth Marketing growth-reporting skill) or for cost analysis alone (gtm-cost-control).
Inputs
- CRM data with source and workflow stamps.
- Sequencer data: sends, bounces, replies and classifications.
- Table data: sourced, qualified, enriched, QA results, segments, signals, prompt versions.
- Costs by workflow.
- Targets for meetings, pipeline and revenue.
Raw SKILL.md file
This is the exact file agents read, including the credit header and licence notice. Save it as gtm-reporting/SKILL.md.
--- name: gtm-reporting description: "Report GTM and outbound results from source to revenue: agreed funnel definitions, attribution by workflow, segment, signal, play and copy version, reply classification, health and unit-cost metrics, dashboards for operators, teams and leaders, weekly and monthly templates and experiments on the weakest stage. Use whenever someone needs outbound or GTM reporting, a pipeline dashboard for Clay workflows, meeting and opportunity metrics instead of opens, results by segment or signal, or a monthly report for leadership." license: CC-BY-4.0 metadata: author: Afeez Adebayo author_url: https://afeezadebayo.com author_linkedin: https://www.linkedin.com/in/afeez-adebayo/ author_x: https://x.com/za_icon source: https://afeezadebayo.com/skills-md/marketing/gtm-engineering/gtm-reporting/ category: marketing subcategory: gtm-engineering version: "1.0.0" created: "2026-10-10" updated: "2026-10-13" --- # GTM Reporting Outbound and GTM automation are often judged on the wrong numbers: emails sent, open rates (unreliable since mail privacy features began loading images automatically) and total replies, including "unsubscribe" and "not interested". These numbers rise while pipeline stays flat. Leaders need to see whether the system produces qualified meetings, opportunities and revenue, at what cost, and which segments, signals, plays and copy drive the results. This skill builds GTM reporting from source to revenue: a full funnel with clear definitions, attribution of meetings and pipeline to workflows, segments, signals, plays and prompt versions, data quality and deliverability health metrics, unit costs, dashboards for different audiences, a weekly and monthly reporting rhythm and experiments to improve weak stages. ## Operating principles 1. **Pipeline over activity.** Meetings, opportunities and revenue are the outcome metrics. 2. **Define every metric.** "Positive reply" and "meeting held" mean the same thing to everyone. 3. **Attribute to the cause.** Results by segment, signal, play, sequence and copy version. 4. **Health and cost alongside results.** Deliverability and unit costs explain changes. 5. **Reports drive decisions.** Every report ends with what to keep, change or stop. ## The GTM funnel | Stage | Definition | Typical owner | |---|---|---| | Accounts sourced | Accounts added to a workflow | GTM engineer | | Accounts qualified | Accounts in tiers A or B | GTM engineer | | Contacts ready | Contacts with verified email and QA pass | GTM engineer | | Contacted | Contacts who received at least one step | SDR or automation | | Delivered | Sent minus bounces | Automation | | Replies | Any human reply | SDR | | Positive replies | Interested, asked a question or referred | SDR | | Meetings booked | Meeting scheduled | SDR | | Meetings held | Meeting happened with a qualified person | AE | | Opportunities | Qualified opportunity created in CRM | AE | | Closed won | Revenue | AE | ## Core metrics | Metric | Formula | |---|---| | Qualification rate | Qualified accounts / sourced accounts | | Match rate | Contacts with valid email / contacts sought | | Bounce rate | Bounces / sent | | Positive reply rate | Positive replies / delivered | | Meeting rate | Meetings held / delivered (or per 1,000 contacted) | | Show rate | Meetings held / meetings booked | | Opportunity rate | Opportunities / meetings held | | Win rate | Closed won / opportunities | | Pipeline created | Value of opportunities from the workflow | | Cost per meeting and opportunity | Total spend / meetings or opportunities | | Time to meeting | Days from first touch to meeting | ## When to use, and when not to Use it to set up GTM dashboards, run weekly and monthly reviews, report to leadership, compare workflows and decide where to invest. Don't use it for full marketing attribution across all channels (the Growth Marketing `growth-reporting` skill) or for cost analysis alone (`gtm-cost-control`). ## Inputs - CRM data with source and workflow stamps. - Sequencer data: sends, bounces, replies and classifications. - Table data: sourced, qualified, enriched, QA results, segments, signals, prompt versions. - Costs by workflow. - Targets for meetings, pipeline and revenue. ## Workflow ### Step 1. Agree definitions Write the definition of each funnel stage and metric; agree with sales leadership. ### Step 2. Make attribution possible Stamp every record with workflow, segment, signal, play and copy version, and carry these into the CRM. ### Step 3. Classify replies Positive, neutral, negative, out of office, wrong person, unsubscribe; use rules or AI with human checks. ### Step 4. Build the funnel Counts and conversion rates by stage, overall and by segment, signal and play. ### Step 5. Add health and cost Match rate, bounce rate, complaint rate, QA pass rate and unit costs per workflow. ### Step 6. Build dashboards An operator view (daily health and pipeline), a team view (weekly funnel and experiments) and a leadership view (monthly meetings, pipeline, revenue, cost). ### Step 7. Set the rhythm Weekly: health, funnel, experiments. Monthly: pipeline, revenue, unit costs, decisions. Quarterly: strategy and model updates. ### Step 8. Turn findings into experiments Pick the weakest stage; test one change at a time with a clear success metric. ## Weekly report template ``` Week <n> Health: match 76% | bounce 1.4% | QA pass 98.9% | complaints 0.04% Funnel: contacted 1,820 | positive replies 41 (2.3%) | meetings booked 19 | held 15 Best segment: Fintech UK tier A, 3.8% positive replies Best signal: new head of growth, 5 meetings Weakest stage: show rate 79% -> test reminder sequence Experiments: subject line v5 vs v4 (running), new DACH waterfall (complete: +12% match) Decisions: pause job-post signal; scale funding play ``` ## Monthly leadership summary ``` Meetings held: 64 (target 60) | Opportunities: 21 | Pipeline: £410,000 Wins this month from GTM-sourced opportunities: 3 (£68,000) Cost per meeting: £72 (ceiling £300) | Pipeline per £1 spent: £44 What worked: funding and new-leader plays What changes next month: expand tier A in Netherlands; stop generic job-post play ``` ## Reply classification guide | Class | Examples | Counts as positive | |---|---|---| | Interested | "Sure, let's talk", "Send more info" | Yes | | Referral | "Speak to my colleague" | Yes | | Question | "How does pricing work?" | Yes | | Not now | "Try next quarter" | No, but schedule follow-up | | Not interested | "No thanks" | No | | Unsubscribe | "Remove me" | No; suppress | | Out of office or wrong person | Auto-replies, left company | No; update records | ## Experiment log Record each experiment with hypothesis, change, segment, start and end dates, sample size, result and decision, so learning builds over time instead of being repeated. ## Edge cases and judgement calls | Situation | What to do | |---|---| | Long sales cycles | Report pipeline and opportunity rates as leading indicators | | Open rates requested | Explain unreliability; show replies and meetings instead | | Several channels touch the same account | Use first-touch and influenced views; avoid double counting | | Small numbers | Report rolling 4 to 8-week windows; avoid over-reading weekly changes | | Reply classification disputes | Sample-check AI classifications weekly | | No CRM source stamps | Start stamping now; estimate history carefully | ## Handoffs to related skills - Costs: `gtm-cost-control` - Scoring and tiers: `icp-account-scoring` - Signals and plays: `signal-based-outbound` - Copy versions: `ai-copy-columns` - Deliverability: `outbound-infrastructure` - Wider growth reporting: the Growth Marketing `growth-reporting` skill ## Worked example A team reported 12,000 emails sent and a 45% open rate each month, while leadership questioned outbound's value. The new reporting stamped workflow, segment, signal and copy version on every record, classified replies and built a funnel to revenue. It showed 64 meetings and £410,000 of pipeline a month at £72 per meeting, revealed that the funding and new-leader plays drove most meetings while generic job-post triggers produced none, and flagged a weak show rate. The team stopped the weak play, added a reminder sequence that lifted show rate to 88% and secured budget to expand. ## Common mistakes - Reporting sends and opens. - Counting all replies as success. - No source stamps, so results cannot be attributed. - Reports without decisions. - Over-reading small weekly numbers. ## Output format ``` 1. Metric definitions 2. Attribution fields and stamping plan 3. Funnel by segment, signal and play 4. Health and cost metrics 5. Dashboards by audience 6. Weekly and monthly templates 7. Experiment backlog ``` ## Self-check before you answer - Does reporting reach meetings, opportunities and revenue? - Are metrics defined and agreed with sales? - Can results be attributed to segment, signal, play and copy version? - Does every report end with decisions? --- Created by Afeez Adebayo, Marketing, SEO & Growth Expert Website: https://afeezadebayo.com LinkedIn: https://www.linkedin.com/in/afeez-adebayo/ X: https://x.com/za_icon Source: https://afeezadebayo.com/skills-md/marketing/gtm-engineering/gtm-reporting/ Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.
Workflow
Step 1. Agree definitions
Write the definition of each funnel stage and metric; agree with sales leadership.
Step 2. Make attribution possible
Stamp every record with workflow, segment, signal, play and copy version, and carry these into the CRM.
Step 3. Classify replies
Positive, neutral, negative, out of office, wrong person, unsubscribe; use rules or AI with human checks.
Step 4. Build the funnel
Counts and conversion rates by stage, overall and by segment, signal and play.
Step 5. Add health and cost
Match rate, bounce rate, complaint rate, QA pass rate and unit costs per workflow.
Step 6. Build dashboards
An operator view (daily health and pipeline), a team view (weekly funnel and experiments) and a leadership view (monthly meetings, pipeline, revenue, cost).
Step 7. Set the rhythm
Weekly: health, funnel, experiments. Monthly: pipeline, revenue, unit costs, decisions. Quarterly: strategy and model updates.
Step 8. Turn findings into experiments
Pick the weakest stage; test one change at a time with a clear success metric.
Weekly report template
Week <n>
Health: match 76% | bounce 1.4% | QA pass 98.9% | complaints 0.04%
Funnel: contacted 1,820 | positive replies 41 (2.3%) | meetings booked 19 | held 15
Best segment: Fintech UK tier A, 3.8% positive replies
Best signal: new head of growth, 5 meetings
Weakest stage: show rate 79% -> test reminder sequence
Experiments: subject line v5 vs v4 (running), new DACH waterfall (complete: +12% match)
Decisions: pause job-post signal; scale funding playMonthly leadership summary
Meetings held: 64 (target 60) | Opportunities: 21 | Pipeline: £410,000
Wins this month from GTM-sourced opportunities: 3 (£68,000)
Cost per meeting: £72 (ceiling £300) | Pipeline per £1 spent: £44
What worked: funding and new-leader plays
What changes next month: expand tier A in Netherlands; stop generic job-post playReply classification guide
| Class | Examples | Counts as positive |
|---|---|---|
| Interested | "Sure, let's talk", "Send more info" | Yes |
| Referral | "Speak to my colleague" | Yes |
| Question | "How does pricing work?" | Yes |
| Not now | "Try next quarter" | No, but schedule follow-up |
| Not interested | "No thanks" | No |
| Unsubscribe | "Remove me" | No; suppress |
| Out of office or wrong person | Auto-replies, left company | No; update records |
Experiment log
Record each experiment with hypothesis, change, segment, start and end dates, sample size, result and decision, so learning builds over time instead of being repeated.
Edge cases and judgement calls
| Situation | What to do |
|---|---|
| Long sales cycles | Report pipeline and opportunity rates as leading indicators |
| Open rates requested | Explain unreliability; show replies and meetings instead |
| Several channels touch the same account | Use first-touch and influenced views; avoid double counting |
| Small numbers | Report rolling 4 to 8-week windows; avoid over-reading weekly changes |
| Reply classification disputes | Sample-check AI classifications weekly |
| No CRM source stamps | Start stamping now; estimate history carefully |
Handoffs to related skills
- Costs:
gtm-cost-control - Scoring and tiers:
icp-account-scoring - Signals and plays:
signal-based-outbound - Copy versions:
ai-copy-columns - Deliverability:
outbound-infrastructure - Wider growth reporting: the Growth Marketing
growth-reportingskill
Worked example
A team reported 12,000 emails sent and a 45% open rate each month, while leadership questioned outbound's value. The new reporting stamped workflow, segment, signal and copy version on every record, classified replies and built a funnel to revenue. It showed 64 meetings and £410,000 of pipeline a month at £72 per meeting, revealed that the funding and new-leader plays drove most meetings while generic job-post triggers produced none, and flagged a weak show rate. The team stopped the weak play, added a reminder sequence that lifted show rate to 88% and secured budget to expand.
Common mistakes
- Reporting sends and opens.
- Counting all replies as success.
- No source stamps, so results cannot be attributed.
- Reports without decisions.
- Over-reading small weekly numbers.
Output format
1. Metric definitions
2. Attribution fields and stamping plan
3. Funnel by segment, signal and play
4. Health and cost metrics
5. Dashboards by audience
6. Weekly and monthly templates
7. Experiment backlogSelf-check before you answer
- Does reporting reach meetings, opportunities and revenue?
- Are metrics defined and agreed with sales?
- Can results be attributed to segment, signal, play and copy version?
- Does every report end with decisions?
On this page
- When to use this skill, and when not to
- Example prompts
- Example output
- What the agent needs from you
- How this skill hands off to related skills
- How to run GTM Reporting step by step
- Situations this skill handles
- What makes this skill different
- Practical tips from real projects
- Frequently asked questions
- Changelog
When to use this skill, and when not to
Use it to set up GTM dashboards, run weekly and monthly reviews, report to leadership and decide where to invest.
Sends and open rates rise while pipeline stays flat. Leaders need meetings, opportunities, revenue and cost, attributed to what caused them.
Example prompts
- “Build an outbound dashboard to revenue.”
- “Which signals and plays create meetings?”
- “Write our monthly GTM report for leadership.”
- “Stop reporting open rates; what instead?”
Example output
The skill returns a fixed structure. A shortened example for an imaginary site:
Meetings held: 64 | Opportunities: 21 | Pipeline: \u00a3410,000 Cost per meeting: \u00a372 Best plays: funding and new leader Stopped: generic job-post play Show rate: 79% -> 88% after reminder sequence
Reports measure meetings, pipeline and revenue, and every report ends with what to keep, change or stop.
What the agent needs from you
It needs CRM data with source stamps, sequencer data, table data on segments, signals and prompt versions, costs by workflow and targets.
How this skill hands off to related skills
GTM Reporting connects to related skills in the GTM Engineering skills, including GTM Workflow QA and GTM Engineering Audit.
How to run GTM Reporting step by step
- Install the skill as
gtm-reporting/SKILL.md. - Agree definitions.
- Make attribution possible.
- Classify replies.
- Build the funnel.
- Add health and cost.
Situations this skill handles
GTM Reporting handles these situations:
| Situation | What the skill does |
|---|---|
| Long sales cycles | Report pipeline and opportunity rates as leading indicators |
| Open rates requested | Explain unreliability; show replies and meetings instead |
| Several channels touch the same account | Use first-touch and influenced views; avoid double counting |
| Small numbers | Report rolling 4 to 8-week windows; avoid over-reading weekly changes |
| Reply classification disputes | Sample-check AI classifications weekly |
| No CRM source stamps | Start stamping now; estimate history carefully |
What makes this skill different
Most outbound reports celebrate activity. This skill traces each meeting and pound of pipeline back to the segment, signal, play and copy that created it.
Practical tips from real projects
- Pipeline over activity.
- Define every metric.
- Attribute to the cause.
- Health and cost alongside results.
A worked example: A team reported 12,000 emails sent and a 45% open rate each month, while leadership questioned outbound's value. The new reporting stamped workflow, segment, signal and copy version on every record, classified replies and built a funnel to revenue. It showed 64 meetings and £410,000 of pipeline a month at £72 per meeting, revealed that the funding and new-leader plays drove most meetings while generic job-post triggers produced none, and flagged a weak show rate. The team stopped the weak play, added a reminder sequence that lifted show rate to 88% and secured budget to expand.
Agree definitions: Write the definition of each funnel stage and metric; agree with sales leadership. Make attribution possible: Stamp every record with workflow, segment, signal, play and copy version, and carry these into the CRM. Classify replies: Positive, neutral, negative, out of office, wrong person, unsubscribe; use rules or AI with human checks.
Build the funnel: Counts and conversion rates by stage, overall and by segment, signal and play. Add health and cost: Match rate, bounce rate, complaint rate, QA pass rate and unit costs per workflow. Build dashboards: An operator view (daily health and pipeline), a team view (weekly funnel and experiments) and a leadership view (monthly meetings, pipeline, revenue, cost).
Set the rhythm: Weekly: health, funnel, experiments. Monthly: pipeline, revenue, unit costs, decisions. Quarterly: strategy and model updates. Turn findings into experiments: Pick the weakest stage; test one change at a time with a clear success metric.
The GTM funnel. Accounts sourced: definition Accounts added to a workflow; typical owner GTM engineer. Accounts qualified: definition Accounts in tiers A or B; typical owner GTM engineer. Contacts ready: definition Contacts with verified email and QA pass; typical owner GTM engineer. Contacted: definition Contacts who received at least one step; typical owner SDR or automation. Delivered: definition Sent minus bounces; typical owner Automation. Replies: definition Any human reply; typical owner SDR. Positive replies: definition Interested, asked a question or referred; typical owner SDR. Meetings booked: definition Meeting scheduled; typical owner SDR. Meetings held: definition Meeting happened with a qualified person; typical owner AE. Opportunities: definition Qualified opportunity created in CRM; typical owner AE. Closed won: definition Revenue; typical owner AE.
Core metrics. Qualification rate: formula Qualified accounts / sourced accounts. Match rate: formula Contacts with valid email / contacts sought. Bounce rate: formula Bounces / sent. Positive reply rate: formula Positive replies / delivered. Meeting rate: formula Meetings held / delivered (or per 1,000 contacted). Show rate: formula Meetings held / meetings booked. Opportunity rate: formula Opportunities / meetings held. Win rate: formula Closed won / opportunities. Pipeline created: formula Value of opportunities from the workflow. Cost per meeting and opportunity: formula Total spend / meetings or opportunities. Time to meeting: formula Days from first touch to meeting.
Reply classification guide. Interested: examples "Sure, let's talk", "Send more info"; counts as positive Yes. Referral: examples "Speak to my colleague"; counts as positive Yes. Question: examples "How does pricing work?"; counts as positive Yes. Not now: examples "Try next quarter"; counts as positive No, but schedule follow-up. Not interested: examples "No thanks"; counts as positive No. Unsubscribe: examples "Remove me"; counts as positive No; suppress. Out of office or wrong person: examples Auto-replies, left company; counts as positive No; update records.
Edge cases and judgement calls. Long sales cycles: what to do Report pipeline and opportunity rates as leading indicators. Open rates requested: what to do Explain unreliability; show replies and meetings instead. Several channels touch the same account: what to do Use first-touch and influenced views; avoid double counting. Small numbers: what to do Report rolling 4 to 8-week windows; avoid over-reading weekly changes. Reply classification disputes: what to do Sample-check AI classifications weekly. No CRM source stamps: what to do Start stamping now; estimate history carefully.
Common mistakes to avoid: Reporting sends and opens. Counting all replies as success. No source stamps, so results cannot be attributed. Reports without decisions. Over-reading small weekly numbers.
Frequently asked questions
What should outbound reporting measure?
Positive replies, meetings held, opportunities, pipeline, revenue and cost per meeting, not sends and opens.
Why not open rates?
Mail privacy features load images automatically, so opens are unreliable.
How do I attribute results?
Stamp each record with workflow, segment, signal, play and copy version and carry them into the CRM.
How often should we report?
Weekly for health and funnel, monthly for pipeline and costs, quarterly for strategy.
Changelog
- 1.0.0, 10 October 2026: first release.
Use, adapt and share this skill under CC BY 4.0: credit Afeez Adebayo and link to this page.
