Consultant, advisor or fractional CTO?
The three kinds of outside technical help do different jobs. How to tell which one your startup needs, what each should deliver, and what to expect after hiring a consultant.
[ SHORT ANSWER ]
A tech consultant solves a defined problem and hands you an answer. A technical advisor gives you judgment over time without owning anything. A fractional CTO owns your technical direction part-time. The differences are ownership and duration, not seniority. If you cannot yet name what is wrong with your team, you need the consultant, because a diagnosis has to come before anyone is hired to execute on it.
Founders who reach out to me have usually already been pitched at least one of the other two. Someone offered to be their fractional CTO. Someone senior offered to advise for equity. They are not sure which of those they need, or whether what they actually need is something else.
The confusion is reasonable, because all three are experienced technical people offering to help from outside. But they do different jobs, they fit different situations, and buying the wrong one is expensive in a way that only shows up months later.
I do the first one. I will try to be fair to the other two.
The three roles, by what they own
The cleanest way to tell them apart is to ask what each one owns, and for how long.
A tech consultant owns a problem
A consultant is brought in to answer a specific question and leaves when it is answered. Why has delivery slipped for three quarters. Is this team the wrong shape. Should we rebuild or refactor. Is the tech lead the bottleneck.
The engagement is bounded. The output is a diagnosis and a set of recommendations you can act on. The consultant does not own your team, your roadmap or your architecture. They own the accuracy of the answer.
What a good one delivers: a written root-cause diagnosis in plain language, a role-by-role read, and a lean plan scoped to your stage. What a bad one delivers: a slide deck of frameworks, a proposal that could have been written for any company, and a recommendation to hire them for longer.
A technical advisor owns nothing, on purpose
An advisor is a senior technical person you can call. A few hours a month, often for equity, sometimes paid. They give you judgment: is this architecture sensible, is this hire reasonable, is this vendor a mistake.
The value is in having someone with pattern recognition who is not inside your company. The limit is that they are not inside your company. They see what you show them, on the schedule you show it. They will not find the problem you do not know you have.
An advisor works when you already have a technical owner who needs a sounding board, or a founder who needs a second opinion on decisions they can already frame. It does not work as a substitute for someone doing the work of looking.
A fractional CTO owns the direction
A fractional CTO is a part-time executive. They own technical strategy, usually manage or lead the engineering team, and carry accountability for delivery, for a defined number of days a week.
This is the right seat when nobody in the company owns technical direction, and the company cannot yet hire that person full-time. It is execution, not diagnosis. A fractional CTO will form a view of what is wrong, but they form it from inside the seat they now hold, and they will naturally see the solution as the seat being filled properly.
That is fine if the absence of a CTO was the problem. It is expensive if the problem was undefined ownership two levels down, or a process that no longer fits the stage, and you have now added an executive on top of it.
Which one you need
Ask yourself one question. Can I name what is wrong?
No, I just know delivery is broken. Consultant. The diagnosis comes first. Hiring someone to execute before you know what to execute on is how founders end up paying for a fractional CTO to discover that the tech lead needed a role change.
Yes, and I have someone technical who owns it, but they need a sounding board. Advisor. Cheap, low commitment, useful for the decisions your technical owner can already frame.
Yes, the problem is that nobody owns technical direction. Fractional CTO, or a full-time one if you can. Just make sure that is actually the problem. A team with a competent tech lead and a broken process does not need an executive. It needs the process fixed.
I am about to make an expensive decision about people or architecture and I cannot verify the reasoning. Consultant, for a bounded second opinion. This is the cheapest way to avoid the most expensive category of mistake.
I wrote about how to run the self-diagnosis before hiring anyone in when to hire a startup tech consultant. Do that first. Whichever role you end up buying, you will brief it better.
What to expect after hiring a consultant
Since this is the one I do, here is what the engagement should produce, and what it should not.
In the first conversation, before any scope is agreed, you should get an honest read on whether they can help at all. A consultant who is sure they can fix your problem before hearing about it is selling a package.
During the engagement, they should be talking to your engineers and watching how work flows, not just interviewing you and your tech lead. If the diagnosis is built from the leadership view only, it will reproduce the leadership's blind spots.
At the end, you should hold three things. A diagnosis in plain language of what is actually wrong, with the evidence. A prioritised set of changes to roles, process or people, scoped to your stage rather than to a company ten times your size. And enough clarity that you could explain the situation to your board in two minutes and brief a new hire properly.
What you should not get: a recommendation to hire them for longer as the primary output, a stack recommendation before a problem definition, or a report that requires the consultant to interpret it.
The test I give founders: if the engagement worked, you should be able to make your next three technical decisions without calling anyone.
I do the diagnosis. I go into the team, watch how work actually flows, and tell you in plain language whether the problem is people, roles or process, and what to change. Book a call. Thirty minutes, free, no pitch.
When to bring someone in
Earlier than most founders do. The signals that it is time are the same ones I described in signs your startup needs a tech mentor: delivery has slipped for more than a quarter with a changing explanation, headcount grew and output did not, and you cannot tell whether individuals are performing.
The reason to move early is cost. A diagnosis is a bounded expense. A wrong restructuring, a wrong senior hire, or a rebuild that turned out to be a process problem are not. Every quarter a team stays broken is runway spent on work that does not compound.
One more distinction
None of the three roles is a substitute for a technical owner inside the company. A consultant leaves. An advisor is not there. A fractional CTO is there part of the week. At some point the company needs someone whose whole job is owning the technical direction, and the outside help should be making that seat easier to fill, not replacing it indefinitely.
If the person you are talking to does not say that, ask them why.
[ FAQ ]
Questions founders ask
- What is the difference between a tech consultant, a technical advisor and a fractional CTO?
- A consultant solves a defined problem and hands you an answer, in a bounded engagement. An advisor gives you judgment over time, usually a few hours a month, without owning anything. A fractional CTO owns your technical direction and often your team, part-time, for as long as you need. The differences are ownership and duration, not seniority.
- Which one does my startup need?
- If you know something is wrong but cannot name it, a consultant, because the diagnosis has to come first. If you have a technical owner who needs a sounding board, an advisor. If nobody in the company owns technical direction and you cannot hire a full-time CTO yet, a fractional CTO. Choosing the wrong one usually means buying execution before you have a diagnosis.
- What outcomes should I expect after hiring a tech consultant?
- A written diagnosis in plain language of what is actually wrong. A specific, prioritised set of changes to roles, process or people, scoped to your stage. Enough clarity that you can explain the situation to your board in two minutes and brief a hire properly. If you get a deck of frameworks instead, you did not get a consultant.
- When should a startup bring in an external consultant for the tech team?
- When delivery has slipped for more than a quarter and the explanation keeps changing, when you have hired and output did not improve, or when you are about to make an expensive decision about people or architecture and cannot verify the reasoning yourself. Earlier is cheaper. The cost of a diagnosis is small next to the cost of a wrong restructuring.
- Is a fractional CTO a substitute for a diagnosis?
- No. A fractional CTO will diagnose as part of taking over, but you are paying for ownership and execution, and they will naturally see the problem through the lens of the seat they now hold. If you are not sure the problem is the absence of a CTO, get the diagnosis first and then decide what seat, if any, to fill.
[ THE OFFER ]
Still trying to figure out if the problem is the team or the tech? That's the call. Book it.