Fractional vs. contract: what's the real difference?

"So are you a contractor, or a consultant, or — what, exactly?" It's a fair question, and I get it often. On the surface the models look alike: someone senior works part-time, solves a problem, and leaves. But the distinction matters a great deal if you're the one deciding what to hire.

The confusion usually starts with the word itself. Fractional what? A year? A week? A day? That question turns out to be the door into the real answer.

The denominator problem

"Fractional" is close to meaningless as a descriptor unless you know what you're taking a fraction of. In practice, an engagement can look like any of these:

• Full-time for four months, to stand up product strategy and hand it off
• Ten to fifteen hours a week for most of a year, shepherding a product through a transition
• Three weeks embedded, to diagnose why the roadmap keeps slipping

Same title. Three different denominators, three different price points, three different shapes of work. If the word described a schedule, those three things would not share a name.

They share a name because they share something else — and it isn't hours.

The real difference is ambiguity

Contract work has a defined scope. You know what you're solving for. The deliverables, the timeline, and the definition of done exist before the contractor starts. If the scope changes, you renegotiate it. The work is clear; execution is the variable.

Fractional work exists because there's ambiguity. You aren't hiring a fractional leader because you've figured out what you need. You're hiring one because you haven't. The problem isn't fully named yet, the duration is genuinely unknown, and someone has to make sense of the mess before anyone can scope the fix.

The difference is audible in how the two engagements get described.

A contract engagement sounds like: we need these six features built by December 15th.

A fractional engagement sounds like: our team is shipping constantly and nothing feels finished, and we don't know whether that's a prioritization problem, a planning problem, or a team structure problem.

Side by side

Why the distinction is worth getting right

It changes who you should hire. Contract work rewards someone who executes cleanly against a spec. Fractional work rewards someone who can walk into an unfamiliar org, form a view quickly, and be willing to tell you the problem isn't the one you described. Those are different people, and they are good at different things.

It changes how you read a shifting scope. In a contract engagement, a moving target is a problem to be managed. In a fractional engagement, discovering that the real issue is upstream of what you were told is the work being done correctly. Teams that expect the first and get the second tend to conclude the engagement is going badly when it's going exactly right.

It changes what you get at the end. A contractor hands over a deliverable. A fractional leader hands over a diagnosis, the fix, and the process your team uses after they're gone — which is also why a good fractional engagement should get progressively less necessary.

The mismatch to watch for

A fair amount of what gets labeled "fractional" is contract work with better branding. When a company says it wants a fractional CMO but means it wants someone to run an existing marketing plan twenty hours a week, that's contract work. The plan is written; execution is the variable. Nothing wrong with it — it just isn't the thing the word describes.

The reverse mismatch is more expensive. A company hires a fractional leader expecting discovery and diagnosis, then hands them a finished roadmap and asks them to staff it. The leader came to figure out what was wrong; the org had already decided. That engagement usually stalls, and it's rarely anyone's fault beyond a shared word doing too much work.

How to tell which one you need

One question sorts it faster than any amount of deliberation: can you describe the exact problem you're solving and how you'll know it's solved?

If you can, you likely need a contractor or a tactical hire, and you should scope it tightly and hold someone to it.

If you can't — if what you have is a pattern rather than a diagnosis, symptoms rather than a cause — then you need someone who can come in, work out what's actually wrong, and fix it. That's a fractional engagement, whatever the hours end up being.

The denominator is a scheduling detail. The ambiguity is the model. If you want to see how that shakes out in practice, the engagement shapes are here.