Why do regulated buyers run vendor assurance separately from commercial evaluation?
In standard B2B sales, the person who wants to buy can approve the purchase. In regulated organisations, the buying process is split:- The business sponsor evaluates whether the product solves the problem and whether the price is acceptable.
- The risk and assurance team evaluates whether the vendor is safe to onboard — independent of whether the product is good.
What risk categories does the assurance team evaluate?
The assurance team evaluates vendors across six categories. Each category requires documented evidence.Security risk
Can the vendor protect data and systems from breach, loss, or unauthorised access?- ISO 27001 certification or SOC 2 Type II report
- External penetration test results (within 12 months)
- Security architecture diagram (hosting, encryption, access controls)
- Incident response and breach notification procedures
- Vulnerability management process
Data risk
Does the vendor handle personal and sensitive data appropriately?- Data processing agreement (GDPR-compliant)
- Data flow diagram showing where data is collected, processed, stored, and deleted
- Retention and deletion policies with automated triggers
- Data classification and handling procedures
- Cross-border data transfer mechanisms (if applicable)
Financial risk
Will the vendor still exist and be solvent throughout the contract term?- Filed company accounts (most recent two years)
- Funding history and current financial position
- Insurance certificates: professional indemnity, cyber liability, public liability
- Key person risk assessment (for small teams)
Operational risk
Can the vendor maintain service availability and performance?- Service level agreements with defined uptime commitments
- Historical uptime data
- Disaster recovery plan and tested recovery time objectives
- Capacity planning and scalability approach
- Change management and release procedures
Regulatory risk
Is the vendor compliant with relevant sector-specific regulations?- Regulatory registrations (FCA, ICO, sector-specific authorities)
- Compliance certifications and audit reports
- AML/KYC policies (if handling financial data)
- Regulatory change monitoring process
Concentration risk
Does onboarding this vendor create over-dependence on a single supplier?- Assessment of whether the vendor provides a critical service with no alternative
- Exit planning: how the buyer would migrate away if needed
- Escrow arrangements for source code or data
- Contractual protections: termination rights, data portability, transition assistance
How does the assurance process typically run?
The vendor risk assessment follows a predictable sequence. Understanding this sequence allows vendors to prepare proactively rather than react. Step 1: Vendor registration (week 1) The buying organisation adds the vendor to its supplier management system and assigns a risk category. Higher-risk vendors trigger a more comprehensive assessment. Step 2: Questionnaire (weeks 2-4) The vendor receives a standardised risk questionnaire covering all six categories. These typically contain 100 to 300 questions. Large organisations use standard formats (SIG Lite, CAIQ, or proprietary questionnaires). Step 3: Evidence review (weeks 4-8) The risk team reviews the questionnaire responses and supporting evidence. They may request additional documentation, clarification, or evidence for specific areas. Step 4: Assessor meeting (weeks 6-10) For higher-risk vendors, the risk team schedules a call or meeting to discuss specific concerns, probe gaps, and assess the vendor’s maturity. Transparency about weaknesses is better received than defensiveness. Step 5: Risk report (weeks 8-12) The risk team produces an internal report summarising the vendor’s risk profile, identifying any residual risks, and recommending acceptance, conditional acceptance, or rejection. Step 6: Approval or remediation (weeks 10-16) If approved, the vendor moves to contract negotiation. If conditionally approved, the vendor must close specific gaps (e.g. obtain a certification, complete a pen test) before the contract can proceed. Total elapsed time: 10 to 16 weeks for a standard assessment. Complex or high-risk vendors may take longer.How should startups prepare for vendor risk conversations?
Startups face specific challenges in vendor assurance: shorter trading history, smaller teams, less formal processes, and fewer certifications. These are not disqualifying — but they require honest positioning.- Build the evidence pack before outreach. Do not wait for the buyer to ask. Having documents ready signals maturity and accelerates the process.
- Obtain baseline certifications. ISO 27001 or Cyber Essentials Plus is the minimum for most regulated buyers. SOC 2 Type II is increasingly expected. Budget 6 to 12 months for certification if you do not have it.
- Run an external penetration test annually. Use a reputable firm. Document remediation of findings. Buyers will request the report and expect to see that issues were fixed.
- Prepare a master questionnaire response. After completing 2 to 3 vendor questionnaires, you will see that 70% of questions repeat across buyers. Maintain a master document with pre-written answers and supporting evidence links.
- Be transparent about gaps. Every startup has gaps. A startup that says “we do not have ISO 27001 yet but we have scheduled the certification audit for Q3 and here is our current security posture” is more credible than one that deflects.
- Engage the risk team early. Request an introductory conversation with the buyer’s risk team alongside the business sponsor. This surfaces blockers early and demonstrates proactive risk awareness.
Common mistakes
- Assuming the business sponsor can override risk. They cannot. Even a C-level sponsor must wait for risk approval. Give them the evidence they need to advocate internally.
- Being defensive about gaps. Pretending gaps do not exist undermines trust. Acknowledge gaps, describe your remediation plan, and provide a timeline.
- Treating the questionnaire as admin. The vendor questionnaire is not a form to fill in quickly. It is the foundation of the risk team’s assessment. Invest time in thorough, evidence-backed answers.
- Submitting without supporting evidence. Claiming compliance without attaching certificates, reports, or policies triggers deeper scrutiny. Attach evidence to every claim.
- Ignoring the timeline. Vendor risk assessment takes 10 to 16 weeks minimum. Founders who plan for a 2-week procurement process will miss deadlines and lose deals.
- Failing to maintain the evidence pack. An expired penetration test, an outdated data flow diagram, or filed accounts from two years ago signal that risk management is not a priority.
- Underestimating concentration risk. If the buyer has no alternative to your product, they will impose stronger contractual protections: escrow, transition assistance, extended termination notice. Prepare for these conversations.
Key takeaways
- Vendor risk and assurance runs independently of commercial evaluation. Both must pass for the deal to close.
- Six risk categories: security, data, financial, operational, regulatory, and concentration. Each requires documented evidence.
- The assessment takes 10 to 16 weeks. Plan for this in your sales timeline.
- Build the evidence pack before outreach. Proactive preparation compresses the timeline and signals maturity.
- Be transparent about gaps. Honesty with a remediation plan is more credible than deflection.
- The risk team has veto power. Engage them early, not as a final gate.
Related pages
- Evidence packs for procurement
- Why pilots fail to become production contracts
- Procurement for startups
- Procurement knowledge
- How to sell fintech products to banks
- Commercial sequencing for fintech GTM
- Evidence Pack Builder framework
- Governance and guardrails for AI in regulated markets
- Consent and risk in open banking
- Closing Foundry