A competitor ships a feature on Tuesday morning. By Thursday afternoon, the PMM is still waiting on input from product, sales has improvised three different responses on calls, and the Slack thread is at forty-seven messages with no draft attached. The response that finally lands on Friday is generic, defensive, and forgotten by Monday.
The bottleneck isn't writing. It's reconciliation — pulling the product's actual capability, the competitor's specific claim, the segment that's exposed, and the sales team's current objections into one coherent paragraph. That's what the Analyst is for.
What "competitive response" actually means
It's three artifacts, not one:
- The internal brief. A paragraph for the GTM leadership Slack channel — what shipped, who it threatens, what we're going to say.
- The sales-facing reframe. A two-to-four-sentence block for the battle card and call-coaching channel.
- The customer-facing rebuttal. Optional. A line a CSM can use if a current customer asks "should we be worried about X?"
Most teams conflate the three and end up with a doc that serves none of them. The Analyst's value is producing all three from the same context payload, in the same session, in the same voice.
Why drafts take so long without it
The reconciliation tax
Each of those five inputs lives in a different place. The PMM's job, traditionally, is to walk between five rooms and write down what each room said. The Analyst keeps the rooms in one context window.
The twenty-minute draft
What the Analyst won't do for you
The first time I tried this, I asked it to "respond to the competitor's launch." It wrote three paragraphs of confident, fluent garbage. The model needs the same brief I'd give a junior PMM — segment, deal stage, what we already say. Without that, it just pattern-matches on competitive-blog-post energy.
The Analyst is a reconciliation engine, not a strategist. It will not tell you whether to respond at all — that's a judgment call about brand posture and category leadership that the human owns. It will not invent a differentiator you don't have. And it will not catch a factual error in your own product capability if your strategic context file is out of date.
The skill that compounds is context maintenance. Teams that update their strategic context monthly produce ten-minute responses. Teams that load it ad-hoc produce hour-long ones — and the responses are worse.
What ships from a good twenty-minute session
What to do Monday
Open last quarter's three biggest competitive responses. For each, count the hours between the competitor's announcement and the moment your AEs had a sales-ready reframe. If it's over twenty-four hours, the bottleneck is reconciliation, not writing — and the prompt pack above is a faster fix than another Slack channel.
Keep reading
How to Use an Analyst for Battle Card Generation
A working PMM's process for generating battle cards with an AI analyst — what to feed it, what to verify, and where the human still has to do the work
How to Use an Analyst for Competitor Profiles
Competitor profiles are tedious to build and quickly go stale. An AI analyst, prompted correctly, can produce competitor profile drafts in minutes — but the draft quality depends entirely on the context you load. Here's the specific workflow and the six-part profile structure.
How to Use an Analyst for Signal Prioritization
A working method for triaging competitor signals with an AI analyst, so the three that matter surface before Monday's pipeline review
Analyst
AI strategy advice grounded in your own context — not generic playbooks.
The Analyst is a chat-based AI strategist that reads your Strategic Context, past audits, and competitive signals before answering. Ask it anything from 'why are we losing to Competitor X' to 'how should we reframe our pricing page' — and get answers that are actually about you.
- ✓Reads your own positioning data before responding
- ✓Grounded in audit findings and competitor signals
- ✓No hallucinated advice — evidence cited inline