# Listing an introduction-only partner program | SourceX

Canonical: https://refer.sourcex.si/guides/a-partner-marketplace-listing-for-an-introduction-only-program
Last updated: 2026-11-05

List it as an introduction, never as an integration. A SaaS company that adds an introduction-only data licensing program to its partner marketplace or partner directory should say plainly that no data passes through its product, that the customer's CEO decides and SourceX contracts with the customer directly, which companies may qualify, and that the vendor may earn a referral reward paid by SourceX. Remove anything that implies a connector, likely payouts or pre-approval.

Marketplaces are built to sell software that connects to other software. An introduction-only program does neither, so the default listing template invites exactly the wrong claims.

## Why the default listing template gets this wrong

Most partner directories ask for an integration type, the data that syncs, an install button and a price. Every one of those fields pushes an introduction-only program toward a false statement. Leave "data synced" blank and readers assume something syncs; fill "install" with a link and they assume a connector.

Microsoft's marketplace listing policies make a useful benchmark even for a vendor's own directory. Section 100.1 says a listing must clearly, concisely and accurately communicate the value proposition and requirements for the offer, and section 100.1.3 asks publishers to describe any limitations, conditions or exceptions before the customer acquires it. For an introduction-only program, the limitations are most of the substance: who qualifies, that SourceX reviews each company, and that no outcome, price or timeline is promised.

The vendor's own stake needs the same care. The FTC's Endorsement Guides treat the possibility of being paid as a material connection that must be disclosed clearly and conspicuously when the audience would not expect it, and the disclosure has to convey the nature of the connection well enough for readers to judge it. A customer browsing its vendor's marketplace does not expect the vendor to be paid for the listing.

## A real customer benefit, and the sponsor who can authorize

The benefit belongs to the customer: its company may license its own operating records directly to SourceX and be paid under its own agreement. The vendor gains a better-served customer and possibly a reward, which it discloses. That benefit is real only for customers that could qualify, so the listing has to state the criteria rather than imply every customer is a candidate.

The reader of a marketplace listing is usually an administrator or an operations lead. Treat that reader as a possible internal sponsor, never as the decision-maker. Licensing is the CEO's decision, signature included, so the listing's call to action asks the reader to involve their CEO, not to connect an account.

## The accurate listing requirements checklist

Check every field against this table before the listing goes live, and again whenever SourceX publishes new program terms.

| Field | Write this | Never this | Why |
|---|---|---|---|
| 1. Listing name | "SourceX data licensing introduction (referral partner)" | "SourceX connector" or "SourceX for [Product]" | No integration exists |
| 2. Category | Partner services or referral programs | Integrations, data connectors or apps | The category sets expectations before anyone reads |
| 3. One-line value | An introduction to SourceX, which licenses business data directly from companies for AI training and evaluation | "Monetize your data in one click" | Licensing runs through review and a signed agreement |
| 4. How it works | We introduce your CEO; your company applies and deals with SourceX directly | "Export to SourceX" or "sync" | The vendor never moves records |
| 5. Data statement | No data passes through [Product], and we never send your records to SourceX | Silence about data flow | Readers assume the template's data flow |
| 6. Who qualifies | The published criteria, including the geography wording | "Available to all customers" | Most small customers cannot qualify |
| 7. Who decides | Your CEO decides; SourceX contracts with your company | "Approved by [Vendor]" | The vendor has no part in the agreement |
| 8. Money for the customer | Terms are agreed between your company and SourceX | Any figure, range or "up to" for the customer | Nothing is known before review |
| 9. The vendor's connection | We may earn a referral reward from SourceX if a license completes, paid by SourceX and never deducted from your payout | No mention, or a footer only | A material connection the reader would not expect |
| 10. Endorsement level | "Referral partner" | "Certified", "preferred" or "official" | Those words imply a program tier or review that does not exist |
| 11. Limits and timing | Not every company qualifies; SourceX reviews each one; no timeline or outcome is promised | "Fast approval" or "pre-approved" | Limitations must come before the customer acts |
| 12. Call to action and consent | "Ask us to introduce your CEO", with contact details shared only after the customer agrees | "Connect account" or automatic sharing | Consent comes before any contact is shared |
| 13. Review date | Program terms checked on a stated date, with a link to the full terms | Undated copy | Program terms are versioned and change |

