How to introduce a vendor to your client without risking trust

What is the right way to introduce a vendor to a client?

Get the client's permission first, explain in one sentence why this vendor fits something the client already cares about, disclose any reward you could earn, and then hand over and step back. That sequence protects the thing you actually own, which is the client's trust in your judgment.

The same sequence applies when the "vendor" is SourceX and the "client" is an owner you advise. SourceX manages data licensing between companies that hold proprietary records and AI developers. Your role is the introduction, nothing else. The owner makes every decision, and nothing is binding until the company agrees price and terms and signs.

What should you have in place before you ask?

You need to be able to answer four questions in your own words before you send anything. If you cannot, the client will notice.

• Why this client? Name the specific trait that makes the company a plausible fit, such as years of documented operations, records across many systems or a recent system migration.
• Why this vendor? Say what the vendor does, in a sentence a busy owner can repeat to a partner.
• What do I get? Know the reward terms well enough to describe them without reading from a page. Read the program terms and the rewards page first.
• What can I not say? Do not promise a price, a buyer, a timeline or a reward. You do not control any of them.

Also confirm that the company is a reasonable candidate. The guide to finding a private company's employee count and peak headcount shows how to check the 50+ full-time employees at peak (contractors excluded) baseline before you spend the client's goodwill.

How do you make the introduction, step by step?

Use five steps and do not skip the first.

1. Ask permission in a separate message. Send a short note that names the vendor and the reason, and asks whether the client wants an introduction. Do not copy the vendor yet.
2. Wait for an explicit yes. "Sounds interesting" is not a yes. If the answer is ambiguous, ask once more, plainly.
3. Send the introduction with both parties copied. Include who each person is, why you think the conversation is worth having and the disclosure sentence.
4. Hand over the next move. Say who will reach out. For SourceX, the simplest route is your referral link, which sends the company to sourcex.si/apply with your code attached so you keep credit while the company applies on its own terms. You can also use the referral form.
5. Step back and close the loop later. Check in once, a few weeks on, to ask whether the conversation was useful. Do not ask about the commercial outcome.

The introduction email builder drafts the email for step 3. If you do not yet know the company's exact legal entity, sort that out with the legal entity guide before the email goes out.

What does the permission email look like?

Keep it under 100 words. It should read as a question, not an announcement.

>

Notice what is missing: no price, no buyer names, no claim that the company qualifies. Qualification is SourceX's call after it reviews size, history, data breadth and rights.

Which introduction mistakes cost the most trust?

How should you handle the reward conversation?

Say it early and say it briefly. Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. The reward is paid only after the buyer pays and SourceX receives its fee; an introduction, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed.

The reward is a share of SourceX's fee and is never deducted from what the company receives. That is a fact worth telling the owner directly, because it answers the first question most owners have. If you are a licensed professional, check your own rules on referral fees and disclosure before you register. The guide on making an introduction when you can't accept a referral fee covers the alternative.

Illustrative: a managed IT provider's client

Illustrative and fictional. An IT consultant advises the owner of a 140-person logistics software firm that has migrated its support desk twice in nine years. The consultant sends a permission note that mentions the old ticketing archive and asks whether the owner wants an introduction. The owner replies two days later with a yes and a question about exclusivity. The consultant answers that deals are typically exclusive for AI training for an agreed term and that the owner can ask SourceX for details. The consultant shares the referral link, thanks both sides and leaves the thread. Three weeks later, one line: "Did the conversation turn out to be useful?" That is the whole job.

When should you not make the introduction?

Skip it when the client has not asked for new vendors, when the company obviously fails the baseline, or when the records belong to someone else, such as an outsourcer holding its customers' data. Also skip it when you feel you would need to downplay the reward to get a yes. The related question of whether this can strain a relationship is covered in will making an introduction hurt my client relationship?.

Next step

Pick one client, draft the permission email above and send it to no one but the client. If they say yes, register as a partner, use your referral link or the referral form, and review how it works so you can describe the process accurately.