Customer knowledge — the double-locked key to winning tenders

This article extends What the Specifications Don't Say, where we showed that the information missing from the specifications (CCTP) is often what wins or loses a contract, and Why Your Client References Convince No One, where we described the projection mechanism that triggers an evaluator's trust. Here, we go back to the source: customer knowledge — and the two radically different ways it acts on your score.

The most overused piece of advice in pre-sales

"Know your customer." It's the first thing you learn in pre-sales. The first thing taught in bid management seminars. The first thing forgotten when the specifications (CCTP) drop and the clock starts ticking.

Every guide to responding to tenders devotes a paragraph to "customer knowledge". Every consultant mentions it. Every post-mortem after a loss cites it as the missing factor. "We didn't know the customer well enough." It has become a truism — one of those truths repeated so often that they've lost all power to act.

The problem isn't that the advice is wrong. It's incomplete. And its incompleteness makes it harmless.

When a bid manager says "you have to know the customer", they're thinking of one thing: adapting the solution. Understanding the needs to respond better. That's the first lock — and most organisations stop there, convinced they've turned the key.

There's a second lock. And this one changes the very nature of the competition.

Key takeaway: "Know your customer" is the most repeated and least exploited piece of advice in pre-sales. Not because it's ignored — because it's only half understood.

---

First lock — shaping the solution

The first use of customer knowledge is the one everyone knows: adapting the proposal to what the customer actually expects.

What it changes in concrete terms

A specifications document (CCTP) is never neutral. It bears the marks of its author — their priorities, constraints, unspoken concerns. Two customers expressing the same functional need do not expect the same response. A local authority burnt by a previous supplier doesn't read a proposal the same way as one renewing a satisfactory contract. A customer going through internal restructuring doesn't have the same priorities as one in growth mode.

Customer knowledge enables three surgical operations on your proposal.

Concentrate. Among the fifty things you could propose, which ones actually interest this customer? Not the generic customer. This customer, with their history, constraints, deadlines. Concentrating means devoting 80% of your writing effort to the 20% of the scope that counts for scoring — instead of spreading your effort uniformly across a 200-page document, half of which will only be skimmed.

Eliminate. What doesn't interest the customer is not neutral. It's noise. Every page of your document covering a peripheral subject dilutes the signal of the pages that matter. The evaluator who scans your bid for 30 seconds per criterion won't forgive you for making them dig through the noise. Knowing the customer means knowing what not to write — as much as what to write.

Don't frighten. This is the blind spot. Some proposals, technically excellent, fail because they scare the customer. A complete IT system overhaul proposed to a customer who's lived through three failed migrations. An agile methodology imposed on a customer whose culture is regulatory and sequential. A team of ten experts proposed to a customer who struggled to manage the previous supplier with three people. The proposal is good — but it triggers an alarm in the evaluator. Not a technical alarm. A visceral one: "It's too much. It's too risky. It's too far from what we know how to handle."

Knowing the customer means knowing where their fears lie. And building a solution that bypasses them — or explicitly reassures them — instead of activating them.

Key takeaway: The first lock of customer knowledge is operational. It allows you to concentrate the proposal on what matters, eliminate what dilutes it, and avoid triggering the customer's fears. It's necessary. It's not sufficient.

---

Second lock — the signal of understanding

This is where customer knowledge moves from operational advantage to strategic advantage. And this is where no one goes.

The scenario no one describes

Picture the scene. A contract up for renewal. The incumbent has been in place for four years. The relationship is fine — not exceptional, but enough. The customer launched the consultation because the Procurement Code requires it. In their head, it's a formality. They're going to renew the incumbent. The other candidates' files will be skimmed out of professional courtesy, scored on the grid, ranked behind. The result is written in advance.

Then they open your proposal.

It doesn't look like the others.

Not in form — the form is compliant, the format is respected, the sections are in the right place. It's not a question of layout. It's a question of content.

From the executive summary onwards, something is different. The stakes mentioned are not the generic stakes of the contract. They are their stakes. The modernisation of the legacy platform that the specifications (CCTP) hint at on page 47 — you've put it on the front line. The risk of skills loss linked to the departure of two key staff members in the department — the CCTP doesn't mention it, but the staffing table in the appendix lets it be guessed, and you read it. The tension between the central IT department pushing for cloud and the business division resisting — it's written nowhere, but the lot structure and the steering committee composition give it away.

