Responding to an RFP: What the Guides Will Never Tell You

This article builds on The Bid Manager's Worst Enemy, where we showed that cognitive biases sabotage the response process, and The Acceleration of Pre-Sales Cycles, where we raised the question of what to do with the time freed by AI. Here, we go back to the root: before producing faster, before writing better — should you respond at all?

The Problem With "How to Respond in 5 Steps" Guides

Type "how to respond to a tender" into Google. You will find ten pages that say the same thing.

Step 1: download the tender package. Step 2: analyze the specifications. Step 3: write your technical proposal. Step 4: compile the administrative file. Step 5: submit on the procurement platform before the deadline.

This is accurate. It is thorough. And it is perfectly useless.

These guides describe the process. Not the strategy. They explain how to fill in a form, not how to win a contract. The difference between the two is the same as between knowing how to drive and knowing where to go.

A bid manager who follows these five steps to the letter will produce a compliant submission. Admissible. Complete. And losing — in 75% of cases, according to industry averages. Because compliance is the entry ticket, not the competitive advantage.

The structural problem with these guides is that they start from the wrong point. They begin at "download the tender package." But the most important decision comes before. It has nothing to do with writing, formatting, or compliance. It comes down to three words: should you respond?

And this question, no one asks it seriously.

---

The Decision No One Makes: Go/No-Go

Here is a fact that most sales directors refuse to hear: 70% of lost contracts were lost before the first word was written.

Not lost because of a mediocre technical proposal. Not lost because of an administrative error. Lost because the company had no realistic chance of winning — and no one had the courage to say so.

The Go/No-Go is the highest-ROI decision in the entire pre-sales process. Each submission mobilizes between 15 and 40 person-days of senior profiles. An architect at EUR 1,200 per day spending three weeks on a doomed submission is EUR 18,000 burned. Multiply by the 20 lost submissions in a year: EUR 360,000 of investment with zero return.

The Go/No-Go as practiced in 90% of organizations looks like this: the sales director sends an email on Friday evening. "RFP received, local authority X, estimated value EUR 2M, deadline in 3 weeks, are we going for it?" Monday morning reply: "We have the skills, go." Five minutes. No analysis. No formalized criteria.

The 7 Criteria of a Go/No-Go That Works

A serious Go/No-Go does not take five minutes. It takes thirty. And it relies on seven criteria, scored and weighted:

1. Client knowledge. Do you have an existing relationship with this client? Have you met them in the last twelve months? Do you know what they expect beyond the specifications? If the answer is no to all three questions, you are responding blind — and your competitors who have the relationship are not.

2. Relevant references. Not "we have references in the sector." References directly transferable to the contract's scope, with verifiable performance indicators. References that convince no one lose contracts just as much as they win them.

3. Identifiable competitive advantage. What do you have that others do not on this specific contract? A technical edge, a named expert, a methodology proven on a similar case, geographic proximity. If you cannot state your advantage in one sentence, you do not have one.

4. Mobilization capacity. Are the right profiles available? Not "we will find someone" — are they identified, briefed, available in the schedule? A submission written with generic CVs and a fictional team is visible from a mile away.

5. Price alignment. Does your cost structure allow you to be competitive on this contract? If the client expects a daily rate of EUR 600 and your rate card starts at EUR 800, the most brilliant technical proposal in the world will not offset a 30% gap on price.

6. Execution risk. If you win, can you deliver? This is the question no one asks at the Go/No-Go stage — and that comes back as a boomerang six months after contract award. A contract won but poorly executed destroys more value than a contract not won.

7. Strategic value. Does this contract open a door? A new sector, a new strategic client, a missing reference in the portfolio? A low-margin but high strategic value contract can justify a Go that financial criteria alone would have rejected.

Each criterion is scored from 1 to 5. Below 21/35, it is a No-Go. Between 21 and 28, it is a conditional Go — with identified mitigation actions. Above 28, it is a clear Go.

The result: instead of responding to 40 contracts with a 15% win rate (6 wins), you respond to 25 contracts with a 32% win rate (8 wins). More wins. Fewer submissions. Less senior mobilization. An ROI that soars.