For field 6, list every published criterion: a peak headcount of 50+ full-time employees (contractors left out), operating history the company can document, the rights to license, 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. Field 12 follows the habit co-sell programs already have: Microsoft's Partner Center documentation tells partners to get the customer's consent before sharing contact details with Microsoft, because Microsoft may contact the customer directly.

**Method note.** The checklist was put together on 2026-10-26 using SourceX's program terms (Version 2026-10-22.2, since replaced by version 2026-11-04) and its screening page, Microsoft's marketplace listing policies and co-sell documentation, and the FTC Endorsement Guides. It tests whether a listing describes the program accurately. It does not review any marketplace's own acceptance rules, which each operator sets, and it is general information, not legal advice.

## Draft lines that fail, and what replaces them (Illustrative)

Illustrative. A generic vendor's first draft, corrected line by line.

| Draft line | Problem | Corrected line |
|---|---|---|
| "Connect [Product] to SourceX and get paid for your data" | Implies an integration and a payment | "Ask us to introduce your CEO to SourceX, which licenses business data directly from companies" |
| "Pre-approved for [Product] customers" | Implies acceptance before review | "SourceX reviews each company; not every company qualifies" |
| "Customers earn thousands from their records" | An unsupported payout claim | "Terms are agreed between your company and SourceX" |
| "Official SourceX integration partner" | Implies a tier and a connector | "Referral partner of SourceX" |
| No disclosure anywhere | Missing material connection | "We may earn a referral reward from SourceX if a license completes; it never reduces your payout" |

The comparison with ordinary software affiliate listings, where the vendor really does sell or connect a product, is drawn in [company data referrals versus software affiliate programs](/compare/software-affiliate-programs).

## The listing must not imply the vendor holds or passes on records

A listing on the vendor's own marketplace can suggest, without saying it, that the vendor holds the customer's records and will pass them on. Field 5 exists to remove that impression. Three things sit in the same product and must not blur in the copy: the customer's content, which is the customer's to discuss licensing, subject to its contracts; personal data inside that content, which the customer controls; and the vendor's product analytics, which are the vendor's own and have no place in the listing at all. Ownership in SaaS is set by the agreement, as [who owns data in SaaS tools](/questions/who-owns-data-in-saas) explains, and the vendor's role in this program is the introduction alone.

## Pilot the listing before it goes wide

Publish the listing to a small audience first, such as an unlisted link shared with customers who ask, and watch for signs that readers misread it.

- **"How do I connect it?" tickets** mean the listing reads like an integration. Rewrite fields 1 to 5.
- **Requests from companies below 50 full-time employees at peak** mean field 6 is buried or vague.
- **Questions about price or timing** mean fields 8 and 11 are not doing their job.
- **Complaints about the vendor's role** mean field 9 is too quiet. Pause until it is fixed.

Count CEO-requested introductions alongside those signals, and ask each requesting customer two questions: was it clear that no data passes through the product, and was the vendor's reward disclosed before they acted? SourceX has not published results from any marketplace listing, so these are measures to collect, not benchmarks.

## What stays with SourceX's review

The listing can state the criteria; it cannot settle them. Whether a customer's contracts allow licensing, whether its records match current demand and what a license would cover are decided in SourceX's review and the customer's own agreement. The partner never handles client records, credentials or exports. Whoever submits introductions must first sign the SourceX Channel Partner Agreement. Rewards follow the program terms: Illustrative, an Actual Supplier Payout of $250,000 gives a reward of $62,500, paid by SourceX on top of, never out of, the customer's payout, and a lead, meeting or signature alone earns nothing. For the program itself, see the [referral partner program overview](/guides/referral-partner-program-for-ai-data) and the [SaaS data partner page](/guides/saas-data-partner); a [disclosure letter template](/resources/referral-fee-disclosure-letter-template) covers longer notices, and the [FTC disclosure examples](/resources/ftc-disclosure-examples-referral) cover short ones.

## 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.

Before the listing goes live, [register for a partner link](/register) to use in field 12, copy the criteria for field 6 from [who qualifies](/who-qualifies) and date field 13 against the current [program terms](/terms). Related SaaS playbooks sit in the [guides library](/guides).

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://learn.microsoft.com/en-us/legal/marketplace/certification-policies
- https://www.ecfr.gov/current/title-16/chapter-I/subchapter-B/part-255/section-255.5
- https://learn.microsoft.com/en-us/partner-center/referrals/manage-co-sell-opportunities
