SiSu RevOps

M7  /  L7.4  /  about 13 minutes

Lists that reconcile, drafts that get reviewed

Why this matters

A campaign goes out. Forty recipients are existing customers, two are in an active negotiation with your own AE, and one asked not to be contacted fourteen months ago.

Nobody chose any of that. The list came from a correct rule, and the records that should have been removed were never in anybody's head as a category. With no reconciliation, nothing announced the skipped step.

What you will be able to do

  • Write suppression as first-class rules rather than a final tidy-up.
  • Produce a count reconciliation that proves nothing was silently dropped.
  • Tell a sourced personalisation line apart from a plausible one.
  • Write the review gate between a draft and a prospect, and name who owns each part.

Suppression is a rule set, not a filter you remember

40-reference/suppression-rules.md, which you write once in this lesson (a seed is at templates/M7/suppression-rules.md in your practice pack) and apply to every list you will ever build:

Rule Why it exists
Existing customers, unless the campaign is for customers The campaign that offers a new-logo discount to a renewing account
Accounts with an open opportunity The AE finds out from their prospect
Do-not-contact and opt-out Legal, and it is the one people find out about publicly
Recently contacted, within N days Sequence collision across teams
Competitors and partners Obvious afterwards
Bad or role-based email addresses Deliverability, which you own even when a tool sends

Three of those are measurable in this dataset right now: 87 accounts are customers and 17 are churned; 62 open opportunity rows sit across 62 distinct account references, 61 of which resolve to a real account (one row carries an account_id that does not exist, which is why the suppression step counts references rather than trusting the join); and 75 of 911 contacts carry opted_out = TRUE with an opted_out_date.

And the failure is already in the data. answer-keys/PLANTED-ISSUES.md in your pack, which you open only after attempting the lab, documents a compliance-optout class of 22 rows in activities.csv: emails recorded as sent after the contact's opt-out date. ACT-0041324, for instance, records an email sent on 2026-03-08 to CON-009112, who opted out on 2025-05-01. Somebody built a list, the suppression step was not in it, and the send happened.

That is why, in LAB-07, the exercise sheet in labs/LAB-07 of your practice pack (start with its README), a segment holding an opted-out contact counts as a safety failure, not a completeness deduction. It is not an incomplete list. It is a list that does harm.


The reconciliation ladder

A segment list states its inclusion rules, its exclusion rules, and a ladder counting every excluded record. If the numbers do not add up, something was dropped without anybody deciding it. Here is a real ladder from the shipped data, targeting EMEA mid-market and enterprise prospects in the four core industries:

ACCOUNTS
  308   accounts in file
- 104   existing customers and churned logos
-  41   accounts with an open opportunity
-  64   SMB segment, out of scope for this campaign
-  29   region is not EMEA
-   9   industry not in Retail, Hospitality, Logistics, Healthcare
=  61   accounts

CONTACTS
  188   contacts at those 61 accounts
-  12   opted_out = TRUE
-   4   role-based mailbox (sales@, admin@, accounts@, rota@)
-   1   malformed or untrimmed email address
-  29   seniority below Manager
= 142   contacts

Three things this ladder does that a total does not.

It proves nothing vanished. 308 minus the five exclusion counts equals 61, exactly. If not, a record was lost between two steps, and you go find out where.

It makes the expensive rule visible. The largest exclusion is 104 existing customers, then 64 for segment. Whoever wants a bigger list sees which rule to argue about, and "SMB is out of scope" is a business decision somebody can reverse in a meeting.

It catches the silent drop. The industry step is where this dataset bites: accounts.industry holds ' Retail' with a leading space, 'logistics' in lower case and 'Hospitality & Leisure' (data/DATA-DICTIONARY.md in your practice pack). A rule matching industry = 'Retail' exactly drops ACC-02948 and never mentions it. Normalise first, and print how many records changed under normalisation. That turns a silent drop into a line in the ladder.


A sourced line and a plausible line

Two personalisation lines for the same account, ACC-02830, Wexley Care Group GmbH. Both read well. One can be checked by a reviewer in forty seconds without opening the CRM.

Line A: sourced

You are running Talvera Shift at 92% seat utilisation across your licensed base with the payroll sync module switched off, and your team costed the fortnightly manual payroll export at two full-time-equivalent days per cycle.

Evidence: product_usage.csv, ACC-02830, 2026-07, seat_utilization 0.924, feature_payroll_sync = FALSE. Second claim reported by the customer on the QBR call and not verified by Talvera: notes/qbr/business-review-wexley-care.md.

Two claims, two source lines, and the second carries its marking through, because the source marks it as the customer's own costing. A reviewer reads the evidence block, opens one file, and approves.

Line B: plausible

As a healthcare group scaling across multiple sites, you are likely wrestling with the compliance reporting overhead that comes with fragmented rostering data.

