# Corporate partner portal listing checklist | SourceX

Canonical: https://refer.sourcex.si/guides/what-to-ask-before-a-corporate-partner-adds-sourcex-to-its-portal
Last updated: 2026-11-05

Ask four questions before a corporate's portal carries a SourceX listing: who can see it, what each line claims and where SourceX publishes that claim, who inside the corporate approves each element, and when the listing must be rechecked or taken down. A listing may describe SourceX in plain facts, disclose any reward and name a person to ask. It may not suggest approval, priority or eligibility, gather company details for SourceX, or outlive the partner agreement behind it.

The portal on this page is the corporate's own: a portfolio-company hub, a supplier portal, a partner marketplace, an employee intranet or a customer community. SourceX's partner dashboard is a different thing, explained in [what a partner portal is](/questions/what-is-a-partner-portal). Endorsement wording is audited asset by asset in the [co-branding permission audit](/guides/how-to-avoid-suggesting-a-corporate-partner-endorses-sourcex); this page covers what sets a listing apart: it stays up, it sits among other listings, and the portal can add badges, forms and analytics nobody wrote.

## Five portals, five messages a listing sends without a word

Placement speaks before the copy does. The same two sentences mean one thing on a portfolio hub and something else on a supplier portal.

| Portal | Who sees it | What placement suggests | Who owns it | Verdict for a SourceX listing |
|---|---|---|---|---|
| Portfolio-company hub | CEOs and staff of the venture unit's portfolio | A perk the investor arranged | Venture platform team | Workable with plain wording; put the size facts first, since many portfolio companies are young |
| Supplier portal | Suppliers' sales, finance and operations staff | A purchasing requirement or a scored criterion | Procurement | Usually no; if procurement agrees to list at all, add a line that the listing has no bearing on purchasing |
| Partner marketplace | Resellers, integrators and their customers | A vetted, approved vendor | Channel or alliances team | Only without approval labels, and naming SourceX as a partner needs SourceX's written authorization |
| Employee intranet | The corporate's own staff | An internal program staff may join | Internal communications | Useful for telling colleagues the corporate is registered, not for reaching companies |
| Customer community | The corporate's customers | Something the vendor wants customers to do | Customer success | Risky; the commercial relationship colors every reply |

Every row involves three separate roles. The corporate owns the portal, the brand and any partner registration. The suppliers and customers who log in carry commercial weight and no licensing role. The operating company behind each login owns its records, and its CEO alone decides whether to talk to SourceX. A portal audience is a list, never consent.

## The listing evidence and approval checklist

A software vendor's directory has its own trap, a template that assumes every listing is an integration, covered in the [introduction-only marketplace checklist](/guides/a-partner-marketplace-listing-for-an-introduction-only-program). A corporate portal's trap is permanence: the listing outlives the colleague who wrote it, the terms version it quotes and, unless someone acts, the agreement behind it. So every row carries a recheck trigger as well as its evidence.

Give each element of the listing one row, and do not publish until every row has evidence and a named approver.

| Listing element | What it may say | Evidence it rests on | Approver | Recheck when |
|---|---|---|---|---|
| 1. Title and category | "SourceX: data licensing introductions" under a resources heading; never under approved vendors, perks or offers | The portal's own category list | Portal owner | The portal is reorganized |
| 2. Logos | The corporate's mark under its brand rules; SourceX's logo only if SourceX agrees in writing | Section 4.5 of the sample agreement grants no trademark license | Brand owner, and SourceX in writing | Either brand changes |
| 3. Description | SourceX licenses business records directly from companies for AI training and evaluation, and pays the companies | SourceX's process and investor pages | Communications | SourceX rewords its own description |
| 4. Who it may suit | The screening facts with the date read: a full-time headcount that reached 50+ at its peak, contractors excluded; years of the company's own records; rights to license them; the CEO's authorization; the geography sentence | Who-qualifies page and section 1 of the terms | Platform manager | A new terms version or a change to the screening page |
| 5. Who it does not suit | Material that belongs to clients, personal consumer or scraped data, and records already licensed for AI training | Who-qualifies page; SourceX's process page lists what a company confirms | Platform manager | The same triggers as row 4 |
| 6. The reward | The corporate is registered and may receive a reward from SourceX, which SourceX pays itself and does not take from the company's compensation | Section 4 of the terms | Compliance | A new terms version |
| 7. Next step | "If your CEO wants an introduction, write to [named person]," or apply to SourceX directly | Section 2 of the terms: a link click alone does not decide credit | Platform manager | The named person changes |
| 8. Forms | None: no fields for headcount, systems, record volumes or contacts | Section 4.2 of the sample agreement gives a partner no authority to share a supplier's records or inventory | Portal owner | Any change to the portal's listing template |
| 9. Analytics | Page views stay in the corporate's own reporting; no visitor list goes to SourceX or to a sales team | Nothing in the terms asks for visitor data | Portal owner | The analytics settings change |
| 10. Audience | The narrowest group that makes sense; suppliers only with a no-bearing-on-purchasing line, or not at all | The portal's access settings | Portal owner and procurement | The audience setting changes |
| 11. Words never used | Approved, preferred, verified, priority, pre-qualified, exclusive offer, and partner unless SourceX has authorized it in writing | Sections 4.5 and 7.1 of the sample agreement | Compliance | Every edit |
| 12. Review and removal date | A date before the agreement's anniversary, and removal within the notice period if either side ends it | Section 9 of the terms: a one-year term, 30 days' notice, renewal only with fresh acceptance and signatures | Platform manager | Each anniversary |

