Partnership to Proposal Team Guide | Issue 5 of 8
Who's This For
You're deep into proposal season. The project description is coming together. The budget is taking shape. Now you need letters of support from your partners.
You have done this before. You draft a template. You send it to partners with a note: "Feel free to modify as needed." They sign it mostly unchanged. The letter goes into the proposal. Reviewers see a generic statement of enthusiasm. The letter adds nothing to your competitive position.
This issue is for anyone who wants letters that actually demonstrate partnership. Not polite endorsements. Not pro forma signatures. Letters that show reviewers your partners understand the project, have shaped its design, and are genuinely committed to making it work.
The Partnership Moment
Your proposal is due in two weeks. You have three partners, each playing a distinct role in the project. Time to collect letters of support.
You write a template letter. It describes the project, lists your organization's commitment, and closes with enthusiasm about the collaboration. You send it to all three partners with instructions: "Personalize as you see fit, put it on letterhead, and send it back signed."
Two partners return the letter within a day. Barely changed. They signed your words.
The third partner takes longer. When their letter arrives, it looks different. They rewrote the organization description in their own voice. They added specific commitments you hadn't thought to include. They connected your project to their strategic priorities in ways you didn't know. Their letter reads like a partner who understands what they're signing up for.
The proposal goes out. Two letters add nothing. One letter demonstrates genuine partnership.
Reviewers notice the difference.
Under the Surface
Letters of support have a specific job in proposal review. They answer three questions reviewers are asking:
Does this partner understand what they are committing to?
Can they actually deliver on these commitments?
Is this a real partnership or just a name on paper?
Generic letters fail all three tests. When a letter could apply to any project, reviewers assume the partner doesn't understand this project. When commitments are vague ("we will collaborate as needed"), reviewers assume no real planning has happened. When the language sounds like the PI wrote it, reviewers assume the partner just signed whatever was sent.
Strong letters require more than a better template. They require a different process. The letter should reflect actual conversations about what the partner will do, why they care about this project, and what capacity they bring. When you draft words for partners to sign, you're doing paperwork. When partners draft words that reflect their genuine commitment, you're documenting partnership.
