Coaching
Four tracks,
one conversation.
The tracks describe the problems I see most often. They aren't rigid — a founder shipping with agents while building outbound is one client, not three. Pick the closest fit and we'll scope the rest live.
01The tracks
- Shipping with AI coding agents
- Founder & 0→1
- AI go-to-market & sales automation
- Career & engineering leadership
01
Shipping with AI coding agents
Go from pasting prompts into a chat window to running a repo where agents do real, reviewable work.
What we fix
- Agent edits that look right, pass review, and quietly break production
- No repeatable workflow — every task starts from a blank prompt
- Context blowouts: huge token bills, worse answers
- Multi-agent setups that burn money without shipping anything
- No idea which work to hand to an agent and which to keep
What you leave with
- A repo configured for agents: instructions, skills, hooks, guardrails
- A personal workflow for planning → building → reviewing → landing changes
- Review habits that catch the specific ways generated code fails
- A cost model you can defend to whoever pays the bill
Why me for this
I run a multi-repo platform where the majority of code is written by agents under a review pipeline I built. The failure modes I teach are ones I paid for first.
02
Founder & 0→1
For technical people turning a working prototype into a company with customers, pricing, and a reason to exist.
What we fix
- Building for months without talking to a buyer
- Positioning that describes features instead of the thing being replaced
- Pricing set by vibes and competitor screenshots
- Scope that grows every week and never ships
- Fundraising prep with no narrative underneath it
What you leave with
- A one-sentence answer to what you replace and for whom
- A pricing model tied to the cost you remove, not hours you bill
- A ruthless next-90-days scope with a kill criterion
- A founder story that survives a skeptical investor or first customer
Why me for this
Four years as CTO of a VC-backed AI startup, then building my own company from zero. I've been on both sides of the build-vs-buy conversation.
03
AI go-to-market & sales automation
Build an outbound and marketing motion run by software instead of a retainer — without becoming the spam everyone hates.
What we fix
- Lists that look big and convert at zero
- AI-written emails that read like AI-written emails
- Domains and mailboxes torched by bad sending hygiene
- No approval step, so bad sends go out under your name
- Tool sprawl: five vendors, no pipeline
What you leave with
- An ICP defined tightly enough to disqualify most of the market
- A sourcing → enrichment → drafting → approval → send pipeline you control
- Deliverability basics done right the first time
- A human approval gate on everything metered or public
Why me for this
I bought agencies across recruiting and marketing before deciding to build the replacement. I'm currently building an AI agent platform for go-to-market teams and dogfooding it on my own pipeline.
04
Career & engineering leadership
IC to lead, lead to exec, or a deliberate pivot into AI work — with a plan instead of a job-board habit.
What we fix
- Doing lead-level work without lead-level recognition
- Promo packets that list tasks instead of impact
- Interviewing badly for roles you could clearly do
- No read on whether to switch companies or dig in
- Manager-track regret nobody warned you about
What you leave with
- A written scope of what your next level actually requires here
- An impact narrative with numbers your skip-level can repeat
- A shortlist of companies worth your time and a way in
- A clear-eyed decision on management vs. staff track
Why me for this
I've hired, promoted, and had the hard conversations as a CTO. I know what the room says after you leave it.
Next step
Not sure which track you're in?
That's most people. Book the intro call and we'll name the actual problem together.