Pre-sales is an exercise in command -- and you are leading it without a staff map

This article extends Pre-sales skills in the age of AI, where we identified systems thinking as a structural competency. Here, we push the operational framework to its conclusion: pre-sales is an exercise in command -- with an adversary, a terrain, forces to compose, and a plan that must survive contact with reality.

What you are fighting against

Let us begin with what nobody articulates.

A tender has an adversary. Not the competitor -- the competitor is a rival, which is different. The adversary is what the client is fighting against. Their pain points. Their frustrations. The limitations of their current system. The legacy that crashes every month. The data that cannot be cross-referenced. The internal team turnover that makes every project fragile. The regulatory compliance that weighs like a ball and chain.

The client's adversary is their status quo. And your mission is to help them overcome it.

But the status quo is not a single obstacle. It is a network of intertwined adversities -- technical, organizational, political, human. The legacy is linked to technical debt, which is linked to the lack of internal skills, which is linked to turnover, which is linked to working conditions, which is linked to the budget. Solving one problem without understanding its ramifications is treating a symptom while ignoring the pathology. You must map the whole before proposing a plan.

---

The terrain

Helmuth von Moltke the Elder: "No plan survives first contact with reality." In pre-sales, no response plan survives first contact with the specifications.

The terrain of a military operation is the physical geography -- hills, rivers, urban areas. But it is also the human terrain: the civilian population, local factions, influence networks, lawless zones.

The terrain of a tender is the specifications -- the documentary geography. But it is also the human terrain: the client's stakeholders, their motivations, their power dynamics, their internal alliances and rivalries. The CIO who wants an ambitious technical solution. The CEO who wants to respect the budget. The project manager who wants not to bear the risk alone. The procurement department that wants the lowest price. Each has their own map of the terrain -- and none look alike.

Mapping this terrain is the first act of any operation. In the military, it is intelligence. In pre-sales, it is the analysis of the tender package. And in both cases, the danger is the same: confusing the map with the territory. The specifications are a map -- drawn by humans, with their biases, their omissions, their unspoken priorities. The territory is the client's reality. The two never coincide perfectly.

---

Intelligence

Military intelligence distinguishes three levels of information:

Open-source intelligence (OSINT) -- publicly accessible information. In pre-sales: the specifications, the rules of consultation, the technical annexes, the contract notices published in official journals. Everything that every candidate possesses.

Human intelligence (HUMINT) -- information obtained through direct contact. In pre-sales: what sales learned during lunch with the CIO. The project manager's tone on the phone. A question asked by a competitor during Q&A that reveals their positioning. The palpable discomfort when the incumbent vendor is mentioned.

Analytical intelligence (SIGINT/IMINT) -- information obtained through systematic data processing. In pre-sales: the structural analysis of the specifications. Repetitions that betray a pain point. Volume asymmetries between lots. Conditional formulations that signal hesitation. Requirements recycled from previous contracts, identifiable by their mismatched drafting style.

The strategic advantage does not come from OSINT -- everyone has access to it. It does not even come from HUMINT -- the good sales teams in each camp gather signals. The advantage comes from analytical capability -- the ability to cross-reference all three levels to produce a map that approximates the territory.

This is exactly what TenderGraph does at the analytical intelligence level. The system processes the OSINT (the specifications) with the rigor of an intelligence analyst: each requirement is classified, weighted, cross-referenced with others. Hypotheses are formulated and tested. Inconsistencies are flagged. Blind spots are mapped. The bid manager brings the HUMINT -- client knowledge -- and the system integrates it into the analysis. The fusion of the two produces intelligence that neither could produce alone.

---

Force composition

A commander does not choose their forces. They compose with what they have. Each unit has its capabilities and its limitations. The art of command is positioning each force where it produces maximum effect -- and not employing it where it would be wasted.

The bid manager does exactly the same thing.

Their forces:

• References -- their most powerful evidence. What they have already accomplished, in comparable contexts. But a poorly chosen reference dilutes the proof instead of reinforcing it. The mirror reference -- same sector, same pain point, same scale, same constraint -- is targeted, precise, and neutralizes the evaluator's doubt.

• Methods -- their structuring framework. Shipley methodology, TOGAF framework, quality processes. But methods deployed for their own sake, without connection to the terrain, are tools in search of a problem. The client does not want to know that you have mastered Agile. They want to know that your Agile method will solve their delivery problem.

• The team -- their living force, and their greatest vulnerability. The proposed profiles, their experience, their complementarity. The project director who has not been involved in the references presented will be exposed in the oral presentation -- in two questions. The consistency between the proposed team and the story told in the proposal is a credibility test that experienced evaluators apply systematically.

• The technical solution -- the foundation of everything else. The IT architecture, the technology choices, the integration with the existing environment. A technical choice inconsistent with the client's constraints collapses the credibility of the whole -- regardless of the quality of the writing.

The operations plan assigns each force to an objective, in a temporal sequence, with coordination points and contingency plans. The response plan for a tender follows the same logic: each force (reference, method, profile, solution) assigned to an objective (requirement, scoring criterion, win theme), in an argumentative sequence, with verification checkpoints and prepared alternatives.

---

Tactical and strategic objectives

Clausewitz distinguishes the strategic goal -- the ultimate political objective -- from the operational objectives -- what must be accomplished to reach that goal. The two must not be confused. Capturing an objective is not winning the campaign. A local victory can even compromise the whole if it exhausts the forces needed for what comes next.

In pre-sales, the same distinction applies.

The strategic goal: it is not winning the tender. It is winning the tender on the right terms -- a price that preserves the margin, a manageable scope, a client relationship that sets up the next contracts. Winning a tender at a loss, with a vague scope and a dissatisfied client, is an operational victory that turns into a strategic defeat.

The operational objectives:

