campaign-benchmarking

Installation
SKILL.md

Applies when a number needs a verdict. Produces the verdict, the layer it was judged against, and the action it implies.

A number without a comparison is not a result

A 5% reply rate is exceptional cold to enterprise executives and poor for warm re-engagement with existing users. The number alone tells you nothing. Benchmarking supplies the missing half — whether to celebrate, optimise, or stop.

Three layers, in order of usefulness

Layer 1 — external averages. Published figures aggregated across platforms and agencies. Use these as a sanity check only: they average across wildly different offers, segments, and levels of competence, so they're a floor for "is something catastrophically wrong", never a target.

Layer 2 — your own history. What the same motion produced for you before. This is the layer that actually drives decisions, and it's the one most teams don't keep. Building it costs nothing but the discipline of recording every campaign's outcome next to its offer, segment, and volume.

Layer 3 — like-for-like within your own book. The same offer to a different segment, or the same segment with a different offer. This is the only layer that isolates a variable well enough to be causal.

Always name which layer you judged against. "Below benchmark" means nothing until you say whose.

Compare like with like, or don't compare

A comparison is only valid when the offer, the segment, the channel, and the relationship temperature are held roughly constant. Campaign A beating campaign B tells you nothing if A went to a warmer list — which is how most internal "winning variant" conclusions get made.

Installs
13
GitHub Stars
99
First Seen
Jul 29, 2026
campaign-benchmarking — swan-gtm/gtm-skills