When a thesis calls for workflow context, who can you introduce? A four-position map that finds the company running the workflow for itself

Short answer

Introduce the company that runs the workflow for itself. Around any workflow a thesis points to, four kinds of company sit close by: the operator doing the work for its own business, an outsourcer doing it for clients, the software vendor hosting it and the advisor who redesigned it. Usually only the operator owns the trail of how each case moved, so only its CEO can put those records on the table. The other three are how you find the operator, and sometimes how you reach its CEO.

Visual briefFull-size diagram
A swimlane of one Illustrative warranty-claims workflow, from case to handoff to exception to outcome, with four lanes: the in-house operator owns all four stages and is marked introduce; the outsourcer holds client files, the vendor hosts tenant data and the advisor holds no records.
Illustrative map of one workflow. Positions and defaults follow the method on this page; no real companies.

So the first ask goes not to the best software company in the category but to the unglamorous operator that has run the same process for a decade and kept every handoff.

What the thesis predicts, and the company question it becomes

Workflow context is the record around a task rather than the task itself: who received a case, who passed it on, what went wrong, what was decided and how it ended.

Anthropic's September 2025 Economic Index report, studying business use of Claude through its API, found that complex tasks arrive with long inputs and concluded that deploying AI for complex tasks might be constrained more by access to information than by model capabilities. Anthropic's engineering guidance on agent evaluations adds the testing side: 20 to 50 simple tasks drawn from real failures is enough to begin.

The thesis, then: dated, real cases of work moving between people and systems, failures included, are useful to teams building and testing AI for business work. That says nothing about any one company's records; SourceX checks relevance to its current data needs only in review.

For a network, the thesis becomes one narrow question: which company in our network runs this workflow at volume for its own business, has kept the trail for years, reached 50 or more full-time employees at peak, and has a CEO that someone we know can ask? Each clause removes a different group.

Clause in the questionWho it removes
Runs the workflow for its own businessOutsourcers working on client files, vendors hosting customer data, advisors
Has kept the trail for yearsOperators that record outcomes but never stored handoffs or decisions
50+ full-time employees at peak, contractors excludedSmall specialist teams, however good their records
A CEO someone you know can askCompanies you can name but could reach only with a cold approach

The workflow-owner referral discovery map

Pick one workflow, not a sector. List every company in your network that touches it and give each one of four positions. The example uses warranty claims on commercial equipment.

PositionAround a warranty-claims workflow (Illustrative)Whose records, by defaultWhat this position can do for youIntroduce?
In-house operatorA 400-person equipment distributor that adjudicates warranty claims on what it sells and servicesIts own, subject to customer contracts and privacy lawIts CEO can authorize a licensing discussionYes, once its CEO wants the conversation
Outsourced operatorA warranty administrator processing claims for 30 manufacturersMostly its clients'; client-owned material is usually not a fitDiscuss the records it created for itself, such as procedures and quality reviewsOnly for material it owns, never client files
Software vendorThe claims platform both of them useIts customers'; for EU personal data, a processor acts only on the customer's documented instructionsTell its own customers about the program and let interested CEOs come forwardNot for hosted data; customers who opt in can be introduced
Advisor or implementerThe consultant who redesigned the distributor's claims processNoneAsk the operator CEOs she already knowsNo; often the relationship owner instead

Two rules make the map work. The position belongs to the record, not the company: a warranty administrator is an outsourced operator for its clients' claims and an in-house operator for its own hiring, billing and quality records. And the three non-owning positions are often the best route to the operator, through a vendor telling its customers or an advisor asking CEOs she knows, with nothing confidential passed on.

A filled map for one platform team:

RowPositionCompany (Illustrative)Trail known at metadata levelRelationship ownerNext action
1In-house operator400-person equipment distributorClaims, technician notes and approvals in one system since 2014Operating partner who sat on its boardOperating partner asks the CEO
2In-house operator260-person property maintenance groupWork orders in a system; dispute notes in emailPortfolio founder who supplies itFounder decides whether to raise it at all
3Outsourced operatorWarranty administrator with 30 manufacturer clientsClient files; its own quality scorecards since 2019LP principalAsk only about its own procedures and quality records
4Software vendorPortfolio company that builds the claims platformCustomers' dataPortfolio CEOVendor tells customers; opt-ins only
5AdvisorClaims-process consultantNonePlatform leadAsk which operator CEOs she can approach herself
6In-house operator45-person regional repair shopComplete trail, ten yearsPlatform leadPark until full-time headcount passes 50

Method note. Positions and default owners come from SourceX's screening guidance, the program terms and, for EU personal data, GDPR Article 28, checked on 2026-10-26. The map does not measure demand, record quality or payout, and SourceX's rights review can overturn any default owner.

Which layers of the trail did the operator keep?

