---
title: "Competitor facts"
description: "How competitor knowledge is gathered, what it is used for, and the rule that governs mentioning a competitor publicly."
updated: "2026-08-18"
verifiedAgainst:
  - packages/shared/src/knowledge.ts
  - packages/shared/src/competitor-intake.ts
  - packages/shared/src/strategy.ts
---

Each approved competitor becomes an entity of kind `competitor`, with facts held
to the same source discipline as your own.

## What is gathered

Public pages: what the product does, how it is positioned, what it integrates
with, and what its own pages say about pricing and limits. Nothing private, and
nothing behind a login.

## What it is used for

- Comparison articles that are accurate about the other side.
- Positioning that reflects the market rather than a guess about it.
- Signals for [Competitor Blog Watch](/growth/competitor-watch), if you enable it.

## The competitor rule

Your strategy carries a policy for how generated content may mention
competitors:

| Rule | Behaviour |
| --- | --- |
| `never` | Competitors are not named in published content |
| `mention` | Competitors may be named where relevant |
| `compare` | Direct comparison is allowed |

It is a founder level decision because it shows up in public writing and is
awkward to reverse.

## Removing a competitor

Removing one stops further gathering and takes it out of future work. Facts
already used in published posts stay in those posts, which is deliberate: an
article that has been live for months should not silently change its argument.