1 team a month · waitlist open
you told them to use AI nothing changed
the memo went out. a few people tried it. a few more pretended to. the work looks the same. this year i've been turning ops, finance and marketing people into people who ship real systems. that's what i do for your team.
2 weeks
one team
1 owner
ships by day 10
day 10 or free
the guarantee
setup was easy. what comes after isn't.
the tools got installed. the licenses got paid for. then half of marketing's week went to arguing which of three numbers is right. the glue between your apps broke and nobody noticed for a month. the one person who got good opened a 45,000-line pull request and nobody knew how to review it. the dashboard says live. nobody believes it.
and it starts at the top. if leadership won't use it, the team won't either. every month it stays that way has a price:
the licenses
paid for every month, opened twice
the glue
automations that fail quietly until a customer finds out
the one who got good
shipping fast with no guardrails, until prod breaks
that part is fixable in two weeks.
what you get
one person shipping. guardrails that hold.
i sit with your team for two weeks and we build something real, on your data, in your repo. everything in the engagement, and what it'd cost you piecemeal:
the diagnosis $4,500
adoption teardown
who's using it, where it's stuck, what's quietly broken
$1,500
one metric, one definition
the number everyone argues about gets a single source of truth
$3,000
the build $5,000+
the system
a named person on your team ships a real internal tool, on your data
core
glue → code
one fragile automation chain rebuilt as code you can read, with alerts and a last-run time
$4,000
honest status
every "live" badge shows when it last synced
$1,000
the guardrails $7,500
permissions + review gate
nothing reaches production without passing review
$3,000
repo rules
one branch per tool, hooks, shared instructions. a 45,000-line PR can't happen
$2,500
customer data off desktops
it lives somewhere with access control, not on a laptop
$2,000
the people $7,500
hands-on onboarding
everyone on the team set up and shipping. 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+
shipped 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 systems worth building, in order
$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 ships 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 ship 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. git got explained with tracing paper, and it stuck.
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:
- you sent the memo. nothing changed.
- you have a team, and they aren't engineers
- someone on it is curious, or already shipping without guardrails
- you'd rather your people own it than rent a consultancy
not yet, if:
- 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 system.
days 1–7
we build it together, in your repo, on your data. a daily Loom so leadership watches it happen.
day 5 · scope check
if it can't ship in scope, we stop here. you keep what we built.
week 2
the guardrails go in. the rest of the team gets set up. one session with leadership.
day 10
shipped. 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 →