# Regional founder data newsletter brief | SourceX

Canonical: https://refer.sourcex.si/guides/a-regional-founder-newsletter-about-data-partnerships
Last updated: 2026-11-05

A regional founder newsletter can explain that SourceX licenses records directly from established companies, but the region it covers is not a criterion and must never read like one. Brief the item before drafting it: quote SourceX's geography sentence as published, sort the region's countries against it, say that the CEO decides whether to talk and SourceX decides fit, state that the fund could be paid, keep any partnership claim off the page unless SourceX has authorized it in writing, and give readers a route that asks nothing of them. The newsletter collects nothing about readers' companies for SourceX.

## A region describes the readership, not the rule

SourceX's screening page warns that a newsletter line saying "our companies qualify" implies an acceptance nobody has given, which is why screening comes before any announcement to a whole portfolio. A regional masthead makes the same mistake easier at country level: an item headed "for Nordic founders" invites readers to assume the region has been cleared.

Under one regional label sit four separate facts: where the reader lives, where the company is, the newsletter's language and the language of the company's records. A Stockholm founder may run a company whose records sit with a subsidiary in Oslo. Funding status adds nothing: SourceX's screen never mentions it, so being in the fund's portfolio neither helps nor hurts.

## Sorting the region's countries against the published sentence

SourceX publishes one location sentence for companies: 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. How a company would work out its English share is explained in the [English-language eligibility guide](/guides/english-language-data-referral-eligibility); the newsletter links that guide rather than restating it.

For an Illustrative newsletter reaching founders in the Nordic and Baltic countries plus the UK, the sort looks like this. EU membership is taken from the EU's own list of its 27 member countries.

| Country | Where it falls in SourceX's sentence | What the item may say |
|---|---|---|
| Denmark, Estonia, Finland, Latvia, Lithuania, Sweden | On the EU's member list; the sentence names the EU with no English clause | "Inside SourceX's published list; SourceX applies each program's criteria in its own review" |
| United Kingdom | Named, with the 70% English condition | "Named where at least 70% of the data is in English; the company works out its own share" |
| Norway, Iceland | Not on the EU's member list, and not named in the sentence | "Not named in SourceX's published list; only SourceX can say whether a program could include it" |
| A company whose records sit in another country from its head office | Depends on which entity holds the records | "SourceX decides which entity it looks at" |

Two limits keep the table honest. The sentence sets no English condition for EU companies, but SourceX's screening page says programs differ in geography and language among other things, so the item never promises that records kept in Finnish or Estonian will suit a program. And because the same page says a company that misses one program may fit another later, "not named" is never written as "excluded". Wording for each situation is worked through in [how to explain SourceX's geography without turning companies away](/guides/how-to-explain-sourcex-geography-without-turning-companies-away). Date the sort, and redo it whenever SourceX's page changes.

## The location-bounded newsletter brief

The editor fills this in before drafting; a second person checks the right-hand column.

| Line | What the editor writes | Check before the issue goes out |
|---|---|---|
| 1. Readership | Who receives the issue and where they are | The region is named as the readership, never as a criterion |
| 2. Country sort | The table above, with the date it was made | Every country the issue reaches sits in one row |
| 3. The sentence | SourceX's geography sentence in English, word for word, with the guide linked | No paraphrase and no shortened list; any translation is marked unofficial |
| 4. The one point | What the item explains, such as a company licensing records of its own work for AI training and evaluation | No market claims, no figures |
| 5. Who decides | The company's CEO decides whether to talk; SourceX decides fit after its review | No "your company qualifies", no "you're a fit" |
| 6. The fund's interest | One sentence saying the fund could receive a reward from SourceX, paid separately | Inside the item, not only in the footer |
| 7. Publicity | Whether any line, logo or archive copy presents SourceX as the fund's partner | SourceX's written authorization on file first |
| 8. No commitments | Nothing on prices, licenses, payouts, speed or acceptance | Agreement sections 4.6 and 7.1 |
| 9. Reader route | Apply directly to SourceX, or reply to a named person to ask a question or request an introduction | No form, poll or field |
| 10. Collection check | Nothing asks for headcount, systems, records or company names for SourceX | Replies carrying company details are never passed on |
| 11. Questions out | Local rules on promotion and disclosure go to the editor's adviser; tax goes to each reader's own adviser | No answers to either in the issue |
| 12. Date stamp | "Checked on [date] against SourceX's terms, version 2026-10-22.2, since replaced by version 2026-11-04" | Rechecked before every issue |

