Proposal Writing for Small Primes: 10 Rules, 1 Framework

A federal proposal isn't creative writing. It's a compliance document graded against a rubric you mostly have to reverse-engineer from the solicitation. Small primes usually lose not because the solution is wrong, but because they were graded against criteria they never spotted.

This is the framework we use at Americurial — ten rules, one process. Works the same whether you've got a forty-person proposal team or you're a solo veteran writing your first one over a weekend.

The framework — 1 map, 10 rules

Every federal proposal follows this flow:

Read the solicitation three times. Once for fit, once for scoring, once for traps.
Build the compliance matrix. Every requirement mapped to a response section.
Write to the evaluation criteria, not the SOW. Compliance gets you in; evaluation criteria decide the winner.
Draft win themes before you write. 2-4 messages that thread every section.
Use the buyer's language.If the SOW says “program management,” you don't write “project management.”
Lead with proof. Past performance, metrics, named clients — before the abstract pitch.
Make everything measurable. Numbers beat adjectives every time.
Price-to-win is research, not guesswork. Pull past awards, calculate, strategize.
Color team review.Pink → Red → Gold, even if “team” is you + a friend.
Brutal final edit pass. Read aloud. Cut 20%. Submit early.

How the framework stacks

Rules 1-3 are compliance. Rules 4-7 are competitiveness. Rule 8 is pricing. Rules 9-10 are quality control. Skipping any of the four layers is why most small primes lose.

Rules 1-3 — Read, re-read, compliance matrix

Rule 1 — Read the solicitation three times

First pass: is this worth bidding? Check fit, set-aside eligibility, size standard. Second pass: highlight every “shall,” “must,” and evaluation criterion. Third pass: hunt for contradictions and traps — double-requirements, hidden page limits, an evaluation rubric in Section M that doesn't match the instructions in Section L. Those happen more often than you'd think.

Rule 2 — Build a compliance matrix

A spreadsheet, one row per requirement. Columns: requirement text, section reference, where you address it in your response, status (draft / final / reviewed), owner. Boring. Essential. This is the document your color-team reviewers will hand back to you.

One missed “shall” and you're out

Contracting officers routinely disqualify proposals that miss a single mandatory “shall” clause. The compliance matrix isn't bureaucracy. It's the only reliable way to avoid automatic rejection on something stupid.

Rule 3 — Write to the evaluation criteria, not the SOW

Section M (evaluation factors) outranks Section C (scope of work) for proposal purposes. The SOW tells you what the work is. Section M tells you how you'll be graded. Organise your response around the evaluation criteria, with the SOW requirements tucked inside each one. It's an obvious move that small primes still miss constantly.

Rules 4-5 — Win Themes & Language

Rule 4 — Draft win themes before you write

A win theme is a repeatable message that threads your proposal. 2-4 of them, total. Each should answer: “why us, for this requirement, over every other bidder.”

Good win themes are specific and proof-backed:

“Proven performance in this exact agency — 3 consecutive CPARS 'exceptional' ratings”
“100% W-2 workforce — no 1099 subcontractor risk”
“Veteran-led operations discipline — our PM is a former Army infantry officer with 2 deployments”

Bad win themes are generic:

“Superior customer service”
“Innovative solutions”
“Commitment to quality”

Rule 5 — Use the buyer's language

Read the agency's website, prior solicitations, and leadership speeches. They have preferred terminology. Use it. If they say “warfighter support,” you don't write “end-user assistance.”

Rules 6-7 — Proof and metrics

Rule 6 — Lead every section with proof

Federal evaluators are trained to find substantiation, and they'll discount any claim that doesn't have it. Every claim should land with one of these attached:

A past performance citation with the contract number
A quantified result (not “improved” but “reduced cycle time 38%”)
A named client or reference
A cert, clearance, or credential

Rule 7 — Make everything measurable

Replace every adjective with a number. “Fast response” becomes “<2 hour dispatch.” “Experienced team” becomes “average 12 years federal experience per staff member.”

The measurability test

After drafting each section, highlight every adjective. For each highlighted word, ask: “compared to what?” If you can't answer, replace with a number.

Rule 8 — Price-to-Win (PTW)

Price is where most small primes either leave money on the table or price themselves right out of the running. A serious PTW analysis is short and unsexy:

Pull all past awards for this agency in this NAICS (USASpending.gov)
Calculate the distribution: 25th / 50th / 75th / 90th percentile
Look at the incumbent's prior contract value + any modifications
Back into the likely budget — agencies price ceilings matter
Position strategically: cheap (below 50th), mid (50th-75th), premium (75th+)
Document your rationale — color team will ask

Small primes usually want to land in the 50th–75th percentile. Competitive without signalling cheap. Below the 40th gets flagged by evaluators for realism — they start wondering what corners you're cutting.

Rule 9 — Color team reviews

Colour reviews are structured internal reads at specific maturity stages. They're boring and they're what wins proposals.

Pink Team (around 40% complete)

Concept-level read. Does the compliance matrix look complete? Are the win themes coherent? Is the approach pointed in the right direction? Cheap to fix things here; expensive later.

Red Team (around 80% complete)

Full proposal read. Every reviewer reads cold, as if they're the evaluator and haven't seen this before. Score against the rubric. Surface compliance gaps, weak sections, claims that don't hold up.

Gold Team (around 95% complete)

Final executive read. Focus narrows to the executive summary, win themes, price position, and top-level risks. Sign-off for submission.

Small-shop color teams

You don't need a committee for this. Solo shop? Hire an experienced proposal consultant for two to four hours per colour team. That's enough to catch around 80% of the issues without a five-figure review budget.

Rule 10 — The Brutal Final Edit

48 hours before submission:

Read the entire proposal aloud. Every section. It forces you to hear awkwardness.
Cut 20% of the words. Any proposal can be compressed 20% without losing content.
Check page limits, font sizes, margins — exactly the spec.
Verify every table of contents, cross-reference, and exhibit label.
Run compliance matrix one more time. Every row green.
Submit 24 hours early if the portal allows. Late submission = disqualified.

Veteran-specific edge

In your executive summary, land the veteran angle with one specific line — not “as a veteran-owned firm.” Be concrete: “Founded by a Navy Boarding Team operator, 2 Atalanta tours — bringing that operational discipline to your facility O&M.”

Want us to write it?

Our Single Proposal Writing engagement handles a full 30-page proposal: compliance matrix, win-theme workshop, writing, graphics, color team reviews. $4,500 standard, $3,600 for verified veterans.

Why this gets easier the more you do it

Federal proposal writing is an applied skill, not a creative one. The rules are knowable. Every proposal you write well makes the next one faster — win themes, templates, and price-to-win work carries forward.

The gap between small primes that win and small primes that don't is almost never solution quality. It's compliance discipline, proof density, and a realistic price position. Applied consistently, every time.