The hardest part of running an independent consulting practice is not the client work. It is the twenty minutes before each client call when you reconstruct where things stand, what you promised last time, and what has happened since.
Multiply that by five clients and you have spent most of a day a week rebuilding context that should have been sitting somewhere waiting for you.
This is the tax that comes with portfolio work, and it grows faster than the client list. Two clients can be held in your head. Five cannot, and the transition happens without warning, usually while you are busy enough not to notice why everything feels harder.
A category that is growing quickly
The shift towards fractional and independent advisory work is now well documented.
The US market for fractional executive services is projected to reach around $15 billion by 2026, on a compound growth rate near 22% from 2023. Globally the market has passed $5.7 billion and is growing at roughly 14% annually. More than 40% of US small and mid-market companies are projected to use some form of fractional leadership by the end of 2026.
On the supply side, around 55% of senior executives surveyed report either considering or having already moved to a portfolio career model. Temporary and fractional management roles have risen sharply since 2020.
These figures come from a mix of research firms and industry bodies with varying methodologies, so treat the exact numbers as indicative. The trend is not in dispute. More senior operators are working across multiple clients, and more small companies are buying leadership in fractions rather than in full-time hires.
What the growth data does not capture is that the operational challenge of running this way is quite different from either consulting inside a firm or holding a permanent role, and most people arrive at it without the systems it requires.
Why multiple engagements break the systems that worked before
When you left a permanent role, the infrastructure around you was invisible because it was somebody else's job. There was a system of record. There were recurring meetings someone else scheduled. There was a shared understanding of priorities that got refreshed constantly through proximity.
Independent practice removes all of it at once and replaces it with a folder structure and good intentions.
The specific failures follow a pattern. Context switching cost rises non-linearly, because each additional client adds not just its own context but the interference between contexts. Commitments made verbally in one engagement leak out of memory during the week you are deep in another. Client-side changes go unnoticed because nobody thinks to tell the fractional person that the priority shifted.
Then there is the structural issue that almost nobody plans for. Business development stops entirely when delivery is busy. This produces the feast and famine cycle that defines most independent practices, and it is not a discipline failure. It is what happens when the only person who can do the work is also the only person who can sell it, and delivery has hard deadlines while pipeline building does not.
Making each engagement legible
The first fix is to give every engagement the same shape, so that switching between them costs less.
Each client needs a small number of standing artefacts that are always current. Not a project plan, which goes stale, but a live picture of the engagement.
The engagement objective, in one sentence, stated as an outcome rather than a set of activities. This is the sentence you will use in month five when the client asks what value they have received. Write it in month one, agree it with them, and refer to it constantly. Practices that struggle to renew usually cannot answer this question crisply, because the engagement drifted into activity without an anchor.
The current state of the two or three measures that define success. If the engagement is about pipeline, that is pipeline. If it is about operating discipline, it might be forecast accuracy or on-time delivery. The measures should be things the client already tracks, or things you have set up for them to track, rather than things only you can see.
The open commitments, yours and theirs. This is the artefact that most obviously repays the effort. Half the friction in advisory relationships comes from a mismatch about who owes what. A visible list of commitments with owners and dates removes the entire category of problem, and it protects you specifically, because most stalled engagements stall on client-side commitments that were never written down.
The decisions taken and why. Six months into an engagement you will be asked why something was structured a certain way, and the honest answer will be that you cannot remember. A running decision log takes a minute per entry and saves considerable credibility later.
Keeping these four artefacts consistent across every client means the twenty minute reconstruction before each call becomes a three minute review.
Structuring the week
Portfolio work rewards structure more than permanent work does, because there is nothing else providing it.
The most useful principle is to allocate days rather than hours where the engagement allows. Half a day on one client is more productive than two hours across three, by a considerable margin, because the context load is paid once instead of three times. Clients generally accept fixed days if you set the expectation early, and many prefer the predictability.
Reserve one block a week that no client can book. This is where the practice itself gets run: proposals, invoicing, follow-ups with prospects, and the writing that generates inbound interest. If this block is negotiable it will be negotiated away every week, and the famine part of the cycle begins about four months later.
Batch the administrative work rather than distributing it. Invoicing, expense capture and time recording done once a fortnight in a single sitting takes a fraction of the time it takes done continuously, and it does not fragment attention during delivery.
Protect a genuine gap between client contexts. Ten minutes between a call with one client and a call with another is not a break, it is a guarantee that the second call will start badly. Twenty five minutes is usually enough to close one context and open the next.
The first thirty days decide the engagement
Most engagements that go badly were set up badly, and the setup window is shorter than people assume.
In the first month the client is paying attention, the sponsor has political capital invested in the decision to hire you, and the organisation is willing to accommodate a new way of working. That willingness decays. Whatever structure exists at the end of month one is broadly the structure you will have at month six.
Three things need to be established in that window.
The first is a fixed meeting rhythm with the sponsor, in the calendar as a recurring series rather than scheduled ad hoc. Ad hoc scheduling means the meeting happens when things are calm and gets skipped when they are not, which inverts the correct relationship. It should be short and frequent rather than long and occasional, because the value of a fractional operator is largely in shortening feedback loops.
The second is access. Access to the systems where the work actually shows up, access to the people who do the work, and standing permission to attend the meetings where decisions get made. Fractional operators who are consulted rather than included end up producing recommendations that nobody implements, which is the most common way these engagements fail while everyone remains polite about it.
The third is a baseline. Whatever the success measures are, capture where they stand before you have done anything. This feels administrative and is the single highest-return hour of the engagement, because in month six the conversation about value will be evidence-based rather than impressionistic. Practices that skip the baseline find themselves arguing from assertion at exactly the moment that assertion is least persuasive.
If any of these three is refused or deferred in month one, treat it as significant information about how the engagement will go rather than as a scheduling inconvenience.
The renewal problem
Most independent practices lose engagements not to dissatisfaction but to drift.
The pattern is consistent. The first three months are clearly valuable because the problems are obvious and the wins are visible. Months four through eight settle into a rhythm that is genuinely useful but harder to point at. Then a budget review happens, someone asks what the fractional person is delivering, and nobody has a crisp answer, including the client sponsor who values the work.
The fix is to make value visible on a schedule rather than assuming it is self-evident.
A short monthly summary sent to the sponsor, covering what changed in the success measures, what was decided, what is in progress and what you need from them, does most of the work. It takes fifteen minutes to write if the artefacts described earlier are current, and it creates a written record the sponsor can forward when the budget question arrives.
A quarterly conversation about the engagement itself, separate from the delivery work, does the rest. What is working, what should change, what should the next quarter focus on. Sponsors rarely initiate this conversation and almost always welcome it, and it surfaces dissatisfaction while there is still time to address it.
The uncomfortable truth is that engagements which end abruptly usually gave signals for two months first. The signals appear as reduced responsiveness, cancelled sessions and the sponsor stopping bringing you into decisions. Those are worth treating as urgent rather than as scheduling noise.
Pricing and scope drift
Scope drift is the other silent killer, and it is structurally different from the enterprise version because there is no procurement function protecting the boundary.
It begins reasonably. A client asks for something small and adjacent, you do it because the relationship matters, and the new thing becomes part of the engagement without ever being priced. Repeat this six times over eight months and the effective hourly rate has halved.
Two practices prevent most of it. First, write down what the engagement includes and what it does not, at the start, in plain language. The exclusions matter more than the inclusions and are usually omitted from proposals because they feel negative. They are not negative, they are the thing that makes the inclusions meaningful.
Second, treat every out-of-scope request as a small, unemotional conversation rather than either a refusal or a silent absorption. "Happy to take that on, it sits outside what we scoped, so let me come back with what it involves" is a complete response and preserves the relationship entirely. Most clients respect this. The ones who do not are telling you something useful.
Pricing by outcome or by retained capacity rather than by hours removes some of this pressure, though it does not remove the need for a scope boundary. It changes what the boundary is drawn around.
Building pipeline while delivering
The feast and famine cycle is the defining operational problem of independent practice, and there is no clever solution, only a structural one.
Pipeline work has to be a standing commitment with the same status as client delivery, or it will not happen. This means a fixed weekly block, a small number of specific activities, and a target that gets reviewed like any other.
The activities that actually generate work for independent advisors are narrower than general marketing advice suggests. Former colleagues and former clients produce the majority of engagements for most practices. Systematic, unpushy contact with that network on a schedule outperforms almost anything else, and it is the first thing that stops when delivery gets busy.
Writing publicly about the specific problems you solve is the second. It works slowly, compounds over years, and is close to useless if done sporadically.
Referral partnerships with adjacent practitioners is the third, and the most underused. An operations consultant and a fractional CFO serving the same client profile will each encounter problems the other should handle several times a year.
Set a minimum: a fixed number of network conversations a month and a fixed publishing cadence, both small enough to survive a busy delivery period. Consistency at low volume beats intensity in gaps.
Capacity, and the number most practitioners avoid calculating
There is a calculation that independent practitioners tend to do once, dislike the answer, and never repeat.
A working year contains roughly 46 weeks after leave and public holidays. Of the available days, a realistic ceiling for client-facing delivery is around 60 to 70%, because the remainder goes to business development, administration, proposals, professional development and the unbillable thinking that makes the billable work good. Anyone planning on 90% utilisation is planning to work weekends, and eventually does.
That means the honest capacity of a full-time independent practice is something in the order of 130 to 150 delivery days a year. Your rate multiplied by that number is your realistic ceiling, and it is usually lower than the figure people carry in their heads when they leave permanent employment.
The number matters for three decisions.
It tells you whether your rate supports the income you need, which is a question better answered before taking on clients than after. Practitioners who underprice at the start find it considerably harder to correct later, because raising rates with existing clients is uncomfortable and raising them with new clients creates an awkward inconsistency.
It tells you how many concurrent engagements you can hold. If a typical engagement consumes two days a week, three concurrent clients is close to full, not the five that sounds achievable when each one is described as a small commitment.
And it tells you when to say no. The most expensive mistake in portfolio practice is accepting a fourth engagement at capacity, delivering three of the four adequately, and losing one of the good ones. Declining work is a capacity decision rather than a confidence one, and framing it that way makes it considerably easier to do.
The systems question
Most independent practitioners run their practice across a document folder per client, a calendar, a notes app and their inbox. This works at two clients and degrades from there.
The problem with the folder-per-client approach is not storage. It is that there is no view across engagements. You cannot see all open commitments in one place, all upcoming client decisions, or how each engagement is tracking against its objective. Every question that spans clients requires opening five things.
What is needed is not complex. A single place where each engagement has its objective, its measures, its open actions and its decisions, with a view that spans all of them. That is the difference between a practice you run and a set of engagements that run you.
Empiraa GPS is used this way by consultants and small advisory firms, with each client engagement carrying its own goals, measures and actions while the cross-client view stays in one place, which removes most of the reconstruction work before client calls.
Ending engagements properly
Every fractional engagement ends. The good ones end because the problem was solved and the client can now run it themselves, which is the outcome the whole model implies but which practitioners are quietly reluctant to bring about.
That reluctance is understandable and worth naming. An engagement that resolves itself removes revenue, and there is a persistent temptation to remain indispensable rather than to work yourself out of the role. Clients notice this, usually before it is admitted, and it damages the referrals that sustain independent practices.
The better economics run the other way. An engagement that concludes well, with a client who can point to a specific before and after, produces referrals for years. An engagement that drifted until the budget was cut produces nothing, regardless of how long it lasted.
Planning the ending from the beginning changes how the work is done. If the objective includes leaving behind a capability rather than a dependency, then documentation, training a successor and building the internal rhythm become part of the delivery rather than an afterthought in the final month.
The handover itself deserves proper attention. The decision log, the current state of the measures, the open commitments and an honest assessment of what remains unresolved should be handed over in a form the client can use without you. This takes a day and it is the difference between a client who remembers the engagement fondly and one who remembers the fortnight after it ended.
It is also worth staying in contact afterwards on a light schedule. A short message twice a year to a former sponsor costs nothing, and former clients moving to new companies is one of the more reliable sources of new engagements in this category.
What good looks like
A well-run portfolio practice has a few observable properties.
You can answer what is happening with any client in under two minutes without opening more than one thing. You know which engagements are up for renewal and what you will say. You have had a conversation about the engagement itself with every client in the last quarter. Your pipeline block happened every week last month, including the busy ones.
None of that is about being a better consultant. The advisory work is presumably already good, which is why the clients are there. It is about the difference between five engagements that each get your full attention and five engagements that each get an interrupted version of it.
The gap between those two states is almost entirely structural, and structural problems respond well to being treated as such.
