The 200-question spreadsheet: answering it without stopping engineering
- Two hundred questions is a person-week of work; treat it as retrieval, not fresh essays.
- Sort every question in one hour into pre-answered, routable, genuinely new, or not-applicable.
- One coordinator owns the document, routes questions, and performs the final consistency read.
- Negotiate scope and priority with the buyer; enterprises say yes more often than founders expect.
- Set an internal service level and hold sales to it, or heroic four-day turnarounds cost a fortnight.
The maths of the problem
Two hundred questions at fifteen minutes each is fifty working hours: more than a person-week, usually demanded inside two, usually landing on the same engineers who are shipping the product the buyer wants. Teams that treat each questionnaire as a fresh essay pay that cost every time. Teams that treat it as retrieval pay it once.
The one-hour triage
Before anyone answers anything, one person sorts every question into four buckets. Pre-answered: it matches something you have answered before, verbatim or near enough; most long questionnaires descend from the same industry templates, so on your second or third questionnaire this bucket is typically well over half. Routable: new, but clearly owned by one function; send it there with a deadline. Genuinely new: needs thought or a decision; these go to whoever owns governance, and there are usually fewer than twenty. Not applicable: answer "N/A" with one line of justification, never a bare dash, because unexplained blanks get returned as questions.
One coordinator, or the Friday spreadsheet
The failure mode has a shape: the questionnaire arrives on a Friday, four teams each answer their sixty questions out of context, the versions contradict each other, and the buyer notices. The fix is structural, not motivational. One coordinator owns the document, routes questions, holds the single live version, and performs the final consistency read. Contributors answer; they do not submit. However senior the contributors, the coordinator's read is the last word before anything leaves the building.
Negotiate the scope, professionally
Buyers expect dialogue. Two asks are routine and respected: "Which sections apply to our engagement?" (many templates are issued whole even when half the sections concern services you do not provide) and "Can we prioritise the sections gating your decision and follow with the remainder?" Enterprises say yes to both more often than founders expect, because their reviewer wants a defensible file, not a complete spreadsheet.
Agree the deadline with sales, then protect it
Sales urgency plus reviewer thoroughness is how security work stops for a fortnight. Fix a service level internally: triage within one day, routable answers within five, full return within ten, and hold sales to communicating that schedule rather than promising "by Friday" on your behalf. A predictable ten days beats a heroic four followed by two weeks of contradiction clean-up.
Key terms
- Triage
- The one-hour first pass that sorts every question into pre-answered, routable, genuinely new, or not-applicable before any writing begins.
- Answer reuse
- The practice of matching new questions to previously answered ones, because most long questionnaires descend from the same industry templates.
- Coordinator
- The single owner of the live questionnaire who routes questions, holds the master version, and performs the final consistency read.
- Scope negotiation
- The professional exchange with the buyer to confirm which sections apply and which sections gate the decision.
- Service level
- The internal turnaround commitment — triage, routable, full return — that sales must communicate rather than override.