A partnerships director who is used to integration-led programs will notice what is missing before noticing what is there. This page sets out both, then gives a 13-week pilot blueprint that tests whether the motion fits your customer base.
What "no integration" removes, line by line
Most SaaS partner programs are built around connecting products or listing them somewhere. This one connects people, and only when one of them asks.
| Element common in SaaS partner programs | In SourceX's introduction-only program |
|---|---|
| API, webhook or data connector | None; nothing connects to your product |
| Marketplace listing or published offer | None required |
| Technical validation or architecture review | None for the partner; SourceX reviews the referred company instead |
| Co-marketing collateral | None required; the public pages on this site describe the program |
| Revenue or consumption thresholds to join | None |
| Customer data flowing through the partner | None; the customer works with SourceX under its own agreement |
| What the partner actually does | Introduces an authorized decision-maker who wants the conversation |
| What partner pay is based on | Actual Supplier Payout, never SourceX's fees, after the conditions in the terms are met |
The trade-off is plain. You get no access to anyone's sales force, no listing and no joint pipeline. What you get is a way to point a qualifying customer at an opportunity that concerns its own records, without your product being part of it.
How an introduction-only motion compares with a co-sell program
Microsoft's Partner Center is a well-documented example of the integration-led model, so it makes a useful benchmark. Its co-sell overview describes statuses for Azure offers, from In-market to Co-sell ready to Azure IP co-sell eligible, each with its own requirements. According to Microsoft's co-sell requirements page, checked on 2026-10-26, co-sell ready needs a live offer on Microsoft Marketplace, a complete business profile, a sales contact for each co-sell-eligible geography, a solution one-pager and a pitch deck, with a reference architecture diagram required for SaaS offers. Azure IP co-sell eligibility adds Microsoft technical validation and a revenue threshold of USD 100,000 in Azure consumed revenue over a trailing 12 months or USD 100,000 in cumulative marketplace billed revenue. That threshold is Microsoft's and has nothing to do with SourceX's program, which sets no entry threshold for partners and no cap on rewards.
| Criterion | Microsoft co-sell, as documented | SourceX introduction-only |
|---|---|---|
| Prerequisite build | A live Marketplace offer; an architecture diagram for SaaS offers | None |
| Validation | Microsoft technical validation for IP co-sell | None for the partner; SourceX reviews each referred company |
| Entry threshold | A revenue threshold for IP co-sell | None |
| What the partner gains | Co-selling with Microsoft sales teams and partners | A reward based on what SourceX pays the referred company, once conditions are met |
| What is being sold | Your solution | Nothing of yours; the customer may license its own records |
| Customer data through the partner | Depends on the solution | None |
Neither model is better in general. They answer different questions. Co-sell asks how to sell more of your product with a platform's help. An introduction-only program asks whether some of your customers would benefit from an opportunity that has nothing to do with your product, and whether you can mention it without damaging the relationship. For how pay compares when a partner does more than introduce, see introduction-only versus co-selling referral fees; for the difference from your own customer-referral scheme, see customer referral program versus partner program.
Which customers belong on the pilot list, and who can say yes
The customer benefit is the whole case. SourceX licenses approved business records directly from companies for AI training and evaluation, and a customer with years of its own documented operations may have records worth discussing. Apply the published screening tests before any account goes on a pilot list: 50 or more full-time employees at peak, contractors excluded; documented operating history the company created itself; rights to license that material; and 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.
On the customer's side, the CEO authorizes a licensing discussion and signs for the company. Your usual contacts, an operations leader or a system administrator, can sponsor the idea internally, but they are not the authorizer. In SourceX's screening, an introduction the CEO has not heard about is usually not a fit, so every introduction in the pilot starts with the CEO's yes.
On your side, the pilot needs three sponsors: the partnerships director who owns it, privacy or legal to approve how accounts are chosen and how the reward is disclosed, and customer success leadership to exclude accounts in an escalation or a renewal negotiation.
The introduction-only pilot blueprint
Thirteen weeks, one owner per phase, and nothing built inside the product.
| Phase | What you sign or decide | What you build | Owner | Done when |
|---|---|---|---|---|
| Week 0, set-up | The company signs the Channel Partner Agreement and registers; legal approves the disclosure wording | An internal page stating the rules on this page | Partnerships director | Agreement signed and partner link issued |
| Weeks 1 to 2, selection | Which 15 to 25 accounts pass the screening tests on public facts and account-team knowledge | A reviewed account list with the evidence source for each fact | Customer success leadership | Privacy has reviewed the selection method |
| Weeks 3 to 8, opt-in asks | Whether each account's sponsor wants a note sent to the CEO | One neutral note template and one CRM consent field | Account leads | Every account answered yes, later or no |
| Weeks 3 to 12, introductions | Which CEOs asked to hear more | Nothing new; the note is copied to the sponsor and the company is submitted through the partner link | Partnerships director | A verified application or a closed row for each yes |
| Week 13, review | Continue, change or stop | A one-page pilot report with the measures below | Partnerships director and customer success | Decision recorded and shared with the account teams |
What you never touch. Customer records, exports or samples; credentials to any customer system; product telemetry as a way to choose accounts; SourceX's review of the company; and the customer's price and terms.
The integration-creep log. Introduction-only programs drift toward integration one reasonable-sounding request at a time. Log each one and answer it the same way.
| Request | Why it looks reasonable | Answer |
|---|---|---|
| "Can you export our records and send them to SourceX?" | It saves the customer effort | No. The customer's own team handles any delivery under its agreement with SourceX |
| "Let's show an in-app banner to our biggest accounts" | Cheap reach | No. Selection stays on public facts and consent, not usage data |
| "Build a dashboard of data-rich customers from telemetry" | Better targeting | No. Your access to customer data exists to run the service |
| "Join the call and describe what we hold" | The customer trusts you | Attend only if the CEO asks, and never describe their records |
How far a partner stays involved after the introduction is set out in how involved a referral partner is after the introduction.
Why your processor role stays unchanged in this program
The motion stays clean because it never changes your role as a processor of customer data. Under the GDPR, the contract between a controller and a processor must require the processor to handle personal data only on the controller's documented instructions (Article 28(3)(a)). Nothing in the referral program asks you to process customer data at all, and the blueprint is designed so that nobody on your team starts.
Records a customer keeps in your product are the customer's. If it decides to license some of them, it does so with SourceX directly, after SourceX's rights review and with its own counsel reading its own client contracts. Your team's part ends at the introduction.
Preserve product trust: what to measure and when to stop
SourceX has not published conversion or acceptance rates for introductions from software companies, and none are reported here. The pilot report should rest on your own measures, defined before week 1.
| Measure | Definition |
|---|---|
| Selection integrity | Share of pilot accounts whose fit facts came from public sources or account-team knowledge, with the source recorded |
| Sponsor opt-in | Accounts whose sponsor asked for a CEO note, divided by accounts asked |
| CEO interest | CEOs who asked to hear more, divided by notes sent |
| Verified applications | Introduced companies that submitted a verified application, the point at which attribution is credited |
| Trust signals | Complaints, escalations or survey comments that mention the program |
| Creep log | Requests logged, and how many were declined |
Stop rules. Pause the pilot after any complaint that a customer felt targeted through product data, any request your team fulfilled from the creep log, or a sponsor-comfort score below your normal account survey baseline.
Illustrative reward arithmetic. The company that registered and submitted is the partner. If a referred customer's Actual Supplier Payout were $40,000, the transaction would fall below the USD 100,000 Minimum Transaction and earn no reward unless SourceX agreed in writing; at $400,000 the default reward on the company's first qualifying transaction would be USD 70,000, the greater of USD 50,000 plus 5% and 15%, and a further qualifying transaction first agreed within 12 months of the first Closing would pay 15% of its own payout. There is no cap per transaction, per company or in total; the USD 50,000 floor applies once per referred company, to its first qualifying transaction. Illustrative numbers, not a forecast. SourceX pays the reward separately and never deducts it from the customer's payout, and it falls due only when the conditions in the terms are met, with a deadline of 60 calendar days counted from the later of two events: completed handoff of the dataset, and the Acquisition Partner's final written acceptance of that complete, validated dataset. Should the customer's supplier payout later be reduced or reversed, the reward is recalculated on the reduced amount. Each company credits a single partner, the one behind the first valid introduction inside the 90-day window, and that credit attaches when the company submits a verified application, so settle with any reseller or implementation partner which of you submits before the note goes out.
Two lighter-weight touchpoints use the same rules: an optional QBR module and a customer education webinar. For the program from a software company's own perspective as a supplier, see the SaaS data partner page.
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.
If your week-0 decisions are made and privacy has approved how accounts will be chosen, register for a partner link, check the first accounts against who qualifies and read the program terms before any note goes out. Sector background is on the software and SaaS industry page, how this differs from affiliate schemes is in company data referrals versus software affiliate programs, and more playbooks are in the guides hub.