Skip to content
$1,500 a month

Someone has to turn goals
into technical work

You have people writing code, or AI agents doing it, and nobody on your side deciding what should be built, in what order, and whether what came back is actually finished.

No sales call · Change level or cancel yourself · Your servers and repository stay yours

What this is for

What stops when nobody leads the work

Goals stay as goals

I break down what you want into work the team can start on tomorrow, with the order decided rather than negotiated every week.

“Done” is a matter of opinion

Every task gets acceptance criteria written before it starts, and the delivered work gets checked against them, not against a demo.

The same decision keeps being remade

Architectural choices get made with you, written down, and applied. Drift gets named while it is still cheap to fix.

Agents produce more than anyone reviews

I prepare the prompts and instructions your people and your AI agents work from, and I read what comes out of them.

How it runs

What a month of technical leadership looks like

  1. The backlog gets shape

    Not a list of everything anyone ever asked for. A prioritized set of work with a reason for the order.

  2. Work gets written down properly

    Each task says what to do, what it must satisfy, and what it deliberately does not cover.

  3. The team builds it

    Your developers, your contractors, your AI agents. I do not take the keyboard on this level.

  4. I review what comes back

    Against the task, not against the impression. What is finished, what only looks finished, what quietly broke something else.

  5. Risk gets reported before it costs money

    Half-finished work, growing technical debt and decisions drifting away from what was agreed.

Included

What comes with this level

A managed backlog

Shaped, prioritized and decomposed. You always know what is next and why it is next.

Your team works with me directly

Developers and contractors ask in their own name instead of relaying everything through you.

Acceptance of delivered work

Someone technical checks the result before you pay for it or ship it.

Is this the right level?

You need a different level if

There is nobody to build the work I would plan

You want me to write the product code myself

You want servers and CI/CD configured by me

You only need occasional advice, not continuous involvement

This level fits if

You have developers, contractors or agents producing code

Nobody technical is deciding what they should build

Work gets delivered and nobody senior checks it

You want decisions written down instead of remembered

Pricing

The middle level, and the one most teams actually need

Move up from advice when there are people to lead, and up again when you want the work built.

Technical Development Lead

$1,500 /month

Continuous involvement in the work

Your team works here too

I run the technical work. Your team does it.

You have developers, contractors or AI agents producing code, and nobody on your side is turning business goals into technical work and checking what comes back.

  • Everything at the advisory level
  • Your goals broken down into technical work the team can actually start on
  • A backlog that is shaped and prioritized, not a list of everything anyone ever asked for
  • Tasks written with acceptance criteria, so "done" is not a matter of opinion
  • Prompts and instructions prepared for your people and for the AI agents they use
  • Architectural decisions made with you and written down
  • Delivered work reviewed against the task it was supposed to solve
  • Risks, half-finished work, drift and technical debt named while they are still cheap

I lead the technical work, I do not replace the people doing it. I personally do not set up servers or CI/CD, do not deploy, and do not write the product code. This level is not a fractional developer.

Start with Technical Development Lead

Vibe Coding

$3,000 /month

Short sprints with a finished result

Your team works here too

I build and ship the product myself.

You want the product built properly, and you would rather have one experienced engineer working with professional AI tooling than assemble a team to find out.

  • Everything at the leadership level
  • Hands-on development: I design the solution and I build it
  • Claude Code Max and Codex Pro used as professional tools, not as a novelty
  • Servers, CI/CD, staging and production delivery set up and maintained
  • Git worked the way an engineering team works it
  • Technical documentation written alongside the code and the infrastructure
  • Short sprints where the result is a working feature, not a report of hours spent
  • Every change reviewed and accepted against what it was supposed to do

This is real engineering delivery, so scope is agreed sprint by sprint. There is no fixed-price quote for an open-ended product, no unlimited volume, and no 24/7 on-call.

Start with Vibe Coding

Get the technical work led by someone technical

Describe your product and your team, and the first backlog conversation happens this week.