build-outbound-enginelisted

# /build-outbound-engine — DM Operations Engine > **Purpose.** Build the canonical outbound DM operations engine — the intent taxonomy, the per-intent sequences, the qualification thread, the booking gate, the lead-list spec, and the operator/VA handoff protocol. This is the engine that runs ~300-500 DMs/month per account at >25% qualified-reply rate. > > **Bar.** A VA running this engine, with the spec + lead list, must produce more qualified booked calls than a $5K/month outsourced SDR. Verified by side-by-side comparison. > > **The 1-of-1 primitive.** Most LinkedIn agencies run one cold sequence to one list. This engine runs **four sequences keyed to four intent classes**. The classification is the leverage; the sequences are the execution. ## When to invoke - New operator onboarding (build for `agency-outbound`) - New client signed → after the client's ICP is built (build `client-outbound`) - DM reply rate <8% (re-build — sequences stale or ICP-list mismatch) - Booking-gate leak (calls booked but no-show rate >35%) — re-build qualification thread - Quarterly DM-sequence refresh (LinkedIn detects template repetition; refresh prevents shadow-banning) ## Required inputs 1. ICP profile ≥75% (from `/build-icp`) — voice-of-customer language is load-bearing 2. Voice profile ≥60% (from `/extract-founder-voice`) — DMs in the wrong voice destroy authority 3. Service-tier offer ≥60% (from `/design-retainer-offer`) — DMs funnel toward this offer 4. **Past DM data** (if available