Evidence-Grounded Customer Objection Mining and Offer Rewrite Matrix

Analyze the supplied offer and customer evidence to determine why prospective buyers may hesitate, which messaging or proof gaps contribute to that hesitation, and how the offer can be rewritten without unsupported claims.

## ChatGPT operating boundary
Use ChatGPT to inspect and synthesize only the text, files, links, and evidence made available in this conversation. Do not imply access to analytics, a CRM, customer interviews, competitor accounts, private systems, or live web pages unless the relevant capability is available, explicitly authorized, and actually used. Distinguish analysis and proposed copy from work that was published, approved, tested, or measured. Do not publish copy, contact customers, alter campaigns, or claim conversion impact.

## Inputs
Product or service: [Product or service]
Target audience: [Target audience]
Current offer: [Current offer]
Current landing page or sales copy: [Current landing page or sales copy]
Known objections: [Known objections]
Customer feedback or reviews: [Customer feedback or reviews]
Competitors or alternatives: [Competitors or alternatives]
Pricing: [Pricing]
Proof or case studies: [Proof or case studies]
Guarantee or risk reversal: [Guarantee or risk reversal]
Conversion goal: [Conversion goal]
Brand voice: [Brand voice]
Definition of done: [Definition of done]

## Input gate
Blocking prerequisites are a sufficiently clear product or service, target audience, current offer or representative sales copy, and conversion goal. If any blocking prerequisite is absent or too ambiguous to support a responsible analysis, ask no more than five focused clarification questions and stop before drafting conclusions or copy.

Useful but non-blocking context includes known objections, verbatim customer language, pricing context, proof, guarantees, analytics observations, sales-call notes, competitor materials, funnel stage, traffic source, brand constraints, and the definition of done. If optional context is missing, proceed only where safe, mark the limitation, and identify the evidence needed to resolve it.

If sources conflict, retain the conflict rather than choosing a convenient version. Treat personal opinions, isolated comments, and assumed buyer psychology as hypotheses—not established customer findings. Redact unnecessary personal or confidential information. Do not reuse identifiable customer quotations publicly without appropriate permission.

## Evidence rules
Classify material claims using these labels:
- Supplied fact: directly stated in the provided offer or business context.
- Customer signal: supported by supplied feedback, reviews, interviews, sales notes, or behavioral data.
- Inference: a reasoned interpretation of supplied evidence.
- Hypothesis: plausible but not yet supported by sufficient evidence.
- Unknown: required information is unavailable.
- Conflict: supplied sources disagree.

For important findings, cite the source by artifact name or a short quotation when available. Never invent testimonials, customer quotations, metrics, competitor features, guarantees, research, case-study outcomes, urgency, scarcity, or financial results. A lack of proof is a proof gap, not permission to create proof.

## Analysis workflow

### 1. Establish the evidence base
Create an input and evidence register containing each supplied artifact, what it can support, material limitations, conflicts, and whether it includes direct customer language or measured behavior. State which systems or sources were not accessible.

### 2. Model the current offer
Summarize:
- what is sold and how it works;
- intended buyer, use context, and funnel stage;
- promised outcome and problem addressed;
- price, commitment, time-to-value, and switching burden when known;
- current differentiators, call to action, guarantee, and reason to act;
- strongest and weakest parts of the offer.

Separate explicit claims in the copy from implied promises. Flag claims that need substantiation, qualification, legal review, or clearer scope.

### 3. Map buyer motivations and decision criteria
Identify practical, emotional, financial, status, convenience, and risk-reduction motivations only to the extent supported by evidence. Map likely decision criteria such as fit, expected value, total cost, implementation effort, trust, time-to-value, compatibility, reversibility, and internal approval. Label unsupported motivations as hypotheses and state how they could be validated.

### 4. Mine and classify objections
Extract explicit objections from customer evidence before inferring additional ones. Group relevant objections into price or value, trust, timing, need, complexity, implementation, risk, switching cost, competitor or alternative, proof, and internal approval.

For every objection, distinguish among:
- a genuine offer limitation;
- missing or weak proof;
- unclear messaging;
- audience or traffic mismatch;
- buying-process friction;
- an unvalidated hypothesis.

Do not treat every objection as a copy problem. Preserve legitimate disadvantages and recommend product, pricing, onboarding, proof, or qualification changes when copy alone cannot resolve them.

### 5. Audit proof and claims
For each material promise, record the claim, available supporting evidence, evidence strength, applicability to the target audience, limitations, and status. Use the statuses supported, partially supported, unsupported, conflicting, or unknown.

Assess relevant proof types: testimonials, case studies, demonstrations, screenshots, product samples, methodology explanations, outcome metrics, before-and-after comparisons, credentials, security or compliance evidence, guarantees, process transparency, and comparison evidence. Recommend proof to collect, its appropriate owner or source, and a safe collection method. Do not recommend fabricating or selectively distorting evidence.

### 6. Review competitors and alternatives
Compare only alternatives represented in supplied or actually inspected materials. Include direct competitors, internal workarounds, manual processes, doing nothing, and postponement where relevant. For each comparison, show the source, comparison date if known, buyer criterion, observed difference, uncertainty, and messaging implication.

If competitor evidence is absent or stale, provide a comparison research checklist rather than factual competitor claims. Reposition through relevant differences and trade-offs; do not use unverifiable superiority claims or unfair attacks.

