Imagine an account executive at a small Hyderabad software company, six weeks into a deal with a private bank’s operations team. The champion has said the words every seller wants: “We are going ahead.” Then an email lands from the bank’s information security department with a spreadsheet attached. Two hundred and forty questions. Reply in a week, please.
The executive’s first instinct is to forward it to the engineering lead with “urgent” in the subject line. That instinct is how deals die in week eight. Let us look at what is actually happening and what a prepared company does differently.
Why the questionnaire exists
The bank’s security team is not obstructing the sale. They are accountable for any vendor that touches bank data, and regulators expect banks to manage third-party risk. The Reserve Bank of India issues guidance on outsourcing and cyber security to regulated entities, and large buyers in other sectors have their own policies. The questionnaire is the paper evidence that someone checked. It also tends to arrive late because security teams are brought in after the business team has chosen a favourite, which is a process flaw but a common one.
The practical point for sellers: ask about security review at the start. A single question in discovery, “Who reviews vendors for security, and what do they need from us?”, can move weeks of delay out of the end of the deal.
What is in the 240 questions
Questions tend to cluster: access control and authentication, encryption of data in transit and at rest, where data is stored and which regions, logging and monitoring, vulnerability management and penetration testing, business continuity and disaster recovery, incident response, employee background checks, sub-processors, and data protection. Some buyers send their own form. Others use standard ones such as the Cloud Security Alliance’s CAIQ or the Shared Assessments SIG. Standard forms are easier to reuse, so offer to answer one if the buyer will accept it.
Certifications shorten the process. An ISO/IEC 27001 certificate or a SOC 2 report answers many questions at once, since the buyer can rely on an independent audit. They do not answer all, because the buyer still wants specifics about their own data, and a certificate has a scope that may not cover every product or office. Read your own scope statement before waving it around.
What the prepared company does
It keeps an answer library: approved answers to common questions, with an owner and a review date. When the 240 arrive, suppose 70% can be answered from the library, which is 168 questions, and that takes a couple of hours to paste and tweak. The remaining 72 need a human. If each takes about twenty minutes of an engineer’s or security lead’s time, that is 24 hours of effort, which is three working days for one person and a day and a half for two. Without a library, all 240 need fresh work: roughly 80 hours at the same rate, two working weeks of a senior person’s time that your product roadmap will feel.
Beyond the library, a few habits help:
- One coordinator, usually in sales operations or security, who owns the response and chases others. Not the AE.
- A public or gated trust page with policies, certificates and a data-flow diagram, which answers a good share of requests before they arrive.
- A quick scan on arrival to flag questions that need legal or product input, such as data residency, liability or audit rights.
Honesty is the whole game
The temptation, with a deadline and a signature close, is to answer “Yes” to everything. Do not. A “Yes” you cannot support becomes a contractual representation in some deals and a breach later, and a bank’s security team will often verify claims with follow-up questions or evidence requests. A truthful “Not currently; planned for Q2, interim control is X” is respected far more than an answer that collapses on the first follow-up. Buyers do not expect perfection. They expect you to know where your gaps are.
Be specific about incident handling. Indian entities are subject to directions from CERT-In requiring reporting of certain cyber incidents within six hours of noticing them, and the Digital Personal Data Protection Act, 2023 sets duties around personal data. Questions about these are common now. Your answers should reflect actual processes, confirmed by your legal or compliance people, not marketing language.
Handling the follow-ups
The first response is rarely the last. Expect a call or a second round on a handful of items. Offer a call between your security lead and theirs. It is often faster than email, and it turns the review from a paperwork exercise into a conversation between two professionals. Track open items in the mutual action plan, so the whole account team can see the review is the critical path.
If a gap is serious, such as no encryption at rest, deal with it directly: a remediation commitment with dates, or a scoped start that excludes sensitive data. Hiding it only moves the problem to after the contract is signed.
Figures and names in the examples are illustrative.
Leave a Reply