Evidence-Traceable Customer Narrative and Positioning Builder

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.

## 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]

## 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.

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.

## 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.

Current positioning, named competitors, objections, source dates, customer segments, buying-stage context, and a decision deadline are useful but may be absent.

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.

## 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.

## Analysis workflow

### 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.

### 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

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.

### 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

Identify sampling bias, overrepresentation of wins or losses, interviewer leading, stale evidence, mixed segments, inconsistent definitions, and missing negative cases where relevant.

### 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

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.

### 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 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
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 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
Provide a table with columns:
Hypothesis | Participant segment | Method and stimulus | Confirming observation | Weakening observation | Decision criterion | Owner | Timing | Consent or privacy control

### 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

Classifications may include supported fact, customer statement, interpretation, hypothesis, assumption, conflict, unknown, or unsupported claim.

### 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.