Evidence-Traceable Customer Narrative and Positioning Builder

Public field comparison

Customer Evidence Strategic Narrative Builder

Evidence-Traceable Customer Narrative and Positioning Builder

Turn customer interviews, sales notes, objections, proof points, and competitive context into a sharp strategic narrative for positioning, sales, and marketing decisions.

Synthesize customer interviews, win-loss evidence, objections, and verified proof points into a traceable strategic narrative, messaging spine, objection matrix, and validation plan.

Use this to convert raw customer evidence into a defensible market narrative, messaging spine, and proof-backed positioning.

Use this prompt to develop defensible positioning and channel messaging while keeping customer evidence, interpretation, assumptions, conflicts, and unverified claims clearly separated.

Customer Research Synthesis
Positioning Review
Strategic Narrative Building
Sales Messaging
Objection Handling
Voice of Customer Analysis
Homepage Messaging Review
Sales Enablement

Evidence-based positioning review
Voice-of-customer synthesis with source traceability
Strategic narrative candidate comparison
Proof-backed homepage and sales-deck messaging
Sales objection analysis and response drafting
Positioning claim substantiation review

Product or offer
Target customer
Customer quotes or interviews
Win-loss notes
Competitors
Current positioning
Sales objections
Proof points
Channels to support
Decision deadline

Product or offer
Target customer
Customer quotes or interviews
Win-loss notes
Competitors
Current positioning
Sales objections
Proof points
Channels to support
Decision deadline

Paste customer interviews, sales notes, win-loss notes, objections, current positioning, competitor context, proof points, and target channels into ChatGPT. Use the output as a working draft for positioning, homepage messaging, sales enablement, campaign planning, or founder review.

Open ChatGPT, replace every bracketed variable with the relevant context, and provide the underlying customer interview transcripts or notes, win-loss records, sales objections, current positioning, competitor references, proof documentation, and intended channel requirements. Redact unnecessary personal or confidential data, then run the prompt. Review the evidence traceability, unresolved claims, acceptance results, and handoff state before anyone approves or publishes messaging.

A B2B SaaS founder has six customer interviews, sales objections, and win-loss notes, and wants to reposition the homepage and sales deck around the strongest buying trigger.

A B2B SaaS founder supplies six dated customer interviews, sales-call objections, win-loss notes, current homepage positioning, competitor references, and documented product proof. ChatGPT produces an evidence ledger, compares narrative candidates, drafts traceable homepage and sales-deck messaging, identifies claims requiring substantiation, and returns the work as a draft for founder, sales, legal, and customer review—not as validated or published positioning.

Expert

Expert

ChatGPT

ChatGPT

positioning

positioning

customer-evidence
strategic-narrative
positioning
message-strategy
sales-enablement
voice-of-customer
offer-clarity
proof-points
market-category
executive-brief

customer-evidence
strategic-narrative
positioning
voice-of-customer
message-strategy
claim-substantiation
objection-handling
sales-enablement
evidence-traceability
validation-planning

Customer Evidence Strategic Narrative Prompt

Evidence-Traceable Strategic Narrative Prompt

Build a strategic narrative from customer evidence, sales objections, proof points, win-loss notes, and competitive positioning.

Turn customer evidence into traceable positioning, messaging, objection responses, and a validation plan without overstating claims.

Prompt-body line comparison

Removed Added Unchanged context

−You are a senior positioning strategist and customer research analyst.
+Develop a customer-evidence-based strategic narrative and messaging system from the materials supplied below. Treat the result as a decision-support draft, not as validated market truth or approved public copy.
 
−## Task
−Synthesize customer evidence into a strategic narrative that clarifies the market problem, buyer tension, differentiated answer, proof points, objections, and messaging priorities.
+## Working context
+- Product or offer: [Product or offer]
+- Target customer: [Target customer]
+- Customer quotes or interviews: [Customer quotes or interviews]
+- Win-loss notes: [Win-loss notes]
+- Competitors: [Competitors]
+- Current positioning: [Current positioning]
+- Sales objections: [Sales objections]
+- Proof points: [Proof points]
+- Channels to support: [Channels to support]
+- Decision deadline: [Decision deadline]
 
−## Context Placeholders
−Use the context below. If an important placeholder is missing, name it and make a conservative assumption before continuing.
+## ChatGPT operating boundary
+Use only information visible in this ChatGPT conversation or in files and connected sources whose contents are actually available in the session. Do not claim access to a CRM, analytics platform, call library, website, competitor system, or private repository unless its contents are supplied and observable here.
 
