The data supply conversation for funds focused on enterprise software: a one-page activation brief that starts with how portfolio companies run themselves, not the data their products host

Short answer

An enterprise software portfolio holds two kinds of records, and usually only one belongs to the portfolio. The data each product hosts is the customers'; a vendor processing it on their behalf cannot offer it. What a software company may own is the record of running itself: support case handling, implementation projects, incident reviews, QA and release histories. Start the data supply conversation there, with companies that reached 50 or more full-time employees at peak, then add two lanes: customers whose CEOs opt in through the vendor, and the enterprise operators the fund already convenes.

Visual briefFull-size diagram
An Illustrative one-page activation brief, six of its fields shown from thesis to stop date, whose lane field connects to three cards: the portfolio company's own operations decided by its CEO, customers who opt in through the vendor, and operators the fund convenes, where the CEO still has to be found; hosted product data is marked as the customer's.
Illustrative brief. Fields and lanes follow the method on this page; no real companies or results.

Turn the enterprise software thesis into a question about records

Most enterprise software funds already hold a view on AI. The data supply version is narrower: teams training and testing agents on office work need realistic records of how a company actually operates, and researchers go to some length to get them. The authors of TheAgentCompany benchmark built a self-hosted, simulated software company, with internal tools such as GitLab, Plane, RocketChat and ownCloud, simulated colleagues and 175 professional tasks; the best baseline agent in their study completed about 30% of those tasks autonomously.

If researchers simulate a software company to get workplace context, the internal operating records of real software companies are worth a question. The question for a portfolio is not "which company has the most customer data", which points at the wrong owner. It is this: which of our software companies has years of internal operating records created by its own staff, reached 50 or more full-time employees at peak, and has a CEO who would want to discuss licensing them?

Record inside a software companyExampleUsually belongs toCan the portfolio company discuss it?
Hosted product dataTickets, documents and transactions customers create in the productThe customerNo; the customer's CEO decides
Support operationsHow the company's own team triaged, escalated and resolved casesThe company, though case text can carry customer contentPossibly, after rights review
Implementation historyProject plans, change requests and go-live checklists for each rolloutThe company, subject to customer contractsPossibly
Engineering operationsIssue tracker history, incident reviews, release and QA recordsThe companyUsually the clearest case
Sales engineeringDiscovery notes, solution designs, questionnaire answersThe company, with customer confidential material insideCase by case

The legal line on hosted data is firm where EU personal data is involved. Article 28 of the GDPR requires a processor to process personal data only on the controller's documented instructions, and a processor that decides the purposes and means itself is treated as a controller for that processing. SourceX's screening guidance reaches the same practical answer from another direction: material that belongs to a company's clients is usually not a fit.

The enterprise-network activation brief

Write the brief once, before anyone contacts a company. It prevents three failures: approaching the wrong owner, approaching through the board seat, and continuing after the evidence has turned.

FieldWhat to writeIllustrative entry
1. ThesisOne sentence about records, not marketsGrowth-stage portfolio companies hold years of support and engineering records their own staff created
2. DisproofThe result that ends the briefFour of the first six companies say their support records are mostly customer content
3. LanesWhich of the three lanes below are in scopeLanes 1 and 3; lane 2 only if a portfolio CEO proposes it
4. Fit factsPeak full-time headcount, years of records, rights, CEOSix portfolio companies above 50 full-time employees, six to twelve years old
5. Record familiesNamed at metadata level onlySupport cases, incident reviews, implementation projects
6. Relationship ownerWho asks each CEOBoard partner for four companies, platform lead for two
7. LimitsWhat the fund will not doNo customer data, no files or logins, no request made in a board meeting
8. PilotSize and end dateTen companies, ending 2026-12-18
9. ReviewWho reads the result and decidesPlatform lead and two deal partners

Method note. The fields come from SourceX's published screening profile and program terms and from Article 28 of the GDPR, checked on 2026-10-26. The brief records ownership defaults, fit facts and relationship paths. It does not estimate demand for any record family, record quality or payout; those are assessed only in SourceX's review. Counts, dates and descriptions in the right-hand column are invented for illustration.

Three lanes, three different decision-makers

LaneWhose recordsWho decidesFirst moveMain risk
1. The portfolio company's own operationsThe portfolio company'sIts CEOThe board partner raises it one to oneCustomer content mixed into support and implementation records
2. The portfolio company's customersEach customer'sEach customer's CEOThe vendor tells its customers; interested CEOs come forwardCustomers reading it as the vendor trading on their relationship
3. Enterprise operators the fund convenesEach operator'sEach operator's CEO, not the executive who attendsAsk the attendee to sponsor an introduction to their CEOTreating a functional executive as the authorizer

Lane 1 is easy to overlook, because a fund tends to think of its portfolio as sellers of software rather than holders of records. A company with ten years of issue tracker histories, incident reviews and support escalations has a decade of its own operating history. Early-stage portfolios are likely to fail the size test here; growth-stage portfolios may not.

