Based in the EU · GDPR-native · English-first
A GTM engineer for Europe — based in Europe.
GTM engineering is a US-born discipline, and almost everyone selling it works from the US. I build the same systems — outbound, enrichment, CRM, AI workflows — from inside the EU: your timezone, your data rules, your infrastructure.
Why Europe-based matters
The same craft. The right side of the Atlantic.
GDPR-native, not GDPR-adapted
Most GTM tooling and agencies are US-first — your prospect data flows through infrastructure you don't control. I build inside the EU, on systems you own, in the region you choose.
Outbound that fits European markets
EU B2B is not the US: lower outbound saturation, different tone, stricter rules. A system tuned for European reply rates — not a US playbook pasted onto Europe.
Your timezone, whole workday
Based in Ireland: a full European workday overlapping London, Amsterdam, Berlin and Paris — plus US-afternoon coverage when the team spans the Atlantic.
What I build
Three systems. One GTM engine.
Outbound engine
Targeting, enrichment, AI-personalised sequences and lead routing — pipeline without hiring an SDR team.
RevOps + CRM
Clean stages, lifecycle logic, dashboards and the integrations that hold the stack together — numbers you can trust.
AI automation
Account research, lead scoring, call prep, CRM updates and follow-up — practical AI on Claude, running in the motion.
Questions
Hiring a GTM engineer in Europe — the real questions.
Which European countries do you work with?+
The work is remote-first and in English — teams in Ireland, the UK, the Netherlands, Germany, France, the Nordics and anywhere else in the EU. US companies that want European coverage are also a fit.
Why does being based in the EU matter for GTM systems?+
Because your prospect and customer data is regulated here. A GDPR-native build means enrichment, outreach and CRM data stay on infrastructure you own, in the region you choose — not routed through a US agency's tooling.
How is this different from hiring a US GTM agency?+
Three ways: the system lands in your stack and you own it; the build is GDPR-native by default; and you work directly with the engineer who builds it — in your timezone, not on a call at 9pm.
What does an engagement look like?+
Focused increments, not a big-bang project. We start with the highest-leverage system, get it live and producing, then build out from there. Your team learns to run it — no lock-in.
Build your GTM engine in Europe.
Fifteen minutes, European timezone, no deck — just a conversation about where your pipeline leaks and what I'd build first.