The Go/No-Go Framework for Digital RFPs: Make the Call in 10 Minutes

Every agency has a version of this story. You spend 45 minutes reading an RFP, get your team excited, put together a bid plan - and then someone asks the question that should have been asked on day one: "Can we actually win this?"

The answer is usually no. Not because your agency isn't good enough - because the decision to bid was made on hope rather than evidence. Go/no-go decisions are where most agencies lose weeks of productive time every year, and they almost never have a formal process for making them.

Here is the framework we use. It takes 10 minutes. It has saved us from a lot of bad bids.

Why Most Agencies Skip the Go/No-Go Step

The pull toward bidding is strong. An RFP lands in your inbox with a healthy budget and a client you recognise. Someone on your team says it's in your wheelhouse. The deadline is three weeks out - plenty of time. You start a proposal document before anyone has asked whether you should.

This is not laziness. It's optimism bias, and it affects every agency regardless of size or experience. The cost is real: a full RFP response for a mid-size digital project takes 40-80 hours of senior time. That's a week of billable capacity per bid. If your win rate is 20%, you're spending five weeks of effort for every project you win. If it's 10%, it's ten weeks.

A disciplined go/no-go process does not make you more conservative. It makes you more selective - which means the bids you do submit are better resourced and better targeted. Win rates go up. Wasted time goes down.

The 10-Minute Framework

There are six questions. Score each one on a 0-2 scale. If your total is below 8, the default answer is no-go. If it's 8 or above, you have a real decision to make.

1. Relationship (0-2)

Have you worked with this client before, or do you know someone inside the organisation? Is there a prior relationship that gives you insight into what they actually want, not just what the document says?

• 2: Prior relationship or warm introduction
• 1: No relationship but familiar with the organisation
• 0: Cold - no relationship, no knowledge of the client beyond the RFP document

This is the single highest-weighted factor in whether you win. Procurement teams write RFPs around suppliers they already trust. If you're coming in cold, you need to be significantly better on every other dimension to overcome the relationship deficit.

2. Fit (0-2)

Does your agency's actual work - not what you could theoretically do, but what you have demonstrably done - match what the RFP is asking for? Not "we do digital" broad. Specific: same project type, same scale, same sector if possible.

• 2: You have directly relevant case studies at the right scale
• 1: You have adjacent experience but not a direct match
• 0: This is a stretch bid - you'd be positioning for capability you haven't yet proven

3. Capacity (0-2)

Do you have the people available to deliver this project if you win it? Not "we'll hire" - that is not capacity, that is a plan. Do the right people have the right availability in the right timeframe?

• 2: Delivery team is available and allocated
• 1: Capacity is tight but manageable with some juggling
• 0: Winning this would require hiring, subcontracting, or pulling people from existing commitments

4. Budget (0-2)

Is the budget real, and does it cover the scope at your rates? Many RFPs list a range that is either aspirational or designed to attract the lowest bidder. If you cannot deliver what's being asked at a margin that makes the project worth doing, this is a no-go regardless of everything else.

• 2: Budget clearly covers scope at your rates with a reasonable margin
• 1: Budget is borderline - you'd need to scope tightly to make it work
• 0: Budget is insufficient for the scope, or the scope is so undefined that the risk of overrun is high

5. Competition (0-2)

Who else is likely bidding? If you're competing against three agencies that have all worked with this client before, you are not a real contender - you are providing competitive cover so procurement can justify choosing someone they already know. Be honest about this.

• 2: You know the competitive field and you have a clear differentiator
• 1: Unknown field, but you have a credible case to make
• 0: You know incumbents are bidding, or the field is stacked against you

6. Strategic Value (0-2)

If you win this project, does it move the needle for your agency beyond the revenue? Does it open a new sector, a new client type, a new reference point? Or is it a commodity project that keeps the lights on but doesn't build anything?

• 2: Winning this opens a door you want opened
• 1: Good revenue, no strategic upside
• 0: Even if you win, it's not a project you'd be proud to put on your website

Reading Your Score

10-12: Strong go. You have a credible path to winning and a clear reason to bid. Commit the resource, do it properly.

8-9: Conditional go. There's a case for bidding but at least one dimension is weak. Consider whether you can address the weakness before committing - a call to the procurement contact, a subcontractor to fill a capacity gap, a case study from an adjacent project.

6-7: Caution. You can probably write a response, but you are unlikely to win. Is there a learning objective that justifies the time? If not, this is a no-go.

Below 6: No-go. Stop here. The time you'd spend on this proposal is better spent finding better-fit opportunities.

The Part Nobody Talks About: Where the Framework Breaks Down

The hardest part of go/no-go is not the scoring. It's the politics. The founder who wants to chase the client. The BD person whose bonus depends on proposal volume. The account manager who insists "we know people there."

A framework only works if you actually use it. The score needs to be visible to the people making the decision, not just the person running the evaluation. And it needs to be completed before the proposal document is opened - not after you've already got two people working on it.

Build it into your intake process. Make it a short Notion page, a Slack form, a spreadsheet - whatever your team actually uses. The tool does not matter. The habit does.

How to Find RFPs Worth Scoring in the First Place

The go/no-go framework solves half the problem. The other half is having a shortlist of RFPs that are worth evaluating at all - opportunities where the budget is real, the scope is clear, and the deadline is live.

That is harder than it sounds. The portals where most agencies source RFPs - Sam.gov, state procurement sites, municipal bid boards - are not built for digital agencies. They require hours of manual filtering every week just to surface a handful of relevant listings. And the signal-to-noise ratio is terrible: most of what you find will be the wrong sector, the wrong budget, or already half-expired by the time you find it.

This is what we built BidReadyRFPs to solve. Every week, we surface 60-75 pre-qualified digital RFPs - web design, digital marketing, UX, data, BI - each one manually reviewed before it reaches you. Budget confirmed. Deadline live. Scope clear enough to run through a go/no-go in 10 minutes, not an hour.

The Digital List ($199/month) gives you the full weekly feed. You run your own go/no-go against it and build your shortlist from there. Cancel anytime.

The framework above is free. Use it. The time you save on bad bids is time you can spend on the ones worth winning.