Letter Proposal
.png)
A letter proposal is a condensed scope, fee, and qualifications document, typically one to five pages, submitted when a client relationship, project scale, or procurement method makes a full proposal package unnecessary.
Where letter proposals actually appear in AEC procurement
Letter proposals are most common in three situations: repeat-client task orders under an existing master services or on-call agreement, small-scale projects where a formal RFP would cost more to respond to than the work is worth, and negotiated procurements where the client already knows who they want and needs documentation rather than competition. Federal task orders under IDIQ contracts frequently require a short technical and price response that functions exactly like a letter proposal, even when the agency doesn't use that name. In the private sector, a long-standing client relationship often means the letter proposal is less a persuasion document and more a scope-confirmation instrument, which changes what it needs to contain and how much time you should spend on it.
What a letter proposal must accomplish in limited space
The constraint is not length; it's that every element of a full proposal still needs to exist somewhere in the document. Scope of work, deliverables, schedule, fee, exclusions, and a basis-of-fee explanation all have to fit without the structure that section headers and tabs provide in a formal submission. The most common failure mode is treating a letter proposal like a cover letter with a number at the bottom: the client receives a relationship narrative but no clear project understanding, which creates scope disputes after award. Firms that win consistently on letter proposals front-load the scope definition and put the relationship context second, because the client already knows the relationship; what they need to sign off on is the work.
The strategic risk that experienced BD teams underestimate
Letter proposals feel low-stakes because they're short and often go to existing clients, but they carry a specific institutional risk: the context that makes them possible lives in people's heads, not in systems. When the seller-doer who manages the client relationship is unavailable, or when a new proposal coordinator inherits the account, the team often can't reconstruct what was promised on prior task orders, what fee basis was used, or which exclusions were negotiated. That gap produces fee compression and scope creep on the next letter proposal in the same relationship. Kantiv surfaces prior task order language, fee structures, and scope exclusions from past submissions so a team can draft a consistent, defensible letter proposal against an institutional record rather than a single person's memory.
Related terms