01 · for founders & boards
Fractional AI CTO
The technology seat, 1–2 days a week — I own architecture, AI strategy, hiring and vendors; my agent fleet ships the proof behind every call.
the roadmap & the hard trade-offs
month to month, no lock-in
Inspired By Frustration// fractional AI CTO · forward-deployed engineer · 12 years in business · powered by agent swarms
I know the business.
Twelve years on the operating side. I know which features move revenue and which are vanity — so I kill the wrong AI bet before you fund it.
revenue sensepricinggtmhiring
the proof half
I orchestrate the AI.
I make the senior AI calls — orchestration, MCP, evals, guardrails — then the swarm turns the idea into a working proof: a real POC in hours, not a sprint.
mcpagent orchestrationevalsguardrails
↳ POC in hours · working proof in a week · production in weeks
Not a dev army — one operator whose swarm ships the proof.
typescript · bun · next.js · supabase · fly.io · mcp · turborepo · playwright · infisical · cloudflare · tailwind v4 · postgres · docker · zod ·
[ 01 / two ways to hire me ]
Two front doors. One operator behind both.
Hire the seat, hire the hands — or combine them in one engagement.
02 · for teams with engineers
Forward-Deployed AI Engineer
Embedded in your team, putting AI to work at scale in your own codebase — automating the manual work, scaling what your engineers ship.
your repo, your review standards
evals wired into CI from day one
12y
on the business side
~55/d
merged PRs, 30-day average
90s
CI per push · was 6–9 min
4
products I run in production
[ 02 / things in production ]
all projects →Proof behind both doors.
Lovable prototypes, finished in production
MCP server · contract-aware scans · agent handoff
bunnext.jsfly.io
One endpoint for every MCP
enterprise control plane · routing, policy, audit
next.jszod/openapisupabase
Bug reports in one script tag
shadow-dom widget · screenshot + console capture
next.jssupabasetailwind v4
CI from nine minutes to ninety seconds
self-hosted runners · turborepo cache · ~50 actions
fly.iodockerci auto-fixer
A membership platform, end to end
marketing + member portal + admin · e2e tested
vite/reactsupabaseplaywright
I’ll tell you what’s worth doing — and what isn’t.
Bluntly. If an idea won’t fly, you’ll hear it from me before you fund it — not at the demo. The same discipline behind both doors: nothing improvised, nothing handed to a junior.
Anchor every engagement to a business outcome
proof
Cut the work across a swarm of agents, in parallel
Kill vanity features before they cost you
proof
Ship it typed, tested, and observable in production
Own the roadmap and the hard trade-offs
proof
Own the merge gates — evals, checks, review where it counts
Set the security and compliance bar
proof
Scoped tools, least-privilege, every action audited
Stay on as fractional CTO / technical lead
proof
Hand over clean — runbooks, docs, no lock-in
strategy — what I decide
proof — what the swarm ships
Anchor every engagement to a business outcome
proof ·Cut the work across a swarm of agents, in parallel
Kill vanity features before they cost you
proof ·Ship it typed, tested, and observable in production
Own the roadmap and the hard trade-offs
proof ·Own the merge gates — evals, checks, review where it counts
Set the security and compliance bar
proof ·Scoped tools, least-privilege, every action audited
Stay on as fractional CTO / technical lead
proof ·Hand over clean — runbooks, docs, no lock-in
[ 04 / the studio ]
More than one person.
One principal owns your build end to end. A swarm does the volume. When a build needs a specific human, I bring in operators I trust — by name, never a faceless bench.
Ralph
principal · accountable
Owns the spine. Makes the business calls. Sets the gates, owns the risky calls. One throat to choke.
The swarm
Up to thirty coding agents cut tickets in parallel — coordinated by AppHandoff, tooling I built. Evals and CI gate every merge; I review what’s risky.
Trusted operators
Named specialists I bring in when a build needs a specific human. Vetted, not outsourced.