Row 4 has a fixed wording for location, and it belongs in the listing whole. 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.

**Method note.** The checklist applies SourceX's terms (Version 2026-10-22.2, since replaced by version 2026-11-04), the unsigned sample Channel Partner Agreement (version 2026-10-19) and SourceX's screening and process pages, all read on 2026-10-27. It checks what a listing claims, what the portal adds around it and who approved each part. It does not test compliance with any law, and SourceX has published no data on how corporate portal listings perform.

## Nine questions for the portal owner before anyone drafts a word

Most listing problems come from the portal, not the writer. Put these to whoever runs it:

1. Who can log in, and can this listing be shown to one group only?
2. Does the portal add a badge to every listing automatically, such as verified, approved or featured, and can it be switched off for this one?
3. Does the listing template attach an inquiry or lead form by default, and can it be removed?
4. Does the portal pass visitor or click data to listed vendors, and can that be turned off?
5. Does listing order or a featured slot suggest a ranking?
6. Is every listing tied to a vendor-onboarding or procurement record that would make SourceX look like an approved supplier?
7. Can the listing carry an expiry date, and who is alerted when it lapses?
8. Who is notified when a reader uses the contact line, and how quickly can they answer?
9. Is the listing copied to other portals or to search, and does the full text travel with it?

Two of the answers decide on their own whether to go ahead. If a badge or a form cannot be removed, do not list.

## Approvals inside the corporate, and the decision each company keeps

Inside the corporate, six people sign off on what they own: the portal owner on mechanics, the brand owner on marks, procurement on any supplier-facing placement, compliance on the reward wording and on which entity is the registered partner, legal only where confidentiality or an existing contract is in question, and the platform manager on the named contact and review date. File each approval with the listing version it covered.

Two approvals never come from the corporate. SourceX must agree in writing before the corporate names it as a partner or uses its logo, since the sample agreement grants no trademark license and says participation creates no partnership. And each company decides through its CEO, or after an acquisition through the acquirer's CEO. Nobody on the portal side decides for a company or collects its data for SourceX, and nothing in the listing suggests a company will be accepted, reviewed sooner or treated differently because it found SourceX through the corporate.

## One supplier portal listing, checked line by line (Illustrative)

Illustrative. A generic industrial corporate and invented numbers; no real portal is described.

A corporate venture team wants SourceX listed on the corporate's supplier portal, which about 1,800 suppliers can see. The checklist turns up four problems:

- **Category.** The portal's only vendor heading is "Preferred services." Row 1 fails until the portal owner adds a resources heading.
- **Badge.** The template stamps "Verified partner" on every listing. The portal owner can switch it off for this listing, so row 11 passes once that is done.
- **Form.** The template adds a "Request an introduction" form asking for company size and systems used. Row 8 removes it, and row 7 replaces it with one sentence naming the platform lead to write to.
- **Audience.** Procurement reads row 10 and declines: even with a no-bearing-on-purchasing line, suppliers in the middle of tenders would read a listing on that portal as expected participation.

The team does not list on the supplier portal. It lists on the portfolio-company hub instead: the brand owner confirms the listing carries no SourceX logo, compliance approves the reward line, the platform lead is named as the contact, row 4's size facts go first because most of those companies are early-stage, and the review date sits 30 days before the agreement's anniversary. Ending up with one listing instead of two is the checklist working, not failing.

## A narrow first listing, and what to watch for 60 days

Publish to one audience for 60 days and log messages to the named contact, CEOs who asked in writing for an introduction, readers who took the listing as an endorsement, a perk or a purchasing expectation, complaints, and whether the copy still matched the current terms on day 60. Ask everyone who writes in: what did you think the listing meant? One reply that reads it as an endorsement or a requirement is reason to rewrite before widening the audience. SourceX publishes no benchmark for portal listings, so these counts are the only evidence.

## Where a careful listing still misleads

- **Its neighbors.** Beside approved vendors, a neutral listing borrows their status.
- **Search snippets.** Results that show only the first line drop the "does not suit" row.
- **Stale copy.** SourceX may publish new versions of its terms, and a listing that quotes an old version keeps saying it.
- **Copies elsewhere.** A syndicated listing travels without its review date.
- **The audience's position.** Suppliers and customers read any vendor listing through the commercial relationship, however plain the words.
- **The approver moves on.** The review date catches a listing whose owner has left; the [staff change protocol](/guides/when-corporate-partner-staff-change-during-an-active-referral) covers the referrals that person held.
- **Fit stays unknown.** A listing makes no company a fit; SourceX's review decides, and creating a link does not by itself make an introduction [eligible for a reward](/questions/does-creating-a-referral-link-make-an-introduction-eligible-for-a-reward).

For wording that informs without vouching, see [making an introduction without endorsing](/guides/introduction-without-endorsement); more corporate venture material is in the [guides library](/guides).

## 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 every row of the checklist has evidence and an approver, [register](/register) the corporate entity as the partner, copy row 4 from the current [who qualifies](/who-qualifies) page on the day you publish, and put the [program terms](/terms) version on the listing's review record.

Listing SourceX on a corporate portal is a partner decision; evaluating SourceX as an investment is a different one, and investor materials are available on request from the [SourceX investor overview](https://sourcex.si/investors).

This article is for information only and is not an offer to sell or a solicitation of an offer to buy securities. Any offering by SourceX is made only to verified accredited investors through its offering documents.

## Sources

- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/how-it-works
- https://sourcex.si/investors
