Files
skills/public/benchmarks.md
zeekayandHanzo Dev 65c3b27843 160 marketing, growth and PM skills, on our own connectors
Four MIT collections ported — growthOS, openclaw-marketing-skills,
Marketing-Skills and pm-skills — as 160 skills, 12 agents and 45
commands, each naming its origin in its own frontmatter so the tree can
be checked against THIRD_PARTY_NOTICES rather than trusted. Sixteen names
appeared in more than one collection and none of the copies were
identical; the longest wins, which lands on the more developed text where
they genuinely diverge.

A fifth collection is deliberately absent. awesome-growth-hacking-skills
carries NO licence, which leaves its author every right by default — and
it is a list of links rather than a collection of skills, so there is
nothing in it to port and no permission to port it with. It is cited as a
directory to read.

THE CONNECTOR SKILLS ARE REWRITTEN, not ported. They arrived installing
vendor SDKs, running OAuth flows of their own, and ending with long-lived
credentials in JSON files under .agents/ and ~/.growthos/ at mode 600.
That is a secret on a disk with no rotation path, protected from other
users and not from the agent — and one auth implementation per skill.
Hanzo holds these connectors in Go, per user, sealed in KMS, so `connect`
is the one home for the flow and the platform skills defer to it by
provider id: google_ads, meta_ads, x. It is reachable as HTTP or as MCP
tools at api.hanzo.ai/v1/mcp — the same routes, typed once in Go, so a
tool and a curl cannot disagree.

Two had nothing real behind them and now say so. There is no
search_console provider, so that skill names what does answer the same
questions (google_analytics, google_bigquery) and states that the remedy
is a provider in hanzoai/cloud rather than a vendor SDK here. And
getxapi-connect was a wrapper around a paid reseller of X's public data
with the vendor's key in an env var; it is `listen` now, on our own x
connector — a skill named after a vendor makes the vendor the capability
and dies with it.

The skills referenced paths that only existed inside the source repo, so
the shared material they read is ported to reference/ and the paths
rewritten. Three skills need the growthOS APPLICATION rather than its
data; per the estate's own split an application belongs in hanzoai/ads,
social, email or sms as a cloud plugin, so those three say what they need
instead of carrying an import that resolves to nothing.

Third-party product names are out of our prose and kept in the notices,
which is where the licence requires them and the only place they belong.
A skill's persona names a role, not somebody else's product.


Co-authored-by: Hanzo Dev <[email protected]>
2026-09-15 01:27:26 -07:00

5.7 KiB
Raw Permalink Blame History

Benchmarks, Data & Expert Methods

Core Performance Metrics (2024–2025)

Metric Average Good Excellent Source
Open rate 27.7% 40–45% 50%+ Belkins, Snov.io
Reply rate 4–5.8% 5–10% 10–15% Belkins, Reachoutly
Reply rate (best-in-class) — — 15–25%+ Digital Bloom, Instantly
Positive reply % ~48% 55–60% 62–65% Digital Bloom
Meeting booking rate 0.5–1% 1–2% 2.3%+ Reachoutly
Bounce rate 7.5% <4% <2% Belkins

Realistic Funnel Model

500 emails → 100 opens (20%) → 25 replies (5%) → 8 positive replies (30%) → 4 meetings (50%) → 1 client (25% close). ~0.2% end-to-end conversion for average performers.

Performance Levers (ranked by impact)

  1. Hook type — Timeline hooks outperform problem hooks by 3.4x in meetings
  2. Personalization depth — Up to 250% more replies
  3. Brevity — 25–75 words optimal, 83% more replies under 75 words
  4. Targeting precision — ≤50 contacts per campaign = 2.76x higher reply rates
  5. Follow-up strategy — First follow-up adds 49% more replies
  6. Reading level — 3rd–5th grade = 67% more replies
  7. Send timing — Thursday peaks at 6.87% reply rate

Declining Effectiveness Trend

Reply rates dropped from 7–8% (2020–2022) to 4–5.8% (2024–2025), ~15% YoY decline. Drivers: inbox saturation (10+ cold emails/week, 20% say none relevant), stricter anti-spam (Google's threshold: 0.1% complaints), AI email flood (more volume, less quality signal). Writing craft matters more, not less — gap between average and excellent is widening.

Response Rates by Seniority

  • Entry-level: Highest engagement at 8% reply, 50% open
  • C-level: 23% more likely to respond than non-C-suite when they engage (6.4% vs 5.2%)
  • CTOs/VP Tech: 7.68% reply
  • CEOs/Founders: 7.63% reply
  • Heads of Sales: 6.60% (most targeted role, highest saturation)

Industry Variation

Highest responding: Nonprofits (16.5%+), legal (10%), EdTech (7.8%), chemical (7.3%), manufacturing (6.1%). Lowest responding: SaaS (3.5%), financial services (3.4%), IT services (3.5%).

Top 15 Mistakes (ranked by impact)

  1. Too long — 70% of emails above 10th-grade level. Under 75 words = 83% more replies
  2. Too self-focused — "We are a leading..." signals sales pitch. Count I/We sentences
  3. No clear value prop — 71% of decision-makers ignore irrelevant emails
  4. Generic templates — {{FirstName}} isn't personalization. Recipients detect instantly
  5. Feature dumping — "Great reps lead with problems" (Lavender). One proof point beats ten features
  6. False personalization — "Loved your post!" without specifics is transparent
  7. Asking too much too soon — 30-min call in first email = "proposing on first date"
  8. Pushy language — "Act Now" stacking increases spam flagging by 67%
  9. No CTA — Without a clear next step, momentum dies
  10. "Just checking in" follow-ups — "I never heard back" = 12% drop in bookings
  11. Wrong tone for audience — Founder ≠ RevOps lead ≠ sales leader
  12. Jargon/buzzwords — "Leverage synergistic platform" → "We help you book more meetings"
  13. Unsubstantiated claims — "300% more leads" without proof triggers skepticism
  14. Too many contacts per company — 1–2 people = 7.8% reply; 10+ = 3.8%
  15. Fake urgency — Fake "Re:" / "Fwd:" / countdown timers destroy trust

Cultural Calibration

Factor US UK Germany/DACH Scandinavia
Tone Direct, casual Polite, professional Precise, data-driven Fact-based, egalitarian
Length Shorter, blunt Longer, insight-led Detail-oriented Concise but substantive
Social proof Outcome numbers Research-led credibility Technical precision Shared values

North America: 4.1% response. Europe: 3.1%. Asia-Pacific: 2.8%. Shorter, more direct sequences work better in US. UK needs more insight/personality. GDPR affects European tone.

Expert Quick Reference

Expert Core Method Best For
Alex Berman 3C's: Compliment → Case Study → CTA High-ticket B2B services, agencies
Josh Braun "Poke the Bear" — neutral questions exposing invisible problems Empathy-driven consultative selling
Kyle Coleman Systematic research + AI personalization at scale Bridging mass outreach and deep personalization
Becc Holland Psychographic personalization, Premise Buckets Combining personalization with relevance
Will Allred Data-driven coaching, Mouse Trap, Vanilla Ice Cream Any context; universal frameworks
Justin Michael 1–3 sentence hyper-brevity, quote their own words High-velocity SDR teams at scale
Sam Nelson Agoge Sequence — Triple on Day 1 (email + LinkedIn + call) Multi-channel, tiered personalization