Unclassified

66 — Analyst Relations

Status: CANONICAL · Commercial OS
Owner: Founder
Last verified: 2026-07-21

Purpose

How a pre-Series A company does analyst relations without pretending to be Salesforce: a narrow, patient program aimed at one outcome — when the category conversation starts, analysts already have our definition in their notes.

Target audience: Founder; future PMM/AR owner.

1. Stage-Honest AR Thesis

We will not buy Gartner seats or chase Magic Quadrant placement (wrong stage, wrong spend). But category creation has an analyst chapter that starts now, because analysts pattern-match early: the vendors who briefed them before the category had a name become the definitional references when it gets one. Our AR program is: be the best 30-minute briefing on human-AI collaborative work that any analyst takes this year.

2. Target Map (tiered, small)

Tier	Who	Motion
T1	The 4–6 individual analysts (across Gartner, Forrester, and independents) covering: digital workplace/collaboration, AI agents & governance, CS/revenue tech	Personal briefing offers post-launch; the rubric as the leave-behind
T2	Independent/boutique analysts and practitioner-analysts with newsletters/podcasts in CS + AI-at-work	Earlier, warmer: founder-to-analyst conversations now; they cite faster and shape practitioner opinion
T3	The category-adjacent voices (authors, framework-makers in CS ops and AI governance)	Content relationships (57); quote exchanges

3. The Briefing (30 minutes, standing deck)

The problem restated as data (5m): fragmentation numbers, the Quiet Demotion, the oversight-requirement stats (06 §1) — analysts collect numbers; give clean ones with sources.
The category + rubric (10m): definition and the five requirements (05 §1,3) — explicitly offered as an evaluation framework for the space, us included. The rubric is the AR product; a framework outlives any vendor pitch.
The demo's three beats (10m): workbench morning → evidence chain → approval + receipt (+ the refusal — analysts remember the refusal).
The honest slide (5m): stage, design-partner status, what's unproven, roadmap posture (69). Analysts grade candor; overclaiming to an analyst is remembered for years.

The ask (explicit, modest): "When you write about humans and agents working together, we'd like to be a data point — and we'll bring you customer evidence as it matures."

4. Operating Cadence

Post-launch: T2 conversations monthly (2/month ceiling) · T1 briefing requests quarterly · every published analyst piece touching the category gets a founder read + a useful (non-corrective unless factual) note · inquiry responses < 48h · evidence updates (new case study, category-pickup milestones) pushed twice yearly, never spammed. All contacts and citations logged (a spreadsheet is fine — the discipline matters, not the tooling).

Rules: never pay for coverage or imply we would · never dispute an analyst's opinion publicly (correct facts privately) · the same claims register governs analyst materials (79) · when giants adopt our language (05 §5 contested-category play), the AR channel is where the rubric does its quiet work — briefings, not press releases.

KPIs: briefings completed (target: 6 T2 + 2 T1 in launch year) · rubric citations/appearances in analyst writing · our category phrase in analyst vocabulary (tracked with 51 §4 pickup) · inquiry response SLA · zero paid-coverage incidents (permanent).