Waging War

5 min read

Core idea

If Laying Plans was about the decision to fight, Waging War is about the cost of fighting and the consequences of letting that cost run. Sun Tzu opens with a logistics inventory — a thousand chariots, ten thousand soldiers, a thousand leagues of provisions — to drive home a single point: a campaign is the most expensive thing a state can do, and its expense compounds the longer it lasts.

The topic is therefore organised around a paradox. War must be decisive (you cannot win by drawing it out) but it must also be affordable (you cannot win if you bankrupt your own state in the trying). The way out is speed and living off the enemy's supplies. "We have all heard of victories that result from a quick strike by a mediocre opponent, but we have yet to hear of a single victory gained by clever schemers who let the hostilities drag on."

Sun Tzu's argument: "In arms, those who value victory eschew lengthy engagements."

Why it matters

Time is the dimension where strategy bleeds

Most strategy literature treats time as a neutral substrate. Sun Tzu treats it as the primary cost variable. Every day a campaign drags on, weapons dull, troops weaken, provisions deplete, prices inflate, and — crucially — other actors notice. The third party who pounces while you are tied up is the deepest fear in the topic: prolonged engagement is an invitation to a fresh attacker.

The home base pays the price

Sun Tzu is unusually concrete about who bears the cost: not the army, but the farmers and the heartland. Long supply lines impoverish the kingdom along the route; prices rise; households empty; "seventy percent of the commoners' ready cash will be used up." A modern manager can substitute "the team," "the runway," or "the customer base" for the heartland: it is the resource base that quietly subsidises the campaign, and it is the resource base that runs out first.

Resupply from the opponent

The most pragmatic of the topic's maxims: "For every cartload of grain seized from the enemy, he saves twenty on his own side." The implied multiplier is enormous. The point is not merely thrift; it is that the same grain weakens the opponent and strengthens you simultaneously. In modern terms: hires from competitors, customers won from incumbents, knowledge captured from acquisitions — all do double work.

Key takeaways

Mental model

Mental model

A grammar of war's costs

Direct costs

Sun Tzu's opening inventory is a remarkable piece of writing — it is almost an Excel sheet from 500 BCE. Chariots, armour, provisions, foreign and domestic outlays, expenditures for clients and retainers, glues and lacquers (for crossbow stocks and shafts), a thousand ingots of gold per day. The catalogue exists to make a single point: before you raise the army, know what one day of war actually costs you. Strategy without a denominator is dangerous fantasy.

Indirect costs — inflation and depletion

Once the army is in the field, the second-order effects cascade. Long transport lines impoverish a kingdom and impoverish farmers. Wherever the troops travel, prices rise. Inflation depletes the farmers, the farmers cannot render service, the heartland empties of viable households. Sun Tzu puts a number on it: seventy percent of commoners' cash, sixty percent of the ruling house's wealth — "broken carriages and worn-out nags, money for armour, helmets, arrows and crossbows."

Strategic costs — the third party

"The local lords will be quick to pounce on any weaknesses." This is the cost that does the most damage and is least often modelled. A prolonged engagement is not just an expensive engagement; it is an advertisement of vulnerability to every other actor in the system. The most dangerous opponent in a long war is rarely the one across the field — it is the one waiting on the sideline.

Practical application

Set an explicit time budget

Before any major commitment, name the date by which the campaign must be over. If you cannot articulate why this date matters, you do not yet have a strategy — you have an aspiration. The time budget is what forces the rest of the planning to be honest about scope.

Resist the siege

A siege, in Sun Tzu's account, is the worst possible operation: months of preparation, one-third of your men dead on the wall, and the city still standing. Modern equivalents: the year-long enterprise sales cycle for a single logo, the multi-quarter integration after a contentious acquisition, the open-ended rewrite of a competitor's product feature for feature. When you find yourself "sending troops up the walls like ants," stop. Find a different objective.

Reinforce by capture, not by re-recruitment

"An expert good at deployment never needs a second troop call-up or a third round of requisitioning supplies." In business: hire the senior engineer who knows the competitor's stack rather than spending eighteen months training your own; acquire the small competitor instead of building their feature; recruit the analyst who used to write reports about you. Every captured asset works twice — once by joining you, once by leaving them.

Example

A startup is competing with a well-funded incumbent for a category-defining customer. The natural plan: spin up a deal-team, drop everything else, run a six-month full-court press. By the end of month three, two engineers have left because they have shipped nothing visible to the rest of the team, the cash runway has shrunk from twelve months to eight, the broader market has moved on, and a third competitor has used the period to ship the feature both incumbents were arguing about.

The Waging War reading: the team treated the deal as a campaign without setting a time budget or counting the indirect costs. The decisive question was not "can we close this account?" but "is this account worth a siege, given what the siege costs us with the other accounts, the team, and the market?" The wiser play was either a quick decisive push (offer something the incumbent cannot match in two weeks and force the choice) or a graceful withdrawal to a different ground. Either way, the cost of time is the budget that should have been set first.

Continue exploring

Tags