How I Think About Campaign Orchestration
10 or 1,000 campaigns a month — no longer an issue. Explore a framework for deciding what gets sent, to whom, and in what order.
Most CRM teams don't have a campaign problem. They have a prioritization problem.
- Every stakeholder has a campaign that "must" go out
- Every campaign has an audience that overlaps with three others
- Every customer wants personalised & valuable offers at the right time
Orchestration is the layer that decides.
Explore the framework I use: 10 pieces that go from how you classify campaigns, to how you score and sequence them, to how you measure whether the whole system is healthy — not just whether one campaign performed.
01 · Foundation
Start with a single campaign taxonomy
Campaigns shouldn't be organized by who requested them. They should be organized by the type of impact they have on the customer and the business. Once every campaign has a type, that type carries a default priority — and service or transactional messages almost always outrank promotional ones.
02 · Audience model
Think in customer states, not segments
"Female, 25–35" or "owners of product X" describes who someone is — it doesn't tell you what to send them right now. A state does. States capture where a customer currently sits in their relationship with the business, so orchestration becomes a question of "what does this person need right now," not just "which campaign are they eligible for."
03 · Category logic
Eligibility and affinity, before anyone sees a category
With more than a handful of product categories, you can't send everything to everyone. Every customer needs four questions answered for every category, before it's even considered — the goal is a ranked list of what's most relevant right now, not a menu of twenty possible campaigns.
04 · Scoring
The priority matrix
A campaign should win a send slot because it scores highest — not because a stakeholder pushed hardest for it. A simple weighted score turns four eligible campaigns into a clear, defensible order.
| Order | Candidate campaign | Why |
|---|---|---|
| 1 | Complaint follow-up | Open negative context — must close before anything else lands |
| 2 | Delivery update | Transactional, time-sensitive, expected by the customer |
| 3 | New product launch | Sent only once context is clear — high business value, no conflict |
| 4 | Weekend promo | Lowest priority — sent only if the customer isn't already overloaded |
05 · Guardrails
Contact policy & frequency caps
Without caps, a thousand well-targeted campaigns still add up to noise. The policy needs to be explicit — daily and weekly limits overall, per-channel limits, and cooldowns after specific events.
| Message type / rule | Policy |
|---|---|
| Transactional | Always allowed — bypasses frequency caps |
| Critical / service | Always allowed |
| Sales promo | Max 2 per week |
| Survey / NPS | Not within 7 days of a complaint |
| Push notifications | Max 1 per day, unless critical |
| Loyal / high-value customers | Lower promo pressure, higher relevance threshold to qualify |
06 · Channel strategy
Channels have roles — omnichannel isn't "send everywhere"
The question isn't "should we duplicate this across channels." It's "which channel carries this specific meaning best" — matched to the customer state and the intent of the message.
07 · Content system
Personalization as modules, not manual work
Hand-personalizing every message doesn't scale. What scales is a library of content blocks that a CRM engine — or a human — can assemble within rules, based on the customer's state and signals.
08 · Governance
A campaign control tower
At scale, orchestration needs one place where the whole system is visible — whether that's a BI dashboard, a CRM calendar, a project tool paired with a dashboard, or a CDP decisioning layer. The tool matters less than having a single view.
09 · Rules
Write the conflict rules down in advance
This is where orchestration actually becomes real — not a philosophy, but a set of if/then rules the system enforces automatically.
| If | Then |
|---|---|
| Customer is in a complaint flow | Suppress sales promo |
| Customer just purchased | Suppress acquisition offers |
| Customer received a high-priority service message | Delay non-critical promo |
| Customer hasn't opened 5 messages in a row | Reduce send frequency |
| Customer shows high intent | Prioritize conversion support |
| Customer is loyal / high value | Don't over-index on discounting |
| Customer fits multiple categories | Pick the single top category by relevance score |
10 · Measurement
Measure the system, not just the campaign
Open rate, CTR, and conversion on a single campaign can be misleading on their own — a campaign can convert today and quietly erode engagement next month. The system needs its own set of metrics.
- Open rate
- Click-through rate
- Conversion rate
- Revenue per campaign
- Incremental lift vs. holdout / control
- Unsubscribe & opt-out impact
- Fatigue score, engagement trend by segment
- Revenue and LTV per customer
- Cannibalization between campaigns
- Retention / repeat purchase
- Complaints after a campaign send