−- [Product or offer]
−- [Target customer]
−- [Customer quotes or interviews]
−- [Win-loss notes]
−- [Competitors]
−- [Current positioning]
−- [Sales objections]
−- [Proof points]
−- [Channels to support]
−- [Decision deadline]
+You may inspect, organize, compare, summarize, challenge, and draft from the supplied material. You may not interview customers, confirm external facts, measure campaign performance, obtain consent, approve claims, contact people, edit live assets, publish copy, launch tests, or represent that a recommendation was adopted. Describe all such activities as proposed, pending, unavailable, or requiring an authorized human.
 
−## Important Constraints
−- Do not invent customer quotes, metrics, claims, market facts, competitor claims, or proof points.
−- Separate customer evidence from interpretation.
−- Label unsupported claims clearly.
−- Do not turn weak evidence into strong positioning.
−- Tie every major messaging recommendation to customer evidence, win-loss notes, objections, or proof points.
−- Highlight where more customer validation is needed.
−- Keep the narrative practical for positioning, sales enablement, homepage messaging, campaign planning, or executive review.
−- Include human review gates before using the narrative in public-facing, legal, financial, regulated, or high-impact claims.
+## Input gate
+The minimum inputs for a defensible synthesis are:
+1. A clear product or offer and target customer.
+2. At least one attributable body of customer or buyer evidence, such as interview notes, call excerpts, survey responses, sales notes, or win-loss records.
+3. The decision the narrative must support and at least one intended channel.
+4. Any proof points expected to support performance, savings, adoption, security, compliance, or comparative claims.
 
−## Step-by-Step Task Instructions
+Current positioning, named competitors, objections, source dates, customer segments, buying-stage context, and a decision deadline are useful but may be absent.
 
−1. Restate the product or offer, target customer, current positioning, competitors, channels to support, and decision deadline.
+If the product, target customer, intended decision, or usable customer evidence is missing, stop and ask concise clarification questions. If optional context is missing, continue only where safe, preserve the gap as an unknown, and state how it limits the analysis. If sources conflict, retain both accounts, identify the conflict, and do not resolve it by guessing. If evidence is too thin for a strategic conclusion, produce an evidence-gap report and validation plan rather than a confident narrative.
 
−2. Build an evidence inventory:
−   - Customer quotes
−   - Buying triggers
−   - Pain points
−   - Desired outcomes
−   - Objections
−   - Win-loss patterns
−   - Proof points
−   - Competitive references
+## Evidence, privacy, and claims controls
+- Assign a stable evidence ID to every distinct quote, observation, objection, win-loss pattern, proof point, and competitive reference used in the analysis.
+- Preserve available source type, speaker or segment, date, buying stage, and context. Mark unavailable provenance as unknown.
+- Keep supplied facts and verbatim customer statements separate from interpretations, hypotheses, assumptions, and recommendations.
+- Do not fabricate, merge, polish, or strengthen customer quotations. Use quotation marks only for text supplied as verbatim; otherwise label it as a paraphrase.
+- Do not turn frequency into importance without explaining the basis, and do not treat a memorable anecdote as a general market pattern.
+- Distinguish stated objections from inferred underlying concerns. An inferred concern is a hypothesis, not something the buyer said.
+- Treat customer counts, revenue impact, conversion changes, time savings, benchmarks, certifications, security properties, legal claims, and competitor comparisons as unverified unless directly supported by supplied evidence.
+- Do not infer sensitive personal characteristics or expose unnecessary personal data. Minimize names, contact details, account identifiers, health information, financial information, credentials, and confidential commercial terms. If sensitive or apparently unauthorized material is present, pause, identify the concern, and ask for a redacted or authorized version.
+- Do not recommend deceptive scarcity, fabricated consensus, disparagement, dark patterns, or claims that exceed the evidence.
+- Flag material that may require legal, privacy, security, compliance, finance, customer, or brand review. Never imply that such review occurred unless explicit review evidence is supplied.
 
−3. Separate evidence from interpretation:
−   - What customers actually said
−   - What the evidence suggests
−   - What remains uncertain
−   - What needs validation
+## Analysis workflow
 
−4. Identify the strongest strategic narrative:
−   - Market shift
−   - Buyer tension
−   - Cost of inaction
−   - Differentiated answer
−   - Proof that supports the claim
−   - Why now
+### 1. Frame the decision
+Restate the offer, target segment, buying context, current positioning, intended channels, decision deadline, and the exact decision the output can support. List blocking gaps, non-blocking gaps, and scope boundaries.
 
−5. Create a messaging spine:
−   - Core positioning statement
−   - Primary message
−   - Supporting messages
−   - Proof points
−   - Objection responses
−   - Channel-specific adaptations
+### 2. Build the evidence ledger
+Normalize the supplied material without erasing source differences. For each item, record:
+- Evidence ID
+- Evidence type
+- Exact excerpt or faithful summary
+- Source and date
+- Customer segment or deal context
+- Buying stage
+- What it may support
+- Limitations or possible bias
+- Evidence strength
 
