If your biggest prospect asked for technical due diligence tomorrow, what would they discover that you should already know?
For a B2B fintech CEO, that question belongs in the sales plan. A prospective enterprise customer needs to understand what happens to its data, how your service will hold up when something fails, and whether your team can support the arrangement you're proposing.
You don't need to answer every technical question yourself. You do need to know which answers your team can support today, which need clarification from the buyer, and which depend on engineering work you haven't planned yet.
The questions below are a starting point for that conversation. Requirements vary with the buyer, the service and the data involved. Ask for the buyer's assessment process early, including who reviews it and which conditions must be met before a contract or go-live. These examples help you prepare; they aren't a universal approval checklist.
Start with the familiar requests
Prepare a current architecture diagram showing the proposed service and its dependencies. Alongside it, map where customer data enters the system, where it is stored and processed, and where copies can appear in backups, logs or support tools. A diagram is more useful when your team can explain how it relates to the product the buyer will use.
Expect to discuss access: who can reach production systems and customer data, how access is approved, and how it is removed when someone changes role or leaves. Include privileged access and the records available for investigating its use. The NCSC cloud security principles give a useful structure for preparing these answers, covering identity, administration, audit information and supply chains.
Security policies, penetration test reports and assurance documents may form part of the review too. If a buyer asks for a SOC 2 report or ISO 27001 certificate, establish the scope they expect and whether what you hold covers the service under discussion. Be clear about what you have today. Planned certification is a different answer from a completed assessment.
Before sharing reports, agree the recipient and an appropriate confidential channel. Give the buyer enough evidence to assess the service without sending credentials, customer records or unrestricted access to internal systems.
Follow the report through to the work
A penetration test report can open a second conversation about its findings. The Hong Kong Government CERT penetration testing guide describes remediation and retesting as follow-up work. Prepare a record of unresolved issues, who owns them, the intended remediation and what has been retested. Explain the scope and date of the assessment so the buyer can understand what it does and doesn't cover.
Apply the same scrutiny to recovery. A backup configuration tells you how data is copied. A recovery test gives you evidence about restoring the service. Ask your technical lead to show the most recent result, including the recovery time, the data recovered and the checks used to confirm that the application worked afterwards.
Two terms help make this discussion precise. The recovery time objective is the target time for restoring service. The recovery point objective identifies how far back in time the data must be recovered, which defines the tolerable period of data loss. Compare your targets with measured test results and with the commitment you are proposing to the customer. NIST's contingency planning guide explains recovery objectives and the role of testing, training and exercises.
For example, a database restore might succeed while an integration the customer relies on remains unavailable. Record what the test covered and where it stopped. The CEO's decision is whether further work is needed before agreeing the customer's delivery date or recovery expectations.
Prepare for questions beyond the questionnaire
Some questions are less obvious when you first assemble an evidence folder. They require your team to explain how the business would operate under pressure. A buyer may ask them directly, or they may emerge from a follow-up discussion.
Could someone else recover the service?
A recovery procedure should be usable by someone other than the engineer who wrote it. Check whether the deputy has the approved access, training and authority needed to act. If the procedure ends with a call to a person who is unavailable, record that dependency.
Start with a discussion exercise. Have the deputy walk through an example incident while the usual expert listens. Arrange any hands-on recovery test separately in a suitable environment with the normal approvals. Our holiday-cover guide includes a record you can use for this handover.
What prevents one customer accessing another's records?
For a service shared by multiple customers, ask your team to explain where customer separation is enforced and how it is tested. Include access through APIs, background jobs and support functions where those exist in your product. A successful login proves who the user is; the application also needs to check which customer's information they are allowed to use.
You should be able to describe the design in plain language and point the reviewer to suitable assurance evidence. NCSC's cloud principles include separation between customers as a distinct area for assessment.
Which other companies can reach the data?
Look beyond the main cloud provider. Your service may also depend on support software, analytics, monitoring, external engineers or other suppliers. Establish what each receives or can access, what it does with that information and how changes are reviewed.
For the CEO, this is also a purchasing question. Introducing another tool can change the answer you give a customer about where its information goes. Keep the supplier record connected to the service's data map so those answers remain consistent.
What happens when the customer leaves?
Prepare to explain how the customer gets its data back, in what format and with what assistance. Identify what remains in logs and backups, how long it is retained, and how deletion is handled. Avoid promising immediate removal from every copy unless the team can demonstrate that behaviour and it matches the agreed retention requirements.
An exit discussion may also cover continuity if your business or a critical supplier can no longer provide the service. The FCA's guidance on outsourcing to cloud and other IT providers includes exit planning and the ability to transfer services. That guidance applies to certain FCA-regulated firms and has explicit exclusions, including banks and payment institutions covered by other guidance. Use it as context for exit questions; the buyer's applicable obligations and contract need their own review.
Turn the answers into a plan for one live deal
Choose an actual opportunity and sit down with your sales and technical leads. Use the buyer's stated requirements first. Where those are still unknown, write down the question to take back to the buyer rather than treating an assumption as a requirement.
For each item, record:
- The buyer's question and the part of the proposed service it concerns.
- The answer you can support now, with a link to dated evidence and its scope.
- Any missing evidence, engineering work or clarification needed.
- A named owner, an effort estimate and the decision required from you.
A hypothetical recovery entry might read: "Database restore tested; application recovery and the customer integration were outside the test. Technical lead to scope a full service exercise before we agree a recovery commitment." That gives you a specific planning decision. "We have backups" leaves the work hidden.
Separate gathering an existing report from producing evidence for the first time. Finding a report may be a short administrative task. Running a recovery exercise or fixing an access-control gap needs engineering time, and the result may change what you can promise. Agree priorities with the team and take any remaining acceptance questions back to the buyer.
This is the preparation behind the B2B fintech due diligence approach we're taking at StationOps: work through the proposed customer arrangement, identify what the evidence supports, and establish the engineering work needed to address gaps. The buyer makes its own acceptance decision.
Before your next delivery commitment, ask your technical lead to walk you through the weakest supported answer for that deal. Decide who will resolve it and where the work fits in the plan.