The evaluator stops. They re-read. They feel something they didn't feel on the four previous files.

They feel understood.

And it's all the more disturbing because they don't know you.

The psychological mechanism

What happens in the evaluator's mind is a four-step sequence — and each step reinforces the next.

Step one: surprise. The evaluator wasn't expecting to be understood by a candidate they've never met. Pre-sales files all look alike — same structures, same promises, same phrasings. When a file breaks the mould, attention awakens. It's a signal in the noise — and the evaluator, even unconsciously, starts reading differently.

Step two: curiosity. Surprise breeds the question: "Who are these people? How do they know that?" The evaluator who thought they had made up their mind starts to doubt. Not the quality of the incumbent — but the certainty of their choice. Doubt is not failure. It's an opening.

Step three: exploration. Doubt pushes the evaluator to read your file in depth — not in a 30-seconds-per-criterion scan, but in a third-pass reading. The kind ordinary files never receive. And what they discover confirms the first impression: the proposal is not only relevant. It's high-quality. The answers are precise. The references are chosen for their proximity to their context, not for their logos.

Step four: liberation. This is the decisive moment. The evaluator who feels understood begins to lower their resistance. The fears they didn't dare express — but which you read between the lines of the CCTP — are reassured. Their aspirations are understood. Their objectives are shared. You unblock their inertias one by one, you free up their desire for change.

The incumbent did nothing wrong. But they did something worse: they did nothing remarkable. Their proposal was correct — yours was personal.

Key takeaway: The second lock of customer knowledge is not operational — it's psychological. Showing the customer that you understand them triggers a sequence surprise → curiosity → exploration → liberation that can tip a contract everyone thought was a foregone conclusion.

---

Why the second lock is invisible

If the signal of understanding is so powerful, why does almost no one exploit it?

The illusion of compliance

Most bidders confuse "responding to the CCTP" with "understanding the customer". These are two different things. Responding to the CCTP means ticking the boxes. Each requirement has an answer. Each criterion is addressed. The file is compliant.

Understanding the customer means reading between the boxes. It means asking why this requirement is phrased this way. It means identifying the worry behind the technical specification. It means recognising that the CCTP is a political document as much as a technical one — that it bears the traces of internal negotiations, previous failures, the commissioning party's ambitions.

Compliance places you in the race. Understanding places you in front.

The expert bidder's bias

The most experienced teams are often the most vulnerable to this trap. They know the field. They've done fifty similar contracts. They know what works. And that's exactly what stops them from seeing the customer.

The expert bidder projects their experience onto the customer. They read the CCTP and think: "I know what they want — it's the same thing as the last fifteen contracts." They write a competent, professional, polished response. A response that would convince any generic customer.

But the evaluator is not a generic customer. They are a specific individual, in a specific organisation, with specific problems. And the expert's response, however brilliant, doesn't speak to them. It speaks to an archetype.

Optimism bias plays an insidious role here: the experienced bid manager believes they understand the customer because they understand the field. It's a confusion between sectoral knowledge and contextual knowledge. The first is generic. The second is surgical.

The perceived cost of investigation

Understanding a customer takes time. You have to read the CCTP beyond the functional requirements. You have to reconstruct the organisational context. You have to cross-reference public information — annual reports, council minutes, committee summaries, previous contracts, decision-makers' LinkedIn profiles. You have to interpret the clues — the lot structure, the choice of criteria, the weightings, the questions and answers from other candidates.

In a three-week cycle — the first week of which is often lost to Go/No-Go and dithering — no one has time to do this investigation. The bid manager is already overwhelmed by writing. Customer analysis is sacrificed on the altar of urgency.

It's the paradox: the investment that pays off the most is the one that is systematically cut first.

Key takeaway: The second lock remains invisible because most bidders confuse compliance with understanding, project their expertise instead of observing the customer, and sacrifice contextual investigation under calendar pressure. The signal of understanding is rare because it's expensive to produce — and that's precisely what gives it its value.

---

Anatomy of a proposal that sends the signal

What does a proposal that turns the second lock look like? Not in principles — in text.

The executive summary that names

The difference plays out in the first 500 words. The generic executive summary says: "Drawing on our expertise in digital transformation and our 200 certified consultants, we are committed to supporting your organisation in modernising its information systems." It says nothing. It could be copy-pasted into any document.