### 7. Prioritize findings
Score each objection using clearly explained qualitative ratings for evidence strength, likely frequency, conversion impact, and addressability. Assign a priority of critical, high, medium, or low. Do not manufacture numerical precision. Explain why the highest-priority objections deserve attention and whether the appropriate response is copy, proof, offer design, product work, sales enablement, or further research.

### 8. Build the objection-handling matrix
For each prioritized objection, provide:
- objection in buyer language;
- evidence label and source;
- underlying concern;
- objection classification;
- affected decision criterion or funnel stage;
- current message or offer weakness;
- truthful response strategy;
- proof required;
- proposed copy angle;
- channel or page placement;
- priority and confidence;
- owner or next evidence action;
- caveat or unresolved issue.

Do not frame dismissal, pressure, false urgency, shame, or concealment of a material limitation as objection handling.

### 9. Rewrite the message system
Draft the following while preserving the supplied brand voice:
- one-sentence value proposition;
- three headline and subheadline options with distinct, named positioning angles;
- concise offer explanation;
- audience qualification statement;
- benefit and mechanism bullets;
- proof module using only available proof or clearly marked proof placeholders described in words without invented content;
- risk-reversal language consistent with the actual guarantee;
- objection-response copy for the highest-priority objections;
- primary and secondary calls to action;
- reason-to-act language only when supported by a genuine deadline, capacity constraint, cost of delay, or timely buyer need.

Annotate each major draft with the evidence or strategic rationale behind it. If a desired claim is unsupported, provide a safer alternative and specify what evidence would be required for the stronger version.

### 10. Recommend landing page architecture
Recommend only sections justified by the buying decision, such as hero, problem, outcome, mechanism, use cases, qualification, how it works, proof, comparison, implementation, objections, FAQ, guarantee, pricing context, and call to action. For each recommended section, specify its communication job, target objection, required evidence, key content, and success signal. Identify sections to remove, merge, or move when they add friction or repeat claims.

### 11. Design validation tests
Propose a restrained test backlog for the conversion goal. Each test must include the hypothesis, audience or funnel stage, control, proposed variant, single primary metric, guardrail metrics, required sample or decision caveat, implementation dependency, and stop condition. Prioritize high-impact uncertainties before cosmetic changes.

Do not report a winner or predicted uplift. If no baseline, analytics data, or adequate testing capability is supplied, mark measurement readiness as blocked and describe what must be instrumented or collected first.

### 12. Prepare the human-review handoff
Identify recommendations requiring approval from marketing, product, sales, legal or compliance, customer success, or analytics. Require human review before publishing claims, customer quotations, pricing, guarantees, regulated statements, competitor comparisons, or campaign changes. Stop and escalate when a material claim lacks support, customer evidence raises a privacy concern, sources materially conflict, or the requested wording would be deceptive.

## Required deliverable

### A. Decision summary
State the offer diagnosis, three highest-priority objections, most consequential proof gaps, recommended positioning direction, and immediate decision required. Include confidence and principal limitations.

### B. Input and evidence register
Use columns: artifact or source, supplied or actually inspected, relevant observation, evidence label, supports, limitation, conflict, and accessibility note.

### C. Current offer and buyer-decision map
Present the offer model, audience, funnel stage, decision criteria, motivations, friction, and explicit versus implied promises.

### D. Objection inventory and prioritization
Separate extracted customer objections from inferred hypotheses. Include classification, evidence, source, likely impact, addressability, priority, and validation need.

### E. Claim and proof-gap ledger
Use columns: claim, current wording, supporting evidence, strength, audience applicability, limitation, status, required proof, safe interim wording, owner, and approval need.

### F. Competitor and alternative comparison
Use evidence-linked criteria and include unknowns, stale information, trade-offs, and research needs. Do not populate unsupported comparisons as facts.

### G. Objection-handling matrix
Provide every field specified in step 8, ordered by priority.

### H. Rewritten message system
Provide the value proposition, headline options, supporting copy, qualification, proof treatment, risk reversal, objection responses, and calls to action. Mark all drafts as proposed and untested.

### I. Landing page content blueprint
For each recommended section, provide purpose, target objection, evidence requirement, content guidance, placement rationale, and intended success signal.

### J. Validation backlog
List each test's hypothesis, control, variant, metric, guardrails, dependencies, stop condition, and current readiness. Keep proposed tests distinct from executed experiments.

### K. Verification and acceptance table
Use columns: check, expected condition, actual observation from supplied materials, evidence, status, and unresolved action. Verify at minimum that:
- every high-priority objection is traceable to evidence or explicitly labeled as a hypothesis;
- every material copy claim appears in the proof ledger;
- no testimonial, metric, result, deadline, guarantee, or competitor fact was invented;
- offer limitations and source conflicts remain visible;
- rewritten copy matches the audience, offer mechanics, brand voice, and conversion goal;
- recommended proof can be collected ethically;
- tests define metrics and guardrails without claiming outcomes;
- publication and approval have not been implied.

Use pass, fail, blocked, or not applicable as statuses. A pass requires cited evidence. If the actual observation cannot be established from supplied materials, use blocked rather than assuming acceptance.

### L. Handoff register
List prioritized next actions, owner, evidence or approval required, dependency, and handoff state using proposed, ready for human review, blocked, or out of scope.

Conclude with a completion statement that accurately identifies what ChatGPT analyzed and drafted, what remained inaccessible or unknown, and what has not been approved, published, tested, or measured.