The pricing page is where positioning gets audited by the people with budget. Every word on it is read against three competitors open in adjacent tabs, and the buyer is looking for a reason to close the tab. Most founders write that page once at seed, edit it twice on instinct, and then stare at conversion data wondering which lever to pull.
The Analyst is built for that exact problem — pressure-testing copy against your own positioning brief, the live competitor pages, and the buyer's decision sequence. It will not write your pricing page. It will tell you which seven sentences are doing the work and which fourteen are filler.
What the pricing page is actually doing
Before any prompt runs, name the job. A pricing page is not a price list. It's a positioning artifact that resolves four buyer questions in sequence:
- Am I in the right place? (Category fit)
- Which tier am I? (Self-classification)
- What does it cost, including the asterisks? (Risk surfacing)
- What happens next? (Commitment)
Copy that misses any one of these creates a friction point the conversion data will eventually surface — but by then you've burned three months of paid traffic. The Analyst's job is to catch the misses before they ship.
A tier name is a positioning claim with a price tag attached.
Step 1 · Load the positioning brief, not just the page
The most common mistake founders make with the Analyst is pasting in the pricing page and asking "is this good?" The model has nothing to compare it against, so it produces generic copywriting feedback — shorter sentences, more benefits, clearer CTAs. Useful for a junior writer. Useless for you.
Start the session by loading the positioning brief into Strategic Context. The brief should already name your category noun, your ICP, the three buyer pains, and the two-to-three competitive alternatives. If it doesn't, fix the brief first — running pricing copy against a hollow brief is the analytical equivalent of measuring with a rubber ruler.
I kept asking the model to make the copy sharper. It kept making it shorter. The third time I realized the brief was wrong — we'd never agreed on the category noun internally. The pricing page was the symptom.
Step 2 · Run the four-question audit
With the brief loaded, paste the pricing page HTML or copy into the Analyst and run the four-question audit. The prompt is in the Pricing Page Prompt Pack, but the structure is:
Run each question as a separate turn. Don't combine them. The model produces sharper analysis when it's holding one question in working memory rather than four.
Step 3 · Pull in the competitive surface
Open the two-to-three competitor pricing pages from the brief. Paste them in. Ask the Analyst a single question: Where do these pages disagree, and where do they converge?
Convergence tells you the category's default conventions — three tiers, "Starter / Team / Business," seat-based pricing, an annual discount. Following the conventions makes you legible. Breaking them deliberately is positioning. Breaking them accidentally is friction.
Disagreement tells you where each competitor is making a positioning bet. One company gates SSO behind enterprise — they're betting that mid-market doesn't care. Another puts API access in the lowest tier — they're betting developers are a key wedge. Read the bets, then decide which ones to match and which to counter.
Step 4 · Audit the asterisks
The asterisks are where pricing pages lie by omission. Usage caps, fair-use clauses, "starting at" prefixes, the contract length required for the listed price, the support tier that comes with the lower plans. Every footnote is a future support ticket or a churn conversation.
Ask the Analyst to extract every conditional claim from the page — anything qualified by "starts at," "up to," "from," "based on," "subject to" — and list them as a separate document. Then read that document as if you were a procurement officer. The questions you have are the questions every prospect has.
The asterisk audit
Step 5 · Stress-test with three personas
Once the page reads cleanly against the brief and the competitors, run it past three personas the model can simulate from your ICP definition. The prompt: Read this page as [persona]. What do they understand, what do they assume, and what do they get wrong?
The personas should include one buyer who is genuinely a fit, one buyer who is borderline, and one buyer who is wrong-fit. The wrong-fit reading is the most useful — it tells you whether the page is filtering correctly or wasting your sales team's calendar.
We thought our pricing page was clear. The Analyst's wrong-fit persona read it as a workflow tool for ten-person teams. We were selling to two-hundred-person operations groups. The page was costing us at least a demo a week to people who couldn't buy.
What the Analyst won't do
Three things to handle yourself, not in the model:
- Set the actual prices. Pricing levels are a strategic call informed by willingness-to-pay research, not a copy exercise. The Analyst audits how prices are presented, not what they should be.
- Predict conversion lift. The model can flag friction; it cannot tell you whether removing it raises conversion by 0.4% or 4%. That's an A/B test, and it requires real traffic.
- Replace customer interviews. The wrong-fit persona simulation is a useful proxy when you can't get a real one in the room. It's not a substitute for ten win/loss calls. Use it to sharpen questions, not to replace answers.
What to do this week
Block ninety minutes. Load the brief into Strategic Context, run the four-question audit on your live pricing page, then run it again on the two competitor pages you compete with most often. Write down the three sharpest observations. Take one of them to your next exec meeting as a proposed change with the rationale attached.
The pricing page that converts better next quarter is the one whose copy was pressure-tested this quarter against the brief, the competitive surface, and the buyer's real decision sequence — not the one with the punchier headline.
Keep reading
Analyst Prompt Library for Positioning Work
Twenty prompts that turn an AI analyst into a useful positioning tool — organized by positioning-layer, each with the specific context the AI needs to produce non-generic output, and the reviewer discipline that keeps the output honest.
How to Use an Analyst for Competitive Deep Dives
A working method for getting specific, defensible competitive analysis out of an AI analyst, instead of the bland summaries most prompts return
The Strategist's Prompt Book: 50 Questions for Your Analyst
Fifty specific, context-loaded questions organized by strategic problem. Each prompt is designed to produce output a senior PMM would find useful, not generic text. Use as a reference; replace bracketed elements with your specifics.
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