"How's the bid going?" — the question that kills pre-sales

This article builds on Your bid reviews are useless, where we showed that bronze/silver/gold reviews are organizational theater that produces entropy without producing decisions, and One tool for ten, where we described tool fragmentation as the primary driver of information loss. Here, we trace these two problems to their managerial consequence: the sales director who doesn't know where the bid stands — and who compensates with the only method available: asking.

Anatomy of a toxic question

The scene is universal. Management meeting, Monday morning. The sales director scans the list of active bids. "The SNCF contract — where do we stand?" The bid manager answers: "Making good progress, the analysis is almost done, we're starting drafting this week." The sales director nods. He moves on to the next bid.

Wednesday, 5 PM. The sales director runs into the bid manager in the hallway. "SNCF — how's it going?" Same answer, slightly rephrased. "Yes, we're on track. Drafting has started."

Friday, 7 PM. Email from the sales director. "Can you give me a quick update on the SNCF bid? The CEO is asking on Monday."

The bid manager spends 45 minutes compiling a status report in an email. He hasn't made any progress on the bid during those 45 minutes. The sales director skims the email. He's no more reassured than before. He'll ask the question again on Monday.

This ritual repeats on every bid. On every cycle. In every organization. And nobody questions it — because "it's normal for management to track bids."

It's normal. And it's a disaster.

Key takeaway: "How's the bid going?" is not a tracking question. It's an admission of blindness. The sales director asks it because he has no other way to know — and the answer he gets ("we're making progress") resolves nothing.

---

What the sales director is really looking for

The sales director isn't asking a question. He's trying to calm two simultaneous fears — and no verbal update can address either one.

The fear of time

"Are we going to be ready?" The deadline is fixed. The submission date is non-negotiable. And between the moment the tender documents land and the moment you click "submit," there are three weeks — the first often wasted on Go/No-Go deliberations, the second on analysis and chaotic early drafting, and the third on panic.

The sales director has seen this pattern a hundred times. He knows that "making good progress" on Monday sometimes means "we're behind but don't want to say so." He knows the real status won't become visible until 48 hours before submission — when it'll be too late to fix anything. His question isn't curiosity. It's an attempt at early detection of a problem he senses but cannot see.

The fear of quality

"Is what we're writing any good?" This fear is more insidious. The sales director isn't always in a position to judge the technical quality of the proposal. He trusts the team — until the final review, where he sometimes discovers that the methodology section is recycled from the previous bid, that the references aren't relevant for this client, or that the executive summary is a catalog of platitudes.

At that point, it's too late. The bid goes out as-is, or gets last-minute corrections that degrade coherence instead of improving it. The sales director blames himself for not checking sooner. But checking sooner would have meant reading an unfinished document — and nobody knows how to evaluate a half-written bid.

Key takeaway: The question "how's the bid going?" masks two distinct fears — delay and quality. Verbal reporting resolves neither. It produces fleeting reassurance that evaporates within 48 hours.

---

Verbal reporting: the worst tracking system ever invented

There's a cruel paradox in pre-sales bid management. The same organizations that instrument every step of their delivery — Jira, dashboards, KPIs, structured steering committees — track their pre-sales verbally. The same director who would demand a burndown chart on a 500K euro delivery project accepts a "we're making good progress" on a bid worth 2 million euros in revenue.

Why? Because delivery has defined milestones, a tracking methodology, tracking tools. Pre-sales doesn't. The bid is an amorphous mass that goes from "not started" to "done" with no intermediate milestones observable from outside.

Verbal reporting is the consequence of this void. And it has three structural flaws.

First flaw: it consumes the time it's supposed to protect. The bid manager who spends 30 to 45 minutes per verbal update, three times a week, on three parallel bids, devotes between 4 and 7 hours per week to reporting. That's a full working day — on a three-week cycle. The irony: the time spent reassuring the sales director is time not spent producing the bid that should reassure him.

Second flaw: the information is volatile. The verbal update isn't recorded. Not structured. Not versioned. The sales director retains an impression — "seems to be progressing" — but not a fact. If someone asks him "where exactly is the SNCF bid?", he can't answer precisely. He has a feeling, not data. And feelings don't enable decisions.

