$8,000 / month · ~20 hrs/week · ~80 hrs/month
Full ownership, deep context, architecture through deployment.
I'm basically on your team. A part of your team.
Twenty hours a week is the tier where the line between contractor and team member dissolves. I'm not visiting your codebase; I'm living in it. I know where the bodies are buried, I know which tests are flaky and why, I know the thing the last engineer did in March that everyone's been meaning to fix.
And when a new feature needs to ship, I can pick it up and run it — architecture, implementation, review, deploy, follow-up. The whole arc.
This is the tier founders reach for when they need to move without hiring. When the product is working, revenue is real, and the bottleneck is senior engineering capacity rather than money. Hiring full-time takes three to six months and a lot of pain; this doesn't.
Workflow
I join the team properly. Daily standups if that's how you work, async if it isn't; I fit your rhythm rather than asking you to change it. Slack, GitHub, your issue tracker, your deploy pipeline — wherever the team already is, that's where I am.
I take real things and own them end to end. A major feature, a platform rewrite, the AI pipeline that works in a demo and falls over with real traffic, a service built from nothing — whatever the biggest item on the roadmap is, I can carry it.
I make architecture decisions on purpose and write down what we gave up to get them. I make deploys something you can watch. I write down how things fail before they fail. This is the work that never happens because everyone's too busy shipping — and it's the work that decides how the next year goes.
And the quiet parts — the reliability engineering, the monitoring, the "why is this slow" investigations — those live inside this tier too. Not as an upsell. Just part of the work.
more info
The whole thing
A senior engineer on your team without the hiring process, the equity conversation, or three months of onboarding. Twenty hours a week from someone who knows your codebase and can take something from architecture all the way to deployed.
This is the tier that moves your roadmap forward; not just reviews it.
Is this for you?
Small teams, shipping fast
Founders whose roadmap is stuck because there isn't enough senior engineering to go round. Teams with an AI feature that works until it doesn't. Companies that found product-market fit and now need the engineering to catch up. Bootstrapped teams hitting real complexity, where hiring one more mid-level engineer won't touch the actual problem.
If you're between "we need someone senior" and "we need to hire a CTO," this is the tier that bridges it. Often for longer than either of us expects.
If twenty hours feels like more than you need, Partner is the halfway point. If you need more than twenty — thirty, full-time-adjacent — that's a conversation, not a tier. Email me, and we'll figure it out.
still here?
let's start and get to work
If this sounds like the shape of the engagement you actually need, there's a discovery call on the other side of the button.
Still comparing? The full picture is over here.