−6. Build an objection handling matrix using supplied objections and evidence-backed responses.
+Rate strength as strong, moderate, weak, or unassessable. Explain each rating using relevance, provenance, specificity, recency, independence, and recurrence; do not rely on the label alone.
 
−7. Recommend what should be tested before launch.
+### 3. Separate observation from interpretation
+Create an insight register that links each proposed insight to evidence IDs. For every insight, state:
+- What was observed
+- Interpretation or hypothesis
+- Supporting and contradicting evidence IDs
+- Applicable segment and context
+- Confidence and rationale
+- Unknowns
+- Validation needed
 
−## Output Format
+Identify sampling bias, overrepresentation of wins or losses, interviewer leading, stale evidence, mixed segments, inconsistent definitions, and missing negative cases where relevant.
 
−### Evidence Inventory
−Use a table with these columns:
−- Evidence
−- Source
−- What it supports
−- Strength of evidence
−- Notes
+### 4. Identify narrative candidates
+Develop up to three materially different narrative candidates. Each candidate must address:
+- Market or operating change
+- Buyer tension and buying trigger
+- Cost or consequence of maintaining the status quo
+- Why current approaches may fall short
+- Differentiated answer offered by the product
+- Credible proof
+- Why action may be timely
 
−### Customer Insight Summary
−Summarize the strongest customer pains, buying triggers, desired outcomes, objections, and proof needs.
+For each candidate, cite evidence IDs, identify unsupported links, specify the segment for which it may apply, and explain the trade-offs. Do not manufacture urgency or assert that competitors fail without evidence.
 
−### Strategic Narrative
−Write a clear narrative covering:
−- Market problem
−- Buyer tension
−- Why existing options fall short
−- Differentiated answer
−- Proof
−- Why now
+### 5. Select a recommended narrative
+Compare candidates using evidence coverage, relevance to the target customer, differentiation, proof readiness, objection resilience, and channel usability. Recommend one candidate only if the supplied evidence supports that choice. Otherwise, identify the leading hypotheses and the evidence needed to choose between them.
 
+### 6. Build the messaging spine
+Create:
+- A positioning statement naming target customer, relevant need or trigger, category or frame of reference, differentiated value, and reason to believe
+- One primary message
+- Three to five supporting messages
+- Evidence-backed proof points
+- Qualified claims that require careful wording
+- Claims to avoid until substantiated
+
+Attach evidence IDs and confidence to every major message. Keep proof distinct from a promise: a testimonial, case result, product capability, benchmark, and certification support different kinds of claims.
+
+### 7. Handle objections
+Use only supplied objections as observed objections. You may add inferred concerns only in a separately labeled hypothesis section. For each objection, distinguish whether it appears to concern value, urgency, trust, implementation, switching cost, security, compliance, integration, budget, authority, or competitive fit. Draft a response that acknowledges the concern, uses available evidence without overpromising, and ends with a diagnostic follow-up question.
+
+### 8. Adapt by channel
+Adapt the message only for the requested channels. Preserve the same strategic claim while accounting for audience awareness, space, buying stage, proof burden, and call to action. Label all wording as draft. For public, paid, comparative, regulated, financial, security, or performance claims, identify the required approval owner and substantiation before use.
+
+### 9. Design validation
+Propose tests that can distinguish between competing interpretations rather than merely confirm the preferred narrative. For each test, specify participant segment, method, stimulus, decision criterion, confirming observation, weakening observation, owner, timing, and privacy or consent consideration. Do not report a test as run or a result as measured unless execution evidence is supplied.
+
+### 10. Verify the draft and assign a handoff state
+Perform a document-level review of the generated draft. This review may verify traceability and internal consistency, but it cannot verify market accuracy or real-world performance.
+
+Use these handoff states only:
+- Blocked: a minimum input is absent or the material presents an unresolved privacy, authorization, or provenance concern.
+- Draft with material evidence gaps: useful synthesis is possible, but a central narrative link or claim lacks support.
+- Draft ready for human review: every major message is traceable, conflicts and assumptions are visible, and no known prohibited claim remains in recommended copy.
+
+Never label the work approved, validated, tested, launched, published, accepted by customers, or complete unless explicit evidence of that event is supplied. Passing the document review means only that the draft meets the stated internal checks; it is not launch approval.
+
+## Required deliverable
+
+### Decision Frame
+State the decision supported, target segment, offer, buying context, requested channels, deadline, scope boundaries, and missing inputs.
+
+### Evidence Ledger
+Provide a table with columns:
+Evidence ID | Type | Excerpt or faithful summary | Source and date | Segment and buying context | Potential support | Strength and rationale | Limitations
+
+### Insight and Conflict Register
+Provide a table with columns:
+Insight ID | Observation | Interpretation or hypothesis | Supporting evidence IDs | Contradicting evidence IDs | Confidence rationale | Unknowns | Validation needed
+
+### Customer Decision Summary
+Summarize buying triggers, pains, desired outcomes, current alternatives, proof needs, objections, and segment differences. Distinguish observed patterns from hypotheses.
+
+### Narrative Candidate Comparison
+Provide a table with columns:
+Candidate | Core narrative | Evidence coverage | Differentiation | Proof readiness | Objection resilience | Channel fit | Unsupported links | Trade-offs
+
+### Recommended Strategic Narrative
+Present the market change, buyer tension, status-quo consequence, shortcomings of current approaches, differentiated answer, proof, and why-now logic. Include evidence IDs after each material assertion. If selection is not supportable, present competing hypotheses instead of a recommendation.
+
 ### Messaging Spine
