# Low-effort referral program, full accountability | SourceX

Canonical: https://refer.sourcex.si/guides/the-difference-between-low-effort-and-low-accountability
Last updated: 2026-11-09

An introduction-only program is low effort by design. The platform team never exports, uploads or describes a company's records, and SourceX runs the agreement, rights review, data preparation, delivery and payout. It is not low accountability. Whoever signs the Channel Partner Agreement answers for confidentiality and for the people acting for the fund, every founder asked is owed an honest outcome, and every message carries a disclosure. Give each duty a named owner and a test for done, book referral income at zero, and stop when loops are left open.

Low effort tempts a platform team to run the program in nobody's name: one associate, a shared link and a hope. That is where the costs appear, and none of them is measured in hours. This page separates what the program takes off your plate from what it leaves on it, then turns the remainder into a matrix with an owner for every line.

## What the founder gets and what the platform team spends

For a founder, the possible benefit is a licensing discussion about records the company already keeps, on the company's terms: it controls whether to proceed, what scope to offer and which terms to accept. Any reward goes to the partner, is paid separately by SourceX and is never deducted from the company's compensation. Whether any value follows is decided in SourceX's review and in the company's own signed agreements, so the honest founder pitch is an option to explore, not an outcome.

For the platform team the scarce input is attention, and it can shrink without warning. In its [archived December 6, 2023 announcement](https://web.archive.org/web/20260102233401/https://openviewpartners.com/openview-refocuses-on-existing-portfolio-companies/), OpenView announced that it was suspending new investments from its current fund to focus on existing portfolio companies, after a restructuring that reduced staffing levels across its teams. A program whose duties live in one person's head does not survive a change like that. A program whose duties have named owners and written tests can be handed over in an afternoon.

## Where the effort is low, and where the duties are not

The left column is real relief. The right column is what that relief does not cover.

| Taken off the platform team | Still the platform team's to answer for |
|---|---|
| Exporting, uploading or describing confidential records | Making sure nobody asks a founder for files, samples or logins |
| Negotiating the license, rights review, preparation, delivery and payout | Telling founders that acceptance and value are decided in SourceX's review |
| Joining every call, email or negotiation between SourceX and the company | Knowing the status well enough to tell a founder yes, no or later |
| Calculating the reward | Having the receiving entity and its tax details ready |
| Committing anyone to prices or terms | Never implying a commitment: the partner is not SourceX's agent |

The partner agreement says the partner need not join every call, email or negotiation, gives the partner no authority to share a supplier's records, and forbids collecting or retaining supplier dataset copies through the program. Those are the reasons the effort is low. They are also limits the fund has agreed to keep.

## The responsibility and follow-through matrix

One row per duty. "Owner" is a role you replace with a name; "Done when" is a test someone else could check; "If it slips" is the failure that shows up later.

| Duty | Effort | Owner | Done when | If it slips |
|---|---|---|---|---|
| Screen on metadata only | Low | Named screener | Each fact on a row cites its source and date | A founder is asked for an export the fund has no right to see |
| Ask the relationship owner first | Low | Head of platform | The owner's yes or no is recorded before any contact | A founder hears about the program from a stranger |
| CEO knows and wants the conversation | Low | Relationship owner | The CEO's written yes precedes the introduction | An introduction without the decision maker's knowledge, usually not a fit |
| Disclose that the fund may receive a reward | Low | Whoever sends the message | The disclosure sits beside the link in every message | A founder weighs advice without knowing about the reward |
| No promises about acceptance or money | Low | Everyone who speaks to founders | No estimate, signature or upload is described as assuring a purchase or reward | A founder plans around a figure nobody committed to |
| Confidentiality | Low day to day, long-lived | The signer of the agreement | Everyone acting for the fund is briefed; dates are calendared | The fund answers for its representatives' breach |
| Close every loop with founders | Medium | Named owner per company | Each founder hears yes, no or later within 30 days of a decision | Goodwill spent; the next ask goes unanswered |
| Dated introduction records | Low | Program owner | Legal name, domain, method and date for each company | Credit questions cannot be answered later |
| Reward administration | Low | Fund finance | Receiving entity and tax details on file before anything is payable | An earned reward waits on the fund |
| Hand-over on departures | Medium | Head of platform | Every open company reassigned within a week | Loops orphaned, the clearest stop signal |
| Exit and survival | Low | The signer | Six-month protection and three-year confidentiality dates set | Duties forgotten once the program ends |

Two rows deserve emphasis. Disclosure is cheap and easy to forget: the FTC's endorsement FAQ advises that an affiliate relationship be disclosed clearly and conspicuously so readers can decide how much weight to give the recommendation, and tells programs to remind participants to disclose. The [FTC disclosure examples](/resources/ftc-disclosure-examples-referral) offer wording, and the guide to [discussing rewards transparently](/guides/how-to-discuss-referral-rewards-transparently-with-a-business-contact) covers the conversation. Confidentiality is cheap and long-lived: the agreement makes each party responsible for its representatives' compliance, and the terms keep confidentiality obligations for three years after the agreement ends.

**Method note.** The matrix was built on 2026-10-26 from the program terms (Version 2026-10-22.2, since replaced by version 2026-11-04), the unsigned Channel Partner Agreement sample (version 2026-10-19), SourceX's who-qualifies and how-it-works pages, and the FTC's endorsement FAQ. Effort levels and the 30-day and one-week tests are our judgments, not measurements. It does not measure hours, founder satisfaction or outcomes; time logs and founder feedback from a permissioned pilot have not been published.

## Work at each stage with referral income at zero

The base case books no referral income, because SourceX has not published conversion rates or typical payouts. The planning figures below are Illustrative, for a 20-company screen; replace them with your own time log after the first month.

| Stage | Platform time (Illustrative) | Loop it opens | Loop closes when | Referral income booked |
|---|---|---|---|---|
| 1. Screen 20 companies on metadata | 5 hours | None | Every row complete and sourced | $0 |
| 2. Ask owners about the 6 that pass | 2 hours | Each owner's answer | Owner says yes or no | $0 |
| 3. CEO consent and introductions for 3 | 2 hours | Each CEO's decision | CEO agrees or declines | $0 |
| 4. SourceX's questions about the introductions | 1 hour | Each question | Answered, with the CEO aware | $0 |
| 5. Outcome back to each founder | 1.5 hours | A founder waiting | Founder hears yes, no or later | $0 |
| 6. Close-out | 1 hour | Records and lists | Kept or deleted on purpose | $0 |

That is about 12.5 hours of platform time with no income assumed. The number to watch is not the hours; it is how many loops in the third column are still open, and for how long. After stage 5, ask each founder one question, whether the ask was useful, neutral or a cost, and count the answers. That count is the founder-usefulness measure; no figures for it have been published.

## Expand, pause or stop on follow-through, not on income

Set these before the first ask, in writing.

- **Expand** to a second batch when every introduced company had a named owner, no loop stayed open more than 30 days after a decision, every message carried the disclosure and most founders called the ask useful or neutral.
- **Pause** when any loop is open past 30 days with no owner, a founder objects to being asked, or a message went out without the disclosure. Fix the cause, then resume.
- **Stop** when an introduction went out without the CEO's knowledge, someone received or forwarded company records, a founder was told a figure as if it were committed, or the program's owner left and nobody took the list within two weeks.

The [zero-revenue time model](/guides/is-data-referral-work-worth-a-platform-team-s-time) counts hours per qualified introduction; this matrix counts the obligations those hours create. Use both, and if you are starting from scratch, the [first-month plan for platform teams](/guides/a-first-month-referral-plan-for-venture-platform-teams) sequences the setup.

## Fifteen companies, one departure: a pilot to halt (Illustrative)

Illustrative. A seven-person platform team at an early-stage fund ran a 15-company pilot. One associate owned everything. In month two the associate left. The matrix shows what happened next: five founders who had agreed to introductions never heard an outcome, one CFO had been told the company "should qualify" and that the program "pays well", and nobody could say which messages had carried the disclosure.

Hours were low throughout, under 20 in total, so a time model would have said continue. The follow-through rules say stop: the owner left and nobody took the list within two weeks, and a founder was given an expectation nobody committed to. The repair comes before any new ask: the head of platform writes to each of the five founders with a plain status, corrects the CFO's expectation in writing, and decides whether to restart with named owners. Whether the fund itself or an individual should be the partner of record is a separate question, covered in [who gets referral credit, the firm or the individual](/questions/who-gets-referral-credit-firm-or-individual).

## Where this matrix could mislead

- **Capacity shocks.** The OpenView restructuring shows that platform staffing can fall quickly. The matrix assumes someone is there to own each row; if nobody is, the right answer is to stop, not to run the program unattended.
- **Demand moves.** SourceX applies the criteria of the specific program, so a portfolio company screened out of one program today may suit another one later. A matrix that keeps old screening answers produces stale promises.
- **Rights.** Material that belongs to a company's clients is usually not a fit, so a low-effort screen that ignores where records came from wastes founders' time.
- **Jurisdiction.** The disclosure guidance cited here is from a U.S. regulator. Funds and founders elsewhere follow their own rules.
- **No measured data.** Conversion rates, typical payouts and founder reactions are unpublished. Every threshold on this page is a judgment you should replace with your own pilot's evidence.

Fit itself is unchanged by any of this. However little effort the introduction takes, the company still has to show a full-time peak of 50+ employees with contractors left aside, a documented operating history, rights to license, and a CEO willing to authorize the discussion. 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. The [overview for venture platform teams](/for/venture-platform-teams) covers the portfolio side.

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

Put a name in every row of the matrix before the first founder hears about the program, then [register for a partner link](/register), screen against [who qualifies](/who-qualifies) and read the [program terms](/terms) with the person who will sign.

Running this program is a platform decision; judging SourceX as a possible investment is a different exercise, 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://refer.sourcex.si/how-it-works
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://www.ftc.gov/business-guidance/resources/ftcs-endorsement-guides-what-people-are-asking
- https://web.archive.org/web/20260102233401/https://openviewpartners.com/openview-refocuses-on-existing-portfolio-companies/
- https://sourcex.si/investors
