Developer tools sit unusually close to a customer's most sensitive history: its code, its defects, its outages. That is why the introduction has to look nothing like a vendor taking an interest in customer data, and why the map below starts with people rather than with what your product can see.
What sits where: customer content, product analytics and your own records
Three layers sit inside a developer tool vendor, plus a fourth that is easy to confuse with them. Only one of them is ever the subject of a license, and it is never the vendor's to offer.
| Layer | What it is | Who owns or controls it | Its role in an introduction |
|---|---|---|---|
| Customer content | Repositories, issues, review threads, pipeline logs and incident timelines stored in your product | The customer | The subject of any license, decided by the customer alone |
| Product analytics | Usage telemetry collected to run and improve the service, such as seats, activity and feature use | You, within your terms and privacy commitments | None: never used to select, rank or describe a customer |
| Relationship facts | Who your contacts are, company size as the customer states it publicly, what customers have asked you about | Your account team | The only basis for deciding whom to invite |
| Your own records | Your company's own engineering and support history | You | A separate question about licensing your own data |
GitHub's terms show a common form of the first row: users retain ownership of and responsibility for the content they create, and the rights they grant GitHub are limited to what it needs to provide the service. Read your own customer agreement for the equivalent clause before anyone drafts outreach. Choosing customers from telemetry is a separate trap with its own guide, keeping usage analytics out of customer referrals. The fourth row belongs on sourcex.si, which covers what engineering data a developer tools company holds and can license itself.
Who inside a customer can turn interest into a conversation
The benefit has to be the customer's. A customer company may license its own engineering history directly to SourceX and be paid by SourceX for it; it keeps ownership because it grants a license rather than selling, as the guide to keeping ownership when licensing explains; and it can start with a short assessment with no uploads needed. The vendor gains a customer conversation that has nothing to do with its own product, and possibly a referral reward.
The records that tend to matter are the ones engineering teams generate as a by-product of work: issue tracker histories, pull requests and code reviews and incident and on-call records. Which of them a customer can license is decided in SourceX's rights review.
Fit comes before enthusiasm. The customer company needs 50+ full-time employees at peak, with contractors excluded, which matters for engineering organizations that lean on outsourced teams. It needs years of its own records, the rights to license them and an authorized contact. 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. Development agencies need extra care: code and tickets built for clients often belong to those clients, as the agency code ownership page explains.
The engineering-owner sponsor map
The map names every role around one decision, on both sides of the relationship, and gives each role exactly one job. The person your team talks to most is rarely the person who matters most here.
Inside the customer
| Role | What they own | Their part in the decision | How you reach them | Never ask them for |
|---|---|---|---|---|
| Tool admin or team lead, your daily contact | Your product's configuration | None, beyond pointing you to the engineering owner if asked | Normal account contact | Exports, access or counts from inside your product |
| Engineering owner, usually the CTO or VP of Engineering | The engineering records and the systems they live in | Sponsor: describes record types and years, and raises the idea with the CEO | Your executive sponsor or account executive | Samples or repository access |
| CEO | The company | Authorizes a licensing discussion and signs for the company | Through the engineering owner, or an existing executive relationship | A commitment before SourceX's review |
| Legal, security or privacy lead | Customer contracts, NDAs, personal data in tickets | Advises on rights; feeds SourceX's review | Only through the customer's own team | Contract copies |
Inside the vendor
| Role | What they own | Their part | What they never do |
|---|---|---|---|
| Account executive or customer success lead | The relationship | Makes the single ask of the engineering owner | Mentions usage figures |
| Partnerships director | The program | Registers, signs the Channel Partner Agreement and submits introductions the CEO wants | Promises acceptance or a payout |
| Product analytics and data teams | Telemetry | None | Supplies lists, scores or segments for this program |
| Legal | Your customer contracts and marketing consents | Confirms the outreach is permitted | Interprets the customer's rights to its own records |
Read the map as two rules. The path climbs from your relationship to the engineering owner to the CEO and never runs through the product. And each role gets one ask: the engineering owner is asked to sponsor, not to approve, and the tool admin is not asked for anything.
Admin access, support access and the customer's decision
Your support engineers may be able to open a customer's repositories under your terms. That access exists so you can provide the service, and it says nothing about what the customer may do with its records or what you may say about them. Nobody on your side sizes, samples or describes a customer's records for this program.
Do not stretch your terms to make room either. FTC staff wrote in February 2024 that it may be unfair or deceptive for a company to adopt more permissive data practices, such as using data for AI training, and to tell users only through a surreptitious, retroactive change to its terms or privacy policy. An introduction program needs no change to your terms at all, which is one of its strengths. Whether your contract and marketing consents allow you to raise the topic is a separate check, covered in when your customer contract restricts promotional outreach.
What SourceX hears from you is short: the company's name, the engineering owner who agreed to talk, and that the CEO wants a conversation. It does not hear seat counts, repository counts or activity levels.
The partner role is narrower than the alliances most software companies know. Microsoft describes co-selling as any collaborative engagement between Microsoft and its partner ecosystem, including building demand, sales planning and sharing sales leads. A SourceX introduction has no joint sale and no deal role for the vendor: the customer applies, contracts and is paid directly, and the vendor's part is finished once the introduction is made. Say plainly that you may receive a referral reward, paid separately by SourceX and never deducted from the customer's payout; the guide to discussing rewards transparently has wording.
Three customer engineering teams on the map (Illustrative)
Illustrative. Generic companies, invented facts, no outcomes implied.
A. A fit with a willing sponsor. A 240-person logistics software company has used your issue tracker and code review tool for nine years. Its VP of Engineering asked your account executive at a roadmap session whether old engineering history has any value. The account executive explains the program in two sentences; the VP raises it with the CEO, who wants a conversation; your partnerships director submits the introduction. If that company later licensed records and SourceX's Actual Supplier Payout were $250,000, the default reward would be $62,500. That is Illustrative arithmetic, not a forecast.
B. An agency whose records are mostly its clients'. A 75-person development agency runs most client projects in your product. Its contracts assign code and project records to clients. Client-owned material is usually not a fit, so there is no introduction on those records. If the agency's own internal tooling and process history is substantial, that is a different conversation its CEO can raise directly.
C. Strong engineering, too small today. A 32-person developer platform startup has meticulous review history but has never had 50 full-time employees. The row is marked "revisit" with one condition: full-time headcount passing 50.
| Case | Engineering owner | CEO | Records | Next move |
|---|---|---|---|---|
| A, logistics software company | VP of Engineering sponsors | Wants a conversation | Its own, nine years | Introduce |
| B, development agency | Not asked | Not asked | Mostly clients' | No introduction on client records |
| C, platform startup | Interested | Not asked | Its own, but under 50 at peak | Revisit when headcount passes 50 |
A first cohort of opt-in introductions
Start with customers who raise the subject themselves, then add one opt-in invitation for engineering leaders, sent through a channel they already chose, such as a customer advisory board. A workable invitation: "If your company has years of its own engineering history and wants to know whether licensing it is an option, we can introduce your CEO to SourceX. We see none of your records and play no part in any deal."
Measure five things for the cohort: invitations sent, engineering owners who opt in, engineering owners who name and approach their CEO, CEOs who want a conversation, and any customer who raises a trust concern. Set the stop rule before the first invitation: one complaint about data handling pauses the program until you understand it. Results from cohorts like this have not been published, so your own counts are the evidence; keep them per stage rather than as one conversion rate.
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 an engineering owner has raised the idea and the CEO wants to talk, your next moves are to register for a partner link, compare the customer with who qualifies and read the program terms, all before you submit anything. The software and SaaS industry page and the guides hub cover adjacent cases.