“So what exactly do you do?”

The question comes up on every first call. For a long time I answered with a list — architecture, technical debt, team structure. It was accurate and it explained nothing, because it described activities rather than the thing being bought.

The useful answer is shorter. A freelancer sells time. A fractional executive sells decisions.

(If that sounds like a distinction without a difference, stay for the invoice.)

The two questions

A freelancer is asked: “Can you build this feature?”

A fractional CTO is asked: “Should we build this feature?”

Everything follows from that. The first question has a schedule attached. The second has a consequence attached — and the consequence outlives the engagement by years.

A freelancer who answers the second question is doing unpaid strategy. A fractional executive who answers the first is expensive labour.

flowchart LR
    subgraph FL["Freelance"]
        F1["Sells time"] --> F2["Deliverable: code"]
        F2 --> F3["Value = hands on keyboard"]
        F3 --> F4["Scales with days worked"]
    end
    subgraph FR["Fractional"]
        R1["Sells decisions"] --> R2["Deliverable: direction"]
        R2 --> R3["Value = 20 years compressed
into a 3-hour call"]
        R3 --> R4["Scales with what it prevents"]
    end
    style FL fill:#1a1a1e,stroke:#666
    style FR fill:#4a3b00,stroke:#fab400

Why the day rate confuses everyone

Put the two on a rate card and the comparison looks absurd. A freelance developer bills €300–600 a day. A fractional CTO bills €1,000–2,000. Same unit, three times the number.

The unit is the problem. Selling a day of a fractional executive as a day is a category error — it prices the input of something whose entire value is in the output.

Alan Weiss made this argument about consulting generally, and it holds here: the moment you bill for time, you have agreed that time is what you produce. You then have an incentive to need more of it.

→ Weiss, A. — “Value-Based Fees”, Jossey-Bass

A fractional engagement is priced against what a wrong architectural decision costs. That number is rarely small, and it is never measured in days.

The test that settles it

Take a decision your team made six months ago. Ask someone who wasn’t in the room why it was made.

If they can answer, someone was doing fractional work — whether or not that was the job title. If they can’t, you bought execution and assumed direction would come free.

When you actually need a freelancer

Most of the time, honestly.

If the direction is clear, the architecture holds, and the constraint is throughput — you need hands, and paying executive rates for hands is burning cash. A fractional CTO on a well-run team with a clear roadmap is an expensive observer.

The reverse failure is quieter and more expensive: hiring execution when the problem is that nobody can decide. The team ships steadily in a direction nobody chose. You find out eighteen months later.

Where the argument stops working

At around two to three days a week over twelve months, a fractional CTO costs more than a full-time hire. That is not a flaw in the model — it is the model telling you something.

If you need someone in the room that often, you don’t need a fractional executive. You need a CTO. A fractional who quietly becomes full-time has failed at the job, which is to become unnecessary.

(Be wary of any consultant whose ROI calculation contains no case where they lose.)

A freelancer bills to do. A fractional bills to think.

And thinking is worth more than execution — because execution without direction is just expensive motion.

Sources

• Weiss, A. — Value-Based Fees, Jossey-Bass
• Field observations — fractional CTO engagements