The questionnaire below fits one call with whoever administers each system, once the CEO has said yes to a conversation.
Records questions and systems questions are different jobs
A records question asks what work the company captured. A systems question asks where that history lives, how far back it really goes and who holds the account. The CEO can answer the first kind; the second usually needs whoever runs each system, often an operations lead or an outside IT provider. So the order is fixed: the CEO first, then the people the CEO names.
What the fund already knows stays out of it. SourceX's who-qualifies page notes that NVCA's model management rights letter makes confidential information an investor receives subject to the Investors' Rights Agreement's confidentiality provisions. Your fund's documents may differ; either way, ask afresh, separately from board business.
Why a go-live year is not history depth
"We've been on this system since 2012" tells you when the system arrived, not how much history survives in it. Three ordinary mechanisms shorten history, and the questionnaire asks about each one.
- Retention settings. Many platforms delete on a schedule an administrator sets. Microsoft's Purview documentation, for example, describes retention settings that keep content, delete it, or keep it for a period and then delete it automatically; the period runs from a start point such as when an item was created or last modified, not from when the policy was switched on.
- Plan limits. Slack says free workspaces can view and search only the last 90 days of messages and files, and that messages and files more than one year old are permanently deleted, applied on a rolling basis from August 26, 2024. A company that ran chat on a free plan may have years of conversations in memory and months in the system.
- Migrations. When a company changes systems, someone decides what moves. Whether closed history moved, stayed in a read-only archive or was left behind is a question to ask, never an assumption to make.
| Pattern | What the CEO says (Illustrative) | What may actually survive | Questions that tell them apart |
|---|---|---|---|
| Continuous | "Same system since 2012" | History since 2012, if no deletion setting applies | Q8: does any retention setting remove older items? |
| Migrated with a cut | "We moved to the new platform in 2019" | 2019 onward, plus earlier years only if migrated or archived | Q6 and Q7: what moved, and where the rest went |
| Rolling window | "It's all in chat" | Months, if a plan limit or retention rule trims it | Q9: which plan tier, and since when |
| Split custody | "The old vendor hosted it" | Nothing reachable, if the old account lapsed | Q11: whose account, and is it still open |
The systems metadata questionnaire
Fourteen questions in five blocks, one row per system. Every answer is a fact about a system, never something taken from inside it.
| No. | Question | Answer format | Usually answered by |
|---|---|---|---|
| Q1 | What kind of system is it: CRM, ERP, helpdesk, field service, document management or chat? | Category; product name optional | System administrator |
| Q2 | Which business work does it record? | One line in the company's words | Department head |
| Q3 | Who enters the records: staff, customers, vendors or automation? | Creator types | Department head |
| Q4 | When did it go live? | Year | System administrator |
| Q5 | What did it replace? | Earlier system category and its years | System administrator |
| Q6 | What happened to the old system's data: migrated, archived read-only or left behind? | One of the three, with years | System administrator |
| Q7 | If migrated, did closed history move or only open items? | Closed and open, open only, or unknown | System administrator |
| Q8 | Does any retention or deletion setting remove older items? | Yes with the period, no, or unknown | System administrator or IT provider |
| Q9 | Has a plan or license tier ever limited how much history is kept? | Yes with the years, no, or unknown | System administrator |
| Q10 | Are attachments and comments stored with each record or somewhere else? | With the record, a separate store, or unknown | System administrator |
| Q11 | Whose account or tenant holds it: the company, a parent, a vendor-managed account or a customer? | Account holder | CFO or IT lead |
| Q12 | Which legal entity holds the contract for it? | Entity name | CFO |
| Q13 | Does a shared identifier, such as an order, job or ticket number, connect it to other systems? | Yes with the key type, or no | System administrator |
| Q14 | Is a renewal, migration, retirement or sale coming, and when? | Event and date | CEO or CFO |
Q1 to Q3 say what work a system holds and who wrote it; Q4 to Q7 fix the real start year; Q8 to Q10 say whether that history survived. Q11 and Q12 say whose records they are and which entity would sign; for the reward cap, a parent and every subsidiary under it are treated as a single company. Q13 shows whether one case can be followed across systems, and Q14 is the only legitimate urgency: a dated retirement, purge or sale.
Questions that never go on the form
| Never ask for | Why |
|---|---|
| Passwords, API keys or read-only logins | Credentials stay with the company; SourceX arranges any access under an agreement |
| Network diagrams, hostnames, security settings or audit findings | Security detail says nothing about fit and is risky to hold |
| User lists, access logs or named org charts | Personal information the introduction does not need |
| Exports, samples, screenshots or test files | Record content, which partners never handle |
| Record counts per customer | Reveals customer relationships |
If something arrives anyway, do not open or forward it; delete it and tell the sender you have.
One company, four systems (Illustrative)
Illustrative. The company, its systems and its dates are made up to show the method.
A 230-person commercial cleaning and facilities company, run by its founder as CEO, has been in the portfolio since 2021. The CEO agreed to a conversation and named the operations director and the outside IT provider to answer.
| System (Q1) | Went live (Q4) | Predecessor and its fate (Q5, Q6) | Survival (Q8, Q9) | Account holder (Q11) | History depth, as answered |
|---|---|---|---|---|---|
| Field service and work orders | 2019 | Desktop scheduling tool, 2010 to 2019, archived read-only | No deletion setting known | Company | 2019 onward; 2010 to 2019 only if the archive still opens |
| CRM | 2016 | Spreadsheets, not kept | No deletion setting known | Company | 2016 onward |
| Email and documents | 2014 | On-premises mail server, not migrated | Retention policy deletes mail after seven years | Company | About seven years of mail; documents since 2014 |
| Team chat | 2021 | None | Free plan until 2025 | Company | Recent months only; treat as no history |
The line that goes to SourceX reads: "Work-order history since 2019 in the current system, possibly since 2010 if a read-only archive opens; CRM since 2016; mail kept about seven years under a retention policy; little chat history. Answers from the operations director and the IT provider; nothing has been checked." Q14 adds one dated event: the server holding the read-only archive is due to be retired next spring. That retirement, not a quarter-end, is the reason to talk soon.
Labels for estimates, constraints and open questions
Every answer carries a source and one status.
| Status | Use it when | Example (Illustrative) |
|---|---|---|
| Answered | The administrator stated it | "Went live in 2019" |
| Estimated | A range or a recollection | "The archive covers roughly 2010 to 2019" |
| Unknown | Nobody has checked | "Whether the archive opens" |
| Constraint | A fact that may narrow scope | "Some work orders sit in a client's portal" |
Flag constraints without judging them: records kept in a customer's tenant or portal (material that belongs to clients is usually not a fit), vendor terms that govern exports, personal information in free-text fields, and a parent company that holds the account. On groups, one point is settled and one is not. A parent and its subsidiaries share a single reward cap. Whether a parent's or sister company's earlier dealings with SourceX change who is credited for this introduction is not covered by the published terms; SourceX resolves it in duplicate review, so write any such contact down and leave the judgment there.
Method note. The questionnaire was built from the program terms (version 2026-10-22.2, since replaced by version 2026-11-04), SourceX's who-qualifies page and the Microsoft and Slack help pages cited here, all checked on 2026-10-27. Vendor limits change, so recheck them before relying on a specific plan. The questionnaire has not been tested with administrators, and SourceX has not published how often stated history depth matches what review finds; those figures are not yet published. To measure it, record for each introduction the depth the questionnaire predicted and the depth review confirmed.
The handoff and the first call with SourceX
- The CEO approves. The CEO sees the completed rows and the summary line and can change either.
- Prior contact is asked, not assumed. A company that already had any application, lead, account or email correspondence with SourceX is a duplicate and is not credited, so ask the CEO and write the answer down.
- One submitter. The program credits one partner per company, for the first valid introduction within the 90-day attribution window, when the company submits a verified application. Settle in writing who submits, and have that person sign the SourceX Channel Partner Agreement beforehand.
- Rows, not files. Send the rows and the summary line with the CEO's permission, and nothing else.
A first call of about 30 minutes, with the CEO, an administrator the CEO chooses and SourceX, can confirm the system list and history depth, take the unknowns that matter most, explain how review and any export would be arranged under an agreement, and agree a next step. The platform team's part ends once that call is booked.
Deal teams can add the four data questions in the IT due diligence checklist. Company-side versions of this exercise are the metadata-only inventory of business systems, the SaaS inventory template and the metadata-only Slack inventory template; for a period-by-period internal document, SourceX's ten-year history brief on its main site.
Where the questionnaire can mislead
- Administrators recall; they do not audit. A retention setting switched on in 2018 may be forgotten, so treat Q8 and Q9 as estimates.
- Settings are not the only deletion. Manual clean-ups, departed users' accounts and lapsed vendor contracts remove history too.
- Deep is not licensable. Fifteen years of history can still be off-limits under customer contracts or vendor terms, which only counsel and SourceX's rights review can read.
- Questions drift toward security. "Who has admin access?" feels harmless and is not needed; keep to the fourteen.
- Enthusiasm is not fit. A keen administrator changes none of the entry tests: the company must have reached 50 or more full-time employees at its peak (contractors do not count), keep documented operating history, hold the rights to license it and offer an authorized contact. 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.
- Demand moves. SourceX checks relevance to its current data needs during review, and a company that fits no program now may fit a later one.
The portfolio overview of the program is at venture platform teams, and related walkthroughs sit in the guides library.
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.
If the fourteen answers point to genuine history depth and the CEO has asked to talk, get your tracked link through partner registration, hold the company up against the qualification criteria and go through the program terms before a single answer leaves the platform team.
Asking a portfolio company about its systems is referral work; evaluating SourceX as a company to invest in is a separate decision, and SourceX shares investor materials on request through its 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.