Module 1 · Project Pursuit · Week 2 — Live Virtual
Every pursuit spends real hours on a future that may never arrive. The Go/No-Go is where we decide which futures are worth the bet.
Pre-work + live session brief · read before our 45-minute virtual sessionThe problem
A lead lands in the inbox. It's a real client, a real project, in a sector we work in. The instinct — the good, ownership-minded instinct — is to go after it. We chase.
But every proposal we write spends something we can never get back: our own people's billable time. In 2024, the average technical lead spent 35 hours on a single proposal — and that's before marketing, principals, and reviewers add theirs. Chase the wrong pursuit and you don't just lose; you've spent a week of senior engineering time on a future that was never going to arrive, time that could have gone to winnable work or to billable projects we already own.
Pursuit isn't free. Every proposal is a withdrawal from the same account that pays for our work — and our ownership.
So the most valuable skill in pursuit is not writing a better proposal. It's deciding, honestly and early, which proposals are worth writing at all. That decision has a name and a process at Weston & Sampson: the Go/No-Go.
The frame
Last week we saw the machine: the firm decides today — what to chase, how to staff, when to hire — on a forecast built from its pursuits. Each opportunity you log carries an expected revenue and a probability of winning. Multiply them and you get weighted revenue; sum that across every pursuit and you get the backlog the firm plans against.
That makes the Go/No-Go the first and most consequential place we touch the forecast. A "Go" doesn't just commit proposal hours. It adds an opportunity to the firm's read on the future. Say "Go" to work we have little chance of winning, and we don't just waste hours — we poison the forecast with revenue that isn't coming.
A disciplined Go/No-Go protects two things at once: the hours we'd spend pursuing, and the trust the firm places in its own backlog.
The instrument
The Go/No-Go form turns a gut feeling into a defensible judgment. It is not a popularity contest, and it is not a test you pass — it is a structured read of fit, positioning, profitability, and readiness, built from a series of honest yes/no questions.
The form has one rule before any answer matters: read the RFP in its entirety first. You only complete it if you can answer its questions honestly. And two questions act as hard gates — answer "no" to either and it's a reason to stop, no matter how strong everything else looks.
The form also forces the data the firm runs on out into the open: a named, committed technical champion; sign-off from the Regional or Client Manager; and — entered into Vantagepoint on the opportunity record — an estimated net revenue and an estimated win probability. Those last two are exactly the numbers that became the weighted backlog last week. The Go/No-Go is where they're born.
The second decision
The Go/No-Go settles whether to pursue. But hidden inside every "Go" is a second decision we tend to make far too casually: what is this work worth, and how do we price it?
Score the opportunity and you know whether to spend the hours. Score the value — how uniquely we fit the need, how compelling an experience we can deliver, how much real business return we can create for the client — and you know what that "Go" is worth. The first read protects our time. The second read protects our price.
Opportunity score asks "should we pursue?" Value score asks "what is it worth?" Confuse the two and you either chase the wrong work — or win the right work at the wrong price.
Value isn't a feeling; it's a read on three dimensions. Uniqueness of fit: are we one of a few who can do exactly this, or one of many? Client experience: do we know this client well enough to make working with us easy and memorable? Business return: do we understand what drives value for them well enough to deliver it? A commodity service competes on cost. A uniquely valuable one earns a premium — and the higher we read on these three, the more our price can reflect the value we bring, not just the hours we burn.
Read the field
Where that second decision happens depends on how the work comes to us. Three patterns cover most of what we chase, and each one puts the pricing decision in a different place — which changes the skill that wins.
Same firm, same value — but quals-based sells it, RFP prices it, and direct-appeal must first discover it.
Before we meet
This is a live week. We won't lecture the form to you — you'll have already used it. Come having done the following, ready to defend your call.
In the room
We'll work the same lead as a group, surface where our reads disagreed, and pressure-test the calls. The disagreement is the point: it's where the difference between an honest forecast and a hopeful one becomes visible.
Next week is self-paced again. Having decided a pursuit is worth the bet, we sharpen the two numbers the Go/No-Go demanded: how we forecast revenue and effort, and how we calibrate an honest win probability — the discipline that turns a guess into data the firm can trust.