The referral program that does not require product integration: what a SaaS partner team signs, builds and never touches in an introduction-only pilot

Short answer

It asks for no build at all. In SourceX's program a software company signs the Channel Partner Agreement, registers and introduces a customer's CEO when that customer wants the conversation. There is no API, data connector, single sign-on, marketplace listing or technical review, and no customer data passes through your product or your team. That makes the motion cheap to pilot, but it moves the hard work from engineering to judgment: choosing accounts without product analytics, getting consent and keeping the customer's records out of your hands.

Visual briefFull-size diagram
Three nodes: the software vendor sends only an introduction note to the customer company, the customer works with SourceX under its own agreement, and the line between the vendor and SourceX is crossed out: no API, no data.
The introduction-only motion. The only thing that leaves the vendor is a note the customer's CEO asked for.

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 programsIn SourceX's introduction-only program
API, webhook or data connectorNone; nothing connects to your product
Marketplace listing or published offerNone required
Technical validation or architecture reviewNone for the partner; SourceX reviews the referred company instead
Co-marketing collateralNone required; the public pages on this site describe the program
Revenue or consumption thresholds to joinNone
Customer data flowing through the partnerNone; the customer works with SourceX under its own agreement
What the partner actually doesIntroduces an authorized decision-maker who wants the conversation
What partner pay is based onActual 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.

CriterionMicrosoft co-sell, as documentedSourceX introduction-only
Prerequisite buildA live Marketplace offer; an architecture diagram for SaaS offersNone
ValidationMicrosoft technical validation for IP co-sellNone for the partner; SourceX reviews each referred company
Entry thresholdA revenue threshold for IP co-sellNone
What the partner gainsCo-selling with Microsoft sales teams and partnersA reward based on what SourceX pays the referred company, once conditions are met
What is being soldYour solutionNothing of yours; the customer may license its own records
Customer data through the partnerDepends on the solutionNone

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.

PhaseWhat you sign or decideWhat you buildOwnerDone when
Week 0, set-upThe company signs the Channel Partner Agreement and registers; legal approves the disclosure wordingAn internal page stating the rules on this pagePartnerships directorAgreement signed and partner link issued
Weeks 1 to 2, selectionWhich 15 to 25 accounts pass the screening tests on public facts and account-team knowledgeA reviewed account list with the evidence source for each factCustomer success leadershipPrivacy has reviewed the selection method
Weeks 3 to 8, opt-in asksWhether each account's sponsor wants a note sent to the CEOOne neutral note template and one CRM consent fieldAccount leadsEvery account answered yes, later or no
Weeks 3 to 12, introductionsWhich CEOs asked to hear moreNothing new; the note is copied to the sponsor and the company is submitted through the partner linkPartnerships directorA verified application or a closed row for each yes
Week 13, reviewContinue, change or stopA one-page pilot report with the measures belowPartnerships director and customer successDecision 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.

RequestWhy it looks reasonableAnswer
"Can you export our records and send them to SourceX?"It saves the customer effortNo. 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 reachNo. Selection stays on public facts and consent, not usage data
"Build a dashboard of data-rich customers from telemetry"Better targetingNo. Your access to customer data exists to run the service
"Join the call and describe what we hold"The customer trusts youAttend 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.

MeasureDefinition
Selection integrityShare of pilot accounts whose fit facts came from public sources or account-team knowledge, with the source recorded
Sponsor opt-inAccounts whose sponsor asked for a CEO note, divided by accounts asked
CEO interestCEOs who asked to hear more, divided by notes sent
Verified applicationsIntroduced companies that submitted a verified application, the point at which attribution is credited
Trust signalsComplaints, escalations or survey comments that mention the program
Creep logRequests 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.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Does SourceX need access to our product or our customers' tenants?

No. The program has no API, connector or data feed. A customer that decides to license records works with SourceX under its own agreement, and nothing passes through your product or your team.

Can we list the program in our partner marketplace or in-app?

Listing is not required, and an in-app placement shown only to accounts chosen by usage data would undo the separation this motion depends on. If you describe the program publicly, keep it accurate: an optional introduction, decided by the customer's CEO, with any reward disclosed.

Who earns the reward, our company or the employee who made the ask?

Whoever registered and submitted under the partner agreement; for a software company that should be the company. One partner is credited per referred company, and the reward is paid separately by SourceX, never deducted from the customer's payout.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. learn.microsoft.com/en-us/partner-center/referrals/co-sell-overview
  4. learn.microsoft.com/en-us/partner-center/referrals/co-sell-requi…
  5. eur-lex.europa.eu/legal-content/EN/TXT

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment