How to Run a Pursuit Kickoff Meeting That Actually Works

You've made the go decision. The team is assembled. Now it's time for the pursuit kickoff — and this is where many firms waste their first and best opportunity to set a winning direction.

The typical pursuit kickoff in construction goes something like this: everyone gathers in a conference room, the proposal manager reads through the RFP section by section (information most people could have absorbed on their own), sections get assigned with deadlines, and people file out with a to-do list but no shared strategy. Two weeks later, the drafts come in looking like four different companies wrote them because nobody agreed on what story they were telling.

A good kickoff produces something different: a shared understanding of why you're pursuing this project, what it'll take to win, and how the team will work together to get there. For the full pursuit management framework, see our complete guide to pursuit management for construction firms.

Why most pursuit kickoff meetings waste everyone's time

The problem isn't that kickoff meetings happen — it's that they're used for the wrong purpose. Reading the RFP aloud is not a kickoff. It's a reading comprehension exercise that should have been completed as pre-work. Assigning proposal sections without first agreeing on your win theme and key messages produces a disjointed proposal that reads like it was stitched together from different companies' submissions.

A pursuit kickoff is a strategy session. Its purpose is to align the team on three things: why you can win this project, what the client cares about most, and how you'll position your firm relative to the competition. The section assignments and timeline logistics are important, but they come second. Get the strategy right first, and the writing flows naturally. Skip it, and you'll spend your entire review cycle trying to impose coherence on disconnected sections.

Who should be in the room — and who shouldn't

The right attendees for a pursuit kickoff are the people who will directly contribute to the proposal content and strategy:

Core team (always attend): Pursuit or proposal manager (facilitator), technical lead or project executive (the person who would run the job), precon or estimating lead (if fee is part of the submission), and the BD lead or relationship manager (who knows the client). These four to five people carry 90% of the proposal development load.

Optional attendees (invite when relevant): A safety manager if the project has significant safety considerations. A specialty trade expert if the technical approach requires niche knowledge. A marketing or graphics person if the proposal requires significant visual design. An executive sponsor if the pursuit is strategically important enough to warrant senior attention.

Who should NOT be there: Anyone who won't contribute to the proposal. This sounds obvious, but many firms include people "for awareness" or "in case they're needed later." Every unnecessary attendee is a person whose time could be better spent on billable work — and their presence often dilutes the strategic conversation with questions that would have been answered by reading the pre-work materials.

Keep the group tight. Four to seven people is the sweet spot for a productive strategy discussion.

The kickoff agenda that produces alignment, not just assignments

A well-structured pursuit kickoff runs 60 to 90 minutes and follows a deliberate sequence:

1. Why we're pursuing this project — the win theme (10 minutes). Start with strategy, not logistics. What's the core reason this client should choose your firm? Is it your unique experience with similar projects? Your team's availability and proximity? A relationship advantage? State the win theme explicitly and get agreement from the group. If you can't articulate it in one sentence, you're not ready to start writing.

2. What we know about the client and competition (15 minutes). Share the client intelligence: who the decision-makers are, what they've said about their priorities, what delivery method they prefer, and what you know about their evaluation criteria. Then discuss the competitive landscape — who else is likely to bid and what their strengths and weaknesses are relative to yours.

3. What the selection committee cares about most (10 minutes). Every RFP has stated evaluation criteria, but the real priorities often differ from the written ones. Discuss what you believe will actually drive the decision based on client intelligence, the owner's history, and the project specifics.

4. Our differentiators for this pursuit (10 minutes). Given what you know about the client, the project, and the competition, what makes your firm the right choice? Identify two to three specific differentiators that your proposal will build around. These become the thread that runs through every section.

5. Technical approach at a high level (15 minutes). Walk through your planned approach to the project — not the full methodology, but the key decisions. What's your execution strategy? Are there innovative methods or lessons from past projects that apply? What risks need to be addressed proactively in the proposal?

6. Roles, timeline, and milestones (15 minutes). Now assign sections and set deadlines. First draft due dates, internal review schedule, red team date, final production timeline, and submission deadline. Build in buffer — if the proposal is due Friday, target Wednesday for final review. Something always goes wrong in production.

What to prepare before the kickoff — the pre-work that makes or breaks the meeting

The quality of your kickoff is directly proportional to the quality of the preparation before it. The pursuit manager should arrive with:

An RFP summary that highlights the key requirements, deadlines, evaluation criteria, and any unusual provisions. Not the full document — a distilled one-pager that gives the team what they need without requiring them to read 80 pages.

Client intelligence: everything you know about the owner, the decision-makers, their history with your firm, and any relationship advantages or gaps.

Competitive landscape: who else is likely to pursue this project and how you compare on relevant dimensions.

Relevant past projects: three to five projects from your firm's portfolio that demonstrate relevant experience. These become the evidence that supports your differentiators.

Having your firm's relevant project experience at your fingertips during kickoff changes the conversation from "I think we did something like this" to "Here are three similar projects." See how ProjectPortfolio helps teams prepare faster by making your complete project history instantly searchable and filterable by project type, size, and client sector.

What a great kickoff produces — the deliverables that set up a winning proposal

By the end of a well-run kickoff, the team should have clear answers to these questions: What's our win theme? Who are we and why should the client choose us? What are our two to three key differentiators? What's the technical approach at a high level? Who's writing what, and when is it due?

These aren't aspirational outputs — they're the minimum that a strong kickoff should produce. Document them in a pursuit plan that becomes the reference document for the entire proposal development process. When section writers start veering off-message (and they will), the pursuit plan brings them back to the agreed strategy.

The kickoff should produce enough clarity that the team can start writing immediately. If your kickoff ends with more questions than answers, something went wrong — either the preparation was insufficient, the wrong people were in the room, or the opportunity needs more qualification before you commit proposal resources.

If your team is spending kickoff meetings trying to remember what projects you've done instead of strategizing how to win, it's time for a better system.