Permission-based outreach is often summed up as "ask before you introduce". That is necessary and not enough. An ask can request permission and still make refusing expensive: the person has to invent a reason, wonder whether your service to them will change, or brace for three follow-ups. This page shows where that cost hides and how to remove it, using one company and four rewritten invitations.
What a no should cost: one reply, no reason, nothing else
The person you are asking owes you nothing. Their no should be as cheap to give as their yes, and in most first drafts it is not.
There is research on the words themselves. A 2013 meta-analysis in Communication Studies pooled 42 studies of the "but you are free" technique, in which a request ends by telling the person they are free to accept or refuse. It found the phrase raised compliance across request types, and that the effect was weaker when the decision was not made on the spot. Read that carefully. It suggests that stating the freedom honestly does not cost you willing yeses; it does not make the phrase a lever, and an email answered days later is exactly the delayed setting where the effect shrank.
The stronger reason is the program's own. SourceX's screening guidance lists introductions made without the decision maker's knowledge among the cases that are usually not a fit. A CEO who agreed only because refusing felt awkward is barely more willing than one who never knew, and the reluctance shows up later, when a real decision about records and terms has to be made.
The decline-cost audit
Score your draft on four costs. Each one is either raised (1) or lowered (0). Send only at 0 of 4.
| Cost to the recipient | Raised by | Lowered by | Test question |
|---|---|---|---|
| Effort | An open question: "What do you think?" | A yes-or-no question and the no already written | Can the answer be one word? |
| Explanation | "If not, let me know why" or saying nothing about reasons | "No reason needed" | Would a bare no feel rude? |
| Relationship | Tying the ask to your service, a past favor or your reward | "Nothing about our work changes either way" | Is anything else riding on the answer? |
| Pursuit | No word on what happens if they stay silent | Stating what you will do if you hear nothing | Does the person know whether you will chase? |
The audit measures the recipient's side only. It does not judge whether the company is worth asking about; settle that first, at metadata level, and ask only when the facts are specific.
The company behind the ask: facts the CEO can check
The examples below use one Illustrative company. A fractional CFO works with a 340-person third-party logistics operator. In a planning meeting the CEO mentioned that nine years of warehouse exception logs and customer service tickets sit in the warehouse management system the company plans to replace next year.
That gives the ask a reason only this company has: a record type, a span of years, a named system and a dated event the CEO raised. Every fact in the ask is one the CEO can confirm from memory. Nothing in it guesses at value, and nothing in it came from a file the CFO opened.
Decline-friendly invitation examples (Illustrative)
Four situations, the same company each time. Each pair shows the first draft, the rewrite and the audit score.
1. An email to the CEO you work with
Before (4 of 4): "I've been thinking about your warehouse data and I'm convinced there's real money in it. I've already mentioned you to a company called SourceX and they're keen. Can we get a call in the diary before month-end? Let me know what works."
After (0 of 4): "A quick yes-or-no question, and no is a perfectly good answer. When we talked about replacing the warehouse system next year, you mentioned nine years of exception logs and service tickets in it. SourceX licenses records like that from companies for AI training and evaluation, after its own review. Would you like me to introduce you? If it's not for you, reply 'not for us' and I won't bring it up again; if I hear nothing, I'll take it as a no. Our month-end work carries on exactly as before. One disclosure: if a license ever completed, SourceX would pay me a referral reward, never out of your payment."
The first draft fails before the audit starts: it named the company to SourceX without asking, which is the step a decline-friendly ask exists to prevent.
2. In person or on a call
Before (3 of 4): "You should really talk to these people. I'll set it up and send you the details."
After (0 of 4): "Can I mention something that's completely fine to wave off? Your old warehouse system might hold records an AI data company would want to license. Want a two-line note about it, or shall I leave it there?"
"Leave it there" is the pre-written no. It costs the CEO three words.
3. Through someone who would have to raise it with the CEO
Before (3 of 4): "Could you get your CEO on a call with SourceX next week?"
After (0 of 4): "Would you be comfortable mentioning this to your CEO? If you'd rather not raise it, that's the end of it, and I won't go to them myself."
Here the person with the decision cost is the operations director, not the CEO. The rewrite gives them an exit too, and promises not to go around them. The CEO still authorizes any licensing discussion; a sponsor can carry the question, but cannot answer it for the company.
4. The only follow-up, when the first message promised none
Before: "Just bumping this to the top of your inbox! Did you get a chance to think about it?"
After: nothing. The first message said silence would be read as a no, so the thread is closed and recorded that way.
If your first message did not say what silence means, send one closing note at most: "Last note on this, then I'll leave it. If it's ever useful, just tell me."
Reading the reply without reopening it
| Reply | What it means | What you do | What you record |
|---|---|---|---|
| "Yes" | The CEO wants a conversation | Confirm by email, then introduce | The date and the CEO's words |
| "Not now" | A timing answer | Ask whether they want it raised again, and when | Their date, not one you chose |
| "No" or "not for us" | A complete answer | Thank them and ask nothing more | The no, dated, with no reason field |
| Silence | No decision | What your ask said you would do | Closed, with the date |
| "Ask my CFO" | A delegation to prepare, not an authorization | Brief the CFO; the CEO still decides | Who said what, and when |
Leave the reason field out on purpose. Recording a reason the person never gave turns a clean no into a guess that someone may later act on.
What a yes commits the company to, and what it means for you
A yes buys the CEO a conversation, nothing more. In that conversation SourceX explains that it licenses data straight from businesses, only what each one approves, for AI training and evaluation, and that it runs the agreement, rights review, data preparation, delivery and payout itself. SourceX may speak with the company directly, and you need not join every call. The company decides what scope it offers and which terms it accepts, and nothing is shared without its approval. Telling the CEO that also keeps later exits easy: agreeing to a call is not agreeing to a license.
Whether the company fits is SourceX's decision in review. The published screen asks for 50+ full-time employees at peak with contractors excluded, years of documented operating history, records the company has the rights to license, and a CEO who authorizes the discussion. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. For the logistics operator, size and history look clear; whether customer contracts limit use of the service tickets, and whether the exception logs match SourceX's current data needs, is unknown until review. Your questions stay at metadata level throughout: no samples, exports or logins.
Your incentive belongs in the ask as information. Under the program terms the reward is the greater of $50,000 plus 5% and 15% of what SourceX actually pays the company, with no cap in total, paid separately by SourceX and never deducted from the company's payment. A lead or a meeting earns nothing on its own, and under the agreement you sign you must never describe a purchase or reward as guaranteed by an estimate, interest or a signature. Partners sign the SourceX Channel Partner Agreement before submitting introductions. How to word the disclosure line is covered in disclosing a reward naturally.
One voluntary next step, and no clock you invented
Offer exactly one thing: a short email introduction, copied to the CEO, after which SourceX arranges a call with them. The only date in the ask should be one the company named, here next year's system replacement, which is a real reason to look at records before they are archived. Month-end, "this week" and "while there's room" are your clocks, not theirs.
If you cannot accept a reward at all, the ask works the same way with an unpaid disclosure; introducing a company when you can't take a fee covers that path. For the permission email that follows a yes, use the double opt-in templates; for the opposite job, turning down someone else's request, see how to decline an introduction request.
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.
When your draft scores 0 of 4 and the CEO has answered yes in their own words, open a partner account, check the company once more against who qualifies and read the attribution section of the program terms before you submit; other message guides are collected under guides.