# 06 — Filled Sample: Content → Customer Bridge

Fictional example only. No real customer, lead, CRM, email, DM, payment, employer, or private data.

## Source content asset

| Field | Filled example |
|---|---|
| Asset name | "Before buying another CRM" email draft |
| Asset type | Email / guide excerpt draft |
| Source work product | Fictional Pipeline Proof Pack sample |
| Buyer | Solo service-business owner with leads scattered across channels |
| Pain explained | Follow-up breaks when inquiries live in forms, DMs, inboxes, notes, and memory |
| Next step offered | Create a local lead-source map before connecting automation |

## Real signal captured

| Field | Filled example |
|---|---|
| Signal type | Fictional reply/question |
| Exact words | "This is us. I don't even know which leads my team already answered." |
| What they seem to want | Visibility before software migration |
| Proof requested | Wants to see what a lead-source map looks like |
| Private / do-not-use | Any names, actual channels, team details, screenshots, revenue, CRM data |

## Guide 06 customer tracker row

| Lane | Entry |
|---|---|
| Status | Needs reply — human approval required |
| Source signal | Reply to CRM/email draft sample |
| Person/context | Fictional local service owner |
| Problem in exact words | "I don't even know which leads my team already answered." |
| Fit status | Good fit for a small diagnostic, not automation yet |
| Next helpful action | Send a fictional lead-source map sample and ask which channels they use |
| Follow-up reason | Promised resource if human approves sending |
| Proof/lesson | Add a FAQ: "What if we don't know which leads were already answered?" |

## Objection / proof request

| Category | Raw language | How to use it |
|---|---|---|
| Trust / proof request | "What does a lead-source map look like?" | Create or route to a fictional sample; do not show real CRM data. |
| Complexity | "I don't know which leads were answered." | Emphasize first step: inventory and status map before automation. |

## Proposal snapshot draft

- Problem: leads exist, but answered/unanswered status is unclear.
- After-state: one visible lead-source map with status, owner, next step, and review rhythm.
- First deliverable: small Pipeline Health snapshot using approved local notes.
- Included: source list, status labels, follow-up gap notes, safe AI draft helper idea.
- Not included: CRM migration, auto-sending, scraping, cold outreach, ads, or live account changes.
- Next decision: human decides whether to offer a small diagnostic or send an educational sample.

## Human-approved follow-up plan

Draft purpose: send the fictional sample and ask one clarifying question.

Human checks before sending: truth, tone, privacy, no implied proof, no CRM claims, no automation promise, no pressure.

Sample draft for human review only:

> You are not alone — answered vs. unanswered status is usually the first thing to make visible. The safest first step is a simple lead-source map, not another automation. I can send a fictional sample of the layout. Which channels do leads currently come from?

## Safety result

- [x] Fictional sample clearly labeled.
- [x] No real customer data.
- [x] No automatic sending or CRM writing.
- [x] No fake proof, revenue, testimonial, screenshot, or outcome claim.
- [x] Human approval required before any real message.