Alex Alekseenko

About

You are running outbound. Probably inbound too. And under both sits the same duct tape: lists rebuilt by hand, enrichment nobody owns, leads routed by feel, a CRM that drifts out of date a week after every cleanup, an AI tool that makes more cleanup than pipeline.None of that is a people problem. It is a data-layer problem, and a data layer is an engineering problem. That is where I come from: ten years of building Python systems and running remote engineering teams across five time zones.So I build the GTM data layer the way software is built. Define it once: who you sell to, which signals matter, where the data lives, how it refreshes. Automate on top in small steps, each one tested before the next ships. Agents come last, with guardrails and logs a human can read, doing work you can verify. In this order, automation compounds instead of breaking.In practice: enrichment pipelines, 0-100 account and lead scoring, inbound routing, CRM automation, AI agents on Claude Code (building AI and agentic systems for 3+ years). Most teams start with my Outbound Engine, a scored account list that refreshes itself - on your stack in weeks, documented, yours to keep. Built to be handed off, not to make me permanent.That build ships against a bar we set up front: the agreed coverage and accuracy, or I rework it. It also starts on net-new data, so your CRM stays closed until you want it open.If your GTM runs on manual work and nobody owns the data layer, send me a note.

Company history

1. 
   WayRayQA Automation Lead2018-12 – 2020-06 · 1y 6mo
2. 
   SberDevicesHead of QA Automation2020-06 – 2022-01 · 1y 7mo
3. 
   Align TechnologySenior QA Automation Engineer2017-10 – 2018-11 · 1y 1mo
4. 
   EvencapFounder & GTM Engineer2026-07 – present · 1 mo
5. 
   AxcientQA Automation Engineer/ QA Engineer2015-05 – 2017-10 · 2y 5mo
6. 
   CloudGeometryHead of QA Engineering2022-01 – 2026-07 · 4y 6mo

Skills

No playbooks indexed for this profile yet.