GTM engineering for EU startups · Berlin

Your pipeline shouldn’t depend on memory.

Signals, enrichment and AI-personalized outreach, wired into working pipeline — for teams too small to hire a GTM function.

Attio + Clay + Claude. GDPR-clean by default.

01What I build

Three parts, one machine.

Not a dashboard, not a deck. A working system that finds the accounts, writes the first line, and puts the result where your team already works.

Hiring spikes, funding rounds, CRM-pain job posts. Your next client announces themselves; the system listens.

ii.

Waterfall enrichment, Claude-drafted outreach that reads like a human wrote it, because one designed it.

iii.

Everything lands in your CRM as working pipeline you own. Documented. No lock-in.

02Proof

Attio webhook → Python → Apollo API → CRM writeback, running as a systemd service on a Raspberry Pi. Event-driven. Zero SaaS middleware.

Domains, mailboxes, deliverability, sequencing, and real-time HubSpot lead routing to reps. Built from nothing to booked meetings.

03Case studies

Real client

Your CRM holds records. Does it run anything?

Reference architecture

A €3,000 patient leaks out of a clinic’s funnel for a boring reason: nobody answered in the first minute.

Certification build

The most useful CRM decisions are about what NOT to build.

04The offer

Signal detection + enrichment waterfall + AI-personalized sequencing + CRM pipeline. You own everything: workflows documented, no lock-in.

Continues as an operate-and-optimize retainer if you want the machine run for you.

Right fit: an EU team of 5–50 whose CRM holds records but runs nothing. First conversation is free and specific.