The pattern nobody could explain
A payments technology company had been pitching to regional banks for two years.
Their product was strong. Their pricing was competitive. Their references were good — three mid-size banks in two countries already using the platform successfully. By any reasonable measure, they should have been converting at a higher rate than they were.
But pitches kept dying at the final presentation stage. Not in early discovery. Not in technical evaluation. After months of work, after getting through procurement screening and IT security review and legal sign-off — the deal would go quiet. A polite email. A vague reference to "internal priorities." A door left open that never reopened.
Seven pitches in eighteen months. Three converted. Four went quiet in the final week.
The head of sales had a different theory after each loss. Timing. Budget cycle. An internal candidate. None of them felt like the complete story.
The document all four of them read
Pitching a payments platform to a regional bank means navigating a buying committee with at least four distinct stakeholders: the Head of Digital or Innovation (who championed the project internally), the CTO (who owned the technical decision), the CFO (who signed off on the budget), and the Chief Risk Officer (who could veto anything they weren't comfortable with).
Each of them had different pre-read materials. Each of them had different evaluation criteria. But all four of them read the executive summary — the 180 words at the top of the proposal document that framed what the product was, why it mattered, and what the bank would get from it.
That executive summary had been written once, reviewed internally by the sales team and the CEO, and used — with minor tweaks — for every pitch.
Nobody had ever tested it against the four people who would read it.
A consultant working with the team suggested running it through RetoraLab against cohorts representing each of the four committee roles. The test took nine minutes.
What the nine minutes found
Half of the CTO cohort read this as a genuine technical commitment. The other half read it as marketing language — the kind of claim every vendor makes and that never survives first contact with the actual infrastructure team. For this sub-group, "seamless integration" was a red flag, not a selling point. It signalled that the vendor either didn't understand the complexity of the integration or was deliberately understating it.
The fault line was between CTOs who valued confidence claims and CTOs who valued technical honesty. The phrase was trying to appeal to the first group and actively alienating the second.
For the CRO, the document was essentially asking them to keep reading in order to find the information they needed before they could decide whether to keep reading. Half of this cohort in the test disengaged before the end of the summary. They didn't reject the pitch. They just stopped being present to it.
What changed in 180 words
The executive summary was restructured around four distinct entry points — one for each committee member's primary concern — without making the document feel like a list.
The opening paragraph addressed the CRO directly: regulatory compliance, data residency, and audit capability named explicitly in the first three sentences. Not because the CRO was the most important reader, but because they were the reader most likely to disengage first.
The second paragraph gave the CTO a different kind of confidence claim: not "seamless integration" but a specific description of the integration methodology, a realistic timeline, and a reference to a comparable infrastructure migration completed for an existing client. Honest, specific, checkable.
The third paragraph addressed the CFO's question before they had to ask it: implementation cost range, licensing model, and a reference to the ROI timeline documented in the case study appendix.
The final paragraph gave the Head of Digital the language they needed for internal advocacy — not a product description, but a framing of what the project would mean for the bank's competitive positioning in the next three years.
Four paragraphs. Four readers. One document that each of them could find themselves in.
180 words, restructured.
The next two pitches
The next pitch converted in the final presentation meeting. The CRO, who had been the quiet presence in previous final meetings, asked specific follow-up questions about the integration methodology — questions that indicated they had read the document closely rather than skimmed it for reasons to object.
The pitch after that converted within a week of submission. The Head of Digital reported that the internal sign-off process had moved faster than any previous technology procurement decision they could remember. Their CEO and CFO had read the executive summary and "got it immediately."
Two pitches. Two conversions. The product hadn't changed. The references hadn't changed. The pricing hadn't changed.
The 180 words had.
What was actually happening in the four losses
The post-mortem on the four deals that went quiet was never definitive. Timing probably was a factor in some of them. Internal politics probably was a factor in others.
But the cohort test made one thing clear: the executive summary that went into those four pitches was written for a single reader. A composite, imaginary reader who cared equally about product capability, technical integration, cost, and compliance. A reader who didn't exist on any of the actual buying committees.
The CRO was reading a document that addressed their concerns last, briefly, and in passing.
The CFO was reading a document that never answered the question they needed answered.
The CTO was reading a phrase that half of their cohort was trained to distrust.
None of them rejected the pitch. They just weren't given a reason to champion it.
That's a different problem from timing. It's a problem 180 words can fix.
