{"slug":"business/66-analyst-relations","title":"66 — Analyst Relations","section":"business","sectionLabel":"Business","status":"unclassified","type":"document","path":"business/66-analyst-relations.mdx","bytes":4812,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\nStatus: CANONICAL · Commercial OS\nOwner: Founder\nLast verified: 2026-07-21\n\n---\n\n## Purpose\n\nHow 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.**\n\n**Target audience:** Founder; future PMM/AR owner.\n\n---\n\n## 1. Stage-Honest AR Thesis\n\nWe 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.**\n\n## 2. Target Map (tiered, small)\n\n| Tier | Who                                                                                                                                                          | Motion                                                                                                 |\n| ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------ |\n| 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                                   |\n| 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 |\n| T3   | The category-adjacent voices (authors, framework-makers in CS ops and AI governance)                                                                         | Content relationships ([57](../11-marketing/57-founder-led-marketing.md)); quote exchanges             |\n\n## 3. The Briefing (30 minutes, standing deck)\n\n1. **The problem restated as data (5m):** fragmentation numbers, the Quiet Demotion, the oversight-requirement stats ([06 §1](../02-category-market/06-market-analysis.md)) — analysts collect numbers; give clean ones with sources.\n2. **The category + rubric (10m):** definition and the five requirements ([05 §1,3](../02-category-market/05-category-definition.md)) — explicitly offered as an evaluation framework for the _space_, us included. The rubric is the AR product; a framework outlives any vendor pitch.\n3. **The demo's three beats (10m):** workbench morning → evidence chain → approval + receipt (+ the refusal — analysts remember the refusal).\n4. **The honest slide (5m):** stage, design-partner status, what's unproven, roadmap posture ([69](69-product-roadmap-story.md)). Analysts grade candor; overclaiming to an analyst is remembered for years.\n\n**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.\"\n\n## 4. Operating Cadence\n\nPost-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).\n\n**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](../14-appendix/79-appendix.md)) · when giants adopt our language ([05 §5 contested-category play](../02-category-market/05-category-definition.md)), the AR channel is where the rubric does its quiet work — briefings, not press releases.\n\n**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](../09-gtm/51-launch-strategy.md) pickup) · inquiry response SLA · zero paid-coverage incidents (permanent).\n\n---\n\n**Related:** [05 Category](../02-category-market/05-category-definition.md) · [65 Press Kit](65-press-kit.md) · [08 Competitive Landscape](../02-category-market/08-competitive-landscape.md) · [69 Roadmap Story](69-product-roadmap-story.md)\n"}