A portfolio operations analyst tends to meet this at an awkward moment: the company looks strong in a board pack until someone asks where the support tickets live and hears "our BPO handles that". The summary does not have to settle the outsourcing picture, only describe it, name who can answer each open point and leave rights to SourceX's review.
Headcount, history and the vendor list come first
Collect four pieces of context through whoever holds the CEO relationship, in the company's words.
| Context | What to write | Who supplies it | Leave out |
|---|---|---|---|
| Full-time headcount at peak | The company's own full-time employees at peak and the year; vendor staff as a separate, described number | The CEO or the finance lead | Contractors and vendor agents folded into one total |
| Operating history by function | The years each function has produced records, with the date it moved to a vendor | The functional head for each area | A single founding year standing in for every function |
| Outsourced functions | Function, type of vendor, since when, whose system the work is done in, contract end date | The operations lead | The vendor's name, unless the company chooses to share it |
| Authorized sponsor | The CEO, and whether the CEO knows about and wants the conversation | The relationship owner | Anyone presented as the authorizer instead of the CEO |
The outsourcing date matters more than the founding date. A customer service function that ran in-house from 2009 and moved to an offshore BPO in 2017 has two archives with different owners of the work, and possibly different systems. One line of "support history since 2009" hides that split.
SourceX's published screen counts 50 or more full-time employees at peak, contractors excluded, so a company with 140 people of its own and 200 agents at a contact-center vendor is a 140-person company for this test. Funding status plays no part in any of the checks.
The vendor-and-owner question map
Two questions place any outsourced record: whose people did the work, and whose system holds the record today. Four combinations follow, and each one sends the summary's questions to a different person.
| Pattern | Typical arrangement | The company answers itself | The company takes to its vendor or its contract | Decided in SourceX's review |
|---|---|---|---|---|
| A. Company's people, company's system | Finance team in the company's own ERP | Years, record types, rough volume, system administrator | Nothing | Demand and rights scope |
| B. Vendor's people, company's system | BPO agents working inside the company's helpdesk; outsourced claims intake keying into the company's claims system | Years in its system, volume range, who administers it | Whether the contract gives the company the work product and notes; whether vendor-authored scripts or QA forms sit alongside them | Which material is the company's to license |
| C. Company's people, vendor-run system | Servers or an ERP run by a managed service provider; a hosted payroll portal | Which systems, since when, what the team uses daily | How an export would work, any fees and notice periods | Rights review once the scope is clear |
| D. Vendor's people, vendor's system | A BPO on its own ticketing platform; a third-party logistics provider in its own warehouse system | What the company receives (reports, extracts, dashboards) and what it can see | Whether data the vendor generates becomes the company's; what happens to it at contract end | Whether anything usable is in the company's control |
Pattern C can look worse than it is. SourceX's guide on outsourced IT says a company in that position still owns its records in most cases, though the provider may need to help with exports and its contract may set terms for that work.
Pattern D can look better than it is, because contracts decide it and contracts differ. In banking, the 2023 interagency guidance on third-party relationships treats a clause stating whether data the third party generates becomes the bank's property as a way to avoid ownership disputes, and suggests exit terms that cover timely return or destruction of the bank's data. Where personal data is involved and the vendor processes it for the company under the GDPR, recital 81 says the processor should return or delete it at the controller's choice once the processing ends. Either way, the end of a vendor contract is a dated event that can decide whether a record set still exists. That is real timing, unlike a quarter-end.
What the partner never does. No call to the vendor, no request for extracts or samples, no reading of the vendor contract and no naming of the vendor outside the company's approved summary. The company asks its vendor if it wants to, under its own contract. From the vendor's side, the same boundary is set out in whether an outsourcing vendor can share client data.
Method note. The four patterns combine two observable facts (who employed the people doing the work, and whose system holds the record) with the published screening criteria, the program terms and the sources cited here, checked 2026-10-27. The map does not measure demand, record quality, payout or the legal effect of any contract. It tells the analyst whom to ask, not what the answer will be.
A filled map for a specialty distributor (Illustrative)
Illustrative. A made-up distributor; every figure is invented and nothing here describes an outcome.
A 210-person specialty parts distributor (its own full-time employees at peak, reached in 2023) also uses about 90 agents at an offshore BPO. It has outsourced four functions over the years.
| Function | Pattern | Since | What the summary says | Status |
|---|---|---|---|---|
| Customer service, 2009-2017 | A | 2009 | Tickets in the company's helpdesk, handled by its own team | Reported by the head of service |
| Customer service, 2017 onward | B | 2017 | BPO agents work in the same helpdesk; the contract's work-product clause has not been read | Open: company counsel to check |
| IT and the ERP | C | 2015 | An MSP hosts the ERP; export route and fees unknown | Open: operations lead to ask the MSP |
| Warehousing | D | 2020 | A logistics provider runs its own warehouse system; the company receives weekly reports | Open: what the contract says about data at exit |
| Payroll | C | 2012 | Employee personal data | Left off the summary |
The approved summary that went to the CEO read, in six lines: "210 full-time employees at peak (2023); about 90 BPO agents, not employees. Customer service tickets in our own helpdesk since 2009; agents from a BPO have worked in it since 2017. ERP hosted by an MSP since 2015. Warehouse records held by a logistics provider since 2020. Open: our BPO and logistics contracts on work product and data at exit. Sponsor: our CEO, who wants a first conversation." No ticket, invoice or report was attached, and no vendor was named.
Payroll came off the list for a reason the map makes visible: it is employee personal data, which runs into the employee-privacy limit in SourceX's published screen, and nothing about the vendor changes that.
Mark each line reported, estimated or open
Every line in the summary carries one of three labels, and the label travels with the line. The examples continue the Illustrative distributor.
- Reported. The company states it, and the CEO approved the wording. "Tickets in our own helpdesk since 2009."
- Estimated. A range with its basis and the person who estimated it. "Roughly 40,000 to 60,000 tickets a year, from the head of service's monthly reports."
- Open. The question, the person at the company who will answer it and the date it was asked. "BPO contract, work-product clause: company counsel, asked 2026-10-27."
Two constraints belong on the page even when nobody likes them. The first is any contract end date in pattern D, because that is when return or deletion is decided. The second is any vendor-authored material in pattern B, such as call scripts or QA scorecards the BPO built, which may be the vendor's own and should be described separately from the company's records. An open question stays open until the company answers it; the analyst's reading of a contract never closes one.
If the BPO has registered as a SourceX partner itself (the program has a page for outsourced support providers), credit is not shared: SourceX works from dated records and, once the company submits a verified application, credits whichever valid introduction came first inside the 90-day attribution window. Where SourceX already had an earlier application, relationship, lead, account or email correspondence with the company, the introduction is a duplicate and neither the BPO nor you receives credit.
Hand the summary over, then run the first call
The CEO approves the summary, the relationship owner sends it, and the company applies itself using the partner's link. The partner whose link is used needs a signed SourceX Channel Partner Agreement before submitting, and one signed under the old Channel Partner Non-Circumvention and Non-Disclosure Agreement title still holds as signed.
A first call between the company and SourceX can follow the map directly:
- The company describes each function, when it moved to a vendor and whose system holds the records now.
- Each function is placed in a pattern, A to D, in the company's own words.
- SourceX explains which contracts its rights review would need, which the company shares with SourceX directly if it proceeds.
- Open lines are reviewed with their owners and dates.
- The company decides whether to continue, and nothing is sent before it does.
If a company's support moved to a BPO recently, what happens to in-house ticket history when support is outsourced covers the archive decision from the company's side.
Where the question map can mislead
- Contracts vary more than patterns do. A proposal on third-party risk management published in the Federal Register in September 2026 says there are no generally applicable expected contract terms for these relationships. Two pattern D companies can end up with opposite answers.
- Hybrid teams blur the quadrants. Co-sourced functions, with company staff and vendor agents in the same queue, produce records of both kinds in one system. Describe the mix; do not force a single pattern.
- Returned data can lose context. A bulk return at contract end may arrive without the notes, links or attachments that made it useful. Whether it is still usable is assessed in review.
- Fit moves with programs. SourceX checks relevance to current data needs during review; a company that misses one program's criteria today could match a different program later.
- Asking costs goodwill. Raising data questions with a vendor mid-contract can strain the relationship. No data on how vendors respond has been published; let the company judge the timing.
The map sits inside the wider portfolio operations review screen; the venture platform teams page covers the rest of 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.
Once a company's map shows records in its own control and a CEO who wants to talk, get your partner link from registration, test the summary line by line against who qualifies, and read the program terms before the CEO sees anything.
An analyst weighing SourceX as a business, rather than as a place to send introductions, has a different decision to make; the SourceX investor overview is where investor materials can be requested.
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.