Automation Engineer

A GTM stack that finally
works as hard as you do

The handoffs, updates and follow-ups your team chases by hand, running on their own.

By the Numbers

Three Years of Shipped Systems

3+ Years building automation and GTM systems.

20+ Systems shipped and still running.

10+ Hours a week of commission admin taken off one sales team.

Worked with teams in the US, UK, Australia and the Netherlands.

What I Do

The Systems Behind Process and Revenue

CRM, data, integrations, AI and outbound, scoped and built by one engineer.

100%

Built Around How Your Team Works

CRM Setup & Admin

Salesforce and HubSpot set up around how you sell. Records your reps don't second-guess, with validation and permissions kept current.

ReportingLive

Data Foundation & Reporting

Dashboards and reporting that hold up in front of leadership, because the numbers underneath are right and stay monitored.

Tool Integration

Every tool your team runs on, connected and kept in sync, so nothing gets re-entered by hand or drifts out of date.

AI Systems & Workflows

I find where AI moves a number the business already tracks, then build and ship the agents and automations that do it.

Meeting notes summarized
Weekly report sent
Follow-up email drafted

Outbound Engineering

Signal-based prospecting, enrichment waterfalls and deliverability infrastructure, measured in pipeline and revenue, not emails sent.

Domain warmed, DMARC passing
Sequence live across 3 domains
Qualified reply routed to CRM

One System, Any Starting Point

Whether you're already running a revenue system or need a process automated somewhere in the business, I build the systems that carry work from first signal to final outcome.

AutomationZion's integration stack in light mode
AutomationZion's integration stack in dark mode

Straight Answers

Steady updates while it's being built and a plain warning when a fix you want would break something else.

Start With One Workflow

The first build solves one problem. Everything after it plugs into the same foundation instead of starting over.

Documented, Not Dependent

Documentation, walkthroughs and a clean handover, so the next person to touch the system isn't working from guesswork.

The Process

Four Steps From Broken Handoff to Running System

The same four steps every time, so you always know what comes next.

  • Map the Process
  • Design the Architecture
  • Build and Ship
  • Own and Improve
Step 01

Map the Process

You get a map of where data breaks, where handoffs fail and where the team is doing work a system should.

Step 02

Design the Architecture

You see the full design before anything is built: data model, workflow logic, integrations and what happens when something fails.

Step 03

Build and Ship

A working v1 goes live fast, tested on real data, then improved by what breaks in production.

Step 04

Own and Improve

I document everything and stay close to the system as the business grows, not just until launch.

The Stack

Tools I Work With

The tools I build in most. If it has an API, I can work with it.

Clay
Instantly
Currently available

Open to Full-Time Roles & Client Work

Tell me the role you're hiring for or the workflow that's costing you time, and I'll reply with how I'd approach it.

Automation Engineer & GTM Engineer building process and revenue infrastructure.

© 2026 AutomationZion. All rights reserved.