Lane 2 belongs to the portfolio company, not the fund. The vendor can tell customers about the program and introduce those whose CEOs ask, while never touching the data it hosts; the customer opt-in flow for software companies sets out the steps, and the guide to aggregated-data clauses in SaaS agreements covers what a vendor's own contract may say about customer data. Whether to make this a fund-wide program at all is weighed in opt-in versus mandatory portfolio programs.

Lane 3 is the fund's convening power: the CIO councils, customer advisory boards and LP operating companies an enterprise platform team already brings together. The people in those rooms run large operations, but a CIO or VP of operations is rarely the person who authorizes licensing. Ask them to sponsor a conversation with their CEO, and only if they think the CEO would want it.

Credit follows the program rules in every lane. One partner per company gets credit, and only for the earliest valid introduction made while the company was still new to SourceX and inside the 90-day attribution window, settled once the company submits a verified application; if SourceX already had a lead, an account or email correspondence with that company from before, it is an existing relationship. Agree in writing, before outreach, whether the fund or the portfolio company submits a lane 2 introduction. Software roll-ups need one more note: a parent and its subsidiaries count as one company, so the USD 50,000 floor applies once, to the group's first qualifying transaction, and does not repeat for each subsidiary. What happens to credit when the parent or a sister company has already been in touch with SourceX, or another partner introduced a sibling, has no published rule; SourceX settles it in duplicate review, so promise nothing in advance.

Ownership and relationship evidence, lane by lane

LaneOwnership evidence to gather (metadata only)Relationship evidenceUnknown until SourceX reviews
1Which internal systems, since which year, rough counts, how much customer text the records carryThe CEO has heard the idea from someone they trust and wants a conversationWhether customer contracts or privacy terms limit reuse; demand
2The customer's own description of its records, given by its CEOThe customer's CEO contacted the vendor, not the reverseThe same, plus whether the customer passes the size test
3The operator's records as its CEO describes themA named sponsor and a CEO who agreed to talkThe same

Every request in every lane stays descriptive: what the records are, roughly how many, over how many years, in which system and administered by whom. Nobody at the fund asks for exports, samples or credentials, and nobody uses a board seat to obtain a portfolio company's records for this purpose. The venture platform overview covers the program from the platform side, and the software partner canvas is the vendor's own view of lane 2.

A two-lane pilot, and the result that would retire the thesis

Run lanes 1 and 3 for eight weeks with ten companies: six portfolio companies above the size threshold and four operators from the fund's councils. Write the thresholds before the first conversation.

LaneCount to watchThreshold written in advanceIf it misses
1Companies whose CEO can describe support or engineering records created by their own staff, with limited customer contentAt least 3 of 6The thesis is wrong for this portfolio; stop lane 1
1CEOs who agree to a first conversation with SourceXAt least 2 of 6Ask whether the idea or the messenger failed before stopping
3Attendees willing to sponsor an introduction to their CEOAt least 2 of 4Lane 3 is a relationship problem, not a data one; pause it

Report counts with their denominators, including companies that declined or were never asked. One more result would retire it outright: CEOs of companies with strong internal records deciding, case after case, that the conversation is a distraction from product. Funding status plays no part in any of this; a well-funded company with 40 full-time employees fails the size test, and an older, quieter one may pass every gate.

Where the enterprise software version of the thesis breaks

  • Simulation instead of records. TheAgentCompany is itself a simulated company. If simulated environments keep improving, demand for real internal records from software companies could narrow.
  • Customer content everywhere. Support cases, implementation notes and sales engineering files often quote customers. If most of a company's internal records cannot be separated from customer material, rights review may exclude them.
  • Size. Many venture-backed software companies stay below 50 full-time employees for years, and contractors do not count.
  • Board-seat pressure. A request that reaches the CEO as a board expectation rather than an option damages the relationship and fails the program's own expectation that the decision maker wants the conversation.
  • Changing programs. SourceX applies the criteria of a specific program and checks relevance in review, so a company declined today may fit another program later, and the reverse.

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 the brief names a portfolio company with years of its own operating records and a CEO who wants to talk, register for a partner link, test it against who qualifies and read the program terms with whoever will submit. Related methods are collected in the guides hub.

Activating a portfolio for data introductions is a referral decision; assessing SourceX as a possible investment is separate, and investor materials can be requested through the SourceX investor overview.

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.

  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

Can a portfolio company license the data its customers create in its product?

No. Hosted product data belongs to the customer, and where it contains EU personal data the vendor may process it only on the customer's documented instructions. The vendor can tell customers about the program; each customer's CEO decides about its own records.

Should the fund raise this at a board meeting?

It is better raised one to one by the partner who knows the CEO. The CEO has to know about and want the conversation, and An introduction the decision maker has not heard about is, under SourceX's screening guidance, usually not a fit.

Do two portfolio companies under one parent count as separate referred companies?

No. A parent and its subsidiaries count as one company, so the USD 50,000 floor on the first qualifying transaction applies once to the group; there is no cap on what the group's transactions can earn. How earlier contact by a sister company, or another partner's introduction of one, affects credit is decided by SourceX when it reviews duplicates.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. arxiv.org/abs/2412.14161
  4. eur-lex.europa.eu/legal-content/EN/TXT
  5. sourcex.si/investors

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