01 Signal intake
Start with the content asset and the real response.
post / email / guide / lead magnet / proof block
02 Customer tracker row
Make the signal visible in Guide 06.
| Lane | Entry |
|---|---|
| Status | |
| Source signal | |
| Person / context | |
| Problem in exact words | |
| Fit status | |
| Next helpful action | |
| Follow-up reason/date | |
| Proof or lesson |
03 Objection + proof request
Preserve market language before rewriting.
price / trust / timing / complexity / DIY / doing nothing / proof
04 Proposal snapshot
Draft only if fit exists.
| Section | Draft |
|---|---|
| Problem in customer words | |
| Desired after-state | |
| First deliverable | |
| Included | |
| Not included | |
| Inputs needed | |
| Price if approved | Human must approve. |
| Next decision |
05 Follow-up plan
Follow up only for a real reason.
promised resource / missing info / requested reminder / proposal answer / none
truth / tone / privacy / claims / promise / timing
Approval gate
The bridge produces review notes. It never contacts the market by itself.
AI may summarize, extract exact words, classify objections, draft tracker rows, draft proposal snapshots, and create local files. Human approval is required before sending, replying, DMing, calling, posting, scheduling, CRM/account writes, checkout/email connections, price/legal terms, proof publication, or private payment/tax/legal/KYC/identity/customer data use.
No auto-sendNo live CRM writesNo fake proofHuman approves risk06 Fictional sample
Pipeline Health signal.
Signal: “I don't even know which leads my team already answered.” Tracker row: good fit for a small diagnostic, not automation yet. Next helpful action: send a fictional lead-source map sample if a human approves. Follow-up rule: one promised resource; no pressure; no automatic sending.