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.
The Shipley-canonical RFP kickoff runs 90 minutes. It is thorough, it produces real artifacts, and for a 50-person proposal shop answering federal RFPs it is the right call. For a five-person team with three concurrent bids, a 90-minute kickoff is the kind of meeting that does not happen — the calendar cannot hold it, the stakeholders cannot attend it, and the proposal manager ends up running a 15-minute Zoom that is all status and no kickoff.
This post is the 30-minute version. Not a replacement for the 90-minute version — a different tool for a different scale.
What the 90-minute version is trying to do
Before trimming it, it is worth knowing what the full version is actually for. The 90-minute Shipley kickoff is trying to produce four things:
- Shared understanding of the RFP and the evaluation rubric.
- A capture summary — what we know about the buyer.
- Draft win themes.
- An agreed response structure and writing assignments.
Those four things are real and they all need to be produced. The question is what gets produced in the room, what gets produced async, and what gets deferred.
The trimmed agenda
30 minutes. Five segments. No slides.
Minute 0–3 — The bid decision, re-confirmed. One sentence: why we are bidding. If anyone in the room disagrees, we stop the kickoff and hold the bid/no-bid conversation first. This is the most common failure mode of small-team kickoffs: half the room still thinks we should be a no-bid on this one. You cannot have a productive kickoff if the bid decision is contested in the room.
Minute 3–10 — The compliance skeleton. The proposal manager walks the section-by-section map of what the RFP requires. Not full requirement readout — just the structure. “The response is six sections. Section 2 has 40 technical questions. Section 4 wants a staffing plan. Section 5 is pricing.” Seven minutes. The full compliance matrix is built offline by the proposal manager — the kickoff is where the shape gets introduced.
Minute 10–18 — Capture summary, five bullets. Who is the buyer, what is the strategic context, who is the incumbent, what did we learn in pre-RFP conversations, what are the disqualifiers. This is where Shipley’s capture work is supposed to land in the kickoff. In the trimmed version, it is eight minutes and five bullets.
Minute 18–26 — Win themes, first pass. We name three to five candidate win themes. Draft quality. The room disagrees about which ones are strongest, and that disagreement is the point. A kickoff that leaves with five consensus themes is almost always a kickoff that settled on generic themes. A kickoff that leaves with three themes the team is confident about and two that are still contested is doing real work. Eight minutes.
Minute 26–30 — Assignments and the review calendar. Who is writing which sections, when the pink-team review lands, when the red team lands. Nobody leaves the kickoff without an assignment and a date.
What gets pushed to async
Three things that the full kickoff covers live:
- Detailed compliance walkthrough. The full requirement-by-requirement readout happens offline. The proposal manager sends the matrix to the team with comments before the pink-team review.
- Deep capture briefing. If a detailed capture briefing is warranted — for a high-value bid, or a buyer the team has not sold to before — it runs as a separate 45-minute session with the capture lead, not as part of the kickoff.
- Staffing discussion. Who backs up whom on which section, who covers the SME asks, who handles portal submission. Ops detail. Goes in a shared doc, not the meeting.
What gets kept
The one artifact the kickoff still has to produce: a written kickoff brief, posted within 24 hours. One page. Buyer, bid rationale, compliance skeleton, five capture bullets, candidate win themes, assignments, review-calendar dates. Every team member reads it. Every stakeholder who could not attend reads it. This is the forcing function — if the brief cannot be written, the kickoff was not complete.
The 90-minute version produces more artifacts. The 30-minute version produces exactly one. That is the trade.
The small-team caveat
This agenda assumes the team is small enough that the people in the room already have context. Five people who have worked together for 18 months do not need the 90-minute ritual to coordinate; they need 30 minutes of focused alignment. A 15-person team onboarding three new writers onto a bid is different — the new writers need more, and the kickoff has to give it to them.
The Bid Lab has argued that Shipley’s full ceremony is too heavy outside massive internal teams; the same is true of the full kickoff. Small shops that import the ceremony without the scale end up with a ritual that consumes time without producing better proposals. Small shops that abandon the ritual entirely end up with kickoffs that do not produce alignment.
The 30-minute version is the middle. It is what we run on our own proposals. It is what the proposal leads we advise run on theirs. When a bid is big enough or strategic enough that it deserves the full 90-minute treatment, we run that instead. Most bids do not deserve it. The honesty of picking the right tool for the bid is the craft.