Growth
Customer Proof Packet
Package customer evidence into useful proof without laundering private details into public copy.
Use when
A promising customer story, testimonial, support win, or product result could become marketing proof but contains private context or unsupported claims.
Intermediatedifficulty
Growthcategory
Mia daily expansionsource
Cadence
Before publishing a case study, testimonial, sales claim, or investor/customer proof point
Verification
Each public-safe claim maps to approved evidence, private details are redacted, and anything using a name, logo, metric, or quote is queued for explicit approval.
Structured loop spec
| Field | Value |
|---|---|
| Name | Customer Proof Packet |
| Category | Growth |
| Trigger | Before publishing a case study, testimonial, sales claim, or investor/customer proof point |
| Objective | Package customer evidence into useful proof without laundering private details into public copy. |
| Allowed inputs | Relevant files, source notes, logs, tests, screenshots, metrics, or task state for this loop |
| Allowed actions | Gather approved inputs: notes, call clips, support threads, metrics, screenshots, contracts, or quotes, and mark their permission status.; Extract the problem, before state, intervention, measurable outcome, objection resolved, and audience relevance without adding unsupported claims.; Redact names, logos, revenue numbers, screenshots, account details, and timelines unless permission is already explicit.; Draft a proof packet with claim, evidence, confidence, allowed attribution, required approvals, and suggested asset formats.; Do not publish, send to prospects, use logos, name customers, or cite precise metrics until the approval queue is cleared. |
| Verification | Each public-safe claim maps to approved evidence, private details are redacted, and anything using a name, logo, metric, or quote is queued for explicit approval. |
| Stop condition | Stop when the verifier passes, the budget is exhausted, no progress is made, a blocker appears, or approval is required. |
| Budget | Set a time, turn, token, retry, file, or dollar cap before running the loop. |
| Approval boundary | Human approval required before publishing, sending, deleting, spending, changing accounts, touching production, or making reputational/legal/financial commitments. |
| Safe output | Draft, report, checklist, table, or approval-gated recommendation |
| Works with | Claude, ChatGPT, Gemini, any tool-using AI assistant |
Steps
- Gather approved inputs: notes, call clips, support threads, metrics, screenshots, contracts, or quotes, and mark their permission status.
- Extract the problem, before state, intervention, measurable outcome, objection resolved, and audience relevance without adding unsupported claims.
- Redact names, logos, revenue numbers, screenshots, account details, and timelines unless permission is already explicit.
- Draft a proof packet with claim, evidence, confidence, allowed attribution, required approvals, and suggested asset formats.
- Do not publish, send to prospects, use logos, name customers, or cite precise metrics until the approval queue is cleared.
Prompt
Run the Customer Proof Packet loop. Given customer notes, testimonials, support wins, call clips, metrics, or screenshots, extract the problem, before state, intervention, outcome, objection resolved, and audience relevance. Map every claim to evidence and permission status. Redact private details unless approval is explicit. Produce a proof packet with claim, evidence, confidence, allowed attribution, approval queue, and suggested asset formats. Do not publish, send externally, name customers, use logos, or cite precise metrics without approval.Run in Claude Code
Paste this into Claude Code (or any tool-using agent) to run the loop bounded: one change per round, the same verification every round, durable state files, and explicit stop conditions.
Run the "Customer Proof Packet" loop from AI Loop Library (https://ailooplibrary.com/loops/customer-proof-packet/) as a bounded loop.
Goal: Package customer evidence into useful proof without laundering private details into public copy.
Rules: one change per round; run the same verification every round (Each public-safe claim maps to approved evidence, private details are redacted, and anything using a name, logo, metric, or quote is queued for explicit approval.); append each round to docs/loops/customer-proof-packet/progress.md and update docs/loops/customer-proof-packet/state.json; stop on verifier pass, 8 rounds, 3 consecutive failed verifications, no progress, a blocker, or anything needing human approval (money, production, outbound, deletion). Finish with a proof report: rounds used, changes made, verification output, remaining risk, and the next human decision.