Compare Two ChatGPT Prompts
A side-by-side way to decide between two ChatGPT prompt drafts — scored on clarity, specificity, output control, and risk instead of gut feeling.
Two landing-page hero/CTA variants loaded for side-by-side scoring — generic vs intent-matched — judged on clarity, specificity, visitor-intent match, and friction, with a recommended variant.
Most landing-page A/B decisions are made on taste, then waited on for weeks of traffic. This resource loads two hero/CTA variants for the same product — a generic, adjective-driven version and a specific, intent-matched one — so the comparison shows exactly where one wins before you ship a test: CTA clarity, the specificity of the promise, how well it matches the visitor's intent, and the friction the wording adds. Variant A is the kind of hero most pages launch with; variant B is built on decisions — a named audience, a concrete outcome, an action-plus-value CTA, and a trust line that flags missing proof rather than inventing it. Load your own two variants the same way to see which is stronger and why.
Compare on CTA clarity and friction
The loaded pair targets the same product. Watch how a specific, action-plus-value CTA scores against a generic "Sign Up".
Read B's specificity and intent match
Named audience, concrete outcome, and a low-friction CTA — each a decision A left to the visitor to fill in.
Note what A leaves vague
"Best", "all sizes", "powerful" — every adjective A uses is a promise it doesn't actually make.
Score your own two variants
Load your real A and B hero/CTA drafts and compare them the same way before committing traffic to a test.
It scores both variants on CTA clarity, specificity, intent match, and friction — for example weighing B's "Start free — no card" against A's bare "Sign Up" — but the prompt-comparator surfaces where one wins, it does not declare a truth or ship it. You run the copy in your own assistant and own the final call before committing traffic.
Replace both baked-in blocks with your real drafts: swap out the InvoiceFlow variant A (Headline / Subheadline / Primary CTA / Trust line) and the variant B fields, keeping the same four labels so the prompt-comparator scores your A against your B on the same clarity, specificity, intent-match, and friction axes.
That marker flags an unproven claim rather than inventing proof: B's trust line says "Works with the invoicing tools you already use. [needs evidence: list real integrations]" so the prompt-comparator can score B honestly instead of rewarding a fabricated trust line like A's "Trusted by businesses everywhere." Fill in real integrations before you ship.
A side-by-side way to decide between two ChatGPT prompt drafts — scored on clarity, specificity, output control, and risk instead of gut feeling.
Seven questions that decide between two prompts — audience, format, length control, constraints, criteria, ambiguity, and contradictions.
Two blog prompt variations for the same topic, compared: which one actually controls angle, audience, structure, and length?
A set of before-and-after examples showing exactly what prompt cleanup removes — and what it deliberately leaves alone.
Formats fuzzy agent instructions into a structured prompt with objective, available tools, constraints, success criteria, and failure handling.
Convert scattered bug notes, Slack messages, or user complaints into structured engineering tasks with reproduction steps, severity, and root cause hypothesis.
Compare two prompts side by side — quality scores, strengths, risks, and a clear recommendation.
Write a landing page that converts, not one that just describes — sharpen the value proposition, draft the hero and benefits, answer objections at the CTA, then A/B the variants to pick the stronger.