50K sends a month.
Deliverability protected, not reacted to.
Full ownership of the Instantly, Apify, Make, HubSpot, Scaledmail, and AnyMailFinder stack you already have live. Inbox rotation, warmup posture, domain health, and bounce control managed on a daily cadence, not a monthly audit. Apify sourcing gated by AMF verification thresholds before anything touches a sending sequence. Make scenarios audited, hardened, and monitored so nothing silently breaks. Weekly reporting on the metrics that actually predict burn (bounce trend, reply quality, inbox placement) with issues flagged before they become problems. I run this exact stack for my own cold email operation and for clients daily.
Three failure modes at 50K sends a month.
At this volume the program does not die from a single mistake. It dies from three quiet drifts that compound if nobody is watching daily.
Domains burn before the dashboard shows it
By the time bounce rate crosses the visible threshold, the reputation damage has already happened. A daily posture check on warmup, sending caps, and inbox placement catches the drift while it is still fixable.
List quality decays silently
Apify runs get looser over time as source pages change. AMF thresholds drift as the operator gets casual. Bad rows hit inboxes, bounce rates climb, and nobody traces it back to the sourcing gate that stopped enforcing.
Make scenarios fail without visible errors
A webhook drops silently. An enrichment step returns null and the downstream logic skips a batch. HubSpot gets fewer contacts than expected and no one notices until reply rate mysteriously softens two weeks later.
Owner posture. Not caretaker posture.
Daily deliverability posture check across every sending domain and inbox before campaigns fire: warmup state, reputation signal, sending caps, bounce trend on a rolling window. Apify sourcing gated by an AMF verification threshold that never gets relaxed for volume, with judgment calls on borderline lists documented so decisions are consistent across campaigns. Make scenarios audited on entry (error handling, retry logic, monitoring hooks) then instrumented so failures alert instead of silently skipping. HubSpot pipeline hygiene maintained so lifecycle stages reflect reality and campaign attribution stays clean. Weekly report goes out on the metrics that actually predict burn: bounce trend, reply quality, inbox placement across major providers, and lead delivery rate to HubSpot, with anything trending the wrong direction flagged with a proposed fix already attached. This is the exact stack and cadence I run for my own cold email program and for client programs today.
What I own. From day one.
The role in your JD, split into five ownership areas with concrete daily and weekly cadences. This is what taking over looks like in practice.
- Daily posture check across every sending domain and inbox in Instantly and Scaledmail
- Warmup state, reputation signal, sending caps, and inbox rotation reviewed daily
- Bounce rate held under 3% at volume with rolling window monitoring
- Preemptive action on any domain trending toward burn before it hits the dashboard
- Apify actors maintained as source pages evolve, breakages fixed before impact
- List quality gate enforced: clean before anything touches an inbox, no exceptions
- AMF verification thresholds never relaxed for volume pressure
- Borderline list judgment calls documented so decisions stay consistent
- Audit of existing scenarios for error handling, retry logic, and silent failure paths
- Monitoring hooks added so failures alert instead of skipping quietly
- Webhook flows sourcing to enrichment to Instantly to HubSpot kept auditable end to end
- New scenarios built and hardened before promotion to production
- Contact-to-sequence routing owned so audiences flow into the right campaigns
- Subject line, opener, and CTA adjustments made from reply data, not gut feel
- Underperforming variants swapped weekly, winners promoted to steady state
- HubSpot lifecycle stages and list segmentation kept clean for attribution
- Weekly summary of open rate, reply rate, bounce rate, domain health, inbox placement, leads delivered to HubSpot
- Issues surfaced with a proposed fix already attached, not just an alert
- Owner posture on every metric: notice underperformance before being asked
- Available for context on any spike, dip, or anomaly the same day it shows up
Take over week one. Owner posture by week four.
The first four weeks of the ongoing engagement, week by week. Click any week to see what lands.
Deliverables this week
- Full audit of Instantly and Scaledmail inboxes: warmup state, sending caps, reputation
- Apify actor inventory: which sources are running, which are stale, which need work
- Make scenario map with silent failure and error handling risk called out
- Deliverability baseline snapshot as the reference point for weekly reporting
Deliverables this week
- Daily posture check operating across every sending domain and inbox
- Inbox rotation schedule locked and monitored against sending caps
- Warmup schedule adjusted based on inbox age, provider, and reputation signal
- Bounce rate held under 3% as the hard operational line
Deliverables this week
- Apify actor maintenance queue running so source drift is caught weekly
- AMF verification threshold enforced across every list before it enters a sequence
- Make scenarios hardened with error handling, retries, and monitoring hooks
- Silent failure paths eliminated: every drop alerts, no batch skips quietly
Deliverables this week
- Weekly reporting format locked: bounce trend, reply quality, inbox placement, HubSpot delivery
- Subject line, opener, and CTA adjustments made from actual reply data
- HubSpot pipeline hygiene running: lifecycle stages accurate, attribution clean
- Steady state ownership posture: issues flagged with fixes proposed, not just alerted
Let's walk the current stack together.
A 30 minute call where I share my screen, walk you through how I run the same stack today, and confirm the first week takeover plan against your live setup. Happy to walk through commercials on the call.