Competitive intelligence with open sources: a reading of Sun Tzu

Knowing a competitor's offer does not mean knowing all their plans. Competitive intelligence starts with a specific question and requires distinguishing between what is published, what is verified, and what is only a hypothesis.

Competitive intelligence inspired by Sun Tzu can be approached as a process of questions, checks and reviewing conclusions. Within Sun Tzu applied to business, this reading focuses on public information and responsible analysis. It does not present industrial espionage as a legal 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 calculations. The five kinds 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 say which information would change a decision. Asking what an offer includes for a certain type of customer makes it possible to identify relevant documents and recognise what those documents still do not explain.

It is also necessary to define what is meant by competitor. Another company may be relevant, but so may the possibility that the customer keeps their current process. Sun Tzu's vocabulary in business allows that comparison to be separated 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 subsequent use is permitted. Specific practices need 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 their published offer includes and what part the customer would have to resolve by other means.

For that example, the sales description, usage documentation and public service terms would be relevant. A general article on the provider's history might add context, but it would not necessarily answer the question about a specific rollout.

Each finding needs to preserve its source, date of access and scope. A document may describe an earlier version or an offer available only to certain customers. Recording those conditions helps avoid a limited claim being presented as a universal feature.

It is also worth noting 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 makes a claim about the company that may require other checks.

Checking without counting repetitions as independent evidence

Suppose a sales note announces support during the launch. The public documentation describes the tasks included and makes clear that certain adjustments are excluded. The second piece allows the announcement to be made more precise. It would not be rigorous to summarise 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 claim repeated several times. When assessing the support for a conclusion, what matters is how the information was obtained, not just how many pages contain similar wording.

A discrepancy should also be preserved. If two documents appear 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 note the uncertainty instead of silently choosing the most convenient version.

Interpreting and explaining what remains unknown

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 by the service description alone.

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 deal with them.

The risk of ignoring the enemy helps explain why internal analysis can be insufficient. The reverse caution also matters: knowing part of another company's offer does not authorise reconstructing its entire strategy or future decisions as fact.

A useful report distinguishes between what was observed, the proposed explanation and the fact 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 remove those distinctions. Accumulating records can repeat the same error, mix versions or amplify an incorrect classification. Before interpreting a pattern, it is worth knowing what each data point represents and what was left out of the collection.

When personal data are involved, the question is not limited to whether they can be found. The purpose of processing, its scope and the conditions of access require specific review. A reference to Sun Tzu does not resolve privacy obligations or authorise building personal profiles that are unnecessary for the business decision.

Mystery shopping or mystery shopping also should not be included as an automatically permissible practice. Its assessment 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 a similarly clear separation. Assessing experience and skills does not mean requesting internal documents, client lists or confidential plans from another company. Bringing a person on board does not turn their previous access to information into permission to use it.

In a startup's strategy against a giant, external information helps to verify a specific difference. That is the practical limit of the comparison: understanding a need and reviewing your 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 force it to be reconsidered. For any specific method of obtaining or handling information, request legal and privacy review.

View all articles in Sun Tzu in business: resources, competition and decisions