GTM engineer · RevOps builder

I build go-to-market systems that reps actually use, and that get better every quarter.

I spent eight-plus years in sales before I started writing code. Now I build the signals, scoring, AI-assisted outbound, CRM plumbing and revenue reporting behind a sales team, and I build it for the people who have to use it.

4 months to build a startup’s full GTM stack, solo
929 / 2,935 deals recovered by fixing rep attribution
~1,950 commits across 23 repos in that stretch

Approach

Tools are the smallest part of the job.

People, then process, then programs

People are the base. Process sits on top of them, and tools sit on top of that. The best system fails without leadership backing the people and process changes. It won’t be perfect on day one, but people have to follow the process consistently, or there’s no clean data to improve from.

Art and science

Engineers who move into GTM tend to want everything measured. Sellers who move into GTM tend to run on feel. I’ve done both jobs, so I build systems that score and forecast, and still leave the judgment calls with the rep.

Adoption is the first metric

If a tool costs a rep more time than it saves, they route around it, and then the system has nothing to learn from. I build inside the rep’s existing flow and ship the guide and the walkthrough video with it.

Rules first, AI where it earns it

  • Rule Same input should give the same output: pricing, routing, approvals, attribution. Auditable and free to run.
  • AI + review Messy text at volume, where a mistake is cheap to catch: research, classification, drafts. A person approves until it’s proven.
  • Person Relationships, exceptions and anything regulated.

Closed loops, proven patterns, bespoke builds

Every system I build measures its outcome and re-weights from it: signals in, score and route, work the handoff, capture the result, adjust. Part of every engagement is a pattern I’ve already built and debugged, which is why it’s fast. Part of it only fits that company, and that’s where my time goes.

Selected work

What I’ve built

Employers are anonymized. Every number comes from my own work records.

How I work

One person, team-scale output, firm rules.

AI-leveraged delivery

I run several Claude Code agents in parallel, with one lead that plans, verifies and merges the work. A weekly worklog records what shipped.

Safe changes to live systems

I prove each change on a copy and snapshot live data first. Outbound sends only after a person approves. Analysis pulls stay read-only.

Proof before claims

Code reviews with fixes, tests that run over real pipeline output, and model changes predicted before cutover and checked after.

Cost control

Small, capped first runs with a cost estimate. Call coaching runs about $1 per 30 calls.

Tools I work in

  • HubSpot
  • Salesforce
  • Apollo
  • Instantly
  • Smartlead
  • Clay
  • HeyReach
  • Chorus
  • n8n
  • Workato
  • Claude API
  • Claude Code
  • Supabase / Postgres
  • Next.js
  • Astro
  • Vercel
  • GitHub Actions
  • Slack Block Kit

Contact

Building out GTM systems? Let’s talk.

Full-time, fractional or project work.