The outcomes we design for
- Speed-to-first-touch under 2 hours for high-intent leads.
- Reply rate lift of 20–35% within 60 days.
- Complaint rate under 0.1% and bounce rate under 1%.
- Clear audit trail: who was messaged, when, and why.
Stack overview
Cadence design that actually converts
We build 2–3 cadences per segment: high-intent, mid-intent, nurture. Each cadence mixes short value emails, SMS nudges, and social-proof drops. Subject lines stay under 6 words; SMS stay under 250 characters. Every branch pauses when a reply is detected.
Behavioral triggers
- Form submits and demo requests → immediate thank-you + fast-lane cadence.
- Page visits (pricing/docs) → short SMS nudge within business hours.
- Link clicks but no reply → branch to a lighter-touch cadence.
- Hard bounces/complaints → automatic suppression and alert to RevOps.
Deliverability guardrails
We warm sending domains, rotate sender identities, and cap daily sends per segment. We validate every email, quarantine risky domains, and drop contacts that fail SMTP checks. Complaint and bounce rates are monitored every 30 minutes; sequences pause if thresholds trip.
Timeline to launch
- Days 1–3: Audience mapping, ICP definition, and content gathering.
- Days 4–7: Build cadences, set up enrichment + validation, warm domains.
- Days 8–10: QA flows, test alerts, and run soft launch on 10–15% traffic.
- Days 11–14: Rollout to full volume, tune copy, finalize dashboards.
Measuring success
We track reply rate, positive replies, meetings booked, revenue influenced, complaint/bounce rates, and time-to-first-touch. Weekly reports show pipeline impact and inbox health with clear next actions.
Common mistakes to avoid
- Over-emailing new domains before warming.
- Using the same copy across all segments.
- Ignoring quiet hours for SMS.
- No suppression logic for hard bounces or complaints.
Playbook to copy
- Enrich + validate every lead before messaging.
- Tag intent (high/mid/low) and route to matching cadence.
- Cap sends per day; pause on complaints over 0.1%.
- Alert humans on replies; stop the bot when a human steps in.
- Review copy weekly; rotate subject lines monthly.
FAQ
Yes. We can add WhatsApp for certain regions with opt-in and template approvals.
We honor quiet hours, include opt-out language, and register numbers where required (e.g., 10DLC in the US).
Yes. We test subject lines, send times, and CTA placement. We default to 70/30 splits with auto-winners.
We add a data-cleanup sprint: normalize phone/email, dedupe, and enrich missing fields before launch.