The hardest part of running an independent consulting practice is not winning the work. It is holding four engagements in your head at once while the fifth prospect asks whether you have capacity next month. Every independent consultant eventually hits the same wall. The practice grows to the point where the work is good, the pipeline is reasonable and the revenue is fine, and yet everything runs on memory and goodwill. You know what Client A is waiting on because you spoke to them Tuesday. You know Client C's deliverable is late because it has been bothering you since Sunday. The system is you, and it works right up until you take a week off or add a fifth client. This has become a more common problem rather than a less common one, because the market for independent and fractional expertise has grown substantially. Various market analyses put the fractional executive space in the billions and growing at double-digit rates, with estimates of practitioner numbers roughly doubling in the space of a few years. The specific figures vary by source and definition, and most come from firms with an interest in the category looking large, so treat them loosely. The direction is not really in question: more experienced operators are working across multiple clients rather than inside one. What has not kept pace is the operational side. Most independent practices are run with a calendar, an inbox, a folder structure and a spreadsheet that is either out of date or maintained heroically. That is enough for two clients. It is not enough for five.
The four things that actually break
It helps to be specific about what fails, because "get organised" is not a useful instruction and buying a project management tool rarely fixes it. The first thing to break is the promise you cannot remember making. Consulting engagements generate small commitments constantly. You said you would send the benchmark data. You agreed to look at the pricing model before the next session. You offered to introduce them to someone. Individually these are trivial. Collectively, across four clients, they are the majority of what determines whether a client feels well served. And they live in your memory and in the middle of meeting notes, which means some proportion of them quietly do not happen. The second thing to break is the sense of whether an engagement is on track. A three-month engagement has a shape: an assessment phase, a recommendation, an implementation, a handover. Halfway through, it is surprisingly easy to be busy on a client without being able to say whether the engagement is where it should be. The work is happening. Whether the work is the work you scoped is a separate question, and it is the question that determines whether the client renews. The third is capacity. Independent consultants routinely make capacity decisions badly, and not through carelessness. It is genuinely difficult to know whether you have room for a new engagement when your existing commitments are expressed as a set of meetings in a calendar rather than as hours of work with delivery dates. The result is the familiar pattern of a comfortable month followed by a month where three clients need something significant in the same fortnight. The fourth is the pipeline, which suffers whenever delivery is busy. This is the structural weakness of solo practice and no amount of discipline entirely fixes it. When you are delivering well, you are not selling, and eight weeks later the pipeline is empty. Then you sell hard, win three engagements, and stop selling again. The revenue chart of most independent practices is a sine wave, and the wave is caused by the operating model rather than the market.
Treating each engagement as its own small plan
The useful mental shift is to stop thinking of client work as a list of tasks and start thinking of each engagement as a small strategy with its own outcomes, measures and review cadence. This sounds like more overhead than it is. For each engagement, you need to be able to answer four questions: what outcome did we agree, what does progress look like at the halfway point, what am I waiting on from them, and what are they waiting on from me. Four answers per client, reviewed weekly. The value of writing the outcome down is not documentation. It is that it makes drift visible. Scope creep in consulting rarely arrives as a formal request. It arrives as a series of reasonable adjacent asks, each of which takes an hour, and by week six you are doing work that was not scoped while the work that was scoped is behind. If the agreed outcome is written somewhere you look weekly, that becomes obvious in week two rather than week eight. The halfway measure matters for the same reason it matters in any plan. If the only checkpoint is the final deliverable, the status is a guess until it is a fact. Defining something observable at the midpoint, even loosely, converts a three-month engagement from a single bet into two. The two "waiting on" questions are the ones consultants most often skip and most often need. A surprising proportion of engagements that feel stalled are stalled on something the client owes you, and a surprising proportion of client dissatisfaction comes from something you owe them that has slipped past the point where they stopped mentioning it. Both are cheap to fix and both are invisible unless you have a place they are recorded.
The weekly review that holds it together
The practice that makes the most difference is unglamorous: a scheduled block each week, ideally the same time, where you go through every active engagement in order and update those four answers. For four clients this takes about thirty minutes. It is the highest-value half hour in an independent consulting week and it is the first thing to be dropped when the week gets busy, which is the central discipline problem of solo practice. What makes it work is doing it engagement by engagement rather than by task. A task list mixes everything together, so you process by urgency and the quiet engagement gets no attention until it becomes loud. Going client by client forces you to look at the ones that are not currently demanding anything, which is where the renewal risk usually sits. Two additions make the review considerably more useful. First, note anything you promised in the last week, from wherever it was said, and put it in the same place as the scoped work. Second, look at the next fortnight across all engagements together, not client by client, because that is the only way collision becomes visible before it happens. The pipeline gets a slot in the same session. Not a full business development exercise, just fifteen minutes on the shortlist: who is in conversation, what the next step is, and what one action you will take this week. Fifteen minutes weekly, sustained, produces a considerably flatter revenue curve than a scramble every quarter, because the work compounds and the relationships stay warm. Empiraa GPS was built for exactly this shape of problem, keeping outcomes, measures and actions connected so the status of each engagement is visible without reconstructing it from notes. For consultants specifically the useful property is being able to run several plans side by side, one per client, and see them together. It is built for consultants running multiple client plans without losing sight of each engagement. You can review the full set of GPS features when designing the practice workflow.
Client-facing visibility, and why it changes the relationship
There is a second-order benefit to running engagements this way that is worth stating plainly. When you have a clear record of the agreed outcome, current status and open items, you can show it to the client. Most independent consultants do not, partly out of habit and partly out of a worry that visible status creates scrutiny. In practice it does the opposite. The clients who become difficult are usually the ones who are uncertain about progress, and uncertainty in the absence of information tends to resolve pessimistically. A short, honest status view removes the uncertainty and with it most of the friction. It also changes the renewal conversation from a sales conversation into a continuation of an existing discussion. If a client has seen the outcome, the measures and the progress against them every fortnight for three months, the question of what happens next arises naturally out of the work. Consultants who only surface progress at the end of an engagement have to sell the next one from a standing start. The other advantage is that it surfaces the client's own contribution. A visible list of what you are waiting on from them is a far more comfortable way to chase than an email asking again, and it accurately distributes responsibility for the timeline, which protects you when a delay was not yours.
The repeatability question
Once three or four engagements have run through the same structure, something useful becomes available: you can see which parts of your delivery are identical every time. Most independent consultants deliver more repeatable work than they believe. The client context differs, the findings differ, the recommendations differ. But the assessment structure, the questions asked in week one, the format of the interim readout, the shape of the final recommendation and the handover process are often close to identical across engagements in the same service line. Consultants tend not to notice because each engagement feels bespoke while you are inside it. Identifying the repeatable parts is worth doing for two reasons. The obvious one is time. If the week-one discovery structure is the same every time, writing it down once removes an afternoon of reinvention per engagement and, more importantly, removes the risk of forgetting a question you always ask. The less obvious reason is pricing. Work that is genuinely bespoke is difficult to price except by the hour, because you cannot predict the effort. Work that is repeatable can be priced as a defined piece with a defined outcome, which is better for the client and considerably better for you, since the entire upside of getting faster at something accrues to whoever bears the delivery risk. A consultant billing hourly for work they have done fifteen times is paying themselves less each time they improve. The practical approach is to keep a template for each recurring engagement type and update it at the end of every engagement rather than trying to design it in advance. After the fourth run, the template is genuinely good, and it was built as a byproduct of work you were doing anyway.
Closing an engagement properly
The end of an engagement is the most commonly mishandled part of independent practice, and it is where the most value is left behind. The typical pattern is that delivery finishes, the final document is sent, there is a positive conversation, and then contact tapers off. Three months later the consultant has no idea whether the recommendations were implemented, the client has drifted, and the relationship that took four months to build is dormant. A structured close changes the economics of the whole practice, because the cheapest engagement you will ever win is the second one with an existing client. Three things are worth building into it. The first is a handover that names who owns what after you leave. Recommendations that are not assigned to a person with a date do not get implemented, and an unimplemented recommendation reflects on you regardless of the quality of the analysis. Writing the ownership down is a small act that materially improves the odds your work survives contact with the client's normal operations. The second is a scheduled check-in, agreed before you leave, typically six to eight weeks out. Not a sales call. A short conversation about how the implementation is going. It costs half an hour, it produces the information you need to know whether your recommendations actually work, and it is the natural setting for the next engagement to come up without anyone selling. The third is a written record of what the engagement achieved against what was agreed. This is your evidence base. Independent consultants routinely struggle to describe their results concretely in proposals, not because the results were poor but because nobody wrote them down at the time and reconstructing them a year later is impossible. Ten minutes at the close of each engagement builds the asset that makes every future proposal easier. The commercial mechanics that quietly determine whether the practice works Two operational details sit outside delivery but affect an independent practice more than most consultants expect. The first is payment terms and invoicing discipline. A solo practice has no finance function, which means invoicing is a task competing with delivery, and delivery always wins. The result is invoices going out late, then payment terms running from the late date, then a cash gap that has nothing to do with how much work you won. Invoicing on a fixed day each month, regardless of where engagements are up to, removes this entirely. Milestone-based invoicing with a deposit at the start is better again, because it aligns cash with the work rather than trailing it by six weeks. The second is what happens when scope changes. Every engagement produces adjacent requests, and the reflex for most independents is to absorb them, because the relationship matters and the individual ask is small. This is usually the right call once and the wrong call the fourth time. The workable middle position is to record the adjacent asks as they arrive, note them in the fortnightly status conversation, and raise the cumulative picture rather than pushing back on any individual request. Framed as "here are six things that have come up outside the original scope, which of these matter most", it becomes a prioritisation conversation rather than a billing dispute. That framing is only available if somebody wrote them down as they happened. There is a related discipline about the free advice that occurs in conversation. Independent consultants give away a considerable amount of genuinely valuable thinking in unbilled calls, and some of that is correct practice because it builds trust and wins work. The problem is when it becomes the delivery mechanism, and the signal that it has is when a client stops booking scoped work but keeps asking questions. Noticing that pattern requires only that you know how much unbilled time each client is consuming, which brings it back to having a record rather than a memory.
Deciding whether to take the next engagement
Capacity decisions get much easier once engagements are expressed as commitments with dates rather than meetings in a calendar. The mistake most consultants make is assessing capacity against average load. The month looks fine on average, so the answer is yes. But delivery work is not evenly distributed. Each engagement has peaks, usually around a deliverable or a workshop, and the question that matters is whether the new engagement's peaks collide with existing ones. Looking at the next twelve weeks with each engagement's heavy periods marked answers this in about five minutes and prevents the most common cause of quality problems in independent practice, which is not incompetence but three peaks in one fortnight. There is also a pricing consequence worth noticing. When you can see genuine scarcity in a specific window, you have a defensible reason to price a rush engagement differently or to propose a later start. Consultants without visibility into their own capacity tend to either decline good work unnecessarily or accept it and absorb the cost personally in evenings.
What to do if you are starting from nothing
If your practice currently runs on memory, the temptation is to design a full system. Do not. Start with a single sheet listing your active engagements, and for each one the agreed outcome, the next milestone with a date, what you owe them and what they owe you. Fill it in for every current client. This takes about an hour and the exercise itself usually reveals two or three things that had slipped, which is the immediate return. Then book the weekly review in your calendar as a recurring commitment and treat it as a client meeting. It is the one you will most want to cancel and the one with the highest return on being kept. Add the pipeline slot in week three, once the review habit exists. Add anything else only when you feel the specific absence of it. Systems built in response to a felt problem survive. Systems built in anticipation of one get abandoned in the first busy month, which is the fate of most consulting practice management projects. The goal is not an impressive operating system. It is being able to answer, without thinking hard, where each engagement stands and whether you have room for the next one. Everything else is optional.
