Pursuit Advisory

Teams don't lose complex public work on capability. They lose on the submission.

A capable team assembles a pursuit. The past performance is real. The right people are on it. The submission goes in, reads competently — and loses. Or it makes the shortlist and loses the interview. The debrief says the same thing it always says: strong team, but the proposal didn't separate you from the field. The capability was never the question.

A submission is the output of an operating model. Who owns the pursuit's strategic logic. Who decides what the team is actually claiming, and what it will prove. Whether the artifact set was aligned and whole before the window closed. When no one owns that layer, a team defaults to the most comfortable version of itself — every voice included, nothing pressure-tested, a smooth consensus that says "we can" instead of showing the thinking that proves "we already have." Comfort is easy to assemble. It is also what makes one capable team's submission indistinguishable from the next. Rigor is the thing that gets taken offline.

Most pursuit help operates downstream — graphics, proposal writing, production support — after the strategic decisions have already been made, or defaulted. Useful work, but it polishes whatever story the team arrived with. I work upstream, at the layer where the team decides what the win actually turns on, what the submission has to prove, and whether the exhibits — which stay the team's own — carry the team's real story instead of a template. The production can come from your people, from me, or from resources I source. The strategy and the governance are the work.

What I Help With
A

We keep making the shortlist and losing the interview.

The interview is a different instrument than the written submission, and most teams prepare for it by rehearsing. I help the team find the few things that decide the room, then govern the prep so the panel sees how this team thinks — not a polished pitch every competitor is also delivering. The goal is a team that walks in aligned, not scripted.

B

Our submissions come out looking like everyone else's.

Capable teams produce interchangeable proposals when no one owns the story. I work with you and your design and trade partners to surface what truly sets this team apart on this project — the real thing, not the version everyone claims — and make the exhibits carry it. A submission that reflects how well you have already thought through the problem is the one that separates.

C

Every pursuit turns into a fire drill, and the package comes together the night before.

That is an operating-model problem, not an effort problem. I define what has to exist and by when, supply or source the production capacity to hit it, and govern the assembly so the artifact set is complete and coherent before the window closes — not scrambled into it. The deadline stops being the thing you survive and starts being the thing you plan against.

Who This Is For

Mid-market general contractors pursuing complex public work — school district lease-leaseback, municipal CMAR, progressive design-build — where the win depends on a team telling one credible story, not on each firm submitting its own. The alignment has to span the design and trade partners you bring into the pursuit, because that is where the seams are.

GC pursuit and preconstruction leaders responsible for assembling that team, who can see the submission isn't reflecting the team's real strength and don't have the internal capacity to govern it pursuit after pursuit.

Firms moving up-market — into healthcare tenant improvements, university capital programs, or federal design-build — where the procurement has become more sophisticated than the pursuit process that got them this far.

How I Work

Pursuit positioning session

A focused working session before a specific pursuit: what sets this team apart, and what a winning submission would have to prove. It sets the strategy the rest of the pursuit is built on. Stands alone, or opens a full engagement. Scoped as a half-day or day.

Pursuit engagement

The core. For a named pursuit, I define the strategy and the artifact set the submission requires, govern its assembly to the submission date, and supply or source production capacity where your team needs it. Scoped per pursuit.

Interview / shortlist war room

High-intensity, once you've made the shortlist. The orals decide it from here. A short, focused push on what moves the panel, who carries which part, and a team that arrives aligned. Timeboxed to the interview window.

Pursuit-program governance

The higher altitude. Ongoing across your pursuit calendar — building the way the firm pursues complex public work into a repeatable capability the team owns, rather than a fire drill it survives each time. Structured as a retainer, with a defined exit once the capability is internal.

Before your next complex pursuit, ask the team: "Who owns the story this submission has to tell — and has it been pressure-tested, or only agreed to?"
Start the conversation

If the honest answer is that no one owns it, the window is already working against you. One conversation is enough to tell whether this is the problem.