
Fractional, Interim, or Advisory: Which CTO Engagement Fits Your Stage
By Tom Lang on September 16, 2026
I'm Tom Lang — I've built and scaled engineering organizations for three decades, through multiple acquisitions, and I work as a fractional and interim CTO for growth-stage companies, with particular depth in regulated and integration-heavy environments.
Founders ask me whether they need a fractional, interim, or advisory CTO as if they're choosing from a menu — or worse, climbing a ladder where one is a promotion over the others. It's neither. The right way to think about it is an ecosystem: one front door, and three internal gears. You don't pick a gear by ambition or budget; you match the amount of executive capacity to the current state of your business. Here's how the pieces connect, and the honest triggers that tell you which gear you're actually in.
(If you're not yet sure what a fractional CTO even is, versus a consultant or a dev shop, start with what a fractional CTO actually does — this post builds on that.)
The front door: a Diagnostic, always
The Technology Diagnostic isn't just an entry point — it's the triage desk. I rarely, if ever, sell a Fractional or Interim engagement cold, and that discipline protects both sides: it protects me from walking into an un-scoped disaster, and it protects you from buying heavy executive capacity you may not need.
Here's how I put it to a prospect: "We don't guess, and we don't start open-ended retainers blindly. We start with a fixed-fee Diagnostic to map the reality of your tech, team, and roadmap. At the end of it, I'll tell you exactly what you need — whether that's me stepping in as your Fractional CTO, an Advisory retainer for your existing leadership, or just a new set of processes."
The Diagnostic tells you your state. The gears give you the capacity to act on it.
The three gears
Think of them as levels of executive capacity, not a hierarchy:
- Advisory — the lightest gear. Board- or founder-level counsel. Judgment on call, but your people execute.
- Fractional — part-time embedded ownership. I'm on your leadership team, owning strategy, delivery, and the team, a couple of days a week.
- Interim — the heaviest gear. Near-full-time leadership for a defined stretch, when something big is on the line.
None of these is "better" than the others. The right one is simply the one that matches what your business needs right now.
The triggers — how you know which gear you're in
The clearest way to find your gear is to notice which of these sounds like your life.
Advisory → Fractional — the execution gap. You're getting good advice, but nobody's actually implementing it. The trigger sounds like: "I know what we should be doing, but my engineering lead isn't doing it, and I don't have the technical authority to hold them accountable. I need someone to own the delivery." Advice isn't your problem anymore; ownership is.
Advisory (or a cold start) → Interim — the crisis or event. Something high-stakes and time-boxed hits. Your CTO abruptly resigns. An aggressive acquisition integration begins. Institutional investors mandate severe technical due diligence before they'll fund you. The house is on fire, and you need a chief on the ground close to full-time until the flames are out.
Interim → Fractional — the stabilization. The crisis has passed. The new processes are built, the team is steady, the fire's out. The trigger: "We survived the transition. We don't need to pay for a full-time executive anymore, but we need you to stay on two days a week to keep the new engine running."
Fractional → a full-time hire — the graduation. This is the real success metric, and the one I aim for. The company scales to where the sheer velocity of daily technical decisions needs a permanent, 40-plus-hour, in-house leader. So I define the spec, interview the candidates, and hand them the keys. A healthy engagement works itself out of a job.
Does anyone move up?
Yes — but only when the business takes a sudden shock, never as a "promotion." Say I'm working fractionally, two days a week, steering a steady-state team. Then the company acquires a rival and has to merge two large codebases in 90 days. I bump up to Interim — four days a week — to run the integration sprint, and dial back to Fractional the moment it's done. The gear followed the business, not the other way around.
The honest framing
That's the whole idea: I'm not selling you a progression to climb. I'm selling the right amount of executive capacity for the state your business is in today — and the willingness to change gears the moment that state changes. The Diagnostic tells you where you are; the gears meet you there.
Not sure which gear you're in? That's exactly what the front door is for. Book a call and we'll start by figuring out your actual state.

Related reading

CTO vs. VP of Engineering vs. Lead Engineer vs. Technical Co-Founder: Who You Actually Need
By Tom Lang on October 5, 2026
Founders use 'CTO,' 'VP of Engineering,' 'lead engineer,' and 'technical co-founder' as if they're the same hire. They're four different jobs — and hiring the wrong one for your stage is an expensive mistake. Here's what each actually does, which one fits your stage, the mis-hires I see constantly, and where a fractional CTO fits.
Read more
How Fractional Leadership Sets You Up to Hire a Full-Time CTO
By Tom Lang on September 16, 2026
Smart founders have a real fear about fractional CTOs: won't they just make themselves indispensable and bill forever? My model is the opposite. The best outcome of a fractional engagement is that I hand you a permanent CTO and leave. Here's the multi-month playbook for how I engineer that hand-off — and why working myself out of a job is the core marketing engine of my practice, not lost revenue.
Read more
Integrating Engineering Teams After an Acquisition
By Tom Lang on September 16, 2026
The instinct after an acquisition is to immediately merge databases and consolidate cloud providers to show cost savings. That instinct destroys value. Mergers don't fail on incompatible tech stacks — they fail on mass attrition and severed context. Here's how I actually run an engineering integration: what I secure on day zero, what I integrate versus deliberately leave separate, the 90-day sequence, the cultural landmines that sink most deals, and the scar that taught me the one rule I never break.
Read more