A Request for Proposal arrives on a Thursday with a deadline three weeks away. It asks for a 120-page response, a pricing workbook, five case studies, CVs for key staff and a solution architecture. Saying yes feels like the ambitious thing to do. Often it is the expensive thing to do. The go/no-go decision is the discipline of deciding, early and honestly, whether this particular bid deserves the effort.

A bid is an investment, so treat it like one

Responding to a large IT services RFP consumes real resources: presales consultants, solution architects, pricing analysts, delivery leaders reviewing estimates, and senior executives preparing for orals. Those people are finite. Every weak bid they work on is a strong bid they are not working on.

A simple expected-value view makes the point. Imagine a deal worth ₹8 crore over its life, at an expected 25% margin, so ₹2 crore of margin if won. Suppose the internal cost of a proper response, counting everyone’s time, is around ₹25 lakh. If your realistic chance of winning is 30%, the expected margin is ₹60 lakh, comfortably above the cost. At 20% it is ₹40 lakh. At 10% it is ₹20 lakh, which is less than you spend to bid. The bid loses money on average before a single line of code is written.

This is a rough model. It ignores the strategic value of a new logo and the learning from losing. But it exposes the uncomfortable truth that win probability, not deal size, is usually the variable that matters most, and it is the one sales teams are most tempted to inflate.

Signals that you are not really in the race

Some RFPs are issued with an outcome already in mind. Procurement rules in many organisations, including public sector bodies, require a competitive process even when the business has a preferred vendor. Warning signs include:

  • You had no contact with the client before the RFP arrived, and nobody there will take a call now.
  • The requirements describe a specific competitor’s product or methodology almost word for word.
  • The timeline is too short for anyone to respond well, except a vendor who already knows the answers.
  • Evaluation criteria weight things like “existing familiarity with our environment”.
  • Clarification questions get thin or evasive answers.

None of these is proof. Together, they suggest you are being invited as a price benchmark, sometimes called “column fodder”.

Building a go/no-go scorecard

Most mature services firms use a weighted scorecard, reviewed by a small bid council that includes sales, presales, delivery and finance. The categories vary, but they usually cover whether you can win, whether you can deliver, and whether you should want it. Here is an illustrative version, with each factor scored from 1 to 5 and weighted:

FactorWeightScore (1–5)Weighted points
Relationship and access to decision makers2028
Solution fit with our capabilities20416
Competitive position1526
Confirmed budget and funding1048
Expected profitability1539
Delivery capacity in the timeframe1048
Strategic value (new logo, new vertical, reference)10510
Total10065

Weighted points are the weight multiplied by the score divided by 5, so a perfect score in every row gives 100. A firm might set a rule such as: above 70, bid; 55 to 70, discuss; below 55, decline unless leadership overrides with a written reason.

This example lands at 65, in the discussion zone. Notice what drives it down: weak relationships and weak competitive position, the two factors most connected to actually winning. Strong strategic value is propping up the score. That is a pattern worth noticing, because “strategic” is the word teams reach for when they want to bid on something they probably will not win.

Knock-out criteria come before scores

Some issues should end the discussion regardless of the total. Common knock-outs include mandatory certifications you do not hold, unlimited liability terms the legal team will never accept, a payment structure that would strain cash flow, a technology stack where you have no credible experience, or a conflict of interest with an existing client. Checking these first saves the bid council from debating a deal it cannot sign.

A decision, revisited at gates

Go/no-go is not a single moment. Many firms review at several points: when the RFP arrives, after the clarification round, before pricing is finalised, and before submission. New information can change the answer. A client’s clarification response might reveal a much larger scope than expected; a key architect might become unavailable; a competitor might be revealed as the incumbent.

A “no-bid” is also not the same as silence. A short, courteous letter explaining that you are declining this opportunity, ideally with a reason and an interest in future work, preserves the relationship. Some clients note who declines gracefully and who ignores them.

Where scorecards go wrong

The scorecard only works if the inputs are honest. If the account manager scores their own relationship, it will rarely be below a 4. Better practice is to ask for evidence: name the decision maker you have met, describe the last conversation, state what you know that the RFP does not say. Tracking win rates by score band over a year or two also helps. If bids scoring 60 win as often as bids scoring 80, the weights need rethinking.

The deepest benefit of a go/no-go process is cultural. It gives presales teams permission to focus, and it turns “we bid on everything” from a sign of hustle into what it usually is: a sign that nobody is choosing.

Written by the RP Strativa Team. Figures, weights and thresholds in the examples are illustrative.

Leave a Reply

Trending