The executive summary that sends the signal says: "The modernisation of your HRIS platform, launched in 2024 and suspended after the departure of your deputy CIO, is today your main technical debt. Your specifications don't say so explicitly — but the unusual weighting of the 'service continuity' criterion (35%, against 20% in your previous contracts) reflects a concern we share: the risk of operational disruption during the transition."

The first executive summary describes the bidder. The second describes the customer. The difference is total — and the evaluator perceives it instantly.

The methodology section that reassures unspoken fears

Every CCTP carries implicit fears. They are never written as such — but they reveal themselves through clues.

The bidder who responds to the CCTP treats these elements as technical requirements. They answer them point by point. The bidder who understands the customer treats them as symptoms. They go back to the cause — and it's the cause they address.

The positioning that frees the desire for change

The most powerful moment in a proposal is not when it answers the questions. It's when it formulates what the customer didn't dare ask.

"Your specifications describe a contract for operational maintenance. We understand this scope. But we also perceive, in the structure of your lot allocation and your scoring criteria, a transformation ambition that current budgetary constraints don't allow you to formalise fully. Our proposal is built to respond to the contract as it is — while preparing the ground for the contract as you wish it to be."

This paragraph promises nothing more than what is asked. It doesn't go beyond the scope. But it tells the customer: I have understood you beyond what you have written. And this sentence — even implicit — is the most powerful signal a bidder can send.

Key takeaway: The signal of understanding materialises in three places: an executive summary that names the customer's stakes (not yours), a methodology that reassures the implicit fears in the CCTP, and a positioning that formulates what the customer didn't dare ask. Each of these elements is verifiable, concrete, and built from public information — not from guesswork.

---

The fatal asymmetry of renewals

The renewal scenario is where the double lock has the most impact — and it's also where it's least exploited.

The incumbent's trap

The incumbent renewing their contract has an apparent advantage: they know the customer. They've worked with them for four years. They know the teams, the processes, the irritations. Their customer analysis is unbeatable.

But this advantage backfires. The incumbent who knows the customer doesn't show that they know them — because they consider this knowledge as a given, not as an argument. Their proposal talks about what they're going to do, not about what they've understood. They capitalise on the relationship — not on the signal.

Their proposal says: "We have recognised expertise in this scope." It doesn't say: "We know that your real stake is X, and our proposal is built to address it." The first sentence is an affirmation. The second is proof of understanding.

The paradox: the incumbent has the customer knowledge but doesn't invest it in the document. The challenger doesn't have the relationship — but if they invest in contextual investigation, they can produce a stronger signal of understanding than the incumbent.

The reversal

The customer who receives five renewal files expects a pre-established hierarchy. The incumbent at the top, the challengers behind. It's the natural order.

When a challenger sends the signal of understanding, they break this order. Not by force — by relevance. The customer finds themselves facing a paradox: someone they don't know understands them better than someone they've worked with for four years. This paradox is destabilising — in the positive sense. It forces the evaluator to reconsider their certainties.

To the incumbent's great surprise, the challenger makes it to the oral round. Or, better, they win the contract directly — because the evaluator, freed from their inertia, finally had the courage to score objectively.

Key takeaway: In a renewal, the incumbent has the knowledge but doesn't show it. The challenger who invests in contextual investigation can produce a more powerful signal of understanding — precisely because it's unexpected. The apparent asymmetry (incumbent advantaged) reverses when the signal is explicit on one side and implicit on the other.

---

Sources of the signal — what's public and what to do with it

The signal of understanding doesn't rely on confidential information. It relies on public information that no one takes the time to cross-reference.

Direct sources

• The CCTP itself — re-read not as a list of requirements, but as a political document. The weightings, the lot structure, the choice of criteria, the unusual phrasings — everything is signal.
• Previous contracts — published on procurement platforms. Who was the incumbent? What amount? How many lots? Which criteria changed between the old contract and the new one? Each change is a clue about what didn't work.
• Questions and answers — questions asked by other candidates reveal their hypotheses. The buyer's answers reveal their implicit priorities. It's a public conversation that no one synthesises.

Indirect sources

