Knowing what a competitor offers does not mean knowing all of their plans. Competitive intelligence starts with a specific question and requires distinguishing what is published, what is verified, and what is only a hypothesis.
Competitive intelligence inspired by Sun Tzu can be approached as work of questions, verification, and review of conclusions. Within Sun Tzu Applied to Business, this reading focuses on public information and responsible analysis. It does not present industrial espionage as a legally permissible activity by definition.
What is taken from Chapter 13 and what changes when it is brought into the company
Chapter 13 links knowledge of the adversary with information obtained from people, rather than replacing it with conjecture or calculation. The five types of spies in Chapter 13 develop that military argument. Their application to open sources is a contemporary adaptation, not an equivalence between each ancient agent and a digital tool.
The business question needs a limited scope. “Knowing everything about the competition” does not indicate what information would change a decision. Asking what a specific type of customer offer includes makes it possible to identify relevant documents and recognize what those documents still do not explain.
It is also necessary to define what is meant by competitor. It may refer to another company, but also to the possibility that the customer keeps its current process. The vocabulary of Sun Tzu in business makes it possible to separate that comparison from a view in which any interlocutor becomes an enemy.
In this guide, working with open sources means starting from published and accessible information, without accessing other people’s accounts or requesting confidential material. Accessibility does not prove that any later use is permitted. Specific practices require legal and privacy review; this article does not determine their legality.
Collecting, comparing, and interpreting are different tasks
Collecting from a question
Imagine a fictional company that wants to understand what support a competitor offers during the rollout of a service. The question is not whether that competitor is “better,” but what work its published offer includes and what part the customer would have to resolve by other means.
For that example, the commercial description, usage documentation, and public terms of the service would be relevant. A general article about the provider’s history could add context, but it would not necessarily resolve the question about a specific implementation.
Each finding needs to preserve its source, consultation date, and scope. A document may describe an earlier version or an offer available only to certain customers. Recording those conditions helps avoid presenting a limited statement as if it were a universal feature.
It is also wise to note absences without turning them into conclusions. “It is not explained in the documents reviewed” is different from “it does not exist.” The first sentence describes the result of the search; the second claims something about the company that could require other checks.
Comparing without counting repetitions as independent evidence
Suppose a sales note announces support during launch. The public documentation describes the tasks included and clarifies that certain adjustments are excluded. The second piece makes it possible to sharpen the announcement. It would not be rigorous to summarize both by saying that any implementation work is included.
If several media outlets reproduce the same note, their agreement does not necessarily provide independent verification. There may be a single original statement repeated multiple times. When assessing the support for a conclusion, how the information was obtained matters, not only how many pages contain similar wording.
A discrepancy must also be preserved. If two documents seem to describe different conditions, it is necessary to check whether they correspond to different dates, versions, or recipients. When that cannot be clarified, the report should state the uncertainty instead of quietly choosing the more convenient version.
Interpreting and explaining what still is not known
In the fictional case, what is confirmed could be that there is published support with a specific scope. A different hypothesis would be that the provider is trying to reduce adoption difficulties. That intention may seem plausible, but it is not proven solely by the service description.
The consequence for our company would be to review what its own customer needs during implementation. Copying the competitor’s offer does not automatically follow from the finding. First, it would be necessary to check whether the same difficulties appear and whether the team has the capacity to address them.
The risk of ignoring the enemy helps explain why internal analysis can be insufficient. The opposite caution also matters: knowing part of someone else’s offer does not authorize reconstructing their entire strategy or future decisions as facts.
A useful report distinguishes what was observed, the proposed explanation, and the data that could change that explanation. If it cannot specify which decision the finding affects, it may be collecting interesting information without answering the original question.
Big data, mystery shopping, and former employees: limits of the analogy
Analysis of large volumes of data does not eliminate those distinctions. Accumulating records can repeat the same error, mix versions, or amplify an incorrect classification. Before interpreting a pattern, it is important to know what each data point represents and what was left out of the collection.
When personal data are involved, the question is also not limited to whether they can be found. The purpose of the processing, its scope, and the access conditions require specific review. A reference to Sun Tzu does not resolve privacy obligations or authorize building personal profiles that are unnecessary for the business decision.
Mystery shopping should not be included as an automatically permissible practice either. Its evaluation requires attention to the context, the form of interaction, and the data intended to be recorded. This reading does not propose false identities or procedures for obtaining restricted information.
Hiring former employees also deserves an equally clear distinction. Valuing experience and skills does not mean requesting internal documents, customer lists, or confidential plans from another company. Bringing someone on board does not turn their prior access to information into permission to use it.
In a startup’s strategy against a giant, external information helps confirm a specific difference. That is the practical limit of the comparison: understanding a need and reviewing the company’s own proposal, without attributing to the competitor intentions that have not been documented.
Before considering a conclusion closed, identify its evidence, its limits, and what data would require revisiting it. For any specific method of obtaining or processing information, request legal and privacy review.
View all articles in Sun Tzu in Business: Resources, Competition, and Decisions
