docs/go-to-market.md — the strategy, private #95

New issue

Closed

opened 2026-09-23 10:46:09 +01:00 by cruelacid · 1 comment

cruelacid commented

2026-09-23 10:46:09 +01:00

Owner

Why

The strategy needs one home. The master issue carries the checklist and the
links; duplicating the reasoning into it gives two copies, and two copies of a
strategy is one copy that goes stale.

What to do

docs/go-to-market.md, covering:

Market definition — security consultancies, red teams and independent
pentesters, and why that segment rather than the larger developer one.
Channels, in priority order, with the self-promotion constraints attached
to each.
The wedge, in a paragraph, and the message discipline inherited from
docs/positioning.md.
The audit answer and the trigger for commissioning a real one.
Sequencing — what happens before the launch gates close, and what waits.
Measuring — and the honest note that ten paying organisations is the only
number that matters and none of the others predict it well at this scale.

Constraints

It stays private. scripts/build-mirror.mjs's PUBLIC_DOCS currently
contains security-model.md and nothing else — the four that used to sit beside
it were removed — and the verifier fails the stage if any mirrored file links a
docs/ path not on that list. So a new private doc is safe by default, and the
only real risk is a mirrored comment citing it.

Being private is what lets it cite positioning.md and competition-relay.md
freely. Neither of those may be quoted in anything public.

When quoting Relay's non-encryption anywhere public, quote their live
documentation and re-verify at the time of writing. This is not hypothetical:
the snapshot taken 1 September 2026 records "we have the technical ability to
access synced content if required", and the page on 22 September reads
"Relay isn't end-to-end encrypted, so the server that can read your documents
still exists; with self-hosting, that server is yours." The claim holds; the
wording moved. Archive what you quote, and never frame them as dishonest — they
document it plainly, which is the strongest version of the point anyway.

## Why The strategy needs one home. The master issue carries the checklist and the links; duplicating the reasoning into it gives two copies, and two copies of a strategy is one copy that goes stale. ## What to do `docs/go-to-market.md`, covering: - **Market definition** — security consultancies, red teams and independent pentesters, and why that segment rather than the larger developer one. - **Channels**, in priority order, with the self-promotion constraints attached to each. - **The wedge**, in a paragraph, and the message discipline inherited from `docs/positioning.md`. - **The audit answer** and the trigger for commissioning a real one. - **Sequencing** — what happens before the launch gates close, and what waits. - **Measuring** — and the honest note that ten paying organisations is the only number that matters and none of the others predict it well at this scale. ## Constraints **It stays private.** `scripts/build-mirror.mjs`'s `PUBLIC_DOCS` currently contains `security-model.md` and nothing else — the four that used to sit beside it were removed — and the verifier fails the stage if any mirrored file links a `docs/` path not on that list. So a new private doc is safe by default, and the only real risk is a mirrored **comment** citing it. Being private is what lets it cite `positioning.md` and `competition-relay.md` freely. Neither of those may be quoted in anything public. When quoting Relay's non-encryption anywhere public, **quote their live documentation and re-verify at the time of writing**. This is not hypothetical: the snapshot taken 1 September 2026 records *"we have the technical ability to access synced content if required"*, and the page on 22 September reads *"Relay isn't end-to-end encrypted, so the server that can read your documents still exists; with self-hosting, that server is yours."* The claim holds; the wording moved. Archive what you quote, and never frame them as dishonest — they document it plainly, which is the strongest version of the point anyway.

cruelacid added this to the Backlog - unscheduled milestone

2026-09-23 10:46:09 +01:00

cruelacid added the

area:docs

marketing

gate:pre-ga

labels

2026-09-23 10:46:09 +01:00

cruelacid referenced this issue

2026-09-23 10:46:56 +01:00

Go-to-market programme #110

cruelacid added this to the Marketing project