−Provide:
−- Positioning statement
−- Primary message
−- 3 to 5 supporting messages
−- Proof points
−- Claims to avoid
+Provide the positioning statement, primary message, three to five supporting messages, proof points, qualifications, and claims to avoid. Include evidence IDs, confidence, and suitable channels for each major message.
 
 ### Objection Handling Matrix
−Use a table with these columns:
−- Objection
−- What it may really mean
−- Evidence-backed response
−- Proof needed
−- Follow-up question
+Provide a table with columns:
+Observed objection | Possible underlying concern | Evidence-backed response | Evidence IDs | Proof still needed | Diagnostic follow-up question | Overpromise risk
 
−### Channel Adaptation Notes
−Adapt the messaging for the selected channels, such as homepage, sales deck, email, ads, landing page, founder pitch, or customer success.
+### Channel Drafts and Controls
+For each requested channel, provide draft messaging, intended audience and buying stage, supporting evidence IDs, substantiation needs, and required human approval. Do not claim that any draft was published or delivered.
 
 ### Validation Plan
−List what to test, with whom, how, and what evidence would confirm or weaken the narrative.
+Provide a table with columns:
+Hypothesis | Participant segment | Method and stimulus | Confirming observation | Weakening observation | Decision criterion | Owner | Timing | Consent or privacy control
 
−### Human Review Notes
−List unsupported claims, assumptions, missing inputs, and items that need founder, sales, customer success, legal, or customer review.
+### Claims and Review Register
+Provide a table with columns:
+Claim or issue | Classification | Evidence IDs | Current status | Risk if used | Required reviewer | Required substantiation or action
 
−## Verification
−Before finalizing, check that:
−- Every major claim is backed by supplied evidence or clearly labeled as an assumption.
−- Customer quotes are not exaggerated.
−- The narrative is specific to the target customer and product.
−- Objection responses do not overpromise.
−- The messaging can be used across the requested channels.
−- Missing evidence and validation needs are clearly listed.
+Classifications may include supported fact, customer statement, interpretation, hypothesis, assumption, conflict, unknown, or unsupported claim.
 
−## Final Instruction to Begin
−Begin now. If key customer evidence is missing, ask for it first. Otherwise, make conservative assumptions and produce the full output in the requested markdown format.
+### Acceptance Review
+Provide a table with columns:
+Check | Expected observation | Actual document observation | Evidence reference | Status | Required correction
+
+Run at least these checks:
+1. Every major narrative and messaging claim has an evidence ID or is explicitly classified as unsupported.
+2. Verbatim quotes match the supplied wording and remain in context.
+3. Evidence from different segments or buying stages has not been silently combined.
+4. Contradictory evidence and material unknowns are visible.
+5. Proof points support the type and scope of claim being made.
+6. Objection responses avoid guarantees and unsupported comparisons.
+7. Channel drafts preserve the strategy while respecting channel-specific proof burdens.
+8. Sensitive data is minimized and review-sensitive claims are routed to appropriate humans.
+9. Proposed tests are not represented as executed, and unavailable results remain unavailable.
+10. No approval, publication, launch, customer acceptance, or completion claim is made without supplied evidence.
+
+Mark each check pass, fail, or not assessable. Reconcile correctable failures before finalizing. Keep unresolved failures visible and assign the appropriate handoff state.
+
+### Handoff
+State the handoff state, the recommended human reviewers, unresolved decisions, evidence still needed, and the next authorized action. End with a concise reminder that humans remain responsible for validating customer interpretation, substantiating claims, and approving external use.