• Achieve the best technical score -- not the theoretical maximum, but the best realistic score given the available forces and the terrain.
• Secure the pass/fail criteria -- before aiming for excellence, lock down compliance. A brilliant proposal that is non-compliant is a magnificent plan that forgot to protect its flanks.
• Position the win themes -- the key messages that will run through the proposal and that the evaluator will retain. The standalone executive summary is the mission briefing that orients the entire operation.
• Prepare the oral presentation -- the decisive moment. The written proposal is the preparation. The oral presentation is D-Day. This is where knowledge of the terrain (the client), force composition (the team), and the plan converge in a single moment.

---

Friction -- and the art of reducing it

Clausewitz calls friction everything that makes the reality of war differ from the plan. The terrain that does not match the map. The fog that blocks the view. The order that arrives late. The unit that is not in position. The morale that falters.

In pre-sales, friction is everywhere:

• Partial information -- the specifications do not tell everything. Ambiguities are structural. The response plan is built on hypotheses -- and some are wrong.
• Cognitive biases -- the recency bias that recycles the last proposal. Anchoring on the first interpretation. Availability that leads to choosing the wrong references.
• Time -- the deadline that compresses everything. The contributor who has not delivered their section. The rushed review. The executive summary written at the last minute.
• Noise -- jargon, redundancies, recycled sections. Entropy increasing at every stage of the production chain.
• The organization -- unavailable contributors, validations that never arrive, arbitrations that are delayed. The proposal is written in two days, but nobody has read it.

The art of military command is not to eliminate friction -- that is impossible. It is to reduce it to the point where it no longer compromises the objective. Training, procedures, communication redundancy, contingency plans, decentralization of decision-making.

The art of bid management is the same thing. And this is exactly what TenderGraph brings: a system that reduces friction at every stage.

Partial information? Hypotheses are formulated and traced. Biases? The system suffers from neither recency, nor anchoring, nor availability. Time? Production is compressed from three weeks to a few hours. Noise? Entropy is minimized through the ontology and Red Team. The organization? The proposal is available by Day 2, leaving 17 days for validations, reviews, and iterations.

Friction never disappears. But it is reduced to the point where the bid manager can concentrate on what makes the difference: judgment, strategy, client relationships. The acts of command that AI cannot replace.

---

Command

Modern military doctrines distinguish two philosophies of command.

Command by orders: the leader gives detailed instructions, each echelon executes. Rigid, predictable, suited to simple situations.

Command by mission: the leader gives the objective and the constraints, subordinate echelons decide how to achieve it. Flexible, adaptive, designed for complex and uncertain environments.

Traditional bid management is command by orders. The bid manager assigns every section, every paragraph, every contributor. They control every sentence, every figure, every reference. It is exhausting, it is slow, and it does not scale.

AI-augmented bid management must be command by mission. The bid manager defines the win themes, the constraints, the objectives per section. The system executes -- and the bid manager challenges, adjusts, validates. They give direction, not orders. They verify alignment with the objective, not compliance with the instruction word by word.

This is the strategic competency at its highest level: commanding by mission, not by instruction. Trusting the system for execution, reserving judgment for orientation. And intervening at the right moment -- when a hypothesis is wrong, when a win theme does not resonate, when the terrain has changed.

"The bid manager of the future does not write. They lead. And a good response director does not give orders -- they give direction."

---

Key takeaways

The operational framework is not a decorative metaphor. Pre-sales shares with operations planning the same fundamental structure: an adversary (the client's status quo), a terrain (the specifications and the human context), forces to compose (references, methods, team, solution), strategic and operational objectives, friction everywhere -- and a plan that must be robust enough to survive contact with reality.

The best bid managers have always operated this way -- intuitively. What AI enables is systematizing this discipline: mapping the terrain with a rigor that time never permitted, formulating hypotheses instead of guessing them, composing forces based on the terrain rather than habit, and reducing friction to the point where the response director can focus on the decisions that matter.

Key takeaway: Your pre-sales proposal is an operations plan. The adversary is the client's status quo. The terrain is the specifications -- and everything they do not say. Your forces are your references, your methods, your team. Your mission is to help the client overcome their problems -- by composing with the terrain's constraints, the organization's friction, and the fog of partial information. TenderGraph is your staff map: it does not make the command decisions -- it makes the terrain readable so that you can.

---

TenderGraph is a general staff, not an executor. It maps the terrain, analyzes the intelligence, formulates the hypotheses, and reduces friction. Command remains with the human -- because the decisions that win tenders require a judgment that the map does not contain. Our vision rests on this conviction: the best AI in the world does not replace a good response director -- it gives them the means to lead.

---

Further reading:

• Tenders and AI: toward a silent market transformation -- The market transformation: the bid manager shifts from executor to response commander.
• Case study: when AI produces industrial mediocrity -- Operating without a map: the model that produced noise without knowing the terrain.
• The bid manager's worst enemy: themselves -- Cognitive friction: biases are the bid manager's fog of war.
• The executive summary myth -- The executive summary is the mission briefing: if it fails, the entire operation drifts.
• The throughput trap -- Producing faster does not compensate for producing off-target. Throughput without strategy is effort without direction.
• Why your client references convince nobody -- References are the bid manager's most powerful evidence -- provided they are targeted, not stacked.
• What the specifications don't say -- Partial information is the fog covering the terrain. Q&A is field intelligence.
• The information revolution -- Analytical intelligence: separating signal from noise in the specifications' information flow.
• The acceleration of pre-sales cycles -- Compressed logistics: when production is solved, command can focus on strategy.
• Pre-sales skills in the age of AI -- From command by orders to command by mission: the skills of a response director, not an executor.
• Analyzing a tender the way you should analyze the news -- Open-source intelligence: the same analytical discipline for the news and for specifications.