01 · Two abstractions, one budget
A campaign is a bounded send: copy, list, sequence, window. When the window closes, the artifacts go cold and the team starts the next one.
A system is a persistent surface: signal detection, enrichment, qualification, routing, reporting. Sends happen continuously inside it. Copy and lists are inputs, not the program.
02 · The hidden cost of campaign thinking
Campaign teams rebuild the same plumbing every quarter — list, infra, copy, dashboard, retro. The variable cost of every campaign is high because the fixed costs were never amortized.
Systems amortize. The fourth quarter of a system costs a fraction of the first because the signal definitions, enrichment graph, and qualification rules already exist.
03 · What a system actually contains
At minimum: a signal definition the whole revenue team agrees on, an enrichment graph with a canonical record, a routing layer with named owners, a qualification SLA, and a reporting cadence the leadership reads on Mondays.
Sequences and copy live inside the system. They are not the system.
04 · Ownership on day 91
The test is simple: on day 91, when the external operator leaves, can the in-house team run the surface without losing a week? If yes, it was a system. If no, it was a campaign with extra steps.