1 team a month · waitlist open
everyone's building nothing's better
the memo worked. your people are building their own tools with AI. the work still runs late, and the numbers still don't match.
2 weeks
one team
1 process
written down, running
day 10 or free
the guarantee
building got cheap. deciding didn't.
anyone on your team can build a tool in an afternoon now. so they do. nobody decides which ones should exist.
every month it stays like this has a price:
the pile
tools nobody asked for, kept alive by whoever made them
the queue
one person reviews everything, or nobody reviews anything
the date
the steps live in three heads and a chat thread, so it slips
that part is fixable in two weeks.
one process running. guardrails that hold.
two weeks with your team, on the one process that keeps running late. you pick it on the first call. everything in the engagement, and what it'd cost you piecemeal:
the diagnosis $4,500
the inventory
everything your team has built, who uses it, what's quietly broken
$1,500
one metric, one definition
the number everyone argues about gets a single source of truth
$3,000
the process $5,000+
written down
one process, step by step, with an owner and a yes or no on each step
core
runnable
the steps your team repeats every week become something anyone can run by asking
$4,000
the red light
when a step is late, its owner hears that day. so does everyone waiting on it
$1,000
the guardrails $7,500
permissions + review gate
nothing reaches production without review, and the person who knows the work reviews it
$3,000
repo rules
one branch per tool, hooks, shared instructions. a 45,000-line PR can't happen
$2,500
access, trimmed
who needs to be in the repo and the systems, and who never did. customer data comes off laptops
$2,000
the people $7,500
hands-on onboarding
the people who run the process, set up. by the tenth person it takes one sitting
$4,000
the tracing-paper session
git and review, explained so it sticks for people who never wanted to learn git
$1,500
the leadership session
the people at the top use it first, so the team follows
$2,000
the close $3,500+
running by day 10
you own 100% of it
included
day-30 check-in
what stuck, what didn't
$500
the runbook + Loom library
so the next hire onboards without me
$1,500
the 90-day map
the next three things worth doing, in order. and the ones to buy instead of build
$1,500
bonuses land by day 30.
total value
$28,000+
you pay
$15,000 fixed.half up front, half on day 10.
a consultancy quotes six figures and delivers a deck. a workshop is half a day and a recording nobody watches. this is two weeks, and something running when i leave.
your person runs it by day 10,or the rest is free.
and there's a floor under it: day 5, we both look at it. if we can both see it won't be running in scope, we stop there. you keep everything we built and pay only for the time used. the risk is mine to carry, not yours.
proof · inside a consumer brand
finance, ops and marketing, shipping their own tools.
since july i've run 22 onboarding sessions across ops, finance, marketing, wholesale and creative. into a shared repo, behind a review gate. none of them were hired to write code. the numbers:
22
onboarding sessions
5
departments
~10
sessions to one-sitting setup
3
glue chains now code
one finance analyst shipped dashboards fast enough that their lead asked them to slow down. the automations that failed quietly are code now, with alerts.
what broke when it worked.
- i became the review queue. everything waited on me.
- thousands of tests, good ones. most never needed to exist.
- i built tools faster than i asked who would use them.
- the process stayed in people's heads. nobody can run that.
so the first thing we make now is a document. the build comes second, and it's smaller.
before this, the craft: a solo therapy practice rebuilt in 4h43m. mobile load 8.3s → 2.9s. pageviews up 185%. same hands.
“He's built three sites for me and with each one, the unique needs and goals of the site dictated his approach, no cookie cutting corners.”
is this for you?
yes, if:
- your team is building. you can't tell what it adds up to
- the people building aren't engineers
- a date slipped and nobody saw it coming
- you'd rather your people own it than rent a consultancy
not yet, if:
- nobody on your team has shipped anything yet. start with the teardown
- it's just you. no team yet
- you want a workshop and a recording
- you want it done for you, with nobody on your side learning
the two weeks.
wk 1 · day 0
a 30-minute call. we pick the person and the process.
days 1–7
we write it down together, step by step, then make each step runnable. a daily Loom so leadership watches it happen.
day 5 · scope check
if it won't be running in scope, we stop here. you keep what we built.
week 2
the red light goes on. the guardrails go in. the people who run it get set up. one session with leadership.
day 10
running. your person owns it. (or the rest is free.)
day 30
check-in. what stuck, what didn't.
one team a month · by appointment
join the waitlist.
if you'd rather not wait, start with the teardown: $1,500, . i look at how your team works today, record a 10-minute Loom on where it's stuck, and write down what i'd fix first. you keep it whether or not we work together.
paid up front. credited against the engagement if you book one within 30 days. if i decline after you've paid, you get all of it back.
read the full terms →