A federal proposal isn't creative writing. It's a compliance document that has to match a scoring rubric you mostly have to reverse-engineer. Most small primes lose proposals not because their solution is wrong but because they're graded on criteria they didn't understand.
This is the framework we use at Americurial. 10 rules, one integrated process. It works for a 40-person team and it works for a solo veteran running their first solicitation.
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 — Read, Re-read, Compliance Matrix
Rule 1 — Read the solicitation 3 times
First read: is this worth bidding? Check fit, set-aside eligibility, size standard. Second read: pull out every “shall,” “must,” and evaluation criterion. Third read: look for contradictions and traps (double-requirements, hidden page limits, evaluation rubrics that don't match Section L).
Rule 2 — Build a compliance matrix
A spreadsheet with one row per requirement. Columns: requirement text, section reference, where it's addressed in your response, status (draft/final/reviewed), owner. This is the document you hand to your color-team reviewers.
Missing requirement = disqualified
Rule 3 — Write to evaluation criteria, not the SOW
Section M (evaluation factors) is more important than Section C (scope of work). The SOW tells you what to do; Section M tells you how you'll be judged. Organize your response around evaluation criteria, with SOW requirements nested inside.
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 & Metrics
Rule 6 — Lead every section with proof
Federal evaluators are trained to look for substantiation. Every claim needs:
- 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
Rule 8 — Price-to-Win (PTW)
Price is where most small primes either leave money on the table or price themselves out. A serious PTW analysis includes:
- 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
For small primes, positioning in the 50th-75th percentile is usually ideal: competitive without signaling low-quality. Below 40th is a red flag for realism to evaluators.
Rule 9 — Color Team Reviews
Color reviews are structured internal reviews at specific maturity stages:
Pink Team (40% complete)
Concept review. Does the compliance matrix look complete? Are win themes coherent? Is the approach directionally right?
Red Team (80% complete)
Full proposal review. Every reviewer reads cold, as if they're an evaluator. Score against the rubric. Find compliance gaps, weak sections, unclear claims.
Gold Team (95% complete)
Final executive review. Focused on executive summary, win themes, price, and top-level risks. Approves for submission.
Small-shop color teams
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
Want us to write it?
The bottom line
Federal proposal writing is an applied skill, not a creative one. The rules are knowable. The framework compounds: every proposal you write well makes the next one faster because your win themes, templates, and price-to-win analyses carry forward.
The difference 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 across every submission.