• Annual reports, council minutes, public records — for local authorities and public bodies. They reveal internal tensions, ongoing projects, budgetary trade-offs.
• Organisational charts and decision-maker profiles — the professional background of the CIO who wrote the CCTP influences how the contract is structured. A CIO from the private sector doesn't write like a career public sector CIO.
• The customer's ecosystem — their partners, their suppliers, their cross-functional projects. Understanding the environment in which the customer operates allows you to contextualise their choices.

What no one does

The problem isn't access to information. The information is public. The problem is cross-referencing. Each source, taken in isolation, gives a fragment. It's the connection between fragments that produces understanding — and the signal.

The bid manager who reads the CCTP knows that the "service continuity" criterion is weighted at 35%. The bid manager who cross-references this with the annual report mentioning a major failure of the previous supplier understands why it's at 35%. And this understanding changes everything — the response strategy, the positioning, the tone.

Key takeaway: The signal of understanding is built from public information — but cross-referenced. The CCTP, previous contracts, questions and answers, annual reports: each source is a fragment. It's the synthesis that produces the signal — and almost no one does it, for lack of time or method.

---

Key takeaways

Customer knowledge is not a single advantage. It's a double advantage — and most organisations only exploit half of it.

1. The first lock is operational. Knowing the customer allows you to concentrate the proposal on what matters, eliminate what dilutes, and avoid triggering their fears. It's the expected use. It's necessary. It's not differentiating.

2. The second lock is psychological. Showing the customer that you understand them — especially when they don't know you — triggers a signal that breaks the inertia of the evaluation. Surprise, curiosity, exploration, liberation. The evaluator who feels understood reads your file differently.

3. The signal materialises in the text. An executive summary that names the customer's stakes. A methodology that reassures their implicit fears. A positioning that formulates what they didn't dare ask. Three places. Three proofs. Zero guesswork — only cross-referenced public information.

4. Renewal is the ideal terrain. The incumbent has the knowledge but doesn't show it. The challenger who invests in contextual investigation produces a stronger signal — precisely because it's unexpected. The asymmetry reverses.

5. Cost is the obstacle — and the barrier to entry. Contextual investigation takes time that the pre-sales cycle doesn't give. That's why the signal is rare. That's why it's powerful. That's why those who automate this investigation have a structural advantage.

The bid manager who responds to the CCTP does their job. The bid manager who understands the customer makes the difference. And the difference, in a market where five compliant files compete for a score, is everything that matters.

---

Double-locked customer knowledge is not a method. It's a shift in perspective. Instead of asking "how do I respond to the CCTP?", it means asking "what does the person who's going to read me feel?" — and building each page so that the answer is: "they understood me". This shift is simple to state. It's hard to execute manually, in the rush of a three-week cycle. But it can be automated — and when it is, the key turns twice on every contract.

---

Read also:

• What the Specifications Don't Say — The unspoken elements of the specifications are the raw material of the signal of understanding. Without them, you only understand what everyone understands.
• Why Your Client References Convince No One — The mirror reference is a special case of the signal of understanding: the customer projects themselves when they recognise themselves in your story.
• What the Evaluator Will Never Tell You — The three-pass scoring process explains why the signal of understanding must be in the first 500 words: pass 1 anchors the impression.
• The Myth of the Executive Summary — The executive summary that describes the customer instead of describing the bidder is the weapon of the second lock.
• The Bid Manager's Worst Enemy: Themselves — The expertise bias that pushes experienced teams to project their sectoral knowledge instead of observing the specific customer.
• The Informational Revolution: Signal and Noise — The signal of understanding is the strongest signal a bidder can emit — in an ocean of conformist noise.
• How to Write a Technical Document That Wins Contracts — The structure of the document must be designed so that the signal of understanding is visible at every level of reading.
• Responding to a Tender: What the Guides Will Never Tell You — The Go/No-Go is the moment when the decision to invest in customer knowledge must be made — or sacrificed.
• Pre-Sales as a Military Operation — Intelligence is the first phase of any operation. Contextual investigation is the intelligence of pre-sales.
• The Acceleration of Pre-Sales Cycles — When cycles shorten, only bidders who automate investigation still have time to turn the second lock.
• Analysing a Tender Like a News Story — The contextual analysis described here is exactly the investigation that feeds the signal of understanding.
• Where Are We With the File? — Time lost in oral reporting is time not invested in customer knowledge. The bifocal model frees this time.