The Arc
Plumber. SDR. GTM Engineer.
every GTM creator has the same about page.
“I was an SDR. then I found Clay. now I teach people how to use it.”
cool. here's mine.
except mine starts with copper pipe and a blowtorch.
the layers
I didn't go from SDR to GTM engineer in a straight line. I went through three layers, and each one rewired how I think about building.
before tech, I was a plumber. not a metaphor. actual plumbing. diagnosing problems by listening to walls, tracing pipes nobody else wanted to touch, fixing systems under pressure with no documentation.
200+ cold emails a day. primary domains, no warmup, SalesLoft sequences, Salesforce activity logging by hand. building buying committees from scratch in accounts nobody wanted.
I stopped working inside the systems and started building them. Clay tables, HubSpot automation, Instantly sequences, web reveal workflows, enrichment pipelines. the same work I used to do by hand, now running on infrastructure I designed.
none of these define me. all of them sharpen what I ship.
the thesis
this is not vibe coding.
I don't prompt once and ship whatever comes back. I use plan mode before I write a single line. I use ask mode when something breaks. I run sub-agents for parallel work. I test, I break things, I read the error, I fix it, I ship it.
AI doesn't do the work for you. it accelerates the work you already understand.
every page on this site was iterated, not generated. every skill was debugged before it was documented. every campaign template was tested on real pipeline before it became a playbook.
the repo has over 400 files. zero of them were one-shot prompts.
three sites, one system
this isn't vanity. it's architecture.
three domains. one monorepo. every page, every API route, every generated image comes from the same codebase. nothing here is an accident.
build with me
this isn't a portfolio you look at. it's a system you can fork.