Marketing people don't sell. That's the line I've heard my whole career. Brand builds the story, sales closes the deal, and the two of you meet somewhere in the middle at a QBR.
I stopped believing that line this month.
I lead brand, GTM, and growth. Not sales. But Employer of Record is a category where nobody wakes up looking for you, so someone has to go find them, across seven countries, every single day. I didn't build this because the org lacked a pre-sales team or a budget for one. I built it because I came across Antigravity a few days ago, saw what it could actually do, and realized nobody had proven yet how far one person could take it. I wanted to be the one who did.
Why I built this
This wasn't about saving money on a hire. It was about getting closer to the buyer than a marketing role usually allows. Most marketing functions wait for sales to close deals, then reverse-engineer what worked and feed it back as content or campaigns. I wanted to flip that. I wanted marketing to know, in advance, what sales could use, not after the fact, but built into the system before a single conversation happens. That only happens if you build the thing that talks to prospects first, not just the thing that talks about them.
The honest reason underneath all of it is simpler. I can, so I must. If a tool exists that lets one person run outbound across seven countries with the judgment of twelve years of buyer psychology behind it, not trying it felt like a bigger risk than building it.
What I actually connected
Four pieces, wired together so they run without me.
- Apollo for the prospect data, the actual list of people and companies in the seven markets I'm targeting: US, Canada, Australia, UK, Germany, Japan, Singapore.
- LinkedIn for context on each prospect, so the email doesn't read like it was written for a database entry.
- Microsoft Outlook to actually send the emails and track what happens after, replies, opens, silence.
- Gemini, run through Antigravity, as the layer that ties the first three together, writes the emails, and manages the follow-up cadence on a schedule.
Underneath all of it sits a collateral bank I built myself: EOR enablement e-brochures, case studies from Rodeo FX and WEC.AI, a testimonial from Rodeo FX that I only used because it was earned, not invented. I also fed it the brand and product detailing decks I'd already built in Canva, so the system writes with the same positioning I'd use if I sat down and typed the email myself.
I didn't build an AI that sells. I built an AI that sells the way I would.
What "the way I would" actually looks like
Here's a sample of the kind of email the system sends, rebuilt here as a dummy for this post since the real ones carry live prospect names.
Hi [First Name],
Saw [Company] is scaling into the DACH region. Most teams find out too late that opening a local entity in Germany takes 8 to 12 weeks, and by then the candidate they wanted has taken another offer.
We handle payroll and compliance for teams like yours inside Germany the same week you make an offer, no entity required.
Rodeo FX made this exact move into three new markets without opening a single local entity. Happy to send the two-page breakdown if it's useful.
Worth 10 minutes this week?
[Signature]
Nothing in that email is generic. The timeline (8 to 12 weeks) is a real, specific cost of doing nothing. The proof point (Rodeo FX) is a named result, not a claim. The ask (10 minutes) is small enough that saying yes costs the reader almost nothing. That's not copywriting instinct the AI invented. That's the same buyer psychology I'd use writing it myself, coded into a system so it fires every time, on schedule, across a hundred inboxes instead of one.
What ₹6,000 actually proved
"Total spend for the whole setup: ₹6,000 for the Antigravity subscription. Everything else, Apollo, LinkedIn, Outlook, I was already paying for or already had."
That number matters less as a cost figure and more as a boundary test. Six thousand rupees and a few days of wiring things together, and here's what one person running it can do:
- 50-plus emails sent in the first weeks, now running at 10 to 15 a day, on pace to cross 300 in a single month
- An 8% reply rate
- A 1% rate of genuine interest, someone writing back to ask for more details instead of deleting the email
- A 0.3% conversion into an actual e-meet on the calendar
- 5 to 6 hours freed up every single day, hours I used to spend finding prospects, writing emails one at a time, and remembering who I hadn't followed up with yet
The target is more than 100 qualified pipelines in three months, across seven markets, and every number above is still climbing. I didn't set out to prove this was cheap. I set out to prove there's no real ceiling on what one person can build if they're willing to try, and the number just happens to also be small.
The snapshot
What went wrong, and what I built in because of it
The system isn't the whole answer. Early on it reached for context it didn't need, pulling more from a prospect's LinkedIn history than the email actually required, which meant slower runs and wasted effort for no gain in the output. I scoped it back hard: Apollo for data, LinkedIn for context, Outlook for sending, nothing beyond that. An AI system given open-ended access will happily take more than it needs and burn time and tokens doing it. I set the boundaries once, and I check the outputs regularly instead of assuming the system is still doing exactly what I built it to do.
That's the part I'd want a CMO or a founder to notice more than the reply rate. Anyone can turn a tool on. Knowing where to turn it off is the harder skill, and it's the one that scales.
Why this matters beyond the numbers
I didn't build this because someone asked me to, and I didn't build it to save the org a hire. I built it because I could, and because a marketing function that only reacts to what sales already learned is always a step behind. Now the insight runs the other way. Every email this system sends is built on the same understanding of buyer behavior I've spent twelve years developing, why a specific timeline creates urgency, why a named result beats a claim, why a ten-minute ask gets a yes a thirty-minute one won't. The AI executes it at a scale one person never could. The judgment behind it is still mine, and proving that judgment scales is the actual point of this whole exercise.
Full build breakdown, including the collateral bank and the exact prompts, is written up as a case study here: the AI GTM Engine case study →
Comments
Comments use GitHub. Sign in with a free GitHub account to join in.