Building an answer library vs buying a tool
- A library is canonical answers with owners, evidence, and a last-true date — not a folder of past questionnaires.
- Manual libraries decay invisibly as the product changes and owners move on.
- A disciplined spreadsheet plus a quarterly review is enough for a handful of questionnaires a year.
- Buy when volume, live-evidence citation, or multiple frameworks make manual truth-keeping the bottleneck.
- No tool fixes an ungoverned company; governance first, library second, tooling when volume justifies it.
What an answer library actually is
Not a folder of past questionnaires. A library is a set of canonical answers, each with the evidence behind it, the owner who vouches for it, and the date it was last true. The questionnaires are outputs; the library is the source. Teams that keep the outputs and skip the source rebuild their answers from memory every quarter and drift a little further from the facts each time.
Where the do-it-yourself version breaks
The honest pattern, reported consistently by teams who have run one: the spreadsheet library works for the first months because one person owns it and the product is fresh in their head. Then the product changes and the answers do not. Then copies proliferate, one per deal, each edited separately, and nobody knows which is current. Then the owner changes role, and the linkage between each answer and its evidence, which lived in their head, leaves with them. The library still exists; its truth does not. The failure is not effort. It is that manual linkage between answers, evidence, and a changing product decays by nature, and the decay is invisible until a reviewer checks.
The honest build case
If you face a handful of questionnaires a year, a disciplined spreadsheet plus a quarterly review ritual is genuinely enough: canonical answers in one sheet, an evidence link and owner per row, a recurring calendar entry to re-verify, and a rule that deal copies are exports, never editable forks. Budget two to four hours a week of someone's time to keep it true, and accept that this budget is the product; skip it and you own a museum.
The honest buy case
Buy when any of these is true: questionnaires arrive monthly or faster; answers must cite live evidence rather than last quarter's documents; you answer across several frameworks and the same fact must stay consistent in each; or the person who maintained truth has left twice. What a tool buys you is not the writing, it is the linkage: answers wired to the controls and records behind them, so that when the product changes, the stale answers surface themselves instead of waiting for a reviewer to find them.
What no tool fixes
A tool cannot govern an ungoverned company. If nothing is inventoried, nothing owned, and nothing evidenced, a tool will generate confident answers to questions your organisation cannot truthfully answer, which is the worst outcome available. Order of operations: minimum viable governance first, library second, tooling when the volume justifies it.
Key terms
- Answer library
- The canonical set of answers, evidence, owners, and last-true dates that questionnaires are exported from — not a folder of past submissions.
- Canonical answer
- The single approved version of an answer to a recurring question, versioned once and reused rather than rewritten per deal.
- Evidence linkage
- The connection between an answer and the control, log, or policy that makes it true; the first thing to decay in a manual library.
- Staleness
- The invisible drift between what an answer says and what the product actually does, revealed only when a reviewer checks.
- Build vs buy
- The choice, driven by volume and evidence needs, between a disciplined spreadsheet and a tool that maintains linkage automatically.