Contract Teardown: How We Scored a $300K Set-Aside RFP
August 6, 2026 · 5 min read
The most useful way to learn government proposal strategy is to watch one solicitation from release to award. This is a teardown of a realistic $300K 8(a) competitive set-aside for administrative and IT support services — the kind of opportunity a certified small business can actually win. The agency, solicitation number, and dates are representative, but the structure mirrors real RFPs we've analyzed, and the lessons carry across agencies.
The opportunity at a glance
- Agency: a civilian agency's regional office (GSA-style procurement)
- NAICS: 541611, Administrative Management and General Management Consulting Services (size standard: $24.5 million)
- Set-aside: 8(a) competitive
- Period of performance: one base year plus two option years
- Estimated value: $300,000
- Evaluation approach: best-value tradeoff, with technical factors weighted above price
- Offers received: 14 — fewer than the agency expected for an 8(a) set-aside, a common pattern when established primes pass on smaller awards
How Section M broke down
Section M is where the government tells you how it will score your proposal. Skipping it is the single most common amateur mistake — teams write what they think the agency wants instead of what the evaluation criteria actually reward. In this RFP the evaluation was:
- Technical approach — 45 points. The agency wanted a project plan tied to the statement of work, a staffing plan, a transition plan, and a quality control approach. Each element mapped to a named requirement in Section L; you lost points for answering a "shall" with a paragraph of marketing.
- Past performance — 30 points. Relevance and quality of up to three prior contracts. The agency explicitly stated that more relevant work beats more impressive-sounding work, and that performance confidence was based on the relevancy of the references — not the size of your company.
- Price — 25 points. Evaluated for reasonableness and realism, not just low cost. An unrealistically low price raised a realism concern rather than earning a reward.
- Small business participation — pass/fail. A small business participation section had to be included even though the set-aside already made the prime small; omitting it made the proposal unacceptable.
The FAR clauses that actually mattered
Beyond Section M, three clauses drove the outcome:
- FAR 52.219-14, Limitations on Subcontracting — required at least 50% of the cost of contract performance incurred for personnel to be performed by the 8(a) firm's own employees. Proposals that quietly leaned on subcontractors for most of the labor failed the self-performance check.
- FAR 52.212-2, Evaluation — Commercial Items — the clause that operationalized Section M's scoring for a commercial-item buy. It made the evaluation factors, and their weights, binding contract language.
- FAR 52.212-4 and 52.212-5 — the commercial contract terms and incorporated clauses. Most teams skimmed these, but they defined invoicing, termination, and compliance obligations that a winning team had to price for.
What a winning response looked like
The winning team's proposal was not the longest. It was the most scorable:
- The technical approach restated each Section L requirement and answered it in order, so an evaluator could find and score every element in minutes.
- The past performance section led with two directly relevant contracts — same agency type, same service — with measurable outcomes, named points of contact, and a short narrative connecting each reference to this specific scope.
- The price volume matched the technical volume: same staffing plan, same hours, same assumptions. The government could reconcile the two without a single unexplained number.
- A compliance matrix showed every "shall," every attachment, and exactly where each was addressed.
What a losing response looked like
The losing teams lost in recognizable ways. One proposed an ambitious portal build when the statement of work asked for routine support — scope creep that no evaluator rewarded. Another submitted strong past performance but wrote the technical approach as a capabilities statement with no plan, no timeline, and no named roles. A third forgot the small business participation section entirely and was deemed unacceptable before scoring began. None of these were bad companies. Each was a good company that answered a different RFP than the one in front of them.
The lesson: score the RFP before you write
Every hour spent mapping Section M before drafting saves a day of rework. That's exactly the discipline Contrax's proposal evaluator bakes in: it reads your draft against the solicitation's Section M criteria, checks compliance against the relevant FAR and DFARS clauses, flags weak arguments, and shows where you're leaving points on the table — before you hit submit, not after the debrief tells you why you lost.
A $300K contract is life-changing revenue for a small firm, and it's decided by a handful of evaluators scoring a rubric for a few hours. The team that wins is the team that makes the rubric easy to score. That's a game you can win with process.