Lesson 3.1.3
Suppression before spend: never pay for a row twice
What this costs
Free, and on a mature workspace it is the biggest single saving available.
Before you start
More than one project, and ideally a campaign history.
A refreshing list re encounters the same companies constantly. Without suppression you pay to enrich them again every cycle, and worse, you contact people who already heard from you last month. Suppression is the step that makes automation safe.
Four things to suppress against
- Companies already in another project in your workspace. Bring the existing data across instead of re researching it.
- People already contacted in a campaign. The worst outcome of automation is double touching someone.
- Companies explicitly excluded: existing customers, current opportunities, competitors, do not contact.
- Rows that failed the same check last cycle. If a company was rejected on a stable criterion, do not pay to re evaluate it every week.
- 1
Run the existing company check first, every cycle
Before anything paid. It is free and it removes the largest group.
- 2
Keep a suppression project
One list holding customers, open opportunities, competitors and do not contact. Every new list is checked against it.
- 3
Record rejections rather than deleting them
A deleted row gets re sourced and re enriched next cycle. A rejected row that you kept, with its reason, is suppressed for free.
- 4
Suppress before enrichment, not before export
Suppressing at export means you already paid. The whole saving is in doing it first.
Check yourself
0 of 2 answered1.When should suppression run?
2.Why record a rejection rather than deleting the row?
This lesson is written and complete. Its screen recording is still to come, and the written walkthrough is designed to stand on its own without one.