I don't run a dev shop

Handoff
July 28, 2026
I don't run a dev shop

If you need a bench of developers, you should hire a firm that sells a bench. I am not that firm. I have been in the room when that model goes well, and I have been in the room when it turns into a second product org you did not mean to own.

My job is the case for change, the proof, and the architecture that survives the handoff. Delivery at scale belongs to a partner who does that for a living. I stay on as architect of record. I do not pretend I am also the factory.

If I have to staff your build, I have already failed the design of the engagement.

Why the bench is a trap for this work

When the advisor also sells the hours, every recommendation is a little bit for sale. You can feel it. Sponsors can feel it. The skeptical CTO in the room can definitely feel it.

I have used lieutenants in the past. Sometimes that is the right call for a single, named engineer under a written agreement. It is a bad default. It puts person-risk on a practice that should be selling judgment, not headcount.

The 2026 version is cleaner. Prove the bet. Then bring in a build partner, including GenUI when the work is industrial, and keep the architecture from drifting while they execute.

What handoff actually means

Handoff is not "here is a deck, good luck." It is a working seed, a written spec, and a person who still attends the hard meetings. The partner owns delivery. You are not locked into me for the next two years of tickets.

If there is no next step, I will say so before we start. Some problems are not a software problem. Some are a staffing problem. Some are a "your sponsor is not in the room" problem, and I will not take that work.

How to tell us apart

A dev shop leads with capacity and a slide of logos. A marketplace leads with a roster. I lead with the choke point and a time box. If that sounds smaller, it is. Smaller is the point.

You can hire me to find the number that matters and prove it. You can hire a partner to industrialize it. You should not hire one company to pretend it is both, unless you like paying for the conflict of interest.

I built and exited twice. I scaled an engineering org from 7 to 200. I still write the first proof when that is what unlocks the budget. I do not need your standups after that, unless you want me in them as the architect. That is a different contract, and it is honest about what it is.

Ready to find the number that matters?

Start with an audit. You'll leave with one number that justifies the next spend, whether you engage further or not.

Contact Us