Blog · Pillar
RFP Mechanics.
66 posts in this archive.
The Monday bid-board review, a year on
A year of running the same Monday ritual. Three changes we made to the review itself after 52 weeks — and one we wish we'd made sooner.
The federal task-order RFP wave of 2026
IDIQ task-order patterns from the first half of 2026. How response windows, page caps, and evaluation schemes have shifted — and how teams are staffing against them.
Section 2: the technical approach without jargon buildup
Why almost every technical approach section opens with the wrong sentence, what the right opening looks like, and a rewritten example from a real bid. The jargon buildup that kills evaluator attention in the first paragraph.
The Saturday scope-creep kill list
A 10-minute Saturday drill. Four questions that retire a pursuit before it eats another sprint — so Monday's bid board reflects what your team can actually win.
The compliance matrix revisited, one year in
What we wrote about compliance matrices in May 2025, what we've learned since, and the five corrections that change the recommendation. A one-year retrospective on a foundational RFP-mechanics piece.
The draft review heatmap: which sections attract edits
A year of reviewer edit data across hundreds of drafts. Which sections attract the most edits in pink, red, and gold review — and what that pattern tells us about where craft weaknesses cluster.
Executive summaries: the shortest high-leverage document in B2B sales
The canonical pillar on executive summaries. Why one page decides whether the proposal gets read, the five parts of a strong exec summary, two before-and-after rewrites, who signs off.
Federal FY Q2 RFP surge playbook
What federal-facing proposal teams should have ready by April 1 to handle the fiscal-Q2 volume surge — pre-approved content, capture-lead calendars, bid/no-bid discipline, and what breaks under load.
The Q2 FY kickoff Monday-morning triage
Eight federal RFPs dropped into the queue over the first weekend of Q2 FY. The 25-minute drill that sorts them into respond-today, respond-this-week, and wait-for-the-amendment.
Mapping every response paragraph to the scoring rubric
The discipline that turns a 60-page response into an evaluator's checklist. Why every paragraph needs a rubric citation, and how to make the mapping visible without cluttering the document.
The Saturday review of outgoing pursuits
A 15-minute Saturday ritual for reviewing the week's outgoing proposal pursuits. Three questions, applied in order: what to kill, what to push, what to staff up. The cheapest pipeline discipline we run.
The defense RFP cycle: March patterns
A teardown of DoD small-business contracting patterns in March across the last three fiscal years. Where the peaks are, what triggers them, and what the shape of March 2026 suggests about FY Q2 volume.
The federal March pipeline looks like this
A short field note on what our own federal-opportunity stream surfaced this week. Three clusters, one surprise, and what it tells us about the FY Q2 surge.
Section 1: the executive summary nuances most teams miss
The executive summary is the section most teams write last, worst, and most generically. When you write it depends on the RFP's shape. Three shapes, three rules, and the nuances nobody tells you.
Federal FY Q2 prep weekend
A two-hour weekend checklist for a team about to enter the March federal spike. What to reconfirm, what to clear off the plate, what to tell your SMEs.
A cross-cut of 30 municipal RFPs
Patterns in sub-state procurement across 30 municipal RFPs posted in Q4 2025. Where buyer-side guidance is catching up to federal norms, where it's still behind, and what the data says for a vendor deciding whether to chase this tier.
The Saturday compliance-matrix catch-up
A 45-minute Saturday routine for a shop that missed the Thursday compliance check-in. Five passes over the matrix, with a stop rule at the first unanswerable row.
The RFP kickoff, the 30-minute version
For small teams where a 90-minute Shipley kickoff is a non-starter. The trimmed agenda, what gets kept, what gets pushed to async, and the one artifact the kickoff still has to produce.
RFIs and RFPs are distinct work
Why treating an RFI like an early draft of an RFP response loses the relationship. RFIs are informational for the buyer, not a preview of evaluation. Respond to them as such.
Healthcare RFP trends for 2026, early read
Seven clauses that were not in 2025 healthcare RFPs and are now showing up repeatedly in the Q4 2025 sample. What they tell us about buyer priorities for the year ahead, with sourcing where it is public.
The annual proposal-team retro template
The questions we ask at year-end and the format that surfaces what monthly retros miss. A 90-minute meeting that produces a durable artifact instead of a slide deck that gets archived and forgotten.
The week between Christmas and New Year, for proposal teams
The slowest week of the year has a use. Five low-overhead rituals that cost an afternoon each, capture the year's learning, and set up the team for a clean January. What to do when nothing is landing.
Anatomy of an enterprise SaaS RFP, 2025 edition
An annotated teardown of a representative enterprise SaaS procurement. Data-residency, AI-usage clauses, three recurring red flags, and where the 2025 version has diverged from the 2024 template.
Proposal post-mortems: the discipline, the template, the follow-through
The canonical long-read on proposal post-mortems. What a post-mortem actually accomplishes, the template that makes the discipline sustainable, how to get a debrief from the buyer, and the three follow-through patterns that work.
An anonymized winning proposal, torn down
A public-sector award with public artifacts. What won, what the scoring rubric rewarded, and three things a typical proposal team would have gotten wrong.
The proposal post-mortem template: preview
A Wednesday teaser for next week's pillar. The fields that matter in a post-mortem template, and the one section most teams skip.
Past-performance library hygiene for year-end
Three questions that decide whether a past-performance entry stays in the library, gets rewritten, or gets retired. A December sweep that pays off in the Q1 pursuit wave.
Color-team review: the full playbook
The operational companion to our color-team essay. Step-by-step procedures for pink, red, gold, and white teams — when to run each, who attends, the rubrics they apply, and the templates that make the discipline portable.
The five compliance-matrix mistakes that lose bids
Real patterns from real debriefs. The matrix mistakes that surface as scoring penalties on the buyer side, and the discipline that prevents each one. Citations to VisibleThread on the most common cause.
The federal Q1 push: triaging three RFPs at once
The 90-minute drill we use when three federal solicitations drop in the same day. Three buckets, four questions per bid, one written decision. The thing you cannot afford to do on a Friday afternoon in October.
Anatomy of a multi-award IDIQ solicitation
Reading a federal multi-award IDIQ end-to-end. Task orders, ceiling prices, evaluation factors, and three red flags to catch before bid/no-bid. Annotated walk-through of a recent civilian-agency vehicle.
Compliance-matrix tooling, a quick bake-off
Four tools, one 60-page state RFP, the same compliance matrix task. Time-to-matrix and accuracy against a hand-built reference. The results were closer than I expected and the failure modes were different than I expected.
The amendment checklist every proposal manager should run
An RFP amendment lands. Six questions to answer before you click 'acknowledge receipt.' Each one has bitten a team I know in the last 18 months.
The RFP section priority matrix
Evaluator weight times effort hours equals where to spend the draft budget. A simple matrix that tells you which sections deserve gold-team review and which sections deserve a paragraph and a citation. With three worked examples.
The federal fiscal-year clock just reset
The federal fiscal year started yesterday. Here is what Q1 procurement volume actually looks like, what bids land in the next 90 days, and how a small proposal team should staff for it.
SME collaboration, Part 4 of 4: a KB your SMEs will actually use
What makes an SME contribute to a knowledge base versus what makes them ignore the tool. Closing the four-part series — the structural choices that decide whether your KB compounds or rots.
The 20-minute proposal retro
The ritual we run after every submit. Five questions. One owner per action item. Twenty minutes. Why most proposal post-mortems don't happen and what makes this one stick.
The color-team review discipline, explained for modern teams
Pink, red, gold, white. The four-team review discipline most modern proposal shops know by name and don't actually run. This post reclaims it — what each team is for, why teams skip it, the rubrics, and how to run reviews async in 2025.
SME collaboration, Part 3 of 4: the 20-minute capture call
The synchronous meeting that saves four days of draft revision when the question is genuinely complex. The agenda template, the recording-and-transcript discipline, and what gets routed to a capture call vs. an async ticket.
The scoring rubric on the first read of any RFP
Three minutes. Find the scoring paragraph. Note the page, the heading, and the weights. The habit that shapes the entire response — and why most teams skip it.
SME collaboration, Part 2 of 4: ticketed asks and response SLAs
Why 'just ping them on Slack' fails as an SME workflow, what a structured ticket form should contain, and the response SLAs that make the queue legible to engineering managers and proposal leads at the same time.
State RFP subcontracting requirements, decoded
Five states, six clauses, and how they score. A research teardown of state-level subcontracting and small-business participation requirements with citations to each procurement code.
A field guide to win themes that actually win
The canonical pillar on win themes. What they are, what they aren't, the swap-name test applied across six worked examples, and the discipline of constructing themes from capture and retiring themes that didn't earn their score bump.
Preview: the field guide to win themes that actually win
A teaser for tomorrow's win-themes pillar. Two worked examples — one theme that fails the swap-name test, one that survives it — and what the difference looks like in the response.
Amendments are the real RFP
Why the third amendment usually contains the evaluation criterion that decides the bid, and what it means for how teams structure intake.
The complete bid/no-bid scoring framework
The canonical bid/no-bid framework. Five variables scored 1–5, weighting, the rubric template, the bid-decision meeting, override discipline, and where the rubric is honestly wrong.
Bid/no-bid is a decision, not a vibe
A preview of Thursday's pillar piece. Why most teams score implicitly, what implicit scoring costs, and the meeting structure that turns a vibe into a decision.
Mandatory vs. desirable requirements, in plain English
The distinction that costs bidders contracts. Four examples of how mandatory and desirable requirements look in real RFP language and how to score them differently.
Good win themes are verbs, not adjectives
Adjective win themes — robust, scalable, frictionless — fail the swap test. Verb win themes describe what changes for the buyer. Three before/after rewrites of real proposal language.
Past performance that actually maps to the scope
Selecting which prior contracts to cite is a craft skill, not a database query. Three worked examples of past-performance selection — what to cite, what to omit, why the relevance map matters more than the impressive number.
Anatomy of a 112-page DoD RFP
A composite walkthrough of a 112-page Department of Defense solicitation — section structure, scoring methodology, evaluation factors, where the editorial weight actually sits. Drawn from public DoD RFP patterns on SAM.gov.
Reading an RFP like the procurement lead who wrote it
RFPs are procurement documents written by named humans with known constraints, drafted from templates reused for fifteen bids. Read them that way and the response writes itself differently. The canonical long version.
The Sunday night compliance check
A 15-minute habit before Monday's kickoff. Read the compliance matrix against the calendar. Find the four things that will hurt you in week three. Write the email Sunday night so Monday is not the day you discover them.
Reading the RFP the procurement lead actually wrote
RFPs are procurement documents written by named humans with known constraints, not sales documents. Read them that way and you respond 40 to 60 percent better. A preview of next week's pillar piece.
Anatomy of a mid-sized municipal RFP: Chicago-shaped
A walk through the structure of a typical mid-sized municipal RFP — front matter, technical scope, evaluation, contractual riders — using a representative Chicago-shaped solicitation as a composite worked example.
A bid/no-bid scoring rubric we actually use
Five dimensions, a 1–5 score on each, a written floor, and a no-bid decision that is as cheap to defend as a bid decision. The rubric I bring into every kickoff.
Win themes when you're the incumbent defending a contract
Defending a contract is a different proposal than winning one. The win themes that worked four years ago will lose you the renewal. Here's what changes when you're already inside.
Federal RFP word counts, 2024 to 2025
What two years of public federal RFPs on SAM.gov tell us about response-document length, page-count caps, and the directional drift of complexity. Research note with sample-size caveats.
The RFP kickoff meeting that saves two weeks
A 60-minute kickoff that decides ownership, win themes, the compliance scaffold, and the review calendar. Run badly, it costs you two weeks. Run right, it pays for itself by Friday.
Anatomy of a 28-page California state RFP
A walkthrough of a representative 28-page state-of-California RFP — the structure, the scoring framework, the compliance language, and the patterns that recur across California state procurements.
A compliance matrix in thirty minutes, not two days
A compliance matrix is the scaffold the rest of the proposal is built on. Most teams build it by hand from a PDF, and it takes two days. Here's the path from PDF to matrix in 30 minutes.
Red flags and the bid/no-bid gut check (Part 4 of 4)
Five signals an RFP is a wired bid, an unfunded wish list, or a procurement that was never serious. The closing piece in the Reading an RFP series.
The unwritten rules inside every RFP (Part 3 of 4)
Procurement leads write RFPs in a particular dialect. Once you can read it, the scoring rubric, the disqualifiers, and the actual priorities surface within the first 20 pages.
The compliance matrix you wish existed (Part 2 of 4)
The compliance matrix is the most consequential artifact in proposal work, and the one most teams build too late. Part 2 of Reading an RFP — what it is, how to build one in 30 minutes, and why it usually doesn't get built.
What 'reading an RFP' actually means (Part 1 of 4)
Reading an RFP isn't reading. It's six discrete passes — scope, compliance language, evaluation rubric, timeline and addenda, procurement signals, deal quality — each producing its own artifact. Part 1 of a four-part series.
The 8-stage RFP response pipeline, explained
A canonical long-read on how a mature proposal shop actually moves an RFP from the hand-off email through submission and the post-mortem that feeds the next bid. Eight stages, what each one owns, and where each one fails.
See the proposal workflow
Take the 5-minute tour, then start a trial workspace when you're ready to run a real pursuit against your own source material.