01 Selected Work
Systems I've built and shipped.
Four systems that shipped and ran in production.
01
A proactive GTM engine, built end-to-end
The challenge
Pipeline was 100% inbound: auto-scored, one manual reply each. It worked, but it was the whole motion. The brief: build the next one.
What I built
An outbound engine that treats public developer activity as intent. It pulls every signal (stars, forks, installs, container pulls, telemetry, hiring), enriches each contact, and scores it on ICP fit plus signal strength.
- Deduped daily against inbound, so no one gets double-touched.
- A Python scoring module (stdlib only) makes every ranking auditable.
- An LLM copy layer drafts each sequence, gated by deterministic rules before send.
- A self-improving loop: every conversion re-weights the model and grades the copy that worked.
The outcome
Shipped as a live app plus a runnable scoring model. Every number came from a real public API. Runs on ~0.1 FTE once live.
02
Production multi-agent marketing system
The challenge
A 30+ person marketing team with zero agentic infrastructure. Everything ran on manual triggers.
What I built
A 24/7 system where orchestrator agents coordinate subagents in parallel. Content, data refresh, reporting, and knowledge upkeep all run without manual triggers.
- Self-improving loops: weekly agents propose rule changes; monthly cycles auto-approve them only if benchmarks improve.
- RAG memory over a ~1,000-doc vector-indexed wiki, with semantic search and automated pruning.
- Decay-weighted scoring that keeps high-value knowledge within token limits.
- Eval frameworks: skill-trigger accuracy, output quality, and retrieval precision, with regression tracking.
The outcome
03
Incrementality testing framework
The challenge
Spend ran on platform-reported conversions, numbers the platforms grade themselves on. No honest read on what was incremental.
What I built
A from-scratch incrementality framework in Python on the ads-platform APIs. Lift experiments that separate causal impact from correlation.
- Set the experimentation culture behind today's agent-driven testing.
- Wired results into budgeting, so spend followed proven lift.
The outcome
04
GTM data infrastructure & conversion tracking
The challenge
Marketing, product, data, and legal ran on inconsistent signals. In-platform and backend numbers disagreed, and the pipeline the agentic layer would need didn't exist.
What I built
The foundation the agentic layer runs on: end-to-end Segment CDP, server-side CAPI events, and lifecycle-stage conversion events, all GDPR-compliant.
- Closed the gap between in-platform and backend data with automated reporting.
- Coordinated marketing, product, data, and legal to keep pipelines clean.
The outcome
05 Open source
Tools and agent skills I've built in the open.