A startup does not need to reproduce a corporation’s full catalogue in order to offer something different. The question is how to find a defined 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 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 link lies in empty and full in chapter 6: one’s own concentration, the adversary’s disposition and adaptation. In business terms, it asks what need a team can serve without trying to match all of another company’s capabilities at once. That formulation 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 method. 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 particular process. That does not make its provider a weak company, nor does it mean it does not understand that process. It may simply have chosen not to prioritise it, or to solve it through a different configuration.
Sun Tzu’s vocabulary in business helps keep those limits in view. ‘Concentrating forces’ translates here into defining work and commitments. It does not mean harassing the competitor, deceiving its customers, or assuming it will disappear when an alternative is published.
A fictional case: simplifying maintenance reports
Imagine a startup of four people: three develop the product and one combines implementation and customer support. Its possible market is small maintenance businesses whose technicians record visits from a mobile phone. The initial aim is to see whether repetition of data between the technician’s report and the administrative review can be reduced.
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 catalogue. 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 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; it is not a universal recommendation. The scope includes recording an intervention, reviewing the data and exporting the result. Left out are full accounting, warehouse management and the specific adaptations for each possible buyer.
The proposed differentiator is completing that journey with fewer manual transcriptions. ‘Simpler’ would be an imprecise promise if it does 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, the point 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 authorising its purchase value the same outcome.
Errors and support time are part of the assessment. If every implementation requires several days of bespoke work, the team may be building a customised service rather than the product it had in mind. That discovery is not necessarily a failure, but it changes the resources needed and the promises it can sustain.
Relying on a single person to implement and handle incidents introduces another limitation. Securing more tests than that person can support would not prove the ability to scale. The case requires examining work after the sale, not just how many people accept a demonstration.
The test may 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 broader investigation of those possibilities belongs to market niche search; here the focus is on how they shape this team’s decision.
When specialisation stops making a difference
The corporation might add a similar feature, change its offer or keep its priorities. None of these responses should be taken for granted. Building the whole project on the assumption that the competitor will not react confuses someone else’s decision with a condition under your own control.
Nor is it enough to spot a similar feature and conclude that the difference has disappeared. You would need to compare the journey users need, 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 the case to be reviewed: every customer asking for a different product, integration preventing the result from being used, or no one seeing any need to change their process. Adding more features in order 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 bet. Needing revenue does not prove that a new product line will produce it in time.
The outcome of the example is left open. A reasonable decision might be to continue with a limited scope, reformulate the proposal or stop the test. What allows it to be assessed 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 relying on exceptional attention. An isolated case does not show that the team can sustain the same promise for other customers.
View all articles in Sun Tzu in business: resources, competition and decisions
