PostHog publishes its org chart. Go read it.

Most competitive research starts at the marketing site, because that is the surface built to be read. PostHog has a stranger artifact: a handbook, published at the same domain as the pricing page, written for its own employees and left open to everyone else.

It is not a careless leak. PostHog decided transparency was worth more than the intelligence it gives away. That decision is the reason the document is useful — a page written for insiders answers questions a landing page is designed to avoid.

Here is what it actually tells you, and what the reading technique generalizes to.

The structure section is an org chart with intent

PostHog organizes around small autonomous teams, each owning a product area end to end. The handbook names them, describes what each one is responsible for, and explains the reasoning behind keeping them small.

Read as competitive intelligence, that section does three things at once.

It tells you the product surface area — not the marketing taxonomy of "the PostHog platform," but the internal division of labor, which is a more honest map of what the company thinks it sells. It tells you relative investment: a product area with a dedicated team is a bet, a product area folded into someone else's team is a side project. And when the team list changes — a new one appears, two merge, one quietly loses its name — you are watching a strategy shift happen before any announcement.

The same signal exists at most companies, just harder to read. Elsewhere you reconstruct it from job postings and LinkedIn titles, which is slower and noisier. We wrote about that reconstruction in what a competitor's hiring page tells you first. PostHog skips the reconstruction step and hands you the answer.

The strategy pages tell you what they refuse to build

The parts of the handbook that describe company strategy are more valuable than the parts that describe the products, and for an unobvious reason: they contain refusals.

A roadmap tells you what a company will do. A strategy document tells you what it has decided not to do, and why. PostHog's handbook is explicit about the kind of company it wants to be — developer-first, product-led, self-serve by default — and each of those commitments implies a set of things it will keep declining. That is where competitive positioning actually lives.

If you sell against a company whose stated strategy is self-serve and developer-first, the gap is not a feature. The gap is every buyer whose procurement process needs a human, a contract negotiation, a security questionnaire answered by a person. A strategy page tells you which customers your competitor is structurally bad at serving, which is more durable than any feature comparison. Features ship in a quarter. A stated commitment to self-serve takes years to walk back.

The corollary matters too. When a company with that stance starts adding enterprise machinery — SSO tiers, contract-only plans, a sales-assist motion — the handbook language usually shifts first, before the pricing page does. That lag is the interesting part.

The compensation and pricing logic explains the price list

Two sections that look like housekeeping are the ones a pricing team should read.

PostHog publishes how it thinks about compensation — the benchmark, the location adjustment, the philosophy. And it publishes the reasoning behind its usage-based pricing, not just the numbers. Together those explain the price list in a way the price list never does.

Cost structure constrains pricing. A company with a stated compensation approach and a published headcount philosophy has told you roughly what it costs to run, which tells you how much room it has to discount, and how sustainable an aggressive free tier actually is. A generous free tier from a company with heavy enterprise sales costs is a different animal from a generous free tier from a company optimized for self-serve — the second one can hold the line indefinitely.

The pricing rationale also tells you what future price changes will look like. A company that has publicly committed to a per-event, pay-as-you-go model has boxed itself in. Its next move is almost certainly a new metered dimension, not a seat-based repackaging. That is a forecast you can make from a document, not a rumor. Datadog's price list works the same way once you know how to read it — we took that apart in Datadog's price list is an org chart.

What to do with a handbook you did not expect to find

Public handbooks are rare but not unique. GitLab has one. A number of remote-first companies do. Some publish only a slice — an engineering handbook, an open roadmap, a public strategy memo — and the slice is enough.

When you find one, three moves are worth the time.

Read it once, fully, as a person. This is the part software cannot do for you, and it is where most of the value is. A handbook rewards an attentive human read in a way no diff feed does.

Note its structure — the URL patterns, the section names, the pages that would change if strategy changed. Then watch those specific pages, not the whole site.

And treat the changes as events, not as new reading. A team added to the structure page, a paragraph rewritten in the strategy section, a compensation benchmark revised — each is a discrete thing that happened on a date, and dates are what let you correlate a handbook edit with a pricing change three weeks later or a hiring surge two months on.

That last part is what Seeto does. It watches the public surfaces you point it at — handbooks, pricing, docs, changelogs — and reports what changed between two points in time, as discrete change events with dates attached. It does not read the handbook for you or tell you what a strategy shift means; a document written by a company about itself deserves an actual human read, and the interpretation is your job. What Seeto removes is the part where you re-read forty pages every month hoping to notice the paragraph that moved. Related: changelogs leak the roadmap.

A company that publishes its handbook has already decided you can read it. The only real question is whether you will notice when it changes.