"The best tender response you will write this year is the one you did not write."

---

Reading a Tender: What Is Said Between the Lines

You have decided to respond. The tender package is downloaded. 200 pages of technical requirements, 80 pages of contract terms, a pricing schedule, a bill of quantities, selection criteria, and three technical appendices. The natural temptation is to start reading at page 1 and finish at page 480.

This is a mistake.

Specifications are not read. They are decoded. And the decoding begins with a simple question: what does this client really want?

The answer is almost never in the explicit requirements. It is in the patterns, the repetitions, the silences.

The recurring keyword test

Take a 200-page specification document for an application management contract. Count the occurrences of certain terms:

• "service continuity": 14 occurrences
• "responsiveness": 11 occurrences
• "innovation": 2 occurrences
• "transformation": 1 occurrence

This document is telling you something very clear, even if it is never written explicitly: this client is afraid. They are afraid their IT systems will go down. They are afraid the service provider will not respond quickly enough. They are not looking for innovation — they are looking for reliability. If you respond with a 15-page section on your innovative approach and two paragraphs on your on-call arrangements, you are answering the wrong question.

The requirements that do not exist

More dangerous still than what the specifications say: what they do not say.

An application development contract that never mentions automated testing. An IT outsourcing contract that does not address business continuity planning. A consulting contract that does not discuss the knowledge transfer methodology. These silences are not oversights. They are blind spots where each bidder will make different assumptions — and most will be wrong.

Specification analysis is not a reading exercise. It is an intelligence exercise. Every ambiguous sentence is an assumption to formulate. Every silence is a question to ask. And the questions you ask the contracting authority are a signal as powerful as the answers you write.

---

Response Strategy: Position Before You Write

You have read the specifications. You have identified the weak signals, formulated your assumptions, asked your questions. Now, the natural reflex is to open Word and start writing.

Resist.

Before writing a single paragraph, you must have three things in place: your win themes, your competitive positioning, and your push/secure matrix.

Win themes: your thesis in three sentences

A win theme is not a slogan. It is a falsifiable proposition that explains why you are the best choice for this specific contract.

Bad win theme: "Our recognized expertise in the field of information systems." Good win theme: "Our team migrated 340,000 business records to the cloud for CNAF in 2024 with zero service interruption — exactly the type of operation your specifications describe in section 4.2."

The win theme links three elements: what the client wants (identified through specification analysis), what you have (your competitive advantage), and the proof that it works (your reference). Three win themes are sufficient. Beyond that, you dilute the message.

Competitive positioning

You are not responding in a vacuum. Three to eight competitors are reading the same specifications at the same time. The question is not "what to propose?" but "what to propose that the others will not?"

If you are the incumbent: your advantage is knowledge of the context. Push continuity, reduced transition risk, the gains from the existing relationship. Your risk is complacency — the client reopening the contract may be looking precisely to change.

If you are the challenger: your advantage is fresh perspective. Push external benchmarks, lessons learned from other clients, innovations the incumbent has not delivered. Your risk is underestimating the cost of transition — the client knows that cost all too well.

If you are the technical specialist: push depth of expertise. If you are the generalist: push functional coverage and integration capability. Never compete on the strongest competitor's home turf.

The push/secure matrix

Each scoring criterion falls into one of two categories:

• Push: criteria where you can create a gap with competitors. These are your attack vectors. Invest the most time, detail, and examples here.
• Secure: criteria where you need to meet the expected standard without standing out. These are your fundamentals. Cover them solidly, but do not over-invest.

A contract scored 60% technical / 40% price with a "change management methodology" criterion weighted at 25 points out of 60 tells you where to concentrate your energy. If change management is your strength: push. If it is your weak point: secure — cover the expected minimum and fight your battles elsewhere.

---

The Organization That Wins: Roles, Timeline, Reviews

The strategy is set. The win themes are defined. The positioning is clear. Now, and only now, does production begin.

And this is where the difference between teams that win and teams that lose becomes most visible. Not in the quality of the writing — in the rigor of the organization.

