The Evidence Hierarchy — Case Studies, Data, and Proof in the Right Order

Proof is not a section of the proposal. It is a layer that runs through the entire document — and the order in which you present different kinds of proof determines how credible the proposal feels. Present the wrong kind of proof in the wrong order and you create skepticism where you intended confidence. The evidence hierarchy is the sequencing principle that governs this: not all proof is equally persuasive, and the most persuasive proof is presented last, not first.

The hierarchy works from most familiar to most compelling. Generic social proof (we have worked with hundreds of clients) is the least persuasive and should appear last if at all. Industry-relevant case studies are more persuasive. Named references from clients in comparable situations are more persuasive still. Specific, quantified outcomes with client attribution are the most persuasive, and they should appear at the moment the reader is closest to their decision.

1. Level 1: Quantified Claims Numbers are more persuasive than adjectives. "We improved sales conversion by 34%" is more credible than "we significantly improved sales performance." Use specific numbers, even approximate ones, whenever you have them. Round numbers signal estimation; odd numbers signal measurement. "About 30%" is a guess. "31.4%" is a finding. If you have data, use the data. If you do not have data, do not invent precision — but note that absence of data is a signal to go gather it before the proposal.
2. Level 2: Industry-Relevant Case Studies A case study from a client in the reader's industry is worth ten generic capability statements. Write case studies in the structure: client situation, specific problem, what you did, measurable outcome. Keep each case study to one paragraph — the reader needs enough to evaluate relevance, not enough to evaluate methodology. If you have a case study from a client in the reader's exact segment, that case study belongs in the problem statement section, not buried in an appendix.
3. Level 3: Named References A specific named reference — a client the reader could call — is the highest-value proof element in most proposals. Most writers relegate references to a line at the bottom of the proposal ("references available upon request"). This is a mistake. Name the reference, their role, and what they would speak to. "[Client Name], VP of Operations at [Company], who oversaw our engagement in 2025 and can speak to the implementation timeline and adoption results." That is proof the reader can verify. Verification is credibility.
4. Level 4: Strategic Placement Do not aggregate all proof in a single section. Place proof near the claim it supports. When you describe the solution approach, include the case study that demonstrates it works. When you state a timeline, include the reference who can confirm your delivery track record. Proof adjacent to the claim it supports is more persuasive than proof isolated in a separate section. The reader should not have to flip to an appendix to find the evidence — find it for them.

One category of proof deserves its own note: the testimonial. Testimonials are the least credible form of proposal proof and the most overused. The reader knows testimonials are curated. They know you did not include the client who was dissatisfied. A testimonial that says "QUILL delivered exceptional results" tells the reader nothing about what those results were or whether they are relevant to the reader's situation. Replace every testimonial with a case study or a named reference. The case study has specificity. The reference has verifiability. The testimonial has neither.