The Go/No-Go Call That Changed How I Think About Bid Decisions
By the WinWorthy Team
Twelve people on a conference call. A municipal software RFP sitting in everyone's inbox. And one sales rep who would not stop talking.
That was the moment I realized most proposal teams don't have a bid decision process. They have a conference call and a prayer.
The Levin Call
His name was Levin — a Cuban-Canadian sales rep at Cartegraph who was famous for boldly not caring what anyone thought of him, ruffling feathers across every department he touched, and winning deals he had no business winning. He also had an absolute inability to yield the floor once he started talking.
We had an RFP from a local government agency looking for municipal asset management software. Solid opportunity, but at that point I was managing eleven active RFPs simultaneously — every one of them competing for the same finite pool of SMEs, writers, and review cycles. We couldn't afford to pursue anything that wasn't a real contender. So I pulled together a cross-functional call — proposal team, sales, product, delivery, subject matter experts. Twelve stakeholders in total, which is already too many people for a working session, but we needed every group's input to score this thing honestly.
Levin joined the call and immediately did what Levin does. He started talking. And talking. About the relationship. About the opportunity. About why this was clearly a must-win. Five minutes in, we hadn't gotten through a single evaluation criterion.
So I cut in.
"Levin, I know you have a lot to say, but we need to decide if we're going to bid this or not."
My coworker sitting next to me nearly lost it. He still brings up that line years later.
But here's the thing — that sentence did exactly what a Go/No-Go process is supposed to do. It redirected twelve people away from opinions and enthusiasm and toward a structured evaluation. Because Levin wasn't wrong to be excited. He just wasn't answering the right question.
The right question isn't "do we want this deal?" It's "do we have a defensible reason to believe we can win it?"
What Happened Next
We went through my scoring framework — a homemade Excel spreadsheet I'd built to bring structure to exactly this kind of chaos. Sixteen criteria, organized into four weighted categories that covered the questions every bid decision should answer. Each stakeholder on the call scored their area of expertise: 0, 1, 2, or 3 on every criterion.
Topic by topic, team by team, we worked through it. The sales team scored relationship strength and competitive positioning. The technical team scored solution fit and delivery risk. Finance weighed in on margins and resource commitment. No one person dominated the conversation because the framework wouldn't let them. Every category had to be addressed. Every score had to be justified.
The result: a clear Go.
And Levin — to his credit — took that green light and ran with it. He flew out for the in-person demo, and he didn't show up empty-handed. He worked with marketing to create styrofoam replicas of manhole covers and fire hydrants — the actual municipal assets our software managed. He walked into that demo and put physical props on the table. It was pure Levin, and it worked.
We won the deal.
Why This Story Matters
This isn't a story about one RFP or one colorful sales rep. It's about what happens when you replace gut instinct with a structured decision.
On that call, Levin's instinct was right — we should have bid. But instinct alone would have told us to bid on every deal Levin brought in, because Levin was excited about every deal. Without the scoring framework, we would have had no way to distinguish the opportunities worth pursuing from the ones that just felt exciting in the moment.
That's the real value of a Go/No-Go framework. It's not about the deals you pursue. It's about the deals you don't.
The Problem With How Most Teams Make Bid Decisions
If your Go/No-Go process looks like a meeting where the loudest voice wins, you already know how this plays out.
Sales pushes hard because they have a relationship or a revenue target. Leadership green-lights it because the contract value looks impressive on a pipeline slide. The proposal team absorbs another 40-hour sprint on a deal they quietly suspect is unwinnable. Nobody wants to be the person who says no to a big opportunity — so nobody does.
Then you lose. And in the debrief, someone says what everyone was thinking: "We probably shouldn't have bid on that one."
This pattern repeats in proposal organizations everywhere. It's not a people problem. It's a process problem. Without a structured framework, every bid decision becomes a political negotiation instead of a strategic evaluation.
The cost isn't just the lost proposal. It's the next proposal — the winnable one your team didn't have capacity for because they were buried in a long-shot pursuit that should have been killed two weeks earlier.
What a Real Go/No-Go Framework Looks Like
The scoring framework I used on the Levin call — and refined over years of running bid decisions — evaluates opportunities across four weighted dimensions. Each one answers a different question about whether a pursuit is worth your team's time.
Does this opportunity belong in our pipeline? Not just whether you can do the work, but whether you should. Does it build capability you need? Does it position you in a market you're targeting?
Can we actually win this? This forces you to honestly assess your competitive position. Do you have an existing relationship with the buyer? Is there an incumbent — and if so, can you realistically unseat them?
What could go wrong if we win? Scope risk, delivery risk, resource risk, legal exposure. Winning a bad contract can be worse than losing a good one.
Does the math actually work? A million-dollar contract at 5% margin with $80K in bid costs is a very different opportunity than a $400K contract at 40% margin with $15K in bid costs.
The output is a score from 0 to 100 with a clear recommendation: Go, Caution, or No-Go.
Why Spreadsheets Break Down
Consistency erodes. When you're running a bid decision at 4pm on a Friday before a Monday deadline, the rigor of your evaluation drops. Criteria get glossed over. The spreadsheet doesn't push back.
History disappears. Every assessment lives in its own file. There's no easy way to look back across six months of bid decisions and ask: "What's our actual win rate on deals we scored below 50?"
Defending the decision is hard. When a VP asks why you recommended no-bid on a $2M opportunity, pulling up a spreadsheet with numbers in cells isn't particularly persuasive.
The political problem persists. If the tool feels informal or improvised, it's easy to override. The framework needs structural authority that overruling it requires a deliberate, documented decision.
The Moment That Became WinWorthy
I built that Excel framework at Cartegraph because I was tired of walking into bid review meetings with nothing but instinct. I kept refining it because I saw it work — the deals we pursued with high scores, we won at a noticeably higher rate. The deals we killed with low scores, we stopped wasting resources on.
That gap — between knowing a structured Go/No-Go process works and having a tool that makes it effortless — is why I built WinWorthy.
It's the scoring framework from that Levin call, evolved into software. Sixteen criteria across four weighted dimensions. A score from 0 to 100. A clear Go, Caution, or No-Go recommendation. AI that can scan an RFP document and pre-fill the scorecard. And a history of every bid decision your team has ever made, so you can finally answer: "Are we actually getting better at this?"
Try WinWorthy free for 14 days
A scored, defensible go/no-go decision on every RFP — in under 15 minutes.