CRM hygiene audit
CRM data is messy and reports cannot be trusted.
You get Issue inventory with counts · Impact ranking · Cleanup plan
Use this weekly or at the end of a campaign. It answers three questions: what is working, where does it break, and what do we change next.
Use it when you need to understand how outbound campaigns are performing and what to change.
“Here's last month's export for 6 campaigns. What's working and what should we change?”
What happens when you ask your agent with this skill installed. Every step below comes straight from the skill.
Here's last month's export for 6 campaigns. What's working and what should we change?
campaign-performance-analyzerReady for your review. Nothing is sent or changed until you approve.
What good looks like
What you bring
What you get
Use this weekly or at the end of a campaign. It answers three questions: what is working, where does it break, and what do we change next.
Contacts → delivered → replied → positive → booked → held → opportunity. Calculate each conversion. Skip open rates as a decision metric; open tracking is unreliable and often turned off for deliverability.
Read references/outbound-benchmarks.md for typical ranges by channel and what each gap usually means. Benchmarks are a sanity check, not a target; your own trend matters more.
The first stage below benchmark is the problem to fix; improving later stages first is wasted effort.
| Break | Usually means | Look at |
|---|---|---|
| Bounces | List quality | Source, verification, catch-alls |
| Low replies, few negatives | Not seen, or not relevant | Deliverability by sender; targeting; first line |
| Replies, few positive | Message or offer mismatch | Angle, persona, ask |
| Positive, few booked | Slow or weak reply handling | Time to respond, booking flow |
| Booked, few held | Weak qualification or reminders | No-show rate, lead time |
| Held, few opportunities | Wrong ICP or poor discovery | Fit of meetings, discovery quality |
By step (which email gets the replies), segment (which persona or industry), sender (deliverability or skill), channel. Small slices need samples of 100+ contacts before conclusions.
One test at a time on the broken stage, with a hypothesis and a success threshold.
Period: | Campaigns: | Contacts:
Funnel (all): contacts → delivered x% → replied x% → positive x% → booked x% → held x% → opps
Best / worst campaign: <name - why>
The break: <stage - evidence - likely cause>
Slices worth noting: <step, segment, sender findings with sample sizes>
Next test: <hypothesis - change - metric - threshold - sample>
Stop / scale: <campaigns to pause, campaigns to give more volume>
Typical ranges for well-run B2B outbound to a targeted list. They vary by market, deal size and offer; use them to spot outliers, then track your own trend.
| Metric | Weak | Typical | Strong |
|---|---|---|---|
| Bounce rate | > 3% | 1-2% | < 1% |
| Reply rate (any) | < 2% | 3-6% | 8%+ |
| Positive reply rate (of contacts) | < 0.5% | 1-2% | 3%+ |
| Positive share of replies | < 25% | 30-45% | 50%+ |
| Meetings per 100 contacts | < 0.5 | 0.8-1.5 | 2+ |
| Spam complaint rate | > 0.3% | < 0.1% | ~0 |
| Metric | Weak | Typical | Strong |
|---|---|---|---|
| Acceptance rate | < 20% | 25-40% | 45%+ |
| Reply rate (of accepted) | < 8% | 10-20% | 25%+ |
| Meetings per 100 invitations | < 1 | 1-3 | 4+ |
| Metric | Typical |
|---|---|
| Connect rate (dials to conversations) | 3-10%, higher with good numbers |
| Meetings per conversation | 10-20% |
| Metric | Weak | Typical | Strong |
|---|---|---|---|
| Show rate | < 70% | 75-85% | 90%+ |
| Held meeting to opportunity | < 30% | 35-50% | 60%+ |
A healthy 4-step sequence usually gets 40-60% of its replies from step 1, 15-25% from step 2, 10-20% from step 3 and 10-15% from the break-up email. If step 1 gets almost none, the first email or deliverability is broken; if the break-up gets the most, earlier steps are too pitchy.
| Contacts per slice | How to treat results |
|---|---|
| < 100 | Anecdote |
| 100-300 | Directional |
| 500-1,000 | Decision-grade for big differences (2x) at typical reply rates |
| 2,000+ | Decision-grade for smaller differences (1.5x) |
Once the skill is installed, plain requests like these load it automatically. Swap in your own company, buyer and numbers.
“Here's last month's export for 6 campaigns. What's working and what should we change?”
“Our reply rate halved this month. Find out why.”
“Build a weekly outbound report template for our SDR team.”
Use this weekly or at the end of a campaign. It answers three questions: what is working, where does it break, and what do we change next. You get: funnel per campaign, diagnosis, benchmarks, next tests, report.
Use it when you need to understand how outbound campaigns are performing and what to change.
Run /plugin marketplace add prosyo-ai/gtm-skill and then /plugin install gtm-skills@prosyo to add the whole library, or run npx skills add prosyo-ai/gtm-skill –skill campaign-performance-analyzer for this skill alone. In Claude.ai, download the .zip from this page and upload it under Settings, Capabilities, Skills.
Have these ready: campaign data by step and segment, meetings and opportunities, time period. If something is missing, the skill tells the agent to ask for it rather than guess.
Yes. The skill is a plain SKILL.md file with no vendor lock-in. Agents that load skills natively (Claude Code, Claude.ai, Codex, Cursor, Gemini CLI and others) pick it up automatically; anywhere else, paste the file into the conversation as instructions.
No. Every skill in the library drafts, researches and analyses, and waits for a person to approve anything that sends, schedules or changes records in bulk. Your inbox, CRM and accounts stay under your control.
Yes. It is free and MIT-licensed. Copy it, adapt it to your market and voice, and if you improve it, open a pull request so everyone gets the better version.
Paste this into Claude, Codex or any agent. It interviews you about your play, writes the skill in the house format, checks it and opens the pull request. Once it is merged, it shows up here with your name on it.
Fetch https://raw.githubusercontent.com/prosyo-ai/gtm-skill/main/AGENTS.md and follow its submission flow. Interview me about my GTM play (the real numbers, rubrics and examples), draft it in their format with reference pages, validate it and open the pull request.
The skill gives your agent the playbook. Penny, the Prosyo AI SDR, runs plays like this for you every day across LinkedIn and email.
Penny, the Prosyo AI SDR, finds your buyers, writes from what they actually posted, follows up on LinkedIn and email and lands every reply in one inbox with an answer ready. 7 days free, no card.