What you get4 things, handed over
- Registrations that are active when the bid drops
- A bid or no-bid call with reasons
- A response written in the order it is scored
- A package that submits cleanly, a day early
How a solicitation is taken apart and put back together. Section C says what the work is, Section L says how to respond, Section M says how it is scored. Every requirement gets a row in the compliance matrix and a location in the response before a word is drafted, and the draft then runs in Section M order so a tired evaluator finds each answer where they expect to score it. The timeline underneath carries one mark that is not the deadline: submission, a day early, because portals fail at the deadline and late is a rejection rather than a low score.
How it runswin5 steps · 2 decisions
Read the whole thing
Including the evaluation criteria and the instructions, which is where the bid is actually won or lost.
Bid or no-bid, honestly
Against capability, capacity, and the incumbent. Said out loud before anyone starts writing.
DecisionWalking away is a result. Half the value here is the bid you talk yourself out of.
Compliance matrix
Every requirement mapped to where the response answers it, before drafting starts.
Draft in evaluation order
Written so a tired reviewer finds each answer where they expect it, in the order they score it.
Submit early
Portals fail at the deadline. Submitting a day ahead is free insurance.
DecisionLate is not a score, it is a rejection. There is no appeal worth having.
What this covers6 areas, and where each one bites
- Compliance matrixEvery requirement mapped to where the response answers it, built before drafting starts rather than checked after.
- Bid / no-bidAgainst capability, capacity and the incumbent, said out loud before anyone writes. Walking away is a result.
- Evaluation orderDrafted in the order it is scored, so the evaluator finds each answer in the section they are scoring.
- RegistrationsSAM, the codes, and the representations, active on the day the bid drops rather than started the week it does.
- TeamingWhere the scope needs capability this firm does not have, the honest move is a teammate named up front.
- Submit earlyA day ahead. Portals fail at the deadline, and there is no appeal worth having.
No set-aside status is claimed. The firm holds no socioeconomic certification, no clearance and no bond, and will not represent otherwise on a form.
The opinion behind it
Most small businesses lose by bidding everything. Bidding less, and better, is a strategy rather than a retreat.
What holds this workstandards we know, not certifications we hold
- FARThe acquisition regulation the solicitation is built from, and the clauses it flows down to you.Every federal bid
- SAM registrationActive registration, the representations and certifications, and the codes kept current.Before the bid
- NAICS 541519The primary code. Size standard and set-aside eligibility follow from which code a solicitation is issued under.Primary
- Sources soughtThe RFI stage, where a requirement can still be shaped and where most of the useful intelligence is.Before the RFP
Where it stopsan empty row is work this firm does not take
What that covers
- RegistrationsGet registered, stay registered, and stop losing bids to expired paperwork.
- ProposalsRead the solicitation, decide honestly whether to bid, and write the response.
- Research grantsMatch a real capability to a topic and write a Phase I that a reviewer can follow.
- TeamingBe the small technical partner on someone else’s prime contract.
Capacity
Bots watch the boards so the calendar is never the reason a bid was missed, and a model takes the first pass at a two-hundred-page solicitation overnight. The bid or no-bid call is made by a person the next morning, with reasons.
Capacity here is deliberately spent on fewer bids. Most small businesses lose by bidding everything; bidding less and better is the strategy, not a retreat from one.
How the work gets doneevery engagement, every page
Bots read the portals
SAM, the state portals and the subcontracting boards, every day, so no opportunity depends on someone remembering to look.
Models do the first pass
The reading, the mapping and the first draft of document-heavy work, where a machine is fast and tireless.
A person decides and signs
Every judgement call, every commitment and every signature is human, and the record says who.
One engineer, fixed scope
You get the person you evaluated, on a scope agreed before the work starts, and no invented follow-on.
How you can hire mescope is agreed first; price is a conversation — the scope sheet
On retainer
A senior quality lead a few days a month, holding the program and reachable when something goes sideways.
Fixed scope
A defined look at one problem, a defined amount of time, a written answer. No obligation after.
By the hour
An hour with someone who has built the thing you are asking about. Straight answers, no deck.
Start a conversationStraight answer, no deck. What it takes to start.
One standard, more than one verbwhy these are four sheets and not four firms
- NQA-1NQA-1 — Build: we write toNQA-1 — Prove: we write toNQA-1 — Automate: does not applyNQA-1 — Win: does not apply
- 10 CFR 50 App. B10 CFR 50 App. B — Build: we write to10 CFR 50 App. B — Prove: we write to10 CFR 50 App. B — Automate: does not apply10 CFR 50 App. B — Win: we write to
- ISO 9001ISO 9001 — Build: we write toISO 9001 — Prove: we write toISO 9001 — Automate: does not applyISO 9001 — Win: does not apply
- CMMC Level 2CMMC Level 2 — Build: we write toCMMC Level 2 — Prove: we write toCMMC Level 2 — Automate: does not applyCMMC Level 2 — Win: we write to
- NIST SP 800-171NIST SP 800-171 — Build: we write toNIST SP 800-171 — Prove: we write toNIST SP 800-171 — Automate: we write toNIST SP 800-171 — Win: does not apply
- WCAG 2.1 AAWCAG 2.1 AA — Build: does not applyWCAG 2.1 AA — Prove: we write toWCAG 2.1 AA — Automate: does not applyWCAG 2.1 AA — Win: we write to
- Section 508Section 508 — Build: does not applySection 508 — Prove: we write toSection 508 — Automate: does not applySection 508 — Win: we write to
- FARFAR — Build: does not applyFAR — Prove: does not applyFAR — Automate: does not applyFAR — Win: we write to
- Audit trailAudit trail — Build: we write toAudit trail — Prove: we write toAudit trail — Automate: we write toAudit trail — Win: we write to
Audit trailThe one line that crosses all four. Every practice here ends in a record of who decided what, because none of the others survive without it.