Third flaw: it's systematically optimistic. The bid manager delivering a verbal update is in a hierarchical reporting situation. Optimism bias is inevitable. "We're on track" is the default answer — because saying "we're behind and the methodology section is weak" triggers a cascade of questions, meetings, and micro-management that slows the bid even further. The bid manager protects his working space by filtering information. The sales director believes he's informed. Nobody lies. Everyone is wrong.

Key takeaway: Verbal reporting devours productive time, produces volatile information, and is systematically biased toward optimism. It's not a tracking system. It's a reassurance ritual — and it reassures no one.

---

Why traditional milestones don't work

The natural objection is: "Then let's set milestones." It's the right instinct. But the way milestones are defined in most pre-sales organizations renders them useless.

"Drafting in progress" is not a milestone

A milestone has three properties: it is discrete (reached or not), it has an exit criterion (you know when it's been achieved), and it is observable (someone outside can verify it).

"Drafting in progress" satisfies none of these properties. It's a continuous state, not a discrete event. It has no exit criterion — when do you go from "in progress" to "done"? When the bid manager says so. And it's not externally observable — the sales director can't tell whether drafting is "in progress" or "stalled" without reading the document himself.

Most tender bid schedules look like this:

One observable milestone across three weeks. Everything else is narrative filler. The Gantt chart for a tender bid is the most fictional document in all of pre-sales — beautiful on day 1, fiction on day 10, abandoned on day 15.

The problem with milestones that lack quality criteria

Even when milestones are better defined — "analysis complete," "solution validated," "proposal assembled" — they only measure progress. Not quality.

"Analysis complete" means what? That someone read the specifications? That they extracted the requirements? All of them? That they identified the unstated expectations? That they formulated assumptions? Without a quality criterion, a milestone reached can mask sloppy work. And that's exactly what happens when schedule pressure pushes the team to "make progress" without consolidating.

The sales director who sees "analysis complete — check" believes the bid is on track. Maybe it is. Or maybe the analysis skimmed over 60% of the requirements and the gaps won't be discovered until the final review — two days before submission.

Key takeaway: A milestone without a measurable exit criterion is an illusion of control. A milestone without a quality indicator is an illusion of confidence. Pre-sales suffers from both.

---

The bifocal model: progress + confidence

If verbal reporting doesn't work and traditional milestones are fictions, what should replace them? A tracking system that simultaneously addresses both of the sales director's fears — time and quality — without pulling the bid manager away from actual work.

The progress axis: business milestones with exit criteria

The lifecycle of a tender bid isn't a continuous line. It's a sequence of discrete information transformations, each with a defined input and a verifiable output.

Every milestone is discrete (reached or not), has an exit criterion (not a declaration from the bid manager, but a verifiable output), and is externally observable. The sales director doesn't need to ask. He sees.

The confidence axis: the coverage score

Progress alone isn't enough. "Drafting consolidated — 5 out of 7 sections" doesn't tell you whether those 5 sections are any good. You need a second axis: confidence in quality.

The most objective proxy for bid quality is requirements coverage. How many of the specification requirements have a traced response in the proposal? This score isn't a subjective judgment — it's a count. Requirement identified, response mapped, link traced. Or not.

This score evolves in real time as sections are written. The sales director doesn't need to read the proposal to know if "it's good." He sees a number. That number is objective, verifiable, and comparable across bids.

And critically: this number changes the nature of the conversation. Instead of "where do we stand?" (open question, narrative answer), the question becomes "why did the score drop from 82% to 74%?" (precise question, factual answer). The first question generates noise. The second generates decisions.

Combined: the bifocal dashboard

This dashboard fits on one screen. It addresses both fears. It requires no verbal update. The sales director consults it when he wants — and when he doesn't, it means everything is green.

Key takeaway: Bifocal tracking — progress via verifiable milestones + requirements coverage score — replaces verbal reporting with an observable, objective, and continuous system. The sales director goes from "I ask and I hope" to "I see and I decide."

---

Push replaces pull

The bifocal dashboard is a structural improvement. But it remains a pull system — the sales director must go fetch the information. The next step is to invert the flow.

The principle: silence is a good sign

In a well-designed system, the absence of a notification means everything is fine. The sales director doesn't need to check whether milestones are progressing — he's notified when a milestone is reached, when a blocker appears, or when an indicator degrades.

This isn't revolutionary. It's exactly what production monitoring systems do in IT. Nobody manually checks that servers are running. A dashboard exists. And if something goes wrong, an alert fires. The rest of the time, silence is a positive signal.

Pre-sales deserves the same treatment. Not because bids are servers — but because the supervision logic is identical: monitor by exception, not by interrogation.

The four triggers

The sales director receives 2-3 notifications per bid per week. Not a 3-page email. One line. One fact. One data point. Reading time: 10 seconds. Production time for the bid manager: zero — the system emits, not the person.

The effect on trust

Inverting the flow transforms the psychological dynamics of bid oversight. Today, the sales director asks because he doesn't know. The bid manager answers because he must. Both are in a defensive posture — one suspects, the other justifies.

When the system pushes information, the relationship changes. The sales director trusts the system — and by extension, the team. The bid manager is no longer interrupted for verbal updates — he works. Formal reviews (bronze, silver, gold) become moments of strategic decision-making instead of information catch-up sessions.

Information flows without friction. Trust builds without conversation. And the time freed up — the bid manager's AND the sales director's — is reinvested in what actually wins contracts: understanding the client, solution quality, oral defense preparation.

Key takeaway: Push replaces pull. Silence becomes a good sign. The sales director goes from "I ask because I don't know" to "I'm notified when it matters." The bid manager goes from "I report because I'm asked to" to "I produce because nobody interrupts me."

---

Key takeaways

The question "how's the bid going?" is the symptom of an absent tracking system. Not an insufficient one — an absent one. Pre-sales operates in an information vacuum that verbal reporting attempts to fill, without succeeding.

Four observations and four solutions:

1. Verbal reporting is a trap. It consumes the time it's supposed to protect, produces volatile information, and is biased toward optimism. The solution isn't better verbal reporting. It's a system that eliminates the need to ask.

2. Traditional milestones are fictions. "Drafting in progress" isn't a milestone — it's a state with no exit criterion. Business milestones with verifiable outputs (requirements extracted, architecture defined, sections consolidated) are observable without intervention from the bid manager.

3. Progress alone isn't enough. The sales director has two fears: time AND quality. The requirements coverage score is the objective proxy that addresses the second fear — without requiring anyone to read the bid.

4. Push replaces pull. Information must flow by exception, not by interrogation. A milestone reached, a blocker, a declining score: three triggers that eliminate 90% of "where do we stand?" questions.

The bid manager who no longer spends 7 hours per week on verbal reporting gains a full day of productive work per cycle. The sales director who has a bifocal dashboard makes better decisions — allocate reinforcements, trigger a targeted review, abandon a poorly positioned bid — because he sees instead of guessing.

The question "how's the bid going?" should never be asked. Not because it's illegitimate — but because a well-designed system answers it before anyone thinks to ask.

---

Pre-sales is the last bastion of blind management. The same organizations that instrument every sprint of their delivery, every step of their supply chain, every interaction in their CRM accept managing multi-million-euro bids through verbal reporting and gut instinct. The day pre-sales adopts the same visibility standards as the rest of the organization, the question "how's the bid going?" will disappear — and with it, the managerial theater that accompanies it.

---

Read also:

• Your bid reviews are useless — Bronze/silver/gold reviews are the symptom of the same problem: reporting that produces no decisions.
• One tool for ten — Tool fragmentation makes tracking impossible: information is scattered across twelve silos that only the bid manager can connect.
• How to respond to a tender: what the guides will never tell you — The structured Go/No-Go is the first business milestone — and the most frequently botched.
• The bid manager's worst enemy: himself — The optimism bias in verbal reporting is a specific case of the cognitive biases that sabotage pre-sales.
• The information revolution: signal and noise — Verbal reporting produces noise, not signal. The coverage score is pure signal.
• What the specifications don't say — Specifications analysis is the first invisible milestone: you never know when it's "truly" complete.
• The myth of the executive summary — The sales director who discovers a hollow executive summary at the final review is the symptom of absent quality tracking.
• The acceleration of pre-sales cycles — Time freed by AI only has value if the tracking system can allocate it intelligently.
• Pre-sales skills in the age of AI — Tomorrow's bid manager is a system operator, not a human middleware between disconnected tools.
• The oral defense: the moment where everything is decided — The oral defense is the ultimate milestone — the one the sales director dreads the most and prepares the least.
• What the evaluator will never tell you — The requirements coverage score is the proxy for the score the evaluator will assign — the only quality measure that matters.
• Why your client references convince nobody — Unsuitable references discovered too late are the direct result of absent quality tracking.