Leadership and readiness
AI data vendor readiness investment: fund what a plan can't answer
By SourceX Editorial · Reviewed by Noah Loul ·
10 sections
Short answer
AI data vendor readiness investment pays when an attainable buyer has put a requirement in writing that a dated remediation plan cannot satisfy, and the fix can land before that buyer decides. Most asks miss that bar: in Google's public vendor questionnaire templates, 129 of 164 warning prompts ask when a gap will be fixed. Fund long-lead items such as attestations for a segment of buyers, not one deal.
Checklist
AI data vendor readiness
Key takeaways
- Procurement readiness is five purchases with different lead times and reuse: questionnaire answers, attestation, insurance, contract terms and supplier onboarding.
- In Google's public VSAQ templates, 129 of 164 warning prompts ask the vendor when a gap will be resolved, and 7 of 45 program questions concern third-party audits.
- The 2023 interagency guidance scales bank due diligence to risk and lets a bank proceed when residual risk is acceptable, so many gaps are negotiable.
- Fund a long-lead item ahead of a deal only when several attainable buyers in the target segment require it in writing and refuse a plan.
- Judge readiness spend by signed buyers per artifact and by the share of asks met with substitutes, not by questionnaires answered.
When is AI data vendor readiness investment worth the expense?
When a buyer the company can realistically win has put a requirement in writing, a dated remediation plan or existing evidence will not satisfy it, and the fix can be finished before that buyer decides. Spending that meets all three conditions converts a blocked deal into a signable one. Spending that meets none of them buys a document for a buyer who has not asked.
For an investor reading a use-of-funds plan, procurement readiness is easy to over-fund because every item sounds prudent. Security questionnaires, third-party attestations, insurance, contract templates and supplier onboarding each cost money and staff time before revenue, and each is defended with the same sentence: enterprise buyers require it. The useful question is narrower. Which buyer, in what words, by when, and would anything cheaper have done?
This article treats readiness as five separate purchases with different lead times and reuse, counts what a large buyer's public questionnaire accepts in place of a finished control, sets out what regulated buyers must and need not demand, and ends with a decision tree, a milestone table, the risks and the questions to ask a data company, SourceX included.
Five procurement asks, five different cost curves
They behave differently enough that a single compliance budget line hides the decision. Questionnaire answers are cheap and reusable; an attestation is slow and recurring; insurance renews every policy term; contract terms are negotiated buyer by buyer unless a template sticks; onboarding cannot even start until a buyer has chosen the vendor.
Regulated buyers explain why each ask exists. The 2023 interagency guidance on third-party relationships from the U.S. federal banking agencies says due diligence typically assesses a third party's information security program and lists insurance coverage as an area to review, with examples including fidelity bond, liability, property hazard and casualty, and gaps a general commercial policy may not cover, such as cybersecurity or intellectual property. Contract provisions, it adds, typically require the third party to maintain specified types and amounts of insurance.
The table maps each ask to the buyer evidence behind it, what can stand in for it and what sets its lead time:
| Procurement ask | Who asks, on the evidence | What can stand in for it | What sets the lead time |
|---|---|---|---|
| Security questionnaire answers | Google's public VSAQ templates; bank due diligence on a third party's information security program | A maintained answer library, with gaps answered by a dated plan | Staff time to answer and keep answers true |
| Third-party attestation or certification | New York DFS's October 2025 letter lists external audits among due diligence considerations | A dated plan, a scope statement and the policies themselves, where accepted | Controls must run before anyone can test that they ran |
| Insurance | 2023 interagency guidance: insurance coverage is a due diligence area; contracts often set types and amounts | Negotiated liability terms or existing coverage, within the buyer's risk appetite | Underwriting and binding, then renewal each term |
| Contract templates and data terms | DORA Article 30 for ICT services to EU financial entities; banks may ask to modify a vendor's standard contract | The buyer's own paper or a clause library | Counsel drafting and redline rounds per buyer |
| Supplier onboarding | Each buyer's vendor setup after selection | Nothing; it follows the buyer's choice | The buyer's process after award |
What one large buyer's questionnaire accepts in place of a finished control
Mostly a dated plan. Google's open-source Vendor Security Assessment Questionnaire repository, which notes that VSAQ is not an official Google product, says in its README that questionnaires like these are used at Google to assess the security programs of third parties. Counting the four templates at the repository's last commit (January 2021) gives 243 questions and 164 warning prompts, the messages that appear when a vendor gives a weak answer.
Of those 164 warning prompts, 129, or 79%, ask the vendor to include an estimate of when the issue will be resolved if it is working on it; 143, or 87%, ask for either that estimate or a description of compensating or mitigating controls. The questionnaire is built to receive a gap with a date attached, not to end the conversation at the first no. Severity labels still matter: 13 prompts are marked critical and 86 high, so a plan for those has to be credible.
Third-party audits are a small part of the ask. In the security and privacy programs template, 7 of 45 questions sit in the third-party audits block: how often audits happen, their scope, the standards checked, how auditors are chosen and whether the vendor will share a management summary. An attestation report answers those seven well and leaves the other 38 to be answered anyway. The other 198 questions, 81% of the total, sit in templates for web applications, infrastructure and physical data centers, which presume systems the vendor operates to deliver its service. The counts by template:
| VSAQ template | Questions | Warning prompts | Prompts asking for a fix date | Critical or high prompts |
|---|---|---|---|---|
| Security and privacy programs | 45 | 34 | 28 | 28 |
| Web application | 73 | 42 | 20 | 17 |
| Infrastructure | 95 | 72 | 67 | 46 |
| Physical and data center | 30 | 16 | 14 | 8 |
Regulated buyers have to ask, but their rules let them proceed
Banks, New York-regulated financial firms and EU financial entities must run third-party diligence, but their rules scale it to risk and allow them to go ahead with gaps. That is the evidence a data company needs before deciding that a requirement is a true gate.
The 2023 interagency guidance says that while a third party may first offer a standard contract, a banking organization may request modifications, additional provisions or addendums. It also says that a bank with limited negotiating power may be unable to get every provision it wants and may still reasonably proceed if the residual risks are acceptable. New York's Department of Financial Services, in an October 2025 industry letter that it says imposes no new requirements, lists among due diligence considerations a provider's cybersecurity history, its financial stability and whether it undergoes external audits.
Contract terms are where EU financial buyers have least room. The Digital Operational Resilience Act defines ICT services as digital and data services provided through ICT systems to internal or external users on an ongoing basis, and its Article 30 requires the contract, including service levels, to be documented in one written document with minimum provisions such as a full service description, where services are provided and data processed, assistance in an ICT incident, cooperation with authorities and termination rights with minimum notice periods. Whether a dataset license falls within that definition depends on how it is delivered: a one-off file transfer is a weaker fit than a refreshed data feed. Counsel should read the specific arrangement.
Decision tree: which readiness asks to fund, defer or refuse
Run every proposed readiness spend through five questions in order and stop at the first that decides it; then release money only against milestones a counterparty can confirm. The questions and the thresholds in the milestone table are this article's editorial framework, and every count in the table is Illustrative.
The order matters because the cheap answers come first. A company that starts at question five, will others need it, ends up buying attestations and insurance for buyers who would have accepted a dated plan. The tree:
- Has an attainable buyer asked in writing? Attainable means qualified, funded and in a segment the company targets. If not, keep the answer library current and spend nothing new.
- Is the ask a gate or a scored preference? A preference is answered from the library, with a dated plan for the gap.
- Will the buyer accept a substitute: a dated plan, existing policies, a narrower scope or negotiated contract terms? If so, offer it and log the acceptance.
- Can the item be finished before this buyer decides? If yes and the buyer refused every substitute, fund it at the narrowest scope that buyer accepts.
- If it cannot land in time, will at least two other attainable buyers in the same segment need the same artifact? Fund it for the segment if so; otherwise let this deal go or wait for the next cycle.
| Readiness step (Illustrative) | Evidence that releases the spend | Milestone that reduces uncertainty | Stop or defer rule |
|---|---|---|---|
| Answer library and dated plans | First questionnaire from an attainable buyer | Questionnaire accepted with gaps carried as dated plans | Never stop; refresh when a plan date passes |
| Contract kit: license, data terms, clause library | A second buyer redlines the same clause | The next buyer signs in fewer redline rounds than the last | If every buyer insists on its own paper, keep only the clause library |
| Insurance named in a contract | A draft contract that names coverage types and amounts | Certificate accepted and contract signed | Bind only coverage a contract names |
| Supplier onboarding | The buyer selects the company | Vendor number issued and first invoice accepted | Never before selection |
| Third-party attestation | Two or more attainable buyers in one segment require it in writing after refusing a plan | A buyer's security review closed citing the report | Defer while fewer buyers require it; scope it to the delivery path |
Which readiness items must start before any buyer asks?
Only items whose lead time is longer than the decision window of the buyers who need them, and only when enough of those buyers exist. Everything else can wait for a written ask, because it can be finished inside the deal.
An attestation is the clearest long-lead item. An auditor cannot report that controls operated over a period until they have operated over that period, so a company that waits for a buyer's written requirement usually cannot produce the report before that buyer decides. That is the strongest argument for funding one early, and it is an argument about a segment, not a deal. Questionnaire answers, contract terms and onboarding all fit inside a normal buying process; insurance usually does too, once a contract names the coverage.
Illustrative: a data company has eight attainable buyers in one segment. Three put an attestation requirement in writing, and one of the three accepted a dated plan instead. The remaining two refusals meet the milestone table's threshold, so the attestation is funded, scoped to the systems that hold and deliver datasets. Had only one buyer refused the plan, the same spend would have bought a report for one deal whose decision date it could not meet.
Does readiness spending follow signed buyers or only requests?
That is the test, because readiness cost can grow faster than accepted delivery. Compliance hires, trust-portal software and questionnaire automation all add fixed cost on their own calendars, while signed buyers arrive on the buyers' calendars. A company can answer forty questionnaires, pass none of them into contracts, and still report rising readiness activity.
Two ratios separate the cases. Readiness spend per signed buyer should fall as artifacts are reused; if it rises with each new buyer, the company is building bespoke documentation it has not priced. The share of written asks met by a substitute rather than new spend should be high in early periods; if it is near zero, the company is buying first and asking later.
Automation earns its place only after answers repeat. Software that fills questionnaires from a library is useful when the same questions come back from several buyers; bought before that, it automates a library that does not exist yet.
What would make plan-first sequencing a mistake
Five developments would make it wrong to answer most asks with a plan and fund only long-lead items for a segment. An investor should ask which one would hurt the company most.
- Buyers stop accepting plans. The VSAQ templates are a January 2021 public snapshot of one buyer's approach; current practice at large AI buyers may require a third-party report before any conversation, in which case waiting loses deals that never reach a pipeline.
- Bank buyers' rules harden. On 15 September 2026 the federal banking agencies proposed revised third-party risk guidance, which would add a section on insurance, indemnification and liability limitations, including negotiating coverage terms relevant to the specific risks of the relationship. If adopted, insurance asks from banks may become more specific.
- Data feeds fall within DORA. If EU financial entities treat a refreshed data feed as an ICT service, the Article 30 contract provisions become a gate for that segment, and a contract kit moves from optional to required.
- Plans become liabilities. A dated plan is a commitment; a company that misses its own dates turns a cheap answer into a credibility problem with every buyer who saw it.
- Readiness is mistaken for supply. Passing a security review says nothing about whether a company may license the records it sells or whether buyers want them, so readiness milestones are never evidence of rights or demand.
Readiness questions to put to any data company, SourceX included
Ask for the written requests behind every readiness line, and for what was offered before money was spent. Good answers name buyers' segments, dates and outcomes rather than badges.
SourceX is one application of the question, and its published pages set the starting point. The company says it runs the chain from sourcing and qualification through rights review, contracting, preparation, delivery and payment, that a supplying company approves scope and terms and signs before any data reaches it, and that large deliveries stay in the seller's own storage or travel on encrypted drives rather than being hosted by SourceX. That last point bears on how much of a hosted-systems questionnaire applies, which is worth asking about directly.
SourceX's trust page, read on 27 October 2026, lists three security and privacy attestation and certification programs as in progress, with no report or certificate issued, and lists independent security assessments as planned. It says questionnaire responses, a business continuity overview, an incident escalation process, contract templates and a data processing agreement where applicable are shared privately after review. Its readiness spending and other commercial figures are not published; they go to investors privately, not into articles. Its capital raise runs under Rule 506(c), so only verified accredited investors can take part, and requests for materials go through the investor page. The questions:
- For each readiness artifact you hold or plan, which attainable buyer asked for it in writing, and when?
- How many written asks did a dated plan, existing policies or negotiated terms satisfy, and how many buyers refused them?
- Which deals stalled on a readiness item, for how many days, and which item?
- What share of a typical buyer questionnaire covers systems you do not run for buyers?
- How has readiness spend per signed buyer moved over the last four quarters?
- Which dates in your remediation plans have passed, and were they met?
Methods note: how the questionnaire counts were made
The counts are this article's own, made on 27 October 2026 with a script that reads only the four questionnaire template files of google/vsaq at commit 366d670 (last commit 11 January 2021): security and privacy programs, web application, infrastructure, and physical and data center. The two test templates are excluded. The script drops comment lines, joins strings the files concatenate with a plus sign, parses each file as JSON and walks every item.
A question is an item of type radiogroup, checkgroup, line, box, check, radio, yesno or upload; the checkgroup with id options at the top of two templates configures the questionnaire and is dropped. A warning prompt is an item of type tip with warn set to yes. A prompt asks for a fix date when its follow-up text contains the phrase estimate of when; it asks for an alternative or a fix date when that text contains estimate of when, compensat or mitigat. Critical or high counts use each prompt's severity field. Percentages are rounded half up on the final value only.
Not measured: how often any buyer accepts a dated plan in practice, what any readiness item costs, how long any attestation takes, and what SourceX or any other company spends on readiness. The decision tree, milestone table and thresholds are editorial and Illustrative, drawn up on 27 October 2026 from the sources cited.
Frequently asked questions
Should an AI data startup get a security attestation before its first enterprise deal?
Usually not before a buyer asks in writing. Most procurement asks can be met with a maintained answer library and dated remediation plans, and an attestation answers only a small part of a typical questionnaire. The case for funding one early is a segment of attainable buyers who require it and whose decisions will come before a report could be produced on demand.
Can a vendor answer no on a security questionnaire and still win the deal?
Often, if the gap comes with a credible date. In Google's public VSAQ templates, 129 of 164 warning prompts ask the vendor to estimate when the issue will be resolved. Bank guidance also lets a buyer proceed when residual risks are acceptable, though critical gaps need a convincing plan.
What insurance do bank buyers look for in a vendor?
The 2023 interagency guidance lists examples such as fidelity bond, liability, property hazard and casualty, and coverage a general commercial policy may not include, such as cybersecurity or intellectual property. Contracts typically require specified types and amounts. A vendor should bind the coverage a buyer's contract names rather than buy every type in advance.
Does DORA apply to a data license with an EU bank?
It depends on how the data is delivered. DORA's ICT services cover digital and data services provided through ICT systems on an ongoing basis, so a refreshed data feed is a closer fit than a one-off delivery. Where it applies, Article 30 sets minimum contract provisions, and counsel should review the specific arrangement.
Does SourceX publish its readiness spending or certifications?
It does not publish spending. Its trust page, read on 27 October 2026, lists three security and privacy programs as in progress with no report or certificate issued, and says procurement materials are shared privately after review. Investors can request company materials through the investor page.
Sources
- Google's VSAQ templates at commit 366d670 contain 243 questions and 164 warning prompts; 129 prompts ask for an estimate of when a gap will be resolved (this article's count). Source
- The VSAQ README says questionnaires like those in the repository are used at Google to assess the security programs of third parties, and that VSAQ is not an official Google product. Source
- The 2023 interagency guidance on third-party relationships covers information security and insurance due diligence, insurance provisions in contracts, contract modifications and proceeding when residual risks are acceptable. Source
- A September 2026 proposal would add a section on insurance, indemnification and liability limitations to the agencies' third-party risk guidance. Source
- New York DFS's October 2025 industry letter lists cybersecurity history, financial stability and external audits among third-party due diligence considerations and says it imposes no new requirements. Source
- DORA defines ICT services as digital and data services provided through ICT systems on an ongoing basis, and Article 30 sets minimum contract provisions in one written document. Source
- SourceX's trust page lists three security and privacy programs in progress with no report or certificate issued, and shares procurement materials privately after review. Source
- SourceX shares company and commercial metrics with investors directly and takes investor materials requests on its investor page. Source
Request SourceX investor materials
SourceX shares company and commercial metrics with investors directly. Any offering is made only to verified accredited investors.