Fractional, agency, or in house
Three ways to put senior capability on a problem. They fail in different directions, and the direction is predictable enough to plan around before you commit.
In short
The three models differ on one axis that rarely gets discussed: who holds the context when the engagement ends. An agency keeps it. A full time hire holds it and can leave with it. A fractional operator is supposed to build it into your systems and hand it over. Choose on whether the work is a function, a project, or a gap, and insist in every case that whoever does it leaves a written process behind.
The three models
A full time hire
Right when the work is a permanent function with enough steady volume to fill a week, and when the role owns an outcome rather than absorbing a queue.
An agency
Right when the work is a specialist discipline you need continuously and never want to run in house: media buying, paid search, large content operations.
A fractional operator
Right when the work is senior, intermittent, and benefits from somebody who has done it before. What you are buying is judgement per hour rather than hours.
A contractor for a defined build
Right when the scope has a clear end. The trouble starts when a project engagement quietly becomes a permanent dependency that nobody planned or reviewed.
Nobody, for now
Right when the honest answer is that this is not yet a function. Hiring ahead of the volume creates a role that has to invent its own justification, which it always manages to do.
The combination most companies land on
A senior operator setting direction, an agency running one specialist channel, and somebody in house owning the day to day. The mix matters less than who holds the context.
The question underneath the staffing question
Most staffing decisions get made from a feeling of being overwhelmed. The feeling is real and it is useful, but it is not a specification. Overwhelm tells you something has outgrown its arrangement. It does not tell you which thing, or whether the answer is a person at all.
The expensive version is hiring to absorb a queue. Work is piling up, so a role is created, and the first job description is essentially a list of things nobody else has time for. It gets filled quickly, the new person is busy from week one, and the arrangement looks like an obvious success.
What has actually happened is that a structural problem has been permanently staffed. The queue was caused by a handoff, an approval, or a system that makes three people re-enter the same information. Putting a person at the end of that removes none of it. It hides it, and now it has a salary attached.
Agencies fail differently. The engagement starts well because they arrive with a process that already works, then it settles into a reporting rhythm. The deck arrives monthly, the numbers get presented rather than interrogated, and after two quarters nobody inside the company can say what would change if the work stopped.
Fractional work fails when the handover never happens. If a senior operator is still personally required after a year, either the scope grew for good reasons or nothing was ever documented. Both are worth naming out loud, and only one of them is acceptable.
The version that works has the same property in all three models. Somebody inside the company can describe how the work runs, and there is a written process that survives the person doing it. Everything past that is a staffing preference rather than a strategy.
What each model is actually good at
Seven factors, read across. The row that decides most engagements is the third one, and it is the row that almost never comes up during the decision.
| Factor | Full time hire | Agency | Fractional operator |
|---|---|---|---|
| Best fit | A permanent function with steady volume. | A specialist discipline run continuously. | Senior judgement applied intermittently. |
| Time to useful | Weeks to months: hiring, notice period, ramp. | Days to weeks. They arrive with a working process. | Days. The method is the thing being bought. |
| Where context lives | In one person, unless you insist otherwise. | With the agency, and it leaves when they do. | Should be built into your systems. Ask on day one. |
| Depth and breadth | Deep in one thing, and deeper over time. | Deep in their discipline, narrow outside it. | Broad across operations, deep in the pattern. |
| How it goes wrong | The role becomes a queue and the person burns out. | Reporting quietly replaces results for two quarters. | It becomes a permanent dependency instead of a handover. |
| Question to ask | What outcome does this person own? | What does this account look like in month six? | What are you leaving behind, and when? |
| Exit | Notice period, plus a knowledge gap if nothing was written. | Notice period, and the tooling usually goes with them. | By design: a documented process that runs without them. |
None of the three is better than the others. They fail in different directions, and knowing the direction in advance is most of what keeps an arrangement healthy.
Five questions before you staff it
Answer these before writing a job description or taking a first agency call. They take an afternoon and they routinely change the answer.
- Is this a function, a project, or a gap?A function is permanent and has steady volume, so hire. A project has an end, so scope it and contract it. A gap is senior work that is real but intermittent, which is the only one of the three that fractional is genuinely built for.
- Would this role own an outcome, or absorb a queue?Write the job description and look at it honestly. If it is a list of things nobody else has time for, you are about to permanently staff a structural problem rather than fix it.
- Has anybody measured how many hours the work takes?One week of rough tallying settles most of these arguments. Teams routinely discover the work is either two days a week, which is not a hire, or that it is spread across four people already.
- Where will the knowledge live in a year?Name the answer before the engagement starts. If the honest answer is "with whoever is doing it", that is the risk, and it applies to a full time hire just as much as to an outside firm.
- What does success look like in ninety days?If nobody can describe the ninety day picture in a sentence, the scope is not ready yet. This one question prevents more bad staffing decisions than any interview process.
Questions we get
What does fractional actually mean?
A senior operator working across a defined scope on part of a week, rather than a full time employee or a project contractor. The unit being bought is judgement and method rather than hours of execution.
The practical test is whether the person is setting how the work runs or doing the work. Fractional is the first one. When it becomes the second for long, it has drifted into being an expensive contractor.
Is fractional just a consultant with a new name?
The difference that matters is ownership. Consulting typically ends with a recommendation. Fractional work ends with something running, documented, and handed to somebody inside the company.
If an engagement produces a deck and no working process, the label on it does not matter much.
When is a full time hire clearly the right answer?
When the work is permanent, has enough volume to genuinely fill a week, and owns an outcome you can name. Those three together are a real role.
Two out of three is usually a sign to wait, restructure the work, or bring in senior help to design the role properly before opening it.
How do we stop an agency relationship going stale?
Agree what would make you end it, in writing, at the start. Then review against that rather than against the monthly report. Reporting is not the same thing as results, and it is very easy to substitute one for the other.
Ask once a quarter what would change if the work paused for a month. If nobody can answer, that is the answer.
Can a fractional operator manage our agencies?
That is one of the clearest uses of the model. Agencies perform better with a competent counterpart on the client side who can read the numbers and say no.
Most underperforming agency relationships are not agency failures. They are the result of nobody inside the company having the time or the standing to hold the work to account.
What should a handover include?
The process written down step by step, where the accounts and credentials live, what breaks and how you know, and a named person inside the company who owns it from that day.
If a handover is a call and a folder of files, it is not a handover. The test is whether somebody who was not in the room can run the thing next month.
How long should a fractional engagement run?
Long enough to diagnose, build, and hand over. That is usually a matter of months rather than years, and the end should be visible from the start.
Ongoing arrangements are legitimate where the scope is genuinely continuing, but that should be a decision somebody makes rather than a default that happens.
We are small. Is any of this relevant yet?
The staffing question arrives earlier than most founders expect, usually the first time work stops moving because one person is the bottleneck for approving it.
At that size the right answer is often none of the three. Fix the handoff, write down the process, and buy yourself another two quarters before adding anybody.
More in the guides and every answer in one place.