Skip to content
$500 a month

You make the calls.
I make sure they are informed.

You own a product that AI coding agents built, and the technical decisions land on you. You do not need to become an engineer. You need an experienced one to think it through with you before you commit.

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

What this is for

The questions that stall you

All of it in writing, by email or messenger, at the pace of your week.

“Is this proposal reasonable?”

A developer wants three months and a rewrite. You get an assessment of what it would fix, what it quietly does not include, and what it would cost you to say no.

“What do I actually own?”

A plain explanation of what your product is made of and where its real weak spots are, based on reading it rather than guessing.

“How do I even ask for this?”

A vague intention turned into a technical brief your developer or your AI agent can act on without inventing the missing half.

“What should I run in Claude Code?”

A prompt written or reworked for your situation: an architecture analysis, an audit of a risky area, a check on what a contractor just delivered.

A typical month

What two hours a week looks like

Not a schedule you have to fill. A boundary, so the answers you get are considered ones.

  1. Week one, I read your product

    Stack, hosting, how it is deployed, who touches it, what you already decided. You write it once and it stays true for everything after.

  2. Any week, you ask

    A question, a proposal you received, a document, a decision you are about to make. You write it as it comes to you, not as a formal ticket.

  3. I answer in writing

    What I think, why, what I would check before committing, and what I would ignore. Not a report. An answer.

  4. Sometimes the answer is a prompt

    When the right next step is for your agent to go and look, I write the prompt and tell you what a good result looks like.

  5. A call when writing is genuinely not enough

    Occasionally, arranged around both our schedules. It is not the default channel, and that is deliberate.

Included

What comes with this level

Written consulting

Email or messenger, whichever you already use. Your questions, my answers, on the record.

Your technical context

Kept between conversations, so the fifth answer is better informed than the first.

A second opinion on demand

On what developers, contractors and vendors propose, from someone with no stake in the outcome.

Is this the right level?

You need a higher level if

You want someone to run your development team

You need tasks written, assigned and accepted

You want servers, CI/CD or deployment set up

You want the product actually built

This level fits if

You make the technical decisions yourself

You want them checked before you commit

You work with contractors rather than an in-house team

You are comfortable working in writing

Pricing

Start here, move up when there is work to run

This is the entry level. Changing it later is a button, not a conversation.

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

Stop approving technical decisions you cannot judge

Describe your product, ask the first question this week, and cancel yourself if it is not for you.