Sun Tzu for startups: competing without imitating a large company

A startup does not need to replicate a corporation’s full catalogue to put forward a different offer. The question is to find a bounded problem it can solve with its resources and to check that this difference matters to the people who would buy the product.

Applying Sun Tzu to a startup requires abandoning 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 bigger competitor

The textual connection lies in empty and full in chapter 6: your own concentration, the opponent’s disposition and adaptation. In business terms, it asks what need a team can serve without trying to match every one of another company’s capabilities at the same time. That formulation is a contemporary interpretation, not a commercial instruction written by Sun Tzu.

A poorly served space does not automatically equal a proven opportunity. An offer may be missing because the problem is rare, because it is hard to charge for solving it, or because users prefer another process. The absence of a visible product leaves an open question; it does not confirm that demand exists.

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

Sun Tzu’s vocabulary in business helps keep those boundaries in place. ‘Concentrating forces’ here means defining work and commitments. It does not mean harassing the competitor, deceiving its customers, or assuming it will disappear once an alternative is published.

A fictional case: simplifying maintenance reports

Imagine a four-person startup: three people develop the product and one combines implementation and customer support. Its possible market is small maintenance businesses whose technicians log visits from their mobile phones. The initial goal is to check whether repetition of data can be reduced 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 replicate that catalogue. Nor has it shown that users want to replace it. Its hypothesis is narrower: some businesses need to improve report closure without changing the rest of their tools.

The segment is defined by that process, not just by the customer’s size. A small business with highly customised jobs may need something different from another 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, not a universal recommendation. The scope includes logging an intervention, reviewing the data and exporting the result. It excludes full accounting, stock management and specific adaptations for each possible buyer.

The proposed differentiation is to complete that workflow with fewer manual re-entries. ‘Simpler’ would be an imprecise promise if it is not defined which task is being simplified. By contrast, observing whether the technician and administration can close the same report without re-entering information allows a concrete difference to be discussed.

The test should not be limited to asking whether people like the app. Within the example, the aim is to observe the current process, carry out an equivalent task with the prototype, and record where help is needed. It also matters 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 assessment. If each implementation requires several days of tailored work, the team may be building a custom service rather than the product it imagined. That discovery is not necessarily a failure, but it changes the resources required and the promises it can sustain.

Reliance on one person to implement and handle issues introduces another limitation. Getting more trials than that person can support would not prove growth capacity. The case requires examining post-sale work, not just how many people accept a demo.

The test can produce different results. 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 general investigation of those possibilities belongs to market niche search; here, the point is how they shape this team’s decision.

When specialisation stops adding a difference

The corporation might add a similar feature, modify its offer or keep its priorities. No response should be taken for granted. Basing the whole project on the competitor not reacting confuses someone else’s decision with a condition under your own control.

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

There are signs that would require revisiting the case: if each customer asks for a different product, if the integration prevents the result from being used, or if no one thinks changing their process is necessary. Adding more features 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. Reading Sun Tzu in a business crisis distinguishes coordination and urgency from a desperate gamble. Needing revenue does not prove that a new product line will generate it in time.

The outcome of the example remains open. A reasonable decision could be to continue with a limited scope, reframe the proposal or stop the test. What allows it to be assessed is the relationship between observed need, delivery capacity and 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 relying on exceptional support. 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