Hello MNTN
More leads at smaller deal sizes put pressure on exactly the systems this role owns. Here's how I'd approach them, and the proof I've built this infrastructure before.
James Praise · GTM Engineer
MNTN hired its first Chief Revenue Officer this year to grow the small and mid-sized business segment. That changes the funnel under this role: more leads, smaller deals and faster cycles. Routing rules built for larger brand accounts tend to misfire quietly under that mix, and sender reputation slips as email volume climbs, usually before either shows up in pipeline numbers.
MNTN already has GTM engineering inside Business Systems, so I'd start by learning what that practice covers before proposing anything. Then I'd map the live Salesforce and LeanData rules against real lead volume, deal size and qualification signals from the new segment, and run a deliverability health check across authentication, sender reputation and domain warming. Any AI qualification step would sit on data that's already been checked, because automation built on unchecked data degrades without anyone noticing.
At Reform, I led the email platform migration from Userlist to Brevo. I set up email authentication (SPF, DKIM and DMARC), cleaned the list from 10,104 to 7,808 contacts with Kickbox and validated every n8n workflow before cutover. Bounce rates fell 18% and email churn fell 22%.
I also built the Prospect & Outbound Engine, a Python pipeline with a self-built email verifier. Before setting send rules, I tested enrichment sources against each other: database-enriched emails came back 71% good against 53% for website-scraped ones, so the rules follow that result. One live run sourced 409 companies and produced 267 send-ready leads.
At FunnelEnvy, I built a cross-brand measurement stack on GA4, HubSpot, Looker Studio and Lightdash, and the outbound stack that lifted reply rates 27%.
If this is the right problem for you, I'd like to talk about it directly.