The opportunity
Villatoro Executive Search needed an internal operating system for outbound recruiting: find companies that are hiring, enrich decision-makers, put the best ones on a daily call list, and pursue them with email and text. The founder was stitching Instantly, Klaviyo, and Twilio into one motion and burning hours that should have gone to clients.
The firm already had the hard parts of an operating picture. Pipeline and company detail lived in one CRM. Today’s List was the daily call surface. Enrichment and presence checks already ran on a schedule. AI call openers were wired. Ops discipline was real, including a release channel for the worker after a live incident taught them why loading agents from the edit directory is a bad idea.
What was missing was the pursuit layer: a sequencer that behaved like Instantly-style domain rotation and Klaviyo-style flows, but for executive search. Plain text, no tracking pixels, and replies treated as the product instead of a side effect. The human outcome we optimized for was simple. Give the founder more time, increase outreach capacity by 3×, and make it easier to find more clients.
Before
- Spray-and-pray tools optimized for volume and opens
- Marketing automation built for ecommerce lists and pixels
- DIY sequences that treat any reply as stop
- Founder time trapped stitching Instantly, Klaviyo, and Twilio
After
- Manual Call List gate before every sequence
- Intent-aware replies as the product
- Email + iMessage on one pursuit system
- 3× outreach capacity with founder time back
Why recruiting outreach usually breaks
Spray-and-pray tools optimize volume and open rates. That is the wrong fitness function when every contact is hand-vetted and a “yes” is a conversation, not a click.
Marketing automation has beautiful flows, but it assumes ecommerce-style lists, tracking pixels, and unsubscribe pages. Wrong channel posture for B2B cold outreach paired with iMessage.
DIY CRM sequences usually treat any reply as “stop,” which collapses a booked meeting and an unsubscribe into the same state. The system cannot tell the difference between interest and opt-out, so it cannot act differently.
We needed something that only sequences contacts a human put on the Call List, personalizes every step from company + job + contact context, treats reply intent as first-class product behavior, stays out of spam, and syncs with the recruiter’s call workflow instead of a parallel ghost system.
Manual-first automation
The design thesis starts with a gate.
A recruiter adds a contact to the Call List. That is the consent to pursue. Enrichment is never enrollment. Capacity and eligibility checks run next; if the pool cannot send, the contact waits in a pending queue with a clear Admin badge instead of creating an alert storm.
Once enrolled, the system drafts the full thread as one coherent narrative: intro email, text, follow-up, text, follow-up, final text across ten days. Then it sanitizes hard: plain text, no cold links, no AI tells, no leftover placeholders. Dispatch respects contact-local business hours with jitter. Texts only fire when the contact is actually iMessage-capable.
That is Instantly + Klaviyo + Twilio capability without renting three products that were never designed for executive search, and without making the founder the integration layer.
Replies are the product
Most sequencers stop when anything comes back. We built the opposite posture: inbound is the centerpiece.
Email and iMessage land in one inbound surface. The channel that spoke does not matter. An intent classifier and rule engine decide what happens next.
Yes stops the sequence without suppressing the contact, auto-replies with real calendar free/busy windows, notifies the owner, and cancels sibling pursuits at the same company. No suppresses that contact only. Out-of-office reschedules a few business days instead of killing the thread. Courtesy stops and flags for human review. Soft bounce retries; hard bounce suppresses. Transactional product email never shares fate with outreach health.
Call List statuses and reply intents write to the same engine. Meeting Scheduled, Not Interested, and Do Not Contact are not a separate CRM drama. They are the same pursuit system speaking two dialects.
Honest deliverability
We refused open-and-click theater.
Cold mail stays plain text and link-free. Health comes from bounces, complaints, and reply rates: signals that survive without a tracking pixel. Dedicated outreach domains warm up with a state machine that can roll back. Sending profiles rotate with capacity-weighted selection and auto-pause on complaint spikes. Outreach keys stay isolated from call sheets and alerts so a cold campaign cannot take down product email.
List-Unsubscribe lives in headers so the body can stay clean. Append-only enrollment events and a GDPR deletion path ship as product features, not afterthoughts. iMessage stays human-vetted personal volume, not carrier SMS dressed up as intimacy.
Five invariants we refused to renegotiate
The plan was not a one-shot. Critique rounds killed the easy answers.
Linear “stop on any reply” became an intent classifier. Single-domain sending became rotation without pixels. Fixed cadence became a flow engine before a visual canvas. Auto-enroll on enrich died in favor of the Call List gate. Nitfixes followed: message threading, capacity exhaustion, self-sent filters, webhook scoping, timezone overrides for remotes.
What survived were five invariants locked so future refactors cannot quietly undo them:
Never sequence without a Call List add. Outreach cannot take down product email. CRM actions and replies share one pursuit system. Enrollment never outruns send capacity. The worker only deploys through the release channel.
Flow builder comes last on purpose. Email core, reply engine, iMessage, and domain rotation ship before a React canvas. Deliverability risk arrives before sequencing flexibility. UI sits on proven parts.
Enrichment is not consent to pursue. The Call List is.
What it produced
Estimated build: roughly 200–260 hours across six shippable phases: email enrollment and drafts, reply pipeline and CRM sync, iMessage, multi-domain rotation, flow engine then visual builder, then analytics. Each phase can land alone.
The operating outcome is the one that mattered. Outreach capacity moved about 3× versus the founder running pursuit alone across Instantly, Klaviyo, and Twilio. Time came back for conversations, shortlists, and closing. Finding more clients got easier because the machine kept the cadence while the founder stayed on the Call List gate.
Worth being precise. This is an internal OS build on top of an existing recruiting CRM, not a growth campaign with vanity open rates. The outcomes are founder outcomes: more time, more pursuit, more clients found with less tool babysitting.
