Sustain | The GTM Field Manual

Win, then decay

Teams pour everything into the attack and nothing into holding. They land the customer, then churn them. They hire the rep, then burn them out. They build the system, then let it rot. The result: every gain is temporary, and you're perpetually re-winning the same ground.

1

All attack, no holding

The budget, the energy, the narrative: all of it goes to winning new ground. Nothing is left to keep the ground already won.

2

Every gain is temporary

Customers churn, systems rot, people burn out. What looked like a win becomes a cost you pay again.

3

Re-winning the same ground

The most expensive customer is the one you already had and lost. The most expensive rep is the one you hired twice.

4

The rule everyone skips

Of the five fundamentals, four are about winning. The fifth is about not losing what you won. Everyone reads the first four.

The military principle: sustain the force

Combat has five fundamentals. Four are about winning. The fifth is about not losing what you won: supply, maintenance, rest, care of the force.

A

Win, then neglect

Take the objective, then move on. No supply, no maintenance, no rest. The best attack in the world dies of neglect three days in.

B

Sustain the force

Supply, maintenance, rest, care. The boring work that decides whether the win holds. Logistics wins wars.

The force that can't be sustained can't win, no matter how good its attack is.

Sustain is two things

Retention, and the feedback loop. One keeps what you won. The other makes everything smarter.

🤝

Retention

Take care of what you've already won: customers, team, systems, relationships. The cheapest revenue is the customer you already have.

🔁

The feedback loop

What converted? What churned? Feed it back into recon, the estimate, and the decisive point. The loop turns a manual into an engine.

🛡️

The moat

A system that learns from every deal compounds into an advantage competitors can't catch. They're still running movement-to-contact.

“Winning is cheap. Keeping what you won is the whole game.”

Koka Sexton

The operating cycle: the manual is a loop

sustain.dashboard

1 · ReconSee who's warm · Chapter 1

2 · EstimateDecide whether · Chapter 2

3 · Decisive PointFocus the force · Chapter 3

4 · Command & ControlCommit the team · Chapter 4

5 · SustainCompound and feed back · Chapter 5

→ Back to ReconThe loop never ends

The procedure: sustain and compound

Five steps. The first two stop the bleeding. The last three make the system compound.

1

Audit what you're holding

Customers, team, systems, relationships. List them, then ask what's decaying. Decay is silent until it's a loss.

2

Fix the leak before the attack

Churn, burnout, rot. Stop the bleeding before you pour in new fuel. Winning faster while leaking is just losing faster.

3

Build the feedback loop

Every win and loss gets logged back into recon. What worked? What didn't? Why? If it isn't logged, it didn't happen.

4

Reinforce what converts

Feed the loop's findings into the decisive point. Double down on what the data says works, not what the calendar says is next.

5

Rest the force

Including yourself. Sustainment is not optional. It's the difference between a sprint and a system.

🔄

Close every loop

What worked feeds what's next. That handoff is the whole engine.

Where it applies

Sustain is the chapter everyone skips, and it's where the compounding actually lives.

💰

Retention over acquisition

The existing customer is the highest-ROI target. Churn is the silent killer. Fix retention before you fund acquisition.

🏰

The loop is the moat

A system that learns from every deal compounds into an advantage competitors can't catch. They're still spraying cold lists.

⚡

You are the force

Rest, recovery, the basics. The system runs on your energy, or it doesn't run. Sustaining yourself is strategy, not indulgence.

Secure what you won before you attack again. And close every loop: what worked feeds what's next.

Koka Sexton

The GTM Field Manual

A written operating system for go-to-market: military doctrine translated for business. One chapter publishes at a time. The frameworks are public. The operating rules behind them are not.

Part I · The Operating System

Chapter 1 · Reconnaissance Pull READ NOW

Chapter 2 · The Estimate READ NOW

Chapter 3 · The Decisive Point READ NOW

Chapter 4 · Command & Control READ NOW

Chapter 5 · Sustain READ NOW

Part II · Tempo & Tactics

Chapters 6-8 · The OODA Loop, The Ambush, Precombat ChecksCOMING SOON

Part III · Read the Battlefield

Chapters 9-14 · Terrain, Center of Gravity, Warfare, Positioning, Counter-Recon, InflectionCOMING SOON

Part IV · Multiply & Adapt

Chapters 15-19 · Force Multipliers, Branches, Main Effort, After Action Review, RehearsalsCOMING SOON

Part V · The Operator

Chapters 20-23 · Simplicity, The Reverse, Negotiation, Defense in DepthCOMING SOON

← Previous: Command & Control

Up Next · Part II

Chapter 6 · The OODA Loop

Out-cycle, don't out-plan. Decide on good-enough, act, re-observe instantly. Coming soon.

Back to the Field Manual

Get each chapter as it publishes

The collection grows one framework at a time. Start with Chapter 1, or apply the doctrine to your own go-to-market.

Explore the Field Manual Apply this to your GTM

The frameworks are public. The operating system behind them is not.