Article Navigation
Ulm, October 1805
In October 1805, Karl Mack expected Napoleon to approach through the Black Forest while Russian reinforcements advanced from the east. French columns instead crossed the Danube and cut the Austrian routes toward Vienna. Fighting tightened the ring around Ulm before Mack agreed to capitulate on October 19. The following day, thousands of Austrian troops marched out and surrendered. The Napoleon Foundation puts that final march-out at 25,000 men; another published account gives 27,000. Napoleon’s maneuver had made a final pitched battle unnecessary, but the campaign was not bloodless.[1][2][3]
The Manifesto for this series said the contractor who knows his ground wins before the work starts. Law 4 argued for keeping the business moving after a setback, while the contractor decision framework focused on making and revising decisions faster. Law 11 applies that thinking to the full job cycle: get a useful quote to the customer, make a reliable scheduling commitment, finish the work properly and invoice without unnecessary delay. Speed matters when it gives the customer a dependable option while the decision is still open.
The Army That Won by Walking
In 1805, Napoleon redirected the army assembled near the Channel toward the Austrian threat. His corps could travel on separate roads and concentrate when needed, allowing a large force to move without depending on a single marching column. The operational lesson is about preparation and positioning: how an army reaches the fight can determine the choices available when it arrives.[2][4]
Mack expected a French advance through the Black Forest and support from the approaching Russian army. French cavalry screened Napoleon’s movement while the main force crossed the Danube and closed the eastern routes. Britannica estimates roughly 210,000 French troops against an Austrian army of about 72,000 across the wider operation. Ulm was therefore not a case of a smaller army overcoming a larger one through speed alone. Napoleon used movement to bring his superior force into position before Mack could coordinate with the Russians.[2]
The encirclement tightened through fighting, including the actions at Wertingen, Günzburg and Elchingen. Austrian columns tried to escape, with different outcomes: some surrendered, while Archduke Ferdinand broke out with cavalry and survivors reached the Russian forces. Mack remained at Ulm without support that could reach him in time. His capitulation ended that position, not every Austrian force involved in the campaign.[1][3]
The final surrender did not require a climactic battle at Ulm because earlier movement and fighting had already narrowed Mack’s options. The corps organization helped French commanders move separately while retaining the ability to support one another. A maxim collected under Napoleon’s name in an 1862 English compilation compares an army’s strength to mass multiplied by rapidity. That is a historical analogy for the effect of movement, not a mathematical formula for business revenue.[2][4][5]
Britannica dates the Ulm operation from September 25 to October 20, 1805. Six weeks later, Napoleon defeated an Austrian-Russian force at Austerlitz. The useful distinction is between the campaign and its conclusion: several battles preceded Ulm’s final capitulation, even though the surrender itself avoided another great battle. Preparation and maneuver helped settle the final outcome.[1][2]
Three Details Worth Carrying
One. Maneuver shaped the final surrender. French troops fought during the campaign, but their position made a final pitched battle at Ulm unnecessary. For a contractor, the analogy is getting the estimate, materials and scheduling decision ready before avoidable delays narrow the customer’s options.
Two. Movement depends on capacity. The maxim attributed to Napoleon is an analogy, not a formula for booked jobs. A smaller shop can remove delays in quoting and scheduling without claiming that speed makes its workforce equivalent to a larger fleet.
Three. Repeatable speed needs structure. The French corps could travel separately and support one another. In a shop, clear quoting limits and scheduling authority let employees act without waiting for the owner to approve every routine decision.
The Contractor Who Marches
Consider two hypothetical shops in the same town, each doing about three million dollars a year. A homeowner’s system quits on Tuesday and she calls both. One shop offers an assessment next week and a quote afterward. The other sends a technician that afternoon, provides a written price and confirms a Thursday start. In this example, she books the second shop before receiving the first quote. The advantage is a useful, credible commitment at the moment she needs one; price, trust and the suitability of the work still matter.
Follow the same hypothetical job through completion and payment. Delays can occur while the quote waits for approval, the crew waits for materials or the completed work waits to be invoiced. Find out which delays actually limit your shop’s capacity rather than assuming every calendar day ties up a crew. Track completed jobs, gross margin, payment timing and callbacks alongside the time saved. Earlier invoices can improve cash timing, while additional completed work still depends on demand, staffing and the jobs you choose.
In the example, the customer values the confirmed start enough to book before the first shop’s quote arrives. Do not assume that explains every lost job. Ask customers why they chose another contractor and compare their answers with your response times, prices and scheduling commitments. That gives you a better basis for changing the process than blaming either price or speed without checking.
Let employees make routine decisions within clear limits. Give qualified technicians a defined quoting range, stage materials for common jobs and let the scheduler commit dates that the crew can actually meet. Define the exceptions that require approval, including unusual scope or costs outside the agreed range. The aim is a process employees can use consistently, not an owner who works faster until the first busy week overwhelms the system.
The Reversal
Faster scheduling is no advantage if the promised date cannot be met or the workmanship suffers. Protect inspection, testing and cleanup when you shorten the job cycle. A quick finish followed by a callback consumes another visit and can damage the relationship you were trying to improve. Remove avoidable waiting while keeping the steps that make the work dependable.
Concentrate the effort on work your shop can deliver well. Chasing every inquiry across a wide area can create travel, scheduling and preparation costs that erase the benefit of a fast response. Choose the services and territory you can support, then give those customers a clear estimate and a realistic commitment.
Five Moves You Run This Week
Move one. Time your whole cycle. Pick your last five jobs and record the dates of first contact, assessment, quote, acceptance, start, completion, invoice and payment. Mark time spent doing the work separately from time spent waiting. Five jobs are a starting sample for finding questions, not a benchmark for the whole market.
Move two. Find the longest pause. Identify where those jobs waited and why. A quote awaiting approval calls for a different fix from a permit delay or a customer-requested start date. Choose a recurring delay your team can control and assign someone to reduce it.
Move three. Improve the first commitment. For routine work you can assess properly, aim to deliver the quote the same day or next day. Tell the customer when a more complex estimate will be ready. Confirm a start date only after checking crew capacity and materials; a fast promise that cannot be kept is not an improvement.
Move four. Build the corps system. Pick one thing that currently waits on you and push the authority down. Let your techs quote inside a set range. Stage the materials for your five most common jobs. Let the scheduler commit a start date. Every choke point you remove is a road the army can march on without you standing in it.
Move five. Close the back of the cycle. Send the invoice promptly when the agreed billing milestone is reached, using the payment terms in the contract. Make the payment instructions clear and track any unresolved scope or billing questions. Measure completion-to-invoice time separately from invoice-to-payment time so you know where the delay occurs.
Key Takeaways
- French maneuver and earlier fighting led to the final capitulation at Ulm without another pitched battle. The campaign itself was not bloodless.
- Speed may give a qualified shop an earlier chance to quote. Whether the customer books before a second quote is a scenario, not an observed rule.
- Mass times velocity is a military analogy. For a contractor, reducing avoidable delays can create capacity, but booked volume still needs measurement.
- In the example, timing changes the outcome. For a real lost job, ask the customer rather than assume price or calendar decided it.
- Repeatable speed comes from structure, not from one man sprinting. Give employees authority to handle routine decisions.
- Fast and focused wins. Fast and sloppy makes mistakes quicker, and fast and scattered just gets you tired. Aim the speed at the jobs worth marching for.
Law 11: Win by marching. Move faster than he can fight.
Reduce avoidable waiting without rushing the work.
Get a useful quote to the customer while the decision is still open.
A faster response gives the shop a chance to earn the job while the customer is deciding.
Related articles in this series
This guide builds on recovery after setbacks in Law 4 and the contractor decision framework.
Apply the five moves above to your own job records before changing the process. The related articles in this series address recovery after setbacks and faster decision-making.
Three Ways to Apply the Laws
Free contractor audit: a 15-factor scorecard, three relevant local competitors and a sequenced 90-day plan, delivered within two business days after qualification, subject to the scope agreed with you
Competitive intelligence applied during website strategy
Managed Websites built on the intelligence: see current managed website plans and pricing
Start with the delay you can document and the commitment your team can reliably keep.
Commercial disclosure: KKS sells website services for contractors. This page has no affiliate purchase links.
Frequently Asked Questions
What does operational speed actually win a contractor?
It can help a shop submit a quote while the customer is still deciding and reduce idle time between jobs. In the hypothetical example, the customer books before the other shop submits a quote. A real customer may wait for more estimates. Whether that turns into more completed jobs or revenue depends on demand, crew capacity, job mix, quality and collections.
How is this different from just answering the phone fast?
Fast phone response is one step. This is the whole march. It is the speed of your entire operation from first contact through quote, start, finish, and payment. A shop can answer fast and still lose because it takes a week to quote and three weeks to start. Law 11 is about compressing the full cycle, not just the first ring.
I am a smaller shop. Does speed really let me compete with the big outfits?
A smaller shop can give customers a prompt assessment, a clear estimate and a reliable start date. Those are useful advantages when larger competitors take longer to respond, but check the actual local competition rather than assuming large firms are slow. Work within your crew’s capacity and judge the change by completed work and customer feedback.
Will moving faster hurt my quality?
Only if you speed up the wrong things. The goal is to cut the dead time between stages, the days a job sits waiting for a quote or a start date, not to rush the work itself. Compress the waiting, protect the workmanship. Removing delays may improve capacity and cash timing. Cutting corners risks costly callbacks.
How do I get faster without personally doing everything?
You build the corps system. Give employees clear decision limits and the materials they need. Let techs quote inside a set range, stage materials for common jobs, and let a scheduler commit start dates. Speed that depends on the owner is a bottleneck. Speed built into the structure runs whether you are there or not.
Does winning on speed mean I have to be the cheapest?
No. A reliable start date can matter to a customer alongside price, workmanship and trust. Explain what you can deliver and when rather than assuming you need to discount. The customer may still compare quotes, so record why jobs were won or lost instead of treating timing as the only reason.
Historical sources
- https://www.napoleon.org/en/history-of-the-two-empires/timelines/austerlitz-2-december-1805-a-timeline. Checked 2026-10-14.
- https://www.britannica.com/event/Battle-of-Ulm. Checked 2026-10-14.
- https://www.napoleon-empire.org/en/battles/ulm.php. Checked 2026-10-14.
- https://the-past.com/comment/war-classic-the-campaigns-of-napoleon. Checked 2026-10-14.
- https://www.gutenberg.org/files/50750/50750-h/50750-h.htm. Checked 2026-10-14.