Four ways to bring me in.

Service 01

Advisory

A sparring partner for founders, CTOs, and heads of engineering.

You’ve got the strategy. You mostly know what to do. You need someone to poke holes in it, name the thing nobody’s naming, and help you sequence the next 90 days. I’ve led Engineering Directors, managers, Delivery, and Data at senior scale, so I work with you directly on process, hiring, delivery discipline, org design, performance calls, and the difficult people conversation you’ve been avoiding.

Best for

Founders and senior leaders at seed → Series C who want an outside brain without hiring one.

How it works

A scoping call → monthly retainer, e.g. ~4 hours a month, ad-hoc between → we adjust as it evolves.

Service 02

Fractional CTO

Founder-shaped engineering leadership, on the days you actually need it.

Most founder-stage companies don’t need a full-time CTO. They need someone senior in the room for the calls that shape the business, and out of the room for the ones that don’t. I sit alongside founders as their fractional CTO for the decisions that matter: architecture, first hires, delivery cadence, technical due diligence for investors, the difficult people conversation. That experience comes from having run Engineering, Delivery, and Data as a Senior Director of Product Engineering, so the same shape also works for scale-stage teams between permanent CTOs or navigating a re-org.

Best for

Founders without a technical co-founder, or scale-stage companies from ~3 → ~150 engineers between permanent CTOs.

How it works

Discovery week → agreed scope and success criteria → 2-3 days a week for a defined period → clear exit plan from day one.

Service 03

AI Workflow Design

Turn scattered AI habits into a delivery practice the whole team can run.

Most teams are stuck between a blanket ban and twenty private Cursor setups with no shared bar for what ships. Neither scales. I help you design the missing middle: when AI is fair game in the delivery flow, how review and ownership work when a model wrote half the PR, what “done” means when code arrives faster than judgment, and which quality checks catch the new failure modes. You leave with a working practice for your real codebase, not a slide deck. Same workflows I use on my own products (see /now).

Best for

CTOs and heads of engineering at teams of ~10-200 where AI use is already uneven, and you want one coherent practice before that becomes a quality or risk problem.

How it works

Map how you actually ship today → workshop the target workflow with leads → 4-8 weeks embedded to introduce it on live work, then hand it over.

Service 04

Mentoring

1:1 sessions for engineers and new leaders. Via MentorCruise.

We meet on a recurring cadence, usually every two to four weeks. You bring the situation: a hard conversation, a promo case, a team you can’t read, a job you’re not sure about. We work it. Straight talk, not therapy. I’ve sat on both sides: as an IC, as a manager, and as the director reviewing the managers, so most of the conversations you’re about to have are ones I’ve already had.

Best for

Senior engineers moving into leadership, new EMs, directors navigating scale, and leaders who need someone in their corner who isn’t their boss.

How it works

Book a slot on MentorCruise → we meet on Zoom → you leave with a next move, not a vibe.

Common signals

When to bring me in.

None of these on their own is decisive, but if two or three ring true, it’s probably time for a conversation.

How I work

Four steps. In that order.

I try to be useful from day one and out of the way by the end. What that actually looks like: