rushogen/enterprise-gtm-skills

Analyst relations

Analyst relations is a compounding programme, not a campaign. The dot on this year's Magic Quadrant was largely decided by the eighteen months of briefings, inquiry transcripts and reference conversations that preceded the submission. Work backwards from that.

First, establish the situation

Before producing anything, get answers to these. If the user cannot answer, say so plainly and flag it as the first gap to close.

1. Which evaluations is the vendor in scope for, and what are the inclusion criteria (revenue floor, customer count, geographic presence, product completeness)? Vendors are excluded on technicalities more often than they are scored badly.
2. Who is the lead analyst, who are the secondary and contributing analysts, and when did coverage last change hands? A new analyst inherits the file but not the relationship.
3. What did the previous evaluation say, verbatim, in the Cautions or Weaknesses section? That paragraph is the scoring rubric for this year.
4. How many inquiry hours does the seat licence include, and how many were used last year? Most vendors buy inquiry and never use it.
5. Which customers were nominated as references last time, and what did the analyst hear from them?

Briefing versus inquiry versus advisory

These are different instruments and confusing them wastes the relationship.

• Briefing — the vendor talks, the analyst listens. Free, typically 30 or 60 minutes. The analyst gives no advice and may use anything said in published research. This is how you get on the record.
• Inquiry — the vendor asks, the analyst advises. Drawn from a paid seat licence. Does not directly feed research, but it is where you learn how you are perceived, and where the analyst's mental model of you gets updated in real time. Underused by nearly everyone.
• Strategic advisory / SAS day — paid engagement, deep, scheduled months ahead. Appropriate before a category repositioning, not before a routine release.
• Vendor questionnaire / RFI — the formal written submission. Scored.

Rule of thumb: brief quarterly with genuinely new proof, inquire monthly with a real question. Never open an inquiry with a pitch; the analyst will end it.

What actually moves placement

Placement is not a popularity outcome. Both major evaluations score against published, weighted criteria.

Gartner Magic Quadrant scores two axes. Ability to Execute covers product or service, overall viability, sales execution and pricing, market responsiveness, marketing execution, customer experience and operations. Completeness of Vision covers market understanding, marketing strategy, sales strategy, offering strategy, business model, vertical or industry strategy, innovation and geographic strategy. Weights vary per market and are published in the methodology section of the document.

Forrester Wave scores three groups — Current Offering, Strategy, Market Presence — against criteria that are published before the evaluation, with weights the vendor can see. There is a scripted demo (often two to three hours) run against a scenario Forrester writes, and it is scored against the script, not against the demo you wanted to give.

The levers that actually change a score, in descending order of effect:

1. Reference quality. Customer survey responses are heavily weighted and are the most common self-inflicted wound. See the reference section below.
2. Fixing a specific low-scored criterion and demonstrating it. Take the two criteria you scored worst on, ship against them, and build the whole year's briefing narrative around the delta. Analysts reward closed loops.
3. Roadmap credibility. The analyst keeps notes. If last year's briefing promised a capability and it did not ship, vision scores fall even when the new roadmap is better. Never brief a roadmap item you would not bet a quarter on.
4. Market presence facts. Customer count, revenue, geographic split, partner count, growth rate. Give real numbers under NDA rather than adjectives. "Strong growth in EMEA" scores nothing.
5. Vertical and geographic strategy. Consistently the weakest section in most submissions because nobody owns it. A named vertical motion with a named leader, three named customers and a quantified pipeline beats a slide listing eleven industries.

The evaluation cycle

Approximate, and the dates shift, but the shape holds. Confirm actual dates with the research operations contact, not the analyst.

Stage	Lead time	What the PMM does
Inclusion criteria published	T-6 months	Check eligibility line by line. Escalate a gap now, not later.
Vendor questionnaire / RFI issued	T-4 months	Assemble the answer team. Budget three to four weeks; it is a 60-to-150-question document with word limits.
Reference nomination	T-3 months	Nominate against the fit profile, not against enthusiasm.
Briefing and scripted demo	T-3 months	Rehearse the script. Do not improvise.
Reference survey fielded	T-2 months	Warn the customers. Do not coach them.
Draft placement / scores shared	T-1 month	Read every word of the Cautions section.
Fact-check window	2 to 5 business days	Corrections of fact only. See below.
Publication	T-0	Reprint rights, embargo, sales enablement.

Reference nomination is where vendors lose

The analyst surveys the references you nominate and weights the results. Common failure: nominating the most enthusiastic customer, who happens to use twelve percent of the product and has never touched the module being evaluated. They score you low on breadth without meaning to.

Nominate against the evaluation's profile:

• Uses the capabilities the criteria actually score
• In production, past the honeymoon, past a real upgrade
• Segment, region and deployment model spread that matches the document's stated scope
• Has survived at least one support escalation and still likes you — this is the strongest signal a reference can give
• Not currently in a renewal negotiation or an open escalation

Warn nominees that the survey is coming, tell them roughly how long it takes, and tell them what it is for. Do not send them talking points. Analysts detect coached references immediately, and it damages more than the score.

The fact-check window is not an appeal

You will get a short window on the draft. It exists to correct factual errors: a wrong revenue figure, a capability described as unavailable that shipped in March, a misattributed acquisition. It does not exist to argue about the dot.

Write the response as a table: quoted text, the specific factual error, the correction, the evidence, and a suggested replacement sentence. One page. Evidence means a release note, a dated document, a customer count from the system of record. Arguing placement in the fact-check burns credibility that you will need next cycle, and it never works.

If the placement genuinely reflects a misunderstanding of the strategy, that is an inquiry topic for the month after publication, not a fact-check item.

Adjacent evaluations worth tracking

• Gartner Peer Insights — review-volume driven, entirely separate from the MQ, with minimum thresholds for inclusion in Voice of the Customer. Runs on a review campaign, not on analyst relationships. Solicitation rules are strict: no incentives tied to review sentiment, no vendor-drafted reviews.
• Forrester Total Economic Impact — commissioned, paid, based on interviews with your customers. Useful and credible, but it is a marketing asset, and buyers know it is commissioned. Do not treat it as third-party validation of placement.
• IDC MarketScape, Everest PEAK Matrix, ISG Provider Lens — matter disproportionately in services-heavy and regionally specific deals. ISG in particular carries weight in DACH sourcing.

Failure modes

• Marking every slide confidential, then wondering why nothing is cited. Decide per slide what is publishable and label it that way.
• Sending the CEO to deliver a capability briefing. Analysts want the product leader for product, the CEO for strategy, and a customer for proof.
• Repeating last quarter's deck. The analyst remembers, and a repeat briefing signals no progress more loudly than saying nothing.
• Missing an analyst coverage handover. Re-onboard the new analyst within four weeks with a dedicated history briefing, or they will write from the file.
• Treating a negative note as a communications problem. Usually it is a product or execution problem the analyst has correctly identified early.
• Losing the reprint rights budget line. Placement without reprint rights is worth a fraction of placement with them, and sales will ask on day one.

Measurement

Placement movement is a lagging, annual, low-resolution metric. Track alongside it: number of inbound end-user inquiries referencing the vendor, analyst mentions in deal debriefs, inclusion in shortlists sourced from analyst advice, briefing-to-citation rate, and unprompted mentions in published notes.

Working files

• references/mq-wave-criteria.md — the criteria groups in detail, with what evidence satisfies each one
• assets/briefing-deck-outline.md — the eight-slide structure that fits a 30-minute briefing
• assets/fact-check-response.md — the response table format
• assets/analyst-tiering.md — tiering map and cadence commitments per tier