Skip to main content
Engagement models

Four ways to put me to work

Every company is at a different point, so I work in a few different shapes. Each is scoped to a different need and a different slice of my week. We can also start in one and move to another as your situation changes.

Technical Advisory · ENG-ADV

Roughly half a day a week. A senior sounding board on call. We meet on a regular cadence and you get me between sessions for the decisions that can't wait. I won't run your team day-to-day; I'll make sure the person who does is making good calls on architecture, hiring, and roadmap.

Best fit: founders or heads of engineering who own delivery but want experienced judgment on the big, expensive decisions.

You get: a recurring strategy session, async access for unblocking, and a running record of decisions and rationale.

Embedded / Interim CTO · ENG-EMB

Two to three days a week. I step in and own the technology function with full accountability — roadmap, team, delivery, and the technical conversations with your board, customers, and investors. The difference from advisory is ownership: the outcomes are mine, not just my advice.

Best fit: companies scaling fast, or between CTOs, that need a steady hand on the wheel now rather than after a six-month executive search.

You get: a leader for your engineering function, present in your rituals and accountable for results, without the cost or commitment of a full-time hire.

Architecture & Build Sprint · ENG-SPR

A fixed-scope sprint, usually four to eight weeks. We set the foundations right: a target architecture, a technical plan with trade-offs made explicit, and a build path your team can actually execute. Ideal when you're at a turning point and the cost of getting it wrong is high.

Best fit: teams facing a rebuild, a new platform, a scaling wall, or a big build-vs-buy decision.

You get: a documented architecture and technical plan, a prioritized backlog, and a clear hand-off — with the option to keep me on in an advisory role while your team executes.

Technical Due Diligence · ENG-TDD

A one-to-two-week independent review. I assess code, architecture, team, and risk, then deliver a written report with a confidence rating, the real risks ranked by severity, and a remediation list. Honest, specific, and readable by both technical and non-technical stakeholders.

Best fit: investors and acquirers who need the technical truth before a decision — and founders who want to know what diligence will surface before someone else runs it.

You get: a clear report you can act on or share, plus a debrief call to walk through the findings.


How pricing works

I keep it simple and predictable: advisory and embedded work runs on a monthly retainer sized to the days involved; sprints and diligence are fixed-scope, fixed- fee. No long lock-in — embedded and advisory engagements are month-to-month, so you can scale me up or down as things change. We'll agree exact numbers on the discovery call once I understand the scope.

Next

Ready to scope something?

Book a discovery call — 30 minutes, no obligation — and I'll recommend the model that fits, even if that turns out not to be me.