Magic Quadrant Strategy

magic-quadrant-strategy

Agent: Analyst Relations Manager

L2 analyst relations manager responsible for analyst briefings, inquiry responses, Magic Quadrant strategy, and peer review platform management.

Department ethos: ideal-marketing.md

Skill Description

Develops the strategy and submission for Gartner Magic Quadrant, Forrester Wave, and similar analyst evaluations that directly shape how enterprise buyers perceive and shortlist vendors.

When to Use

• An analyst firm announces an upcoming evaluation cycle for the company's category and submissions open.
• The company's positioning in a previous evaluation was weaker than desired and a strategic push is needed for the next cycle.
• A new category definition emerges that the company should be included in to reach a different buyer segment.
• Product or market changes create an opportunity to move the company's position in an evaluation framework.

Workflow

1. Identify the evaluation: confirm the analyst firm, evaluation type, category definition, timeline, and submission requirements. Complete Section 1 of assets/mq-strategy-plan-template.md. Review the MQ and Wave framework definitions in references/framework.md to understand axis definitions and scoring methodology.
2. Assess the company's current position: review the previous evaluation results, analyst feedback, and the gap between current placement and target placement. Complete Section 2 of the strategy plan template using the criteria mapping table from references/framework.md.
3. Map the evaluation criteria to company strengths and gaps using the criteria mapping section in references/framework.md. Prioritise criteria with the highest estimated weighting. Identify where the company can credibly improve its score vs. what requires longer-term investment. Complete Section 4 of the strategy plan.
4. Develop the positioning narrative using the key messages structure in Section 3 of assets/mq-strategy-plan-template.md: the strategic story that connects the company's vision, product capabilities, market traction, and customer outcomes to the evaluation criteria.
5. Coordinate the submission: gather product capability responses, customer reference lists, financial data, and roadmap details from across the organisation. Complete references/checklist.md Checklist 1 to confirm submission readiness. Apply the consistency requirements from references/framework.md before filing.
6. Prepare customer references using the reference tier model and preparation protocol from references/framework.md. Brief references on evaluation context, likely questions, and key messages. Check for reference fatigue. Complete Section 5 of the strategy plan. [GATE: confirm all listed references are briefed and available before submitting reference list to analyst firm.]
7. Submit the completed questionnaire and supporting materials by the deadline. Log all submitted claims in the strategy plan evidence library (Appendix C) for future reference.
8. Prepare for the analyst demo and follow-up briefing: rehearse the demo flow, anticipate tough questions, and assign roles using references/checklist.md Checklist 1 demo preparation section.
9. Conduct the demo and briefing. Note analyst reactions, follow-up questions, and any concerns raised. Record in the AR tracker.
10. After publication, complete references/checklist.md Checklist 3. Analyse the results: compare placement against target, review strengths and cautions using the post-publication gap-closure planning section of references/framework.md, and develop a gap-closure plan as Section 8 of the strategy plan.

Anti-Patterns

• Submitting inflated claims that cannot be verified by customer references. Why: Analysts cross-reference vendor claims with customer feedback; inconsistencies destroy credibility and result in harsher evaluations.
• Treating the evaluation as a one-time submission instead of a year-round effort. Why: Analyst perceptions are shaped by every briefing and inquiry throughout the year; last-minute submissions cannot overcome months of neglect.
• Focusing only on product capabilities and ignoring market presence criteria. Why: Evaluations weight market traction, customer satisfaction, and sales execution alongside product features; a complete product with weak go-to-market still places poorly.
• Selecting customer references without briefing them. Why: Unprepared references may share negative experiences or miss opportunities to reinforce key themes, undermining the submission narrative.
• Ignoring cautions from the previous evaluation. Why: Analysts expect vendors to address cited weaknesses; repeated cautions signal a lack of self-awareness or execution ability.

Output

Success artifacts:

• Evaluation strategy document with positioning narrative and criteria mapping
• Completed submission questionnaire with supporting materials
• Customer reference briefing packets
• Post-publication analysis with gap-closure plan for the next cycle

Failure reporting:

• Flag submission deadline risks at least 3 weeks in advance
• Escalate customer reference availability gaps or internal content blockers to marketing leadership immediately

Related Skills

• analyst-briefing-scheduler — Evaluation briefings and demo sessions are coordinated through this skill as part of the submission process.
• analyst-inquiry-responder — Formal evaluation questionnaires are the highest-priority inquiry type; this skill governs the response strategy.
• analyst-report-monitor — Post-publication analysis of evaluation results uses the report monitoring framework to extract positioning intelligence and build the gap-closure plan.
• peer-review-platform-manager — Analyst evaluations increasingly incorporate G2/Capterra data as market presence evidence; strong review presence supports execution scores.