# Supplier relationship data referrals: 7 gates | SourceX

Canonical: https://refer.sourcex.si/guides/when-a-supplier-relationship-opens-a-company-introduction
Last updated: 2026-11-04

A supplier relationship opens an introduction only when two things hold: the company's CEO can say no at no cost to the commercial relationship, and your reason for asking rests on public clues or on what the company tells you for this purpose. Which side of the invoice you sit on sets the main risk. If you buy from the company, it is leverage. If you sell to it, it is what you learned while serving it. Introduce only after the company confirms the screening facts itself.

A business development lead at a channel partner sees both kinds every week: the vendors the firm buys from and the customers it serves. Both can lead to a good conversation. Neither is a list to work through.

## Which side of the invoice are you on?

Start by naming the direction, because each one has a different owner and a different way of going wrong.

| Direction | Who owns the relationship | What goes wrong | What keeps it clean |
|---|---|---|---|
| You buy from the company: it is your supplier | Whoever in your firm manages that supplier day to day | The supplier hears a customer's request and does not feel free to refuse | Ask outside any tender, renewal or price talk, never from procurement, and say in writing that the answer has no bearing on orders |
| You sell to the company: you are its supplier | Your account lead for that customer | The ask rests on what you saw while delivering your service | Use public facts and what the CEO says now; read the confidentiality clause in your contract first |
| Your client buys from the company | Your client, not you | You spend your client's goodwill with its own supplier | Your client decides whether to raise it at all; a no ends the route |

The selling side is where most partners underestimate the constraint. Large customers write it down. Microsoft's Supplier Code of Conduct, in its July 2026 version, tells suppliers to "protect confidential information" and to "use Personal data only as agreed to by Microsoft representatives or Microsoft's customers." Its commercial supplier terms on the U.S. General Services Administration schedule go further, saying each party "will use the other party's Confidential Information only for purposes of the parties' business relationship." Those are one company's documents, quoted to show how such clauses read; your own contract governs you. A licensing introduction is not the purpose a managed-services or consulting contract was signed for, so knowledge gained under it cannot be the reason you ask.

The buying side has the opposite problem. Nothing you know is confidential, but your request carries weight you may not feel. A supplier whose second-largest customer suggests a conversation may agree simply to stay agreeable, and a yes given that way is not the CEO's free choice.

## The public clue and the person who can ask

A supplier relationship makes some clues easy to see. Use them to decide whom to ask and what to ask, never as facts about the company's records.

- **An accredited quality certificate.** IAF CertSearch is a database of accredited management system certifications, such as ISO 9001, where a certificate's status, scope and issuing body can be checked against a named organization. A current certificate suggests a company that runs a documented quality system. It does not show who owns the resulting records, how far back they go, whether they are any good or whether anyone wants them.
- **Years of trading with your firm.** Your purchase history tells you the supplier has operated steadily for a long time. It is your firm's information, useful for deciding whether to ask, and it never appears in an introduction.
- **The supplier's own publications.** Case studies, a project list or a dated "since" line on its website. These say what the company chose to show customers.

Then name two people. Inside your firm: the person who owns the relationship and must agree before anyone else speaks. At the company: the person that owner can reach who will take the topic to the CEO. If either name is missing, the route stops there. A long-standing link between your warehouse team and their dispatch office is a relationship between two operations teams, not a path to a CEO.

## The supplier-contact permission pathway

Seven gates in order. Each one can end the route, and none of them asks anyone to open a file.

| Gate | The question | Passes when | Stop or wait when |
|---|---|---|---|
| 1. Direction | Do we buy from them, sell to them, or know them through a client? | One line in your notes names the direction and the owner | Nobody can say who owns the relationship |
| 2. Clue | What public, dated fact makes this company worth a question? | A source anyone could check, with the date you looked | The only reason comes from delivering your service or from a client's confidential information |
| 3. Owner | Will the relationship owner ask, or let us ask? | The owner agrees, in writing or in a logged conversation | The owner, or your client, declines |
| 4. Timing | Is anything commercial open between the two firms? | No tender, renewal, price negotiation, dispute or audit is running | Something is open: wait until it closes |
| 5. Contract | Do our agreements limit this contact or this use of information? | Confidentiality and non-solicitation clauses, and any supplier code, allow it | A clause bars it, or your counsel cannot clear it |
| 6. Permission | Will the contact hear an unrelated topic and carry it to the CEO? | Yes, after hearing that the introducer may be paid a reward by SourceX | No, or "only if it helps our account" |
| 7. Confirmation | Does the company itself confirm the screening facts and want the conversation? | The CEO confirms them and says yes | A fact fails, or the CEO is not interested |

Gate 4 is the one partners skip. A permission request made during a price negotiation reads as part of the negotiation, however carefully it is worded. Waiting six weeks costs little; the company's records will not disappear because a renewal closed first, and if a documented migration or deletion date really is close, that date can be named plainly as the reason for raising it now.

Gate 6 includes the disclosure on purpose. The terms describe the reward as paid separately by SourceX and never taken out of what the company receives, and a supplier deciding whether to hear the topic deserves to know that its customer or vendor has an interest.

## What you saw, what you assume and what the company confirmed

