Broad customer-message review may feed identities and revenue data into marketing proof
Source references: 4The Skill recommends reading every refund email and sales-call transcript from six months, while separately recommending case studies with names, numbers, photos, and revenue metrics. It does not require scope confirmation, customer consent, NDA checks, or de-identification first.
Refund reasons, call contents, customer names, photos, and revenue data could enter model context or marketing materials, exposing personal or commercially confidential information.
The instructions call for reading “every” refund email and sales-call transcript from six months, which may contain customer identities, contact details, complaints, contracts, or business information. Another active recommendation promotes proof using names, photos, and revenue figures. Although the purpose is objection analysis, access authorization, confidentiality review, minimization, and customer consent are still needed before this material enters a model or marketing asset. Users can restrict input to approved, de-identified summaries.
### How to find your buyer's actual objections1. Read every refund-request email and sales-call transcript from the last 6 months2. Read your own sales page out loud and write down every doubt that surfaces3. Ask 3 recent buyers: "What almost made you not buy?"The answers cluster around 3–6 objections. Build a bonus for each.Show 3 other places
### How to increase- **Proof** — case studies with names, numbers, before/after metrics, photos. Specific > glossy.- **Methodology specificity** — name your process. "The 5-step VAULT framework" beats "our proprietary system." Even if the substance is the same, naming it raises perceived likelihood.- **Guarantees** — risk reversal directly raises perceived likelihood (more in [guarantee-design.md](guarantee-design.md)).- **Reduce sample-of-one objection** — show people *like them* who got results. "Other people get results but I'm different" is the universal objection.- **Pre-empt the failure path** — explicitly address what could go wrong and how you handle it. Builds trust faster than hiding the risk.- Name the methodology: "The VAULT framework — 5 angles every winning sales page uses"- Add 8 named-customer case studies with before/after copy + revenue numbers- Add an "even if you've never written before" cohort with 3 named graduatesLowest: effort & sacrifice and perceived likelihood are tied. Pick one (perceived likelihood — easier to move and unblocks more downstream work):- Name the methodology: "The VAULT framework — 5 angles every winning sales page uses"- Add 8 named-customer case studies with before/after copy + revenue numbers- Add an "even if you've never written before" cohort with 3 named graduates