Sun Tzu for Startups: Compete Without Imitating a Large Company

A startup does not need to reproduce a corporation’s entire catalog in order to offer something different. The question is how to identify a bounded problem it can solve with its resources and verify that the difference matters to the people who would buy the product.

Applying Sun Tzu to a startup requires setting aside the idea that small means agile and large means slow. The guide to Sun Tzu applied to business uses analogies, not rules about company size. The following case is fictional and allows us to examine a product choice, its tests, and its limits.

What it means to focus against a larger competitor

The textual connection is in empty and full in chapter 6: your own concentration, the opponent’s positioning, and adaptation. Its business version asks what need a team can serve without trying to match every capability of another company at the same time. That framing is a contemporary interpretation, not a commercial instruction written by Sun Tzu.

An underserved space is not the same as a proven opportunity. A product may be absent because the problem is uncommon, because it is hard to charge for solving it, or because users prefer another process. The absence of a visible product leaves the question open; it does not confirm demand.

Weakness must be expressed in relation to a task. A platform may offer many functions and still be poorly suited to a specific process. That does not make its provider a weak company, nor does it mean the company does not understand that process. It may simply have chosen not to prioritize it or may solve it through a different configuration.

Sun Tzu’s vocabulary in business helps keep those limits clear. “Concentrating forces” is translated here into defining the scope of work and commitments. It does not imply harassing the competitor, deceiving its customers, or assuming it will disappear once an alternative is published.

A fictional case: simplifying maintenance reports

Imagine a startup with four people: three build the product and one combines implementation and customer support. Its possible market is small maintenance businesses whose technicians log visits from their phones. The initial goal is to test whether it can reduce repeated data entry between the technician’s report and the administrative review.

In the example, a corporation offers a broad platform that includes scheduling, inventory, and invoicing. The startup does not have the resources to reproduce that catalog. Nor has it shown that users want to replace it. Its hypothesis is narrower: some companies need to improve report closure without changing the rest of their tools.

The segment is defined by that process, not only by the customer’s size. A small company with highly customized jobs may need something different from another company that carries out repetitive interventions. Mixing them in the same test would make it harder to understand which need is being validated.

Suppose the team sets aside six weeks for a prototype. That timeframe belongs to the fictional case; it is not a universal recommendation. The scope includes recording an intervention, reviewing the data, and exporting the result. It excludes full accounting, warehouse management, and specific adjustments for each possible buyer.

The proposed differentiation is completing that workflow with less manual transcription. “Simpler” would be an imprecise promise if it did not define which task is being simplified. By contrast, observing whether the technician and administration can close the same report without re-entering information makes it possible to discuss a concrete difference.

The test should not be limited to asking whether people like the app. Within the example, what matters is observing the current process, carrying out an equivalent task with the prototype, and recording where help is needed. It is also important to check whether the person using the product and the person approving the purchase value the same outcome.

Errors and support time are part of the evaluation. If each implementation requires several days of custom work, the team may be building a custom service instead of the product it imagined. That discovery is not necessarily a failure, but it changes the resources required and the promises it can sustain.

Depending on a single person to implement and handle issues introduces another limitation. Getting more trials than that person can support would not demonstrate scalability. The case requires examining post-sale work, not just how many people agree to a demo.

The test can produce different outcomes. It may confirm a repeatable improvement, show that the current tool already solves the problem once configured, or reveal that the savings do not justify the change. The broader exploration of those possibilities belongs to the search for market niches; here the focus is on how they shape this team’s decision.

When specialization stops making a difference

The corporation might add a similar function, modify its offering, or maintain its priorities. None of those responses should be assumed in advance. Basing the whole project on the idea that the competitor will not react confuses someone else’s decision with a condition under your own control.

Nor is it enough to observe a similar function and conclude that the difference has disappeared. You would need to compare the workflow users need, the implementation, and the support. The criterion remains the problem being addressed, not the number of matching checkboxes in two catalogs.

There are signs that would force a review of the case: every customer requesting a different product, the integration preventing the result from being used, or no one considering a change in process necessary. Adding more functions to avoid acknowledging those signs can undo the initial focus without solving its cause.

Economic pressure does not turn a hypothesis into an opportunity either. Sun Tzu’s reading in a business crisis distinguishes coordination and urgency from a desperate bet. Needing revenue does not prove that a new product line will generate it in time.

The example’s outcome is left open. A reasonable decision could be to continue with a limited scope, reframe the proposal, or stop the test. What makes it possible to evaluate is the relationship between the observed need, delivery capacity, and the evidence obtained. The size of the company does not answer any of those questions on its own.

Before expanding the product, check whether the observed difference repeats without depending on exceptional attention. An isolated case does not prove the team can sustain the same promise for other customers.

View all articles in Sun Tzu in Business: Resources, Competition, and Decisions