Analyst Use Case: Competitive Response Drafting

A competitor ships a feature on Tuesday. The first sales rep hears about it on a Wednesday demo. The PMM hears about it on Slack on Thursday. By the time a response draft lands in the battle card, it's the following Tuesday and three more deals have stalled.

That gap — signal to sales-ready language — is where most competitive response work breaks. Not because the PMM is slow. Because the work is fundamentally a research-and-writing sprint, and most PMMs are running four of those simultaneously across a launch, a pricing change, an analyst briefing, and the competitor in question.

The Analyst, in Stratridge's vocabulary, is a positioning-aware reasoning surface — it has your category, your ICP, your past briefs, your win/loss themes, and your competitor profile already loaded as context. When you ask it to draft a response, it isn't writing from scratch.

The bottleneck isn't the writing. It's the reassembly of context the PMM already has, scattered across six tools.

What "response drafting" actually is

Strip the workflow back. A competitive response draft is four things stitched together:

1. A factual summary of what the competitor did.
2. A reframe — why it matters less, or differently, than the competitor's launch post claims.
3. Two to four objection-handling lines a rep can paste into an email or speak on a call.
4. A pointer to the deeper artifact (the battle card, the technical brief) for reps who need more.

Most PMMs do this in a Google Doc with six browser tabs open. The reframe is the hard part — the rest is mechanical. Done well, the whole thing is forty-five minutes of writing wrapped in two hours of context-gathering.

The Analyst version of the workflow

The whole sequence runs in fifteen to twenty minutes once you have the prompts memorized. The first time, expect an hour while you learn which prompts your Analyst answers well and which need rewording.

What sales actually wants in the response

We've watched maybe thirty AEs read draft responses out loud in war rooms over the last year. Two patterns hold every time.

The second pattern: AEs trust responses that name the competitor's real strength before pivoting. "Their multi-region story is genuinely better for global teams under five hundred seats; here's why that doesn't apply to your environment" lands. "They claim multi-region but actually it's just—" doesn't.

The prompts that do most of the work

Five prompts cover ninety percent of competitive response drafts. The Response Drafting Prompt Pack below has all twelve we use, with annotations on when each one earns its keep.

What this changes about the PMM week

The PMMs we work with who run this loop end up doing two things differently. They stop saving competitive response work for "when I have time" — because twenty minutes is a window that exists most days. And they stop writing first drafts alone — the Analyst writes the first draft, the PMM edits.

That second shift is the bigger one. PMM time spent on a response shifts from sixty percent typing and forty percent thinking, to ten percent typing and ninety percent judging what the Analyst produced. Judgment scales further than typing does.

What to do Monday

Pick the next competitor signal that lands in your inbox. Run it through the five-prompt core. Time the work. If it takes more than thirty minutes the first time, the bottleneck is almost certainly that your Analyst doesn't have your positioning brief, ICP definition, or last six win/loss interviews loaded as context. Fix that once and the rest of the year of competitive response drafting gets faster.