You searched “product-led growth” or PLG because someone told you: let the product be the siege engine — self-serve, viral loops, expand seats, and you win. You want to know whether to rebuild around that engine. This page does not teach a PLG funnel. It gives one judgment first: if growth only works by pressing attention, wallets, or champions through the product, you are still besieging — just with a UI. Ask three questions before you treat that engine as default.
“Let the product attack” sounds like spending fewer. It may only be siege with a different skin
In business today, product-led growth usually means growing more through self-serve product, sharing, and seat expansion, and less through hard outbound push. That is a modern idea; Sun Tzu never said it. What you read here is this site setting it next to the Energy chapter only to borrow one judgment.
The chapter’s judgment on this site is short: “Use momentum to shorten conflict and spend fewer people. Ordinary force is enough when timing and coordination line up — you do not need more destruction.” If you only move the old pressure into notifications, paywalls, and seat traps, you have not spent fewer people; you have hidden the spend inside the product. The page then asks: “Once combined, do the forces point toward less waste, or more escalation?” If the direction is escalation, it is still siege.
Check one: does this motion spend fewer people — or hide the spend inside the product?
Count who is paying time, attention, and relationship cost. If outbound effort drops but users are nudged daily, pushed to upgrade, and asked to pull others into seats, the spend only changed hands. Ask yourself: if you turned those pressure surfaces off tomorrow, would growth still hold?
If it would, the product may be forming real momentum, and this ground may fit you. If it collapses, admit it: the engine is continuous pressure, not product value. The classical line says 故善战者，求之于势，不责于人, which this site’s English gives as “those skilled in warfare seek to create advantageous momentum rather than demand perfection from their soldiers.” Dumping pressure on everyone who opens the product is demanding from people, not seeking momentum.
Check two: are you earning a next voluntary use, or forcing expansion through friction?
List what you plan to ship this quarter and ask of each item: does this make people want to come back, or make it harder to leave, downgrade, or refuse an upgrade? The first is voluntary use; the second is friction. Not every friction is wrong; some steps need a real confirm. But you should know it is pressure you carry, not momentum you won.
Run a plain check on people who stayed recently. Did they stay because the product works, or because cancel is painful, seats are locked, and the path they need sits behind a paywall? If you can answer, you know what you are building. One check on the chapter page fits: “Are you building conditions, or demanding perfection from people?”
Check three: when “product-led” only means more siege surfaces, when do you stop?
Write yourself a stop rule: if the next stretch of “product-led” growth comes mainly from more notifications, paywalls, and seat locks rather than helping people get results with less effort, you stop and change posture. Do not treat PLG as a fight you must take by default.
This site’s Energy page puts the next step plainly for you: write the combination and the moment that would create momentum and reduce fighting; next, verify only whether coordination happens. Bring that home to your own case: your team, your users, the people willing to open the product next round. Protecting a spend-fewer path is harder to copy than turning the product into a siege tool, and it is one less needless fight.
Questions people ask after searching “product-led growth”
Did Sun Tzu talk about product-led growth?
No. PLG, self-serve expansion, and viral loops are modern business terms. Sun Tzu never discussed them, and this site does not present them as his idea. This page borrows only one judgment from the Energy chapter: use momentum to shorten conflict and spend fewer people. If you read that Sun Tzu already explained product-led growth, that is a stretch. Keep the source text, the translation, and your modern reading apart.
Does that mean I should never build self-serve or seat expansion?
Not at all. Self-serve can spend fewer people, and shared seats can make work easier. The question is what you treat them as. As aids to spend fewer, you will ask whether people return by choice. As a siege engine, you will keep adding pressure surfaces. Ask yourself: if users could leave or downgrade tomorrow with no friction, would you still sleep well?
Rivals are all pushing PLG. If I don’t, will I fall behind?
First ask whether your force still points toward spend fewer. Someone else’s default win is not automatically your ground. If you rebuild the company only because rivals push PLG, they are moving you. Write down why people would still open your product after you turn the pressure off. If you can, put your effort there. If you cannot, the “engine” you build will still be a siege.
How do I tell spend-fewer apart from spend hidden in the UI?
Keep two ledgers: how much outbound effort your team saved, and how much extra attention, forced upgrades, and internal-champion persuasion your users now pay. If the first falls and the second rises, the spend moved into the product. You can also count your roadmap: how many items reduce friction, and how many add siege surfaces.
Is this the same as the bingshi, flywheel, PMF, lean, or network-effects essay?
No. The bingshi spend-fewer piece owns the chapter judgment itself, with no PLG frame. Flywheel refuses keep-pushing. PMF refuses whatever-it-takes until fit. Lean refuses fail-fast as the default open. Network effects refuses lock-in as a moat. This piece owns refusing “product as siege engine” as the default win for you. Do not make those other frames the main subject here.
What should I do after reading this?
Write three lines: what growth still rests on after you turn pressure off; which items this quarter earn voluntary use and which add siege surfaces; and your stop rule if “product-led” only means more siege surfaces. If you cannot write the first line, stop there. If you can write all three, open the Energy chapter and set your answers against the four checks on the chapter page.
The next step is not another plan for turning the product into a siege engine. Ask whether you spend fewer or hide the spend, separate voluntary use from friction, and write your stop rule. That judgment is the one this chapter is named for here: Spend fewer. If your team wants this check first, Contact Us. We talk teaching, training, and content, not how to besiege people with a UI. We reply within two business days.