What else a platform item should carry, and how to test its lines for misreadings, is in [what to include in a VC platform's data partnership newsletter](/guides/what-to-include-in-a-vc-platform-s-data-partnership-newsletter); this brief adds the country work.

## Disclosure and endorsement lines that follow the partner agreement

Section 4.5 of the sample Channel Partner Agreement reads: "Neither Party may publicly identify the other as a partner or disclose non-public deal details without written authorization, except as legally required." The same section says "No data license, trademark license or right to train models is granted." An issue archived on a public website is public, so the item names SourceX plainly, uses no SourceX logo, and calls nothing a partnership without SourceX's written authorization.

Section 4.6 bars telling a company that an estimate, positive interest, a signature or an upload assures a purchase or a reward, so the item says nothing about outcomes or amounts. Section 7.1 says the partner may not commit SourceX to prices, licenses or payouts, so "we can get you a quick review" is out.

The fund's interest goes in one plain sentence, inside the item (Illustrative): "If a company we introduce licenses data to SourceX, SourceX may pay the fund a referral reward. SourceX pays it separately, so the company receives the same amount with or without us." The second sentence rests on section 4 of SourceX's terms: the reward "is paid separately by SourceX and is never deducted from the supplier's agreed compensation." Where in an issue a disclosure holds up is covered in [the newsletter disclosure placement guide](/guides/how-to-keep-referral-incentives-transparent-in-a-member-newsletter), and whether a disclosure rule applies where the newsletter is published is a question for the editor's own adviser, with [do I have to disclose a referral fee](/questions/do-i-have-to-disclose-a-referral-fee) as a starting point.

The item never suggests that SourceX selected, vetted or recommends the fund, that readers get a faster or kinder review through it, or that anyone gains access to a company's data. Nothing the fund learned from a board seat appears in it.

## Readers reply to ask, never to report

The newsletter is not an intake channel. It carries no form, no poll about data, no "reply with your headcount and main systems and we'll tell you if you fit". SourceX applies its own screen in its own review, and section 4.2 of the agreement gives a partner no authority to share a company's inventory, records or raw data.

Readers get two routes: the company applies to SourceX itself, or its CEO asks the named person at the fund for an introduction. Each introduction concerns one company whose CEO asked for it, submitted by someone who has already signed the SourceX Channel Partner Agreement. SourceX's terms say an earlier link click alone does not decide credit, so there is no reason to add tracking for SourceX's sake.

If a reader replies with company details anyway, thank them, point them to the application, and pass nothing to SourceX.

## A Nordic-Baltic item, drafted and corrected (Illustrative)

Illustrative. An invented draft from an invented fund.

> **Draft:** "Great news for Nordic and Baltic founders: your companies qualify for SourceX, our data partner. Reply with your headcount and main systems and we'll tell you whether you fit and fast-track your review."

| Draft phrase | What is wrong | Fix |
|---|---|---|
| "your companies qualify" | Implies an acceptance nobody gave; Norway and Iceland are not even named | Quote the sentence; say SourceX decides |
| "our data partner" | A public partner claim without written authorization | Name SourceX plainly as a company |
| "Reply with your headcount and main systems" | Turns the newsletter into an intake form | "Your company can apply directly, or your CEO can ask [name] for an introduction" |
| "fast-track your review" | Commits SourceX and implies preferential access | Delete |
| No mention of the fund's interest | Readers cannot weigh the recommendation | Add the disclosure sentence |

> **Corrected:** "Some established companies with 50 or more full-time staff at their peak license records of their own work, such as years of service tickets or project files, directly to SourceX for AI training and evaluation. SourceX decides whether a company fits after its own review; the CEO decides whether to talk at all. On location, SourceX publishes one sentence, quoted here in full: 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. Norway and Iceland are not named, and only SourceX can say whether a program could include a company there. Your company can apply directly, or your CEO can ask [name] for an introduction. If a company we introduce licenses data, SourceX may pay the fund a reward, separately; the company is paid the same either way."

## Where readers' questions go, and the line you keep

| A reader asks | It goes to |
|---|---|
| "Does my Norwegian company fit?" | SourceX, after the company applies |
| "Would records in Finnish count?" | SourceX's review |
| "Is the fund allowed to promote this here?" | The editor's own adviser |
| "How would a reward be taxed?" | The reader's or the fund's own adviser |
| "Can you look at our files first?" | Nobody at the fund; the company applies itself |

For each reply, keep one dated line: the issue, the question, where it went, and the outcome, which is an introduction the CEO requested, a no-fit noted with its reason, or an answer taken from a published SourceX page.

## Where a regional item can still mislead

- **The masthead.** A region's name above the item can imply a program for that region; the country sort has to sit close to the headline.
- **Archives outlive terms.** Old issues stay online after SourceX's pages change. Add a dated note to archived items when the terms or screening page change, as in [when a regional partner shares outdated country criteria](/guides/when-a-regional-partner-shares-outdated-country-criteria).
- **Forwarding.** A disclosure that sits only in the footer is lost when one item is forwarded.
- **Translation.** "May" can become "will" in another language; use the checks in [when translation is needed before a company can evaluate the opportunity](/guides/when-translation-is-needed-before-a-company-can-evaluate-the-opportunity).

**Method note.** The brief and the country sort are this page's design, built on 2026-10-27 from SourceX's screening page and terms (version 2026-10-22.2, since replaced by version 2026-11-04), the unsigned sample of its Channel Partner Agreement and the EU's member list, and not tested on readers. More designs are in the [guides hub](/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.

Before the next issue goes out, check the country sort against [who qualifies](/who-qualifies) and the item against the [program terms](/terms), and make sure the person named as the reader route has [registered as a partner](/register).

A newsletter that tells founders about data licensing is a referral matter; readers weighing SourceX itself as an investment are making a separate decision and can request investor materials 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/who-qualifies
- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://european-union.europa.eu/principles-countries-history/eu-countries_en
- https://sourcex.si/investors