Nothing in that sentence is false. Nothing in it is checkable either. It was not read out of any file; it was inferred from the account being in healthcare with more than one site. It will pass a skim review, land as generic, and if the prospect answers "actually our compliance reporting is fine, that is the one thing we sorted last year", the seller has nothing to fall back on.

The test is one question: which file and which record would I open to check this? No answer means a plausible claim, and it does not go in a customer-facing asset as a statement about the customer.

What a good reviewer says about line B

The line is fluent, on-brand, and not usable, and not because it is wrong. It may well be true. Nobody can establish whether it is true, so it is not personalisation, it is a segment-level assumption in the second person.

Which file and record would you open to check "wrestling with compliance reporting overhead"? No answer. Meanwhile this account's own folder holds, with no external research: seat utilisation at 92.4% in the most recent month, the payroll sync module switched off, an open 74,000 EUR expansion on payroll sync and compliance reporting, and a QBR document in which the customer's own operations director costed the manual payroll workaround. Four checkable, specific, unused facts.

An inferred line is also invisible to a review gate: a claim with no source presents nothing to check, so it passes. The gate fails silently, which makes this class of line the one most likely to reach a prospect.

Fix the brief, not the draft. Add: "Every personalisation line carries an evidence block naming the file and the record it came from. A line that cannot carry one is not written." Re-run and count how many drafts lose their opening sentence. That count is how much of your personalisation was ever personal.

If you want the industry framing, keep it and label it. "Teams like yours often tell us X" is a claim about your other customers, not this one, and checkable against your own data if you state the number.


Draft-only, and what makes a draft reviewable

Sequence drafts and campaign briefs are draft-only by definition, stated in the output header, not assumed:

BLAST RADIUS: draft-only
Reviewed by: <name> (factual claims), <name> (messaging), <name> (product and
regulatory claims)
Not to be sent until all three have signed.

A draft is reviewable when the evidence travels with it: every personalisation line carries its evidence block underneath, so a reviewer checks the claim without opening the CRM. Strip the blocks before sending; keep the version with them in 30-output/demand/.


The review gate, written down

40-reference/review-gate.md, which you write now (a seed is at templates/M7/review-gate.md in your practice pack). This is your own policy, and the file says so; the product does not enforce it.

What is being reviewed Who owns it What they are checking
Factual claims about the account The seller who owns the account Every evidence block resolves, and nothing is stated that the record does not support
Messaging and positioning Marketing or brand It sounds like the company, and it does not promise something the product does not do
Product claims and regulated segments Legal or compliance Anything making a product claim, and anything touching a regulated segment or region
Suppression Whoever owns the list The ladder reconciles, and the opt-out count is not zero when it should not be

Two lines belong underneath the table:

  • Nothing generated in this module reaches a prospect without a human reading it. Not a sample. Every asset.
  • Deliverability, consent and regional contact rules are outside the scope of this course and are your own obligation. We teach the suppression discipline. We do not tell you what the law is where you operate.

Keep the rules, not the output

The segment expires in a month. The briefs expire the day after the meeting. What survives:

  • 40-reference/icp-rules.md, with its fire-rate check dated.
  • 40-reference/suppression-rules.md.
  • 40-reference/review-gate.md.
  • 20-briefs/account-research.brief.md.

Each is a document most GTM teams have never written down, each is portable to any tool, and none depends on this product. Cowork carries no memory between sessions, so these files are not documentation of your process. They are your process.


Try this now

  1. Write 40-reference/suppression-rules.md from the table above, one row per rule.
  2. Build the segment from your ICP scores, with the reconciliation ladder alongside the list: every exclusion counted, normalisation changes counted too.
  3. Check the arithmetic. If the ladder does not add up, say: "A record was lost between two steps. Find which step, and show me the records."

What you keep

  • 40-reference/suppression-rules.md and 40-reference/review-gate.md.
  • 30-output/demand/segment-YYYY-MM-DD.csv with its reconciliation ladder in a header comment or a companion markdown file.
  • At least one draft asset with an evidence block under every personalised claim, and its blast radius stated in the header.

Check yourself

  1. Your segment ladder starts at 1,209 leads and ends at 300, and the exclusions add to 880. What do you do before you send anything?
  2. Marketing asks you to drop the open-opportunity suppression because it costs 41 accounts and the list is small. Give the answer, and the alternative that meets them halfway.
  3. A reviewer approves a sequence in four minutes across twelve accounts. What can they not have checked, and what change to the draft format would have forced it?
  4. Which of these needs legal review before it leaves the folder, and why: (a) a subject line; (b) "cuts payroll reconciliation time by half"; (c) a personalisation line quoting the prospect's own published headcount; (d) a follow-up to a contact in a regulated healthcare segment.

Where this goes next

LAB-07 runs the whole pack on the shipped dataset with a detection scorecard that scores your suppression, then on your own data behind the redaction gate. M8 turns to the accounts you already have: the same brief pattern becomes a QBR pack, and the work starts repeating on a cadence you have to design.