Skills / Finding the buyer / Analyst relations at seed

Do Gartner and Forrester matter at seed — and how do Latio and the independents actually move deals?

Being named on the map is a starting gun, and it fires for your competitors too.

analyst-relations

SKILL.md · 864 words

Verified Sept 2026

Download the folder
What your agent reads.
name
analyst-relations
description
Analyst relations for a seed-stage cybersecurity company: whether Gartner, Forrester and IDC matter yet, what a vendor briefing and an inquiry seat buy, how the security-native independents (Latio, the practitioner newsletters and research shops) actually move a shortlist, what a landscape map or a named category does to a young company, and the one paid analyst spend that has paid at seed. Use when a founder is pitched an analyst subscription, invited to brief, offered a place on a market map, told the category is about to be named, or stuck in a buying committee that reads the big firms. Not for platform absorption once a category is named (platform-annexation-check), the practitioner ground itself (early-gtm-motion), or the buyer's own research habits before a first meeting (first-ciso-meetings).
title
Analyst relations at seed
question
Do Gartner and Forrester matter at seed — and how do Latio and the independents actually move deals?
subtitle
Being named on the map is a starting gun, and it fires for your competitors too.
summary
You cannot buy coverage from the big analyst firms at seed, and being named by them helps your later competitors more than it helps you. Take the free briefing so you are in the analyst's notes, give the practitioner-led independents your tool rather than a pitch, and spend on an analyst only when a large deal is stuck in a committee that reads the firm.
group
buyer
verified
2026-09-08
order
40

810 / 1024 characters

This is the top of the SKILL.md file, exactly as it downloads. Your agent reads the description field to decide when to load this skill. The rest of this page is for you.

You are being asked to buy a relationship with people whose job is to name markets, and at seed the naming is the part that hurts you. What follows is what we have watched analyst attention do to young security companies, and the small amount of it worth paying for.

Being named is a starting gun.

You will pursue getting your category named and getting onto the map as a milestone worth paying for. It is the starting gun for the competitive phase. Well-funded competitors appear within a couple of quarters of an analyst naming a category, because a name is what lets generalist investors underwrite the space, and a name is what puts your category on a platform product team's slide. The naming helps later entrants more than it helps you. They arrive with the name already in the buyer's vocabulary and skip the years you spent teaching it.

Read the map for its count, not your dot.

You will look for your own dot first when a landscape map appears. Read the count first. A crowded map is a category about to be absorbed, and a sparse one is a category nobody funds yet. Your position on the page is the least informative thing on it, and buyers read the count the same way.

The big firms cannot cover you yet.

The subscription is sold on the promise of influence, and the quadrant is years away, with criteria written for the platforms. Read those published criteria anyway, because they are a list of what the platforms will absorb first.

What the big firms sell a seed-stage company that is worth having is small. A vendor briefing costs nothing and puts you in the analyst's notes, which is where a buyer's inquiry call finds you. An inquiry seat buys an hour with the analyst who covers your buyer's category, and the right use of that hour is to interview the analyst about buyers, because the analyst hears from your buyers all day and you do not. Ask what the buyers are asking. Do not pitch.

The independents move the shortlist.

You reach the shortlist through the people practitioners read, and in security those are the independents: the practitioner-led evaluation shops, the newsletters, and the researchers who run the tools themselves. They move a deal by being in the thread where a security engineer asks a peer what to look at, not by issuing a badge.

They respond to one thing, which is a product they can run themselves and an honest technical account of what it does and where it fails. Pitching them a category is the wrong pitch. Give them the tool, answer the hard questions in public, and accept that a negative review from them reaches your board within days, because the same qualities that make them trusted for you make them trusted when they turn.

Buyers read peers first.

The analyst does not open the door. Peers do. A security leader forms an opinion of you among other security leaders and the practitioners who report to them. The analyst matters at the close, when a procurement committee asks for a third-party name to put in the file. Have the briefing on record for that moment, and expect nothing from it earlier.

One paid hour has paid off.

Reprints, event sponsorships, and advisory retainers are each a brand purchase priced as if it were pipeline. The one paid analyst spend we have watched pay off at seed is a single inquiry hour when a large deal is stuck in a committee that reads the firm, used to learn how that buyer's peers decided. It costs an hour and it moves a deal already in motion. Nothing else on the price list does.

When you are named anyway.

The naming comes whether you wanted it or not, and the accounts you deployed while the space was quiet are the defense you have when it stops being quiet. Describe your product as the obligation the buyer is measured on, once, and do not chase the analyst's label for it. Do not rename to stay off a slide either. Once the name lands, the question in front of you is whether a platform will absorb you, not marketing.

Working the question.

  1. Take the free vendor briefing so you are in the analyst's notes, and pitch nothing.
  2. Read the published criteria for your category as the list of what the platforms will absorb first.
  3. Give the practitioner-led independents the tool and an honest account of where it fails.
  4. Buy one inquiry hour only when a large deal is stuck in a committee that reads the firm.
  5. When the category is named, deploy every account you can while the space is quiet, and do not rename.

Working with an agent.

Give your agent your product documentation and your positioning. Ask it to draft the free vendor briefing, thirty minutes and no money, that puts you in an analyst's notes. Take that briefing before you pay for anything. A paid place on a market map mostly tells later entrants which category to enter.

Install the skill.

You are reading the skill itself — this page and the download are the same files. Unzip it into ~/.claude/skills/ (or a project’s .claude/skills/) and Claude Code loads it when the question comes up; so does any agent that reads Agent Skills.

mkdir -p ~/.claude/skills && cd ~/.claude/skills && curl -sLO https://techoperators.com/skills/analyst-relations.zip && unzip -oq analyst-relations.zip && rm analyst-relations.zip

analyst-relations/SKILL.md

No terminal? Download analyst-relations.zip and drop into your assistant’s project files.

Kevin Skapinetz

Tell us what you see.

Whether you’re thinking about starting a company, building one in stealth, or raising a round: send Kevin or Dan what you see on LinkedIn, in your words.