The Procurement of Trust: Why Narrative Wins Proposals That Compliance Alone Can't
- Aug 6
- 4 min read
When a donor, a federal agency, or a foundation issues a request for proposals, most organizations pour their energy into the technical side — logic models, budgets, compliance checklists. That work matters, and it's usually done well.
The narrative section — the part that explains why this organization, specifically, should be trusted with the work — often gets treated as an afterthought. It's handed off late, built from recycled language, and written to satisfy a checkbox rather than to make a case.
That's not really a communications failure. It's a sequencing problem. Technical compliance gets an organization into consideration, but it rarely gets one chosen when several finalists meet the same bar. What separates them at that point is harder to quantify: how clearly an organization can explain its own value, and how much the reader trusts what they're reading.
Here's a framework for thinking about trust as something built deliberately into communications, rather than something that happens by default when the technical work is strong.
Technical Strength Can Get Lost in the Language
Dense, jargon-heavy writing can undercut how credible a piece of work seems, even when the underlying substance is excellent. Research published in the journal Cognition found that unnecessary complexity in an explanation reduced how intelligent and credible readers judged the writer to be — independent of the quality of the idea itself.
That runs counter to a common instinct in technical teams: the assumption that precise, specialized language signals expertise. Sometimes it does the opposite. It makes a reviewer work harder to find the actual substance, and that friction quietly costs the writer.
A proposal evaluator reading dozens of submissions isn't looking to be impressed by vocabulary. They're looking for a clear, confident answer to "why you, and not the other three organizations who can also do this work." When that answer is buried in administrative language, a stronger technical program can end up reading as interchangeable with a weaker one. The narrative section deserves to be treated as an argument to be made clearly, not a formality to get through.
Communications as Infrastructure, Not Overhead
Organizations tend to categorize communications and branding as a support function — the first line item trimmed when budgets tighten. Research suggests that framing is costly. A 2025 study in Nonprofit Management and Leadership found that when nonprofits lean into commercialized messaging without sufficient transparency, public trust and donation intent measurably decline. The same research found that transparency and a strong existing reputation can soften that effect.
Separately, research on nonprofit brand equity has linked how well an audience recognizes and trusts a brand to actual giving and engagement decisions, not just awareness.
Communications and brand consistency aren't decoration sitting on top of the "real" work. They're part of how an institution earns and keeps the trust of the people funding it. A fragmented or inconsistent public-facing presence isn't just a cosmetic issue — it's a credibility signal, whether it's meant to be one or not. The point isn't "spend more on marketing." It's that narrative consistency is being evaluated, even when it's not written down as a line item.
Diagnose Before You Pitch
Demonstrating this to a prospective client or partner takes more than asserting it. Rather than leading with a portfolio of past projects, a more useful starting point is looking directly at an organization's current public presence — its website, its reports, how its leadership shows up — and walking through it together.
This isn't a universal scoring system. It's a structured way of naming specific things: where the language is harder to follow than it needs to be, where visual presentation feels inconsistent across platforms, and where leadership is largely absent from the public conversation. Instead of asking a client to trust a general reputation, this points at something specific and asks, "Does this match how you want to be seen?" That tends to be a more productive starting point than a generic pitch.
Deliverables That Can Travel Upward
The last piece is what actually gets handed over at the end of an engagement like this. A communications or positioning recommendation often has to be escalated to a director, board, or investor who wasn't part of the original conversation. A loose set of creative suggestions is hard for someone else to defend in a budget meeting.
It's worth treating deliverables the way any other internal business case would be treated: clear enough that someone who wasn't in the room can follow the reasoning, and structured enough to connect the communications recommendation to something the organization already cares about — risk, funding, or reputation.
A Question, Not a Pitch
None of this is about chasing a trend or performing authenticity for its own sake. In a competitive field where many organizations can meet the same technical bar, how an organization communicates does more work than most teams give it credit for.
The next time your organization puts together a proposal, look at how much time went into the technical sections versus the sections explaining who you are and why you're trusted. If that ratio feels off, it's probably worth an internal conversation before your next deadline — not after.
Comments