Why the suppression pass runs before the fit screen
Because a fit screen run first produces an attractive list, and attractive lists get worked. Once a company is tagged "strong fit", the decline sitting in a colleague's inbox starts to look like a misunderstanding.
The UK Information Commissioner's Office makes the underlying point in its direct marketing guidance: when someone no longer wants to hear from you, put their details on a suppression list rather than deleting them, because a deleted record leaves nothing to check the next list against. Its example is a company that erased a number and later called the person who had objected. Checking a new list against old objections is exactly what an inventory build is.
Timing matters too. The FTC's CAN-SPAM guide gives a sender 10 business days to honor an email opt-out. A business development team that rebuilds its inventory each quarter works far slower than that clock, so a no has to reach the record on the day it arrives; the inventory pass is the second check, never the first. Whether a particular note about SourceX counts as marketing in the legal sense depends on the message and the jurisdiction, and counsel can tell you. Run the pass either way.
Where a partner firm keeps its noes
Declines rarely live in one place. Before the pass, collect them from every source below.
| Where it sits | What it holds | How it goes wrong |
|---|---|---|
| CRM activity notes | "Not interested", typed by a colleague after a call | Free text nobody searches, with no scope and no date |
| The email platform's unsubscribe list | Opt-outs from newsletters and event mail | Kept apart from the CRM, so business development never sees it |
| A colleague's memory | "The CEO told me at dinner to drop it" | Gone when the colleague leaves |
| Engagement letters and client instructions | A client asked the firm never to share its name | Read by the engagement team, not by business development |
| Earlier asks for other programs | A no to a different vendor's referral or partnership pitch | Treated as irrelevant, though the person may have meant every such ask |
| The relationship owner's call | "Don't raise it with them this year" | Never written down, so a junior colleague asks anyway |
The consent and decline tracking template
The template has two parts: the fields every row carries, and a fixed set of states that says who is allowed to change each one.
Part 1, the fields. One row per person and company pair.
| Field | What goes in it | Rule |
|---|---|---|
| Key | An internal ID, never a free-text note | One row per person and company pair |
| Relationship owner | The colleague who can ask this person | A row without an owner cannot be asked |
| State | One of the eight states in part 2 | Exactly one state at a time |
| Scope of a no | This program, every data-licensing ask, or any outreach from the firm | When the words are ambiguous, record the wider scope |
| Source and date | Where the state came from, such as their email or the owner's call, and the day | No state without a source |
| Who may change it | The person, the relationship owner or a dated trigger | Set at the same time as the state |
| Public clues | Dated observations, kept in their own column | A clue never changes the state |
Part 2, the states.
| State | What it means | Next action allowed | Who can move it |
|---|---|---|---|
| Not yet asked | Nobody has raised the program | Ask the relationship owner first | The relationship owner |
| Owner will ask | The relationship owner agreed to raise it | The owner asks; nobody else does | The person's answer |
| Asked, no reply | Raised once, no answer | One follow-up at most, then treat it as a no | The person |
| Yes to a conversation | The decision-maker wants to talk | Prepare the introduction | The person |
| Declined, this program | A no to data licensing through SourceX | Nothing | Only the person, by raising it |
| Do not contact | A no to any outreach from the firm | Nothing, on any subject | Only the person |
| Owner said no | The relationship owner will not raise it | Nothing, and no route around the owner | The relationship owner |
| No fit on a published fact | A dated failure, such as peak headcount below 50 | Revisit only when the named trigger occurs | The trigger, with the owner's agreement |
The last column is the point of the template. Most suppression failures happen when someone with no standing moves a row: a new hire reads "declined" as "not yet asked", or a partner reads an acquisition announcement as permission. Here, a clue can be noted but cannot move anything.
Public clue, confirmed fact or inference
A clue tells you a question might be worth asking. It never tells you the answer, and it never outranks a recorded no. The rows below are Illustrative: generic companies, invented facts, no outcome implied.
| Row | What you have | Type | State and next action |
|---|---|---|---|
| A. 300-person freight forwarder | A job post, dated, for a data migration lead | Public clue only | Not yet asked: ask the audit partner who owns the relationship |
| B. 120-person engineering consultancy | In July the COO confirmed peak headcount, systems and the year records begin, and the CEO said yes | Confirmed company facts | Yes to a conversation: prepare the introduction |
| C. 210-person property manager | In March the CEO wrote "please don't raise this again"; in September the company announced an acquisition | A recorded no, then a clue | Declined, this program: the acquisition is noted in the clues column and changes nothing |
| D. Regional accounting practice | The managing partner says 38 full-time staff at the firm's largest | A failed published fact | No fit on a published fact: revisit only if peak full-time headcount reaches 50 |
| E. Client of the firm's tax practice | The tax partner says not during audit season | The owner's decision | Owner said no: nothing until the tax partner changes it |
Row C is the one teams get wrong. "They've just bought a competitor, they'll have twice the records" is an inference about volume. It says nothing about whether the CEO wants the conversation, and the CEO has already answered that.
Running the pass on a 40-contact inventory (Illustrative)
Illustrative. One business development lead's inventory of 40 contacts, run in this order:
- Merge. Every source in the table above goes into the template, one row per person and company pair.
- Suppress. Seven rows leave: three declined this program, two asked not to be contacted at all and two relationship owners said no. 33 remain.
- Find the asker. For 18 of the 33, the relationship owner agrees to raise it. The other 15 stay as "not yet asked"; nobody without the relationship goes ahead alone.
- Screen on known facts. Of those 18, nine look plausible on what the company has already told you: peak full-time headcount, records it created itself over several years, the right to license them and a CEO who might want to talk. Four fail a published fact and five have a key fact missing. Missing is not failing; it is a question for the relationship owner.
- Ask, through the owner. Nine people may now be asked. That is a permission list, not a forecast.
Swap steps 2 and 4 and the result looks the same on paper, but the seven suppressed rows would have been screened, discussed and ranked first. Some of them would have scored well, and a well-scored row is hard to leave alone.
What SourceX sees, and what stays inside your firm
Declines stay with you. Submitting a declined company to SourceX "just in case" is an introduction the decision-maker did not agree to, and SourceX's screening profile lists that among the cases that usually fail. The suppression record also tells SourceX nothing it needs: under section 3 of the terms, SourceX checks its own records before it invites an introduced company, so a person who declined you may already have spoken to SourceX directly, and you have no reason to know. Suppression has no effect on credit either way; section 2 decides credit from dated introductions and verified applications.
The state model also helps when a company asks you, months later, what happened to an earlier conversation. You can show the source and date of every state, and nothing else, because nothing else was kept. If you want to understand an outcome on SourceX's side instead, see why a company with extensive documentation can still be declined and how to understand why a referral was declined.
Where the template breaks
- A person changes jobs. "Do not contact" follows the person. "Declined, this program" was a decision for a company, so the new employer is a new row, and the relationship owner decides whether to open it.
- A company changes hands. The earlier no was the old CEO's decision. The new CEO is a new row; a sale is never a reason to hurry the ask.
- An assistant or shared mailbox replies. A no from either counts as a no.
- Silence. Silence moves a row to "asked, no reply", never back to "not yet asked".
- Over-recording. Keep the fields above and no reasons. Notes about a founder's finances, health or disputes have no place in an inventory, and the ICO's guidance on suppression is to keep only what you need to honor the preference.
For the wording of the ask itself, how to make a referral ask easy to decline and how to decline an introduction request cover both directions, and the difference between partner models is set out in channel partner versus referral partner.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
Once the pass leaves a short list of people whose relationship owners will ask, register, test each survivor against the screening profile and check the program terms before the first ask goes out.