Proposal Development and the Shipley Discipline

Federal proposal development is often described as a writing exercise. It is more accurately described as a decision-making and evidence-assembly exercise that happens to end in a document. The companies that win consistently are not the ones with the best writers. They are the ones with the most disciplined process for deciding what to bid, what to say, and how to prove it.

Capture before proposal

Capture is the work done before a solicitation is released. It includes identifying the opportunity early, understanding the customer's mission need, learning who the incumbent is and how they are performing, assessing the competitive field, and — where legitimate engagement channels exist, such as requests for information, industry days, and one-on-one meetings — contributing to how the requirement is understood. See Anatomy of an RFP for how a requirement eventually becomes Sections A through M.

Capture is not lobbying and it is not access-buying. It is the ordinary, well-documented work of understanding a customer's problem before being asked to solve it in writing under a deadline. Companies that skip capture and wait for the RFP are, in effect, choosing to learn the requirement at the same time as every competitor, with less time to respond to what they learn.

The bid/no-bid decision

Not every opportunity should be pursued. A disciplined bid/no-bid decision weighs, at a minimum: whether the requirement fits the company's actual technical capability, whether the company has or can credibly present relevant past performance, whether pricing can be competitive without being unsustainable, whether the incumbent has a structural advantage that cannot be overcome, and whether the opportunity is worth the cost of pursuit relative to its probability of award.

A "no-bid" decision made early, on the basis of honest self-assessment, is not a failure. A "bid" decision made out of momentum, after capture has already revealed a weak position, is the more common and more costly mistake. Reversing course after a proposal team has been staffed is organizationally difficult, which is exactly why the decision should be made deliberately and early, and revisited at defined checkpoints as more information arrives.

Building the compliance matrix

The compliance matrix is the single most important working document in a federal proposal. It decomposes Section L (instructions to offerors) and Section M (evaluation factors) into a line item for every requirement, and maps each line item to a specific location in the proposal outline. It answers two questions for every instruction: where is this addressed, and does the language there actually respond to what was asked.

• Every "shall," "will," and "must" in the RFP becomes a traceable line.
• Page and volume limits are captured alongside content requirements, not separately.
• The matrix is a living document, checked at every review gate, not built once and filed away.

Storyboarding before drafting

Storyboarding is the practice of outlining each proposal section — its headline, its supporting points, its graphics, and its proof — before full narrative text is written. It forces the team to agree on what a section is arguing before anyone spends time wordsmithing it. Storyboards are reviewed and approved before writers proceed to full draft, which prevents the common failure mode of a technically strong section that does not actually answer the evaluation criteria it was meant to address.

The color team review sequence

Federal proposal practice, most closely associated with the Shipley method, structures review into a sequence of independent color team gates. Each gate has a distinct purpose and expects a different level of draft maturity.

• Pink team reviews storyboards or early drafts against the compliance matrix and win strategy, checking whether the outline answers the right questions before prose is polished.
• Red team reviews a substantially complete draft as an evaluator would, scoring it against the stated evaluation criteria and flagging weaknesses, deficiencies, and compliance gaps.
• Gold team reviews a near-final draft, focused on whether red team findings were actually resolved and whether the proposal reads as one coherent document rather than a set of independently written sections.
• White-glove review is the final pass before production and submission, checking formatting, page limits, cross-references, and compliance details rather than substance, which should already be settled by this point.

Each gate uses reviewers who did not author the material under review. Independence is the point: a writer cannot reliably evaluate their own section the way an unfamiliar reader, and eventually an unfamiliar evaluator, will.

Win themes and discriminators

A win theme is a short, benefit-oriented statement of why a particular approach matters to the customer's mission. A discriminator is a specific, factual difference between the offeror and its competitors that a customer would plausibly value. The distinction matters: a win theme without a discriminator behind it is an assertion, and evaluators are trained to discount unsupported assertions. See Evaluation Criteria and How Sources Are Selected for how those assertions are actually scored.

Effective win themes are stated early in a section, restated at points of emphasis, and each one is paired with a concrete proof point — a metric, a named process, a specific past result, or a verifiable fact about the company's approach. Language such as "world-class" or "industry-leading" carries no evaluative weight on its own and is generally avoided in favor of specific, checkable statements.

Proof points and past performance

A proof point is the evidence that turns a claim into a fact an evaluator can credit. It draws on relevant past performance, technical data, staffing credentials, and process documentation. Companies without an extensive federal past performance record still have proof points available to them, including commercial results, subcontract performance, and the individual qualifications of proposed staff. See Past Performance: Building It When You Have None for how a thin record is legitimately built and presented.

Production and submission

The final phase of proposal development is mechanical, and treated with the same discipline as the substantive phases. Volumes are checked against page and file-size limits, formatting requirements are verified line by line, required forms and certifications are assembled, and submission is completed with enough margin to survive a portal failure or a formatting error discovered at the last hour. Late proposals are, with narrow exceptions defined in the FAR, not considered, regardless of quality.

Monarch Space Systems' leadership has worked inside prime-level proposal organizations and brings that discipline — capture ahead of the RFP, a living compliance matrix, independent color team review, and evidence-backed win themes — to the proposals it develops. That discipline does not change based on company size; it changes in scale.