[ Builds with ]
Everything I built falls into three buckets. Each has its own page with the systems, the diagrams, and what they actually did for people.
The campaigns and automations that fed the SDR team: job-change and job-posting signals, Lemlist lead routing by CRM ownership, reply handling from Slack, and warm intro discovery.
the SDR systems ?The full "email BTW" program: an AI-operated campaign pipeline with do-not-email rules it can't skip, plus granular deliverability monitoring on EmailBison and EmailGuard.
the cold email program ?The things that keep producing on their own: a lead magnet that generated $700K in pipeline in weeks, an attribution portal leadership trusts, and the Claude Code operating system underneath it all.
the infrastructure ?This is the actual mental map of the systems I built at AirOps: every signal, every workflow, every place the work lands, on one chart. Picture your own company's GTM stack laid out the same way, then imagine it a little more connected and a little less manual — this is roughly how I'd go about closing that gap.
flowchart TB
subgraph Signals["Buying signals come in"]
CR[Contact
changed jobs]
JOBS[Target company
is hiring]
REPLY[Prospect replied
or email bounced]
LI[Team LinkedIn
networks]
WEB[Company on
the website]
end
subgraph Systems["Systems I built"]
JC[Job-change
auto-enroll]
JP[Job posting
bot]
PEL[Pelican
reply hub]
BISON[Email
health ops]
ROUTE[Lemlist
ownership routing]
NM[Network
Mine]
EMAIL[Campaign
factory]
OS[OutboundSync]
PORTAL[Attribution
portal]
AEO[AEO Scorecard
connector]
ENG[Analysis
engine]
ADS[Warm ad audiences
sequencing unfinished]
LSCORE[Supabase lead scoring
draft, unfinished]
RB2B[RB2B page-aware
visitor outbound]
end
subgraph Destinations["Where the work lands"]
SEQ[Outreach
sequences]
CRM[(CRM: the
shared record)]
SLACK[Slack, where
the team works]
SCORE[Public scorecard
product]
ADPLAT[LinkedIn / Meta
ad audiences]
RANK[Ranked account
shortlist]
end
CR --> JC
JOBS --> JP
REPLY --> PEL
REPLY --> BISON
LI --> NM
WEB --> RB2B
JC --> SEQ
JC --> SLACK
JP --> SLACK
JP --> SEQ
PEL --> SLACK
PEL --> SEQ
BISON --> SEQ
BISON --> SLACK
NM --> SLACK
RB2B --> SEQ
EMAIL --> SEQ
SEQ --> OS
BISON --> OS
OS -->|writes activity| CRM
BISON -->|writes bounce status| CRM
SEQ --> PORTAL
PORTAL -->|writes attribution| CRM
CRM -->|nightly sync ? writes owner| ROUTE
ROUTE --> SEQ
CRM --> NM
CRM --> JC
AEO <--> ENG
AEO --> SCORE
REPLY --> ADS
CRM --> ADS
ADS --> ADPLAT
CRM --> LSCORE
LSCORE --> RANK
LSCORE --> SEQ
style Signals stroke:#8b5cf6
style Destinations stroke:#10b981
style CRM stroke:#10b981,stroke-width:3px
style ADS stroke:#f59e0b
style LSCORE stroke:#f59e0b
drag to pan ? + / - to zoom ? Ctrl + scroll also zoomsswipe to pan ? tap + / - to zoom
Not everything, just a representative slice. One line each, and every diagram and detail lives on the pillar pages.
Everything I automate, I've done by hand first. That's why the systems work.
Built the systems on this site: signal automations, cold email infrastructure, attribution, deliverability ops, and AI research products.
Employee #2 and first sales hire. Helped the team raise $5M from Base10. Built the outbound and channel partner program from the ground up: recruiting, RevOps, brand, trade shows, the sales playbook, strategic partnerships, and a six-figure budget.
True enterprise outbound, built from the ground up: targeting, messaging, process, and tooling.
I am not afraid of getting my hands dirty, literally. Working these jobs is what makes me great at what I do now. I know how lucky I am to work from home and get paid a good wage. I'm not some trust fund kid who has only ever worked at big SaaS companies and never bussed a table or handled a mop.