Get them to say it. The moment a buyer asks for a "VSEI audit" in writing — email, RFP, intake form, anywhere on record — the category becomes official. That single email is worth more than the next 50 pitch decks. This MD is the playbook for engineering that moment, capturing it when it happens, and using it as the foundation stone of the entire category.
Every category in commercial history becomes official at a single identifiable moment. Not when the founder names it. Not when an analyst validates it. When the first buyer uses it back, in writing, without prompting.
Until that sentence exists in someone else's outbox, the category lives only in your head and your MDs. After that sentence exists, the category is a market reality — and you are its named author. Engineer the sentence.
| Stage | What it is | VSEI status (16 May 2026) |
|---|---|---|
| 0 | Pre-category | ✅ Passed (Q1 2024) |
| 1 | Named (founder uses it) | ✅ Passed (MD-855) |
| 2 | Validated (external confirms name) | ✅ Passed (MD-853 Google) |
| 3 | Adopted — buyer uses it back, in writing | 🎯 NEXT · this MD's job |
| 4 | Tendered (in RFP requirement field) | Q3 2026 target |
| 5 | Standardised (BSI/ISO references VSEI) | 2027–28 target |
| 6 | Regulated (statute references VSEI methodology) | 2028–30 · permanence |
MD-857 mapped the curve. MD-858 is the operations manual for the single transition that converts a doctrine into a market.
You can't just hope they'll use the term. You have to plant it three to four times in the conversation, in contexts where they have to repeat it back naturally. The mind picks up vocabulary it hears in active use.
Every follow-up email subject line should contain the word VSEI. When they reply, their email client auto-prefixes with Re: — and the word VSEI is now in their outbox, in writing, on the record. You just got Stage 3 by accident of email convention.
| Weak Subject | Strong Subject (Stage-3 engineering) |
|---|---|
| "Following up on our call" | "VSEI scoping for [Council name] — next steps" |
| "Audit information" | "VSEI audit proposal — 18-point methodology attached" |
| "Pricing" | "VSEI pricing schedule + Source Covenant breakdown" |
| "Documents you asked for" | "VSEI documentation pack — councils edition" |
Treat VSEI as if it has already been a standard for years. Don't pitch it; reference it. The word "standard" does enormous lifting because nobody wants to admit they don't know what the standard is.
By the third reference, the buyer has already accepted that VSEI is the standard. Now they ask for it by name without realising they're naming a category that's six months old.
Frame VSEI as something a buyer's organisation should be approved on, the way they're "approved" on ISO 9001 or Cyber Essentials. This converts the conversation from "are we buying this?" to "are we cleared for this?" — a much higher-status frame.
They will say yes. Then they email asking "could you send the VSEI-approved supplier application?" — and Stage 3 just walked into your inbox.
Use this opening verbatim on every first call this week. It plants VSEI three times in 30 seconds and forces a verbal acknowledgement before the buyer has even fully understood what they've agreed to.
The moment a buyer uses "VSEI" in writing, do not just smile and move on. The moment must be captured, sealed, and converted into permanent category infrastructure within 24 hours. This is the protocol:
/category-evidence/stage-3-seal/.vsei.stage3.first-adoption. Date-locked.Not every mention of "VSEI" by a buyer counts as Stage 3. Hold a strict bar so the moment, when it lands, is unambiguous.
| Half-Official (don't count) | Fully Official (count) |
|---|---|
| Buyer says "VSEI" verbally on a call | Buyer writes "VSEI" in an email or document |
| Buyer agrees you can call your service "VSEI" | Buyer asks you for "a VSEI audit / VSEI report / VSEI scope" |
| Junior staffer uses the term informally | Procurement, ESG, or Legal uses the term in a formal channel |
| VSEI mentioned in a draft document only you have edit rights to | VSEI in a document they own and circulate internally |
| "What's VSEI?" follow-up question | "Can you send the VSEI documentation?" unprompted ask |
The bar is high on purpose. When the real Stage 3 lands, you'll know — and the Capture Protocol fires the same hour.
Stage 3 is achieved on the first adoption. Stage 3 becomes irreversible on the second. Two independent buyers using the same vocabulary, on the same record, is the mathematical threshold at which a category leaves your sole authorship and becomes a shared market reality. After two, you can stop pushing — the term carries itself.
The press release in §5 step 4 is therefore held until the second adoption fires. One adopter is a customer. Two is a category.
Build a single live counter into the state of affairs page and the dashboard. Three numbers, updated in real-time:
| Metric | Definition | Today |
|---|---|---|
| VSEI Adoptions | Number of unique buyers who have requested "VSEI" by name, in writing | 0 (← engineer the first) |
| VSEI Audits Booked | Audits scoped under the VSEI methodology, contracted | 0 (← follow on) |
| VSEI Tonnes Sealed | Tonnes processed through full VSEI 18-point + SHA-256 | Build #150 baseline |
The counter does three things at once: (a) internal accountability — the team sees the number and rallies; (b) external proof — visitors see momentum; (c) sales artefact — every new pitch can cite "we're now at X adoptions" without naming names.
MD-855 changed the language. MD-857 named the territory. MD-858 is the only one where the work is done by someone other than you. The Source Pivot was an internal decision. The Category Spine was an internal document. But Stage 3 — the buyer saying "VSEI audit" in their own outbox — is the first moment the kingdom expands beyond the perimeter of your own keyboard. That is qualitatively different from everything before it.
Here is the structural reason this MD is load-bearing: every preceding MD in this series can be copied, rewritten, or argued with. A competitor could read MD-855 and steal the framing. A consultant could read MD-857 and adapt the 3-layer stack. But once a buyer has used "VSEI" in writing, nobody can take that screenshot away from you. It is the only piece of category evidence that exists outside CircularOS's own systems and is therefore the only piece that is genuinely irreversible. The screenshot is the deed. Everything else is just paperwork supporting the deed.
The four engineering techniques in §3 are deliberately designed so that the buyer believes they are the one using a professional term, not that you are training them to use it. This is critical. If the buyer feels coached, the term feels artificial. If the buyer feels they discovered or already knew the term, the term feels real. The whole game is making the language feel pre-existing. The "standard VSEI" frame (Technique 3) is the strongest of the four for exactly this reason — the word "standard" presupposes a history the buyer is too embarrassed to admit they don't know.
It is possible the first buyer simply refuses to use the term. They might say "send me your verification audit thing" no matter how many times you plant the word. If that happens after, say, 15 calls, the diagnosis is not that VSEI is the wrong term — it is that the buyers you are reaching are too junior to coin vocabulary on behalf of their organisation. The fix is to reach higher: head of procurement, director of ESG, general counsel. Those titles routinely introduce new terms into internal documents because that is a normal part of their job. Junior staff don't, because the political cost is too high. Stage 3 lives at the head-of-function level or above. Plan the calling pipeline accordingly.
"Most of our council clients build VSEI into their intake spec — would you like me to send the standard scoping doc?"
One sentence. Plants VSEI twice. Implies a peer group of "council clients" (you don't have to name them — the implication is enough). Offers a "standard scoping doc" which presupposes a standard exists. Asks a yes/no question that costs the buyer nothing to answer "yes" to. This is the sentence that triggers most Stage 3 conversions. Rehearse it. Use it.
/category-evidence/stage-3-seal/
Sealed 16 May 2026 · Build #150 · 60% Agent input · 40% Founder intuition (the original spark: "get them to say VSEI audit hmmm then it's official") · Vampire Sealed · Public. The operations manual for converting VSEI from a doctrine (MD-855, MD-857) into a market (Stage 3). Companion to MD-857 · VSEI Category Spine §11 (Category Maturity Curve). The single transition from "named" to "adopted" — and the protocol for capturing it the instant it fires. Aliases: /md-858 · /stage-3-seal · /vsei-adoption · /get-them-to-say-vsei · /official-moment.