Process, principles, and who decides what - in plain language.
Everything here is specific to how we run engagements: the first ninety days, the journey from signal to meeting, decision rights, stack philosophy, and FAQs about logistics - written for operators, not glossed over for a hero section.
Use the interactive step-through to see where most “outbound programs” silently leak before you ever notice in a dashboard.
How we think before we send
First 90 days
What actually happens - in order
Generalized map; your dates shift. We do not blast cold traffic on day three to decorate a dashboard.
Blueprint and guardrails
- ICP and anti-ICP locked
- Offer and objection map captured
- Sending architecture designed
- First signal definitions drafted
Infrastructure live
- DNS and mailboxes provisioned
- Warmup sequences started
- Clay tables and scoring v1
- Suppression and compliance rules
First production motion
- Tier 2 sequences at sustainable volume
- Tier 1 white-glove path for hottest rows
- Reply routing and calendar tests
- Weekly readouts with concrete changes
Stabilize and compound
- Kill underperforming segments
- Double down on winning signals
- Tighten copy from real replies
- Optional: expand channel mix
Blueprint and guardrails
- · ICP and anti-ICP locked
- · Offer and objection map captured
- · Sending architecture designed
- · First signal definitions drafted
Infrastructure live
- · DNS and mailboxes provisioned
- · Warmup sequences started
- · Clay tables and scoring v1
- · Suppression and compliance rules
First production motion
- · Tier 2 sequences at sustainable volume
- · Tier 1 white-glove path for hottest rows
- · Reply routing and calendar tests
- · Weekly readouts with concrete changes
Stabilize and compound
- · Kill underperforming segments
- · Double down on winning signals
- · Tighten copy from real replies
- · Optional: expand channel mix
Signal → meeting chain
Tap a step. Each stage is a common leak point when nobody owns the full path.
Source
We pull from sources that update - jobs, posts, funding, tech, intent - not a static CSV from 2019.
Governance: two lanes, zero ambiguity
Final say on offer, positioning, and pricing
Sequence strategy, send cadence, and list logic
Approve first-wave copy and sensitive segments
Day-to-day copy iteration within approved bounds
Show up to booked meetings
Own reply triage up to the handoff point you define
Brand and legal review on risky claims
Deliverability and compliance mechanics on outbound
Tools serve the system
Traceability, rotation, and a clear answer to: why did this person get this message on this day?
Data & enrichment
Tables that stay fresh, scoring that is explainable, and exports that do not rot in a folder.
Sequencing & inbox
Tools chosen for deliverability and audit trails - not whatever was cheapest on AppSumo last week.
Monitoring
Placement and reputation signals so we react before your domain is a crater.
Documentation
You always know what ran, why, and what changes next - without sitting in a daily standup.
Process
How it works - FAQ
Pick a topic on the left (desktop) or below (mobile). The answer stays readable in one place - no hunting through tiles.
Answer
Why is month one “quiet” on sends?
Because burning a domain in week one costs you quarters. Warmup and sequencing discipline upfront prevent the “we sent 40k and got nothing” story.
How do approvals work in practice?
We batch decisions: you approve first-wave copy and sensitive segments. Within those rails we iterate weekly based on replies - without scheduling a committee for every comma.
What access do you need from us?
Calendar routing, CRM or spreadsheet handoff preference, brand boundaries, and someone who can say yes to ICP tweaks within a few business days.
Can we pause or pivot mid-quarter?
Yes - we would rather redirect volume than pretend a dead segment is “testing.” Major pivots get a scoped plan so deliverability stays intact.
Why is month one “quiet” on sends?
Because burning a domain in week one costs you quarters. Warmup and sequencing discipline upfront prevent the “we sent 40k and got nothing” story.
How do approvals work in practice?
We batch decisions: you approve first-wave copy and sensitive segments. Within those rails we iterate weekly based on replies - without scheduling a committee for every comma.
What access do you need from us?
Calendar routing, CRM or spreadsheet handoff preference, brand boundaries, and someone who can say yes to ICP tweaks within a few business days.
Can we pause or pivot mid-quarter?
Yes - we would rather redirect volume than pretend a dead segment is “testing.” Major pivots get a scoped plan so deliverability stays intact.
Your next two clients are already out there signaling.
20 minutes. No deck. No pitch. A real conversation about your pipeline and whether there is a fit.
If we are not a fit, we will tell you on the call and point you somewhere better.