The response kick-off (D+0)

Not an email sent on a Friday evening. A 45-minute meeting, on the day of the Go decision. Participants: bid manager, sales lead, identified technical contributors, designated reviewer.

Non-negotiable agenda:

1. Client context (sales lead: 10 min). What the specifications do not say. The history. The implicit expectations.
2. Response strategy (bid manager: 10 min). Win themes, positioning, push/secure matrix.
3. Contribution assignments (bid manager: 10 min). Who writes what, by when, at what level of detail.
4. Timeline and milestones (bid manager: 10 min). Intermediate delivery dates, review dates, finalization date.
5. Open questions (all: 5 min). Blocking issues, assumptions to validate, Q&A questions to submit.

Teams that win hold this kick-off systematically. Teams that lose "don't have time."

The standard timeline (21 days)

The key point: writing occupies only 5 days out of 21. The rest is analysis, strategy, review, and coordination. The "5-step guides" discuss only the writing. Teams that win invest 75% of their time on everything else.

The Red Team review

This is the practice that most clearly separates winners from losers. And it is the one almost no one does.

The principle: a reviewer who was not involved in the drafting reads the complete submission as if they were the evaluator. They score each section against the selection criteria. They identify weaknesses, blind spots, inconsistencies. They look for hollow sentences, unsubstantiated promises, off-topic sections.

This reviewer is not there to be polite. They are there to find the flaws before the evaluator does. Every flaw corrected before submission is a point saved. Every flaw left in place is a point lost.

A serious Red Team improves the technical score by 3 to 8 points out of 60. On a competitive contract, that is the difference between first and fourth place.

---

The Three Traps That Cost You the Contract

Twenty years of bid management reveal recurring patterns. Three mistakes come back with troubling regularity — and they are rarely mentioned in conventional guides.

Trap 1: Responding to everything without prioritizing

A specification document requests 47 deliverables. The conscientious bid manager's reflex is to treat each deliverable with the same level of detail. Result: a 300-page submission where everything is covered, nothing is deepened, and the evaluator retains nothing.

The evaluator has 4 hours to read your submission. Four hours for 300 pages. They do not read — they scan. They look for answers to the 3-4 points that truly matter to them. If those answers are buried in 296 pages of filler, they will not find them.

The right approach: identify the 20% of the submission that carries 80% of the score. Invest 80% of your effort there. The rest: compliant, complete, concise. Nothing more.

Trap 2: Recycling the previous submission

"We responded to a similar contract six months ago. We take the base and adapt."

This is the most tempting and most destructive shortcut. An experienced evaluator spots a recycled submission in less than two minutes. The clues are everywhere: a client name poorly replaced in a table, a reference that does not match the scope, an organization chart showing generic profiles instead of the dedicated team, a methodology discussing a different context.

Beyond detection: a recycled submission does not address the specific need of this client. It addresses a vaguely similar need of another client, six months earlier. The priorities are different. The context is different. The stakes are different. A recycled submission tells the client: "You are not important enough for us to work specifically for you."

Reuse building blocks, yes. Recycle a submission, never.

Trap 3: Ignoring the Q&A process

The Q&A phase is the most underexploited moment in the process. 60% of bidders ask no questions. Among the 40% who do, the majority stick to administrative clarifications.

What is worse: 30% of bidders do not even read the published answers — including those to questions asked by competitors. These answers sometimes contain information that fundamentally changes the landscape: a scope clarification that alters the staffing model, a criterion clarification that redirects the strategy, an implicit admission about the client's real expectations.

Ignoring Q&A is going into battle blindfolded while your competitors have read the briefing.

Key takeaway: These three traps share a common thread — they betray a lack of strategic rigor, not a lack of writing competence. The submission does not lose because it is poorly written. It loses because it is poorly thought through.

---

What TenderGraph Does

Everything described above — structured Go/No-Go, specification decoding, positioning strategy, production organization, Red Team — is the method the best bid managers apply when they have the time. The problem is that they never have the time.

