testimonial-collectorlisted

# Testimonial Collector ## Mode Detect from context or ask: *"One script, full system, or full system with campaign?"* | Mode | What you get | Best for | |------|-------------|----------| | `quick` | 1 outreach script + 1 format template | Asking one client, right now | | `standard` | Full collection system: timing, scripts, formatting, display guidance | Building repeatable social proof | | `deep` | Full system + multi-channel strategy + case study pipeline | Sales enablement, proposal library | **Default: `standard`** — use `quick` if they have one client in mind. Use `deep` if they want a system they can hand to a VA. --- ## Context Loading Gates **Before proceeding, gather:** - [ ] Client name, company, and industry - [ ] Project type and specific deliverables - [ ] Key results — push for at least one number ("even a rough estimate") - [ ] Desired output format (short quote / medium paragraph / full narrative) - [ ] Urgency (this week vs. building a library) If results are vague (e.g., "things improved"), **stop and ask:** "Can you name one specific number — even a rough estimate? That's what makes a testimonial credible and usable." Do not draft until you have this. If the user wants to skip a field: note it and flag the quality impact in the output. --- ## Phase 1: Situation Analysis Before drafting anything, reason through: 1. **Client relationship stage:** Was this a quick project or a deep engagement? Depth affects how much authentic language is availabl