An operator can own its records and still hold little workflow context. Ask, at metadata level, which of four layers survive and for how long:

  1. The case record. What was asked for, by whom and when. Which system holds it, and since what year?
  2. The handoff trail. Each change of owner or status, with a time. Does the system keep the status history or only the current status?
  3. The decision notes. Why a case was escalated, approved or refused. Are decisions written in the system, or in email and phone calls?
  4. The outcome. How the case ended and whether it came back. Can a reopened case be linked to the first one?

An operator that kept all four for years is the row the thesis describes; one whose decisions live in inboxes may still be worth a conversation if the introduction says so plainly. The live guide on workflow context versus isolated files lists where these records tend to sit, and the evidence-gap page shows how to describe a missing piece honestly.

Relationship and ownership evidence before the first ask

Collect two kinds of evidence separately: that the records are the company's to discuss, and that a trusted person can ask the CEO.

EvidenceWhat you need before askingWho supplies itStill unknown until SourceX reviews
OwnershipThe records were created by the company's own staff for its own workThe operations lead, through the CEOWhether customer contracts, employee privacy or third-party terms limit reuse
HistoryThe years each layer coversThe system administratorWhether those years match a current program
AuthorityThe CEO knows about the conversation and wants itThe CEOWhat a license would cover and pay
PathA named person who will ask the CEOYour relationship ownerNothing; settle this yourself
Prior contactNo earlier lead, account or email between SourceX and the companyThe CEO, then SourceX's duplicate reviewWhether credit is available

Every question stays descriptive: record type, rough count, span of years, system and administrator; files, samples, screenshots and logins are out of scope. Ask about prior contact first, because Section 3 of the program terms treats any lead, account or email correspondence the company already had with SourceX as an existing relationship, and a new introduction cannot be credited for one.

One partner per company is credited, namely the one whose valid introduction came earliest within the 90-day attribution window, and that credit settles only when the company submits a verified application; when an operating partner, LP or portfolio founder owns the relationship, agree in writing who submits. For operators filed under a different industry code, the sector specialist's tracing method finds them, and the outsourced support page covers the outsourcer's own records.

A narrow pilot, and the results that would change the thesis

Run the map on one workflow for six weeks, with three predictions and their refutations written before the first conversation.

PredictionRefuted ifWhat you change
In-house operators hold more of the four layers than any other positionFewer than half the operator rows can describe a handoff trail or decision notesChoose a workflow where decisions are written down
The three non-owning positions lead you to operatorsVendors and advisors produce no operator row you did not already haveDrop the outer positions and map operators directly
Operator CEOs asked by a trusted owner agree to a first conversationMost decline, or the relationship owners will not askTreat the path as the constraint and fix relationship ownership first

Keep declined and parked rows in the count, and report a dozen rows as counts, not rates.

One result would change the thesis itself rather than the map: operators that kept all four layers, introduced with their CEOs' agreement, repeatedly turned away for relevance. Demand for this workflow would then be weaker than the research implies. For the general method of turning a thesis into a short company pilot, see the thesis-to-introduction canvas.

Where the workflow-context thesis could be wrong

  • Simulated workplaces. Researchers already build simulated companies to test agents: TheAgentCompany benchmark is a self-hosted software company with simulated colleagues and 175 professional tasks, on which the best baseline agent completed about 30% autonomously. If simulations satisfy developers, demand for real trails could narrow.
  • Scattered context. The same Economic Index report flags dispersed context as a barrier to deployment; decisions buried in inboxes may never assemble into a usable record.
  • Rights. Customer contracts and privacy law can limit even an operator's own records. SourceX's rights review decides, and it can say no.
  • Program fit. SourceX applies each program's own criteria, so a strong operator can be declined today and fit another program later.
  • Goodwill. Every ask spends a relationship owner's credibility with a CEO; record what it costs in your own pilot.

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 map shows an in-house operator with a known trail and a relationship owner ready to ask, register for a partner link, check the row against who qualifies and read the program terms before the CEO hears from anyone. More network methods are in the guides hub.

Choosing whom to ask is referral work; evaluating SourceX as an investment is a separate exercise, with investor materials available 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 software company in our portfolio introduce the customers whose workflows it hosts?

It can tell its customers about the program and introduce those whose CEOs ask to take part, but it cannot offer the data it hosts. That data belongs to the customer, and each customer's CEO decides whether to discuss licensing its own records.

Is an outsourcing firm ever the right company to introduce?

Sometimes, for records it created for its own business: its procedures, training material, quality reviews and internal operations. Client files it processes stay off the table, and SourceX's screening guidance treats client-owned material as usually not a fit.

If the thesis is right, will an operator's records be licensed?

Not necessarily. The thesis describes demand in general. Whether a given company's records match a current program, whether its contracts allow reuse and what a license would cover are decided only in SourceX's review and a signed agreement.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. anthropic.com/research/anthropic-economic-index-september-…
  4. anthropic.com/engineering/demystifying-evals-for-ai-agents
  5. arxiv.org/abs/2412.14161
  6. eur-lex.europa.eu/legal-content/EN/TXT
  7. 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