Keep three registers apart in your notes, and send only the third.

| Statement | Register | Who can move it to confirmed |
|---|---|---|
| Accredited ISO 9001 certificate, current, scope covers machining at one site | Observed: public database, dated | Already public; says nothing about records |
| Keeps nonconformance and corrective-action history | Inferred from the certificate | The quality manager, through the CEO |
| Has supplied us for nine years | Observed: our own records | Not shared; context for us only |
| More than 50 full-time staff | Inferred from plant size and shifts | The CEO or the finance lead |
| The records are the company's to license | Unknown | The company, then SourceX's rights review |
| The CEO wants a conversation | Unknown until asked | The CEO alone |

The inference column is where supplier relationships mislead most. You may know a vendor's plant manager, its delivery record and its quality escapes in detail. None of that is the company telling you what it owns. Corrective-action history in particular can be a rich record family, as the [supplier corrective action guide](/guides/workflow-supplier-corrective-action-closure) shows, and it is precisely the material most likely to mention customers by name.

## Three suppliers on the pathway (Illustrative)

Illustrative. Generic companies, invented facts, no outcome implied.

**A. You buy from it: introduced.** A 240-person contract machining shop has made parts for your firm's assembly work for nine years. Its accredited ISO 9001 certificate shows as current when your operations director checks on 20 Oct 2026. The director owns the relationship and agrees to ask, but only after the annual price review closes on 15 Nov. In a separate call, not at a commercial meeting, the shop's general manager hears the topic and takes it to the CEO. The CEO confirms 240 full-time staff, work-order and inspection records in its ERP since 2011, and says yes. One complication is written down rather than solved: some of what the shop holds are drawings your own firm supplied, which it cannot license. That stays out of scope, and your counsel, not the referral conversation, handles any question about it.

**B. You sell to it: parked.** Your firm manages IT for a 130-person engineering consultancy. Your technicians know its file server holds project folders back to 2008; that knowledge is off the table. The public clue is the project list on its website, which starts in 2009. The account lead asks the CEO whether she would hear an unrelated topic. She would, and she volunteers that most project files contain clients' drawings and data. The rights picture fails gate 7 for project files. The row is parked with a note that internal QA checklists and proposals are the company's own and might be worth her asking about later.

**C. Your client's supplier: stopped.** Your client, a regional grocery chain, buys from a 400-person produce distributor with decades of trading history. You ask your client whether it would mention the program. It declines, because it is renegotiating supply terms. The route ends at gate 3, the row is marked "owner declined," and nobody approaches the distributor another way.

## Asking permission, then routing only what still holds

The permission request should be short enough to decline easily. For a supplier you buy from, something like: "This is nothing to do with our orders, and a no changes nothing between us. Would your CEO want to hear about a program that pays companies to license their own operating records? If I make the introduction, SourceX may pay me a referral reward, which never comes out of your company's payment." Then stop talking and let the contact decide whether it goes any further.

If the CEO wants the conversation, the company confirms the screening facts in its own words: full-time headcount at its peak with contractors left out, the records it created itself with their systems and start years, who else might have a claim on them, and its location. 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. Suppliers abroad make that sentence matter more than usual.

Before submitting, sign the SourceX Channel Partner Agreement. Credit is decided from dated records, and section 3 of the terms treats a company as already known if there was "any earlier lead, account or email correspondence between SourceX and the company, however it began", so ask the CEO about earlier contact and record the answer as the CEO's. If the company relies on outside vendors for parts of its operations, the [summary for a business with outsourced operations](/guides/a-referral-summary-for-a-business-with-outsourced-operations) shows how to keep those vendors out of the questions. Worried about the relationship itself? The live answer on [whether an introduction can hurt a client relationship](/questions/does-referring-clients-hurt-relationship) covers the client side; the gates above cover the supplier side.

## Where supplier relationships mislead

- **Familiarity is not fit.** Years of reliable deliveries say nothing about full-time headcount at peak or about who owns the records.
- **Pressure you cannot see.** From your desk the request is casual. From the supplier's, it comes from a customer. Gate 4 and the written separation from orders exist for that reason.
- **Your own material in their files.** Drawings, specifications and forecasts your firm supplied are part of the supplier's records and belong to you, which complicates the scope before it starts.
- **Certificates are narrow.** A certificate's scope can cover one site or one process, and status changes. Date every check.
- **Spend is not size.** A supplier you pay a great deal may be small, and one you barely use may employ hundreds.

## 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 a supplier has cleared all seven gates and its CEO has said yes in the CEO's own words, set up your partner account at [registration](/register), compare what the company confirmed with [who qualifies](/who-qualifies) and read the [program terms](/terms) before the introduction goes out. Related sourcing guides, including [reading public operating-history signals](/guides/how-to-spot-useful-operating-history-without-knowing-revenue), are in the [guides hub](/guides).

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/microsoft/accex/documents/presentations/Microsoft%20Supplier%20Code%20of%20Conduct.pdf
- https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/microsoft/final/en-us/microsoft-brand/documents/mcaps-MSFT-GSA-Commercial-Supplier-Agreement-Terms.pdf
- https://www.iafcertsearch.org/verify-certificates
