plugins/marketing/skills/testimonial-harvesting/SKILL.md
Builds a pre-launch social proof strategy through structured beta programs using D'Souza Brain Audit interviews. Use when launching new products/services and need compelling testimonials, planning a beta cohort, designing interview questions to harvest objection-busting social proof, improving video testimonials for landing pages, or designing case studies with metrics. Trigger phrases include "beta tester program for testimonials", "pre-launch social proof", "Brain Audit testimonial framework", "case study harvest", "reverse testimonial", "video testimonial mechanics", "social proof landing page", "sběr referencí", "beta tester program", "testimonial pro landing page", "social proof před launchem", "rozhovor s klientem", "case study sběr", "reference před spuštěním". NOT for ongoing case study production (use growth-hacking case-study approach), offer design (use offer-creation), or conversion optimization (use ux-optimization).
npx skillsauth add petrogurcak/skills testimonial-harvestingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Testimonial-harvesting is a systematic process for generating social proof before public launch through a structured beta program and strategic interviews. The core principle — from Sean D'Souza's Brain Audit framework — is that testimonials are constructed, not harvested. Using a 6-question interview script designed to expose objections first (reverse testimonials) rather than elicit praise, a 10-person paid beta cohort over 6 weeks produces 8-10 usable testimonials, 3-5 video cases, and measurable metrics to support the launch narrative.
Announce: "I'm using testimonial-harvesting to build objection-crushing social proof using the Brain Audit framework and video testimonials."
USE this skill:
DON'T use this skill:
growth-hacking case-study approachoffer-creationux-optimizationproduct:discoverySean D'Souza's Brain Audit framework (Psychotactics) is the canonical foundation because it reframes testimonials from praise-gathering to objection-crushing. Unlike generic "tell us what you loved" approaches, Brain Audit forces a two-step narrative:
The Mirror-image Rule (D'Souza) states: identify your 3-5 biggest sales objections, then harvest 1 testimonial per objection using Q1 to surface it naturally. Result: testimonials that pre-handle specific buyer hesitations rather than generic praise.
7 Red Bags Concept: If a testimonial sounds like a "résumé" (vague, polished, abstract), it's a red bag. Brain Audit forces specificity through concrete questions — "specific feature" (Q3), "story/example" (implicit in conversational flow).
Cohort size: 10 testers (Nielsen sweet spot for variety + manageability; 5–15 is acceptable range).
Recruitment: DM or email 30–50 most-engaged people from your existing audience, Twitter/LinkedIn connections, or community. Use application form (Typeform/Tally) to filter for ICP-fit and ability to articulate results. Select 10 who show commitment signals: detailed form answers, relevant problem they're solving.
Offer structure (paid beta mandatory):
Why paid betas work: Free beta attracts tire-kickers with zero commitment. Paid filters for invested testers who actually finish the program and generate usable testimonials. Industry consensus: "If you charge from day one, you weed out the people who won't finish."
Format: 20–30 minute recorded Zoom call. Ask conversationally, not like a rigid questionnaire. Let answers breathe — follow curiosity, dig into specifics.
| Q# | Question | Why it matters | Expected yield | |---|----------|---|---| | Q1 | "What was the obstacle or hesitation that would have prevented you from buying/joining?" | Reverse testimonial. Most powerful question. Surfaces specific objections a prospect might have. Q1 answer becomes a proof-point that crushes that exact objection when you say "Q2: here's what shifted." | "I thought I couldn't fit it into my schedule" / "I was worried it was just another course that overpromises" | | Q2 | "What did you find as a result of buying/using this? What shifted?" | Transformation proof. Directly answers Q1. Shows that specific hesitation was unfounded. Q1 + Q2 pair = complete objection-busting narrative. | "I actually saved 5 hours a week and could scale while my kids were sleeping" | | Q3 | "What specific feature or moment did you like most about the product/service?" | Concrete detail. Prevents vague praise ("it's great"). Forces specificity tied to actual experience. | "The daily templates — I just had to fill in 3 blanks instead of building from scratch" | | Q4 | "What would be three other benefits you got, beyond the main result?" | Going wide. Shows secondary/unexpected value. Prevents single-benefit positioning. | "1) Community accountability kept me consistent, 2) Email copy library was a bonus, 3) I finally felt like I had a system" | | Q5 | "Would you recommend this to someone? If so, why? Who specifically?" | Psychological commitment. Forces them to articulate buyer profile. Creates natural "this is for X type of person" framing. | "Yes — to other e-commerce founders who are bootstrapped and tired of agencies taking 30% of revenue." | | Q6 | "Is there anything else you'd like to add? Anything a future customer should know?" | Warm-state mining. Captures unprompted insights, unexpected concerns, or strongest emotional moment they want to highlight. | "Honestly, the thing I'd tell someone hesitating is that the first 2 weeks felt slow, but by week 4 it compounded. Don't quit early." |
Interview Structure (30 min total):
Pro tips:
Step 1: List your top 3–5 sales objections.
Example:
Step 2: During recruitment or intake, note which objection each beta tester represents most strongly (their Q1 answer).
Step 3: Harvest 1 primary testimonial per objection using Q1 to surface it, Q2 to crush it.
Output: 3–5 mirror testimonials, each directly addressing one objection. When a prospect visits your landing page, they see their specific hesitation reflected and immediately see it's been overcome.
Example mirror testimonial placement:
Justin Welsh (LinkedIn OS course, 250+ testimonials) discovered: capture testimonials at week 3, not end-of-cohort.
Welsh's data: 70% testimonial yield rate at mid-course vs ~30% at end. Reason: week-3 energy is still high, they haven't plateaued, unexpected wins are fresh. By week 6, some have tuned out; others are tired.
Dual-capture strategy:
Intermission testimonial is often warmer and more energetic. Closure testimonial has actual results/ROI to cite.
Video testimonials convert 2–3x better than written on landing pages. Wyzowl 2024 data: 72% trust uplift (video vs written), 79% influenced to buy after watching, 64% more likely to purchase.
Recording setup (Zoom):
Post-production workflow:
Caption requirement (non-negotiable):
Trust signals to capture:
Why: GDPR penalty up to 4% global revenue or €20M. Cannot reuse testimonials without documented consent.
Form fields (required, explicit opt-in language):
TESTIMONIAL CONSENT & DATA USAGE AGREEMENT
I give permission to [YOUR NAME/COMPANY] to use:
□ My full name
□ My job title and company/organization
□ My photo/headshot
□ My video recording
□ Direct quotes from our conversation
□ Case study narrative with results/metrics
Permitted usage channels (check all that apply):
□ Website/landing pages
□ Email marketing campaigns
□ Social media (LinkedIn, Twitter, etc.)
□ Paid advertising (Google Ads, Facebook, LinkedIn Ads)
□ Case study PDFs and downloadable resources
□ Podcasts/webinars
□ Print materials
I understand:
☐ My testimonial will be edited for clarity and length
☐ My data is stored securely and not shared with third parties
☐ I can withdraw this consent anytime by emailing [EMAIL]
☐ Upon withdrawal, my testimonial will be removed from public channels within 30 days
☐ Your company will delete my data within 30 days of withdrawal request (except legal obligation)
☐ Data retention: [6 months / 1 year / 2 years] after campaign ends
Signature: ________________ Date: ________
Email: ________________
EU-specific clause:
Per GDPR Article 7, I confirm this consent was freely given, specific, informed, and unambiguous. I have a right to withdraw at any time.
Implementation notes:
| Tool | Purpose | Cost | Notes | |------|---------|------|-------| | Senja | Testimonial collection + widget + Wall of Love | $16/mo | Best value for solopreneurs; 26 integrations; free tier = 15 testimonials | | Descript | Auto-transcription + edit-by-text video editing | $24/mo (Creator) | Superior for podcast-style interview editing; AI summary function | | Zoom Pro | Recording, cloud storage, transcription | $14.99/mo | Most people already have; enables "Record separate audio" | | Tally or Jotform | Consent + intake forms with audit log | $0–19/mo | Free tier sufficient for <1000 responses | | Optional: Loom | Async feedback capture (beta testers submit weekly Loom) | $10/mo | Alternative if testers prefer video feedback | | Optional: Testimonial Hero | Done-for-you video production | $7,800/year | Premium service; use only if budget allows or high-ticket offer | | Total | ~$55–65/mo during 6-week launch phase | Drop to $16/mo (Senja free tier) post-launch if needed |
Above fold:
Mid-funnel (where doubt creeps in):
Below fold (case study deepening):
Footer:
Tone & narrative:
Visual presentation:
Legal (GDPR + local):
Testimonial authenticity verification (Omnibus compliance):
| Mistake | Why it fails | Fix | |---------|------------|-----| | "Would you write a testimonial for us?" | Blank page paralysis. No structure, no prompt, they deliver generic praise or nothing. | Use 6-question Brain Audit script. Structure forces specificity. | | End-of-cohort capture only | Energy drops, some testers have mentally moved on, unexpected wins are stale. 30% yield. | Dual-capture: intermission (week 3) + closure (week 6). 70% yield. | | "Sugary" praise testimonials | "Amazing product, highly recommend" — red bag. Zero specificity, zero objection-busting. | Q1 (obstacle) + Q2 (transformation) forces authenticity. Specific examples (Q3) anchor credibility. | | Random pile of testimonials | No strategy. Reads like generic praise heap. Doesn't address buyer hesitations. | Mirror-image rule: 1 testimonial per top objection. Strategic placement. | | Email interview > phone | Email = stilted, polished, filtered. Phone = conversational, stories, unexpected detail. Welsh = 15–20min phone yields 5× content depth. | Always phone/Zoom. Record. Transcribe. Edit written + video variants later. | | Missing consent documentation | Can't legally use after 6 months. Violates GDPR. Buyer uncertainty. | Signed consent form before interview. Store linked to testimonial record. Audit log. | | Free beta | Attracts tire-kickers. Low commitment, no testimonials, wasted 6 weeks. | Charge 50–70% off. Filters for invested testers. Generates testimonials + validates demand. |
Week 1–2: Planning & Recruitment
Week 3: Beta Cohort Starts
Week 3: First Testimonial Capture (Intermission)
Weeks 4–6: Ongoing
Week 6: Closure Testimonial Capture
Week 7–8: Wrap-up & Production
Launch:
Research source: /Users/petrogurcak/Projects/skills/docs/research/2026-05-12-testimonial-harvesting-beta.md (D'Souza Brain Audit canonical + Claude WebSearch + Gemini grounding + Wyzowl 2024 data + Justin Welsh case data)
Key sources cited:
development
Use when planning a product launch and the product type is unclear or could be either generic (SaaS/app/physical) or info-product. Routes between marketing:launch-strategy (generic launches) and marketing:info-product-launch (courses, memberships, ebooks, cohorts, communities). Trigger phrases - "launch", "spuštění", "go-to-market", "product launch", "release strategy", "uvedení na trh", "launch plan", "spuštění produktu", "launch sequence", "launch strategy". Do NOT trigger when product type is already clear (use specific skill directly).
testing
Specialized 8-week launch cadence for info-products — online courses, cohort programs, memberships, communities, ebooks, masterminds. Combines Jeff Walker's Product Launch Formula (Seed/Internal/JV variants, PLC sequence, open-cart day-by-day) with Stu McLaren's membership mechanics (closed cart, Success Path) and Hormozi Grand Slam Offer stacking. Use when planning "launch online kurzu", "info-product launch", "PLF launch", "course launch", "membership launch", "cohort launch", "ebook launch", "open cart close cart", "8-week launch of online course", "beta cohort to launch sequence", "spuštění kurzu", "launch členské sekce", "open cart strategie". Differentiates from marketing:launch-strategy (generic SaaS/app launches) — info-product-specific. NOT for SaaS launches, physical products, or services.
development
Use when releasing an Expo/React Native mobile app to App Store and Google Play - covers eas submit, ASC "Submit for Review", Play promote Internal→Production, OTA update, and decoding common silent failures (Apple agreement expiry, missing English locale, Background Location declaration, web bundle failure on react-native-maps).
data-ai
Use when writing long-form video scripts that need retention engineering and narrative structure. Trigger phrases - "writing YouTube video script", "VSL (video sales letter)", "long-form video script", "course module video", "explainer video", "retention curve optimization", "video script for course", "scénář YouTube videa", "VSL skript", "long-form video", "scénář kurzového videa", "video script". Do NOT use for short-form TikTok/Reels under 60s — use copywriting:ig-content.