Three weeks per submission. Four submissions in parallel. Technical contributors who deliver their sections at D-2. A Go/No-Go dispatched in five minutes because they need to "get moving." A Red Team that never happens because no one is available at D-3.

TenderGraph does not replace the method. It makes it possible.

Automated Go/No-Go. The system analyzes the tender package in minutes and produces a structured score across the 7 criteria. Not to decide in place of the sales director — to give them the facts before they decide. "Client knowledge: 2/5. Relevant references: 4/5. Price alignment: 3/5. Overall score: 23/35 — conditional Go." The decision remains human. The analysis that informs it is instantaneous.

Requirement extraction and weak signal detection. TenderGraph does not summarize the specifications — it interrogates them. It counts occurrences, detects patterns, identifies silences. "Service continuity: 14 mentions. Innovation: 2 mentions. No mention of disaster recovery despite a high-availability context — assumption to formulate." The bid manager receives a terrain map, not a summary.

Q&A question generation. Each identified ambiguity generates a candidate question, formulated to maximize the value of the response. The bid manager selects, refines, submits. In thirty minutes instead of three hours.

Signal concentration. The first draft of the technical proposal is produced in hours, anchored to every requirement in the specifications, structured according to the scoring criteria. The bid manager shifts from writer to response director — they challenge, adjust, enrich, instead of starting from a blank page.

Complete traceability. Every claim in the submission is linked to the requirement it covers. Every assumption is explicit. Every dependency is visible. When a Q&A response invalidates an assumption, the system propagates the change — and the bid manager sees exactly what has shifted.

The result: the seventeen days that production used to consume are returned to strategy, review, discussions with the sales team, and the Red Team. The acceleration of cycles is not a productivity gain. It is a change in the nature of the work.

"TenderGraph does not respond to tenders for you. It gives you the time and the tools to respond the way you always wanted to — but never could."

---

Key Takeaways

Responding to a tender is not a writing exercise. It is an exercise in strategic decision-making under time and information constraints.

The first decision — Go or No-Go — determines the return on everything that follows. A poorly calibrated Go burns tens of thousands of euros. A clear-eyed No-Go frees resources for the contracts where you have a real chance.

Reading the specifications is not a passive act. It is an intelligence exercise: decode weak signals, formulate assumptions, identify silences, ask the questions no one else asks.

Response strategy precedes writing. Win themes, competitive positioning, push/secure matrix — these three tools are defined before opening Word, not during.

Organization — structured kick-off, realistic timeline, systematic Red Team — is what transforms a good strategy into a good submission. Without it, even the best analysis in the world ends in last-minute chaos.

And the traps that cost contracts are not writing errors. They are method errors: responding without prioritizing, recycling without adapting, ignoring available information.

The five-step guides are not wrong. They are incomplete. They describe the mechanics. They omit the intelligence. And it is in the intelligence — from the Go/No-Go to the positioning through the Red Team — that the difference between winning and losing is made.

Key takeaway: The contract is not won by writing better. It is won by deciding better — what to respond to, how to position, where to concentrate effort, and when to have the courage to say no. TenderGraph makes this discipline accessible by compressing production to free the time for strategy. Our vision rests on this conviction: the market transformation will not reward those who produce fastest, but those who think best.

---

Further reading:

• Tenders and AI: Toward a Silent Market Transformation — The underlying reality: the market is transforming, and the winners will not be those who automate production, but those who elevate the level of decision-making.
• Case Study: When AI Produces Industrial Mediocrity — What happens when you recycle faster instead of thinking better: mediocrity at scale.
• The Bid Manager's Worst Enemy: Themselves — The cognitive biases that sabotage the Go/No-Go, specification analysis, and Red Team — the three critical moments of a response.
• Generative AI Is Not Enough — Why a chatbot that writes solves nothing if the strategic positioning is wrong from the start.
• What the Specifications Do Not Say — Partial information is the bid manager's playing field. The questions matter more than the answers.
• The Acceleration of Pre-Sales Cycles — Seventeen days freed by compressing production. What you do with them determines everything.
• How to Write a Technical Proposal — The technical proposal is the execution of the strategy. Without strategy, it is an exercise in style.