Running four engagements at once costs you the switch. Mail arrives in the order other people sent it. Each message asks you to put down one client’s world and pick up another’s before you can write a line. Group the writing by client and you pay that cost once per client instead of once per message.
- Reloading a client’s situation is the expensive part, and the reading is cheap. Ten threads from one client cost you less than four threads from four.
- Arrival order is the order somebody else’s day happened in. It suits their day, and it charges you a switch on every line.
- Attention follows noise. The engagement quietly going wrong is almost always the one you’ve heard least from.
- Every client bought the same thing, which is you rather than a team. Hold six well and none of them can tell there are six.
What it costs to hold four at once
Volume is the easy thing to measure, and it’s the small part of this. Four clients send you perhaps twice the mail of one. That mail is spread across four unrelated situations, and the spread is where your day goes.
Each live engagement is a state you hold before any of its mail makes sense. Where the work stands against what you promised. What you said on Tuesday’s call. Who Dan is and why he’s nervous about the second site. Which version of the model everyone has seen. What’s confidential, and to whom. Open a thread from a client you last touched nine days ago, and the message itself takes seconds to read. Rebuilding all of that from the surrounding threads is what takes the rest, and you do it before you can safely answer three lines.
Then the register multiplies. One engagement carries perhaps three open loops: something you owe them, something they owe you, something still undecided. Four engagements carry twelve, and each one asks for a different frame. Twelve items from one project make a to do list. Twelve items from four projects make four to do lists shuffled together. The shuffling is what makes twelve feel unmanageable at a number that ought to be trivial.
There’s a quieter cost that rarely gets a number put on it, and it’s the voice. Each client has a register you’ve settled into. A set of first names, a level of formality, an internal politics you’re careful about. Carrying one of those is free. Carrying six is where the errors in the second half of this guide come from. It’s why a Friday afternoon reply to your fourth client of the day reads slightly wrong even when everything in it is correct.
Underneath all of it sits the promise. A client hires an independent partly on the assumption that they’re one of a few rather than one account among forty. Undivided attention goes to one client at a time, for you and for anybody else they might have hired. Aiming past that is aiming at the wrong standard. The achievable one is narrower and far more useful. Your handling of any one client keeps quiet about how many others there are. Every delay reaches them as a warning in advance. Every reply arrives with that client’s own context in it. And every week holds some contact, however loud somebody else’s bad Tuesday was.
Work one client at a time
Deciding what a message needs and writing the reply are two different jobs, run at two different speeds. That case is argued at the front of this collection, and it’s worth having in place first. What belongs here is the question that appears once you have several clients. What order does the writing run in?
The default order is arrival, and arrival interleaves your clients at random. Hartley at 9:10, Renwick at 9:12, Hartley again at 9:40, an admin thread, then Renwick’s finance team. Worked top to bottom, that morning charges you five reloads for five messages. Two of those reloads are for a client you already loaded twenty minutes earlier.
So group the writing by client and finish one before you start the next. Everything Hartley needs, in one sitting, with Hartley’s whole situation in your head. Then close it and open the next. A message from Renwick that arrived at nine waits until eleven. That sounds like worse service and it’s almost always better, because the eleven o’clock reply comes from somebody holding the full picture rather than somebody halfway between two clients.
Three things improve immediately, and speed is only the first.
You stop contradicting yourself. Answer three Hartley threads two hours apart and you can easily agree a date in one that clashes with a commitment you made in another. Answer them together and the clash shows up before you send.
You stop repeating yourself. Two or three people at the same client often ask overlapping questions in separate threads. Handled separately they get three slightly different answers, and that’s how a client ends up believing two incompatible things about your work. Handled together, one of the replies says what the others said and copies the right people.
And the writing gets better in the way that actually matters commercially. A considered reply is a good part of what a consultant is paid for, and considered replies come from sitting inside one client’s situation rather than between two.
Two boundaries on the rule. Anything genuinely blocking crosses it, and the test for that is narrow: somebody else is stuck on their own work today until you answer. Being waited on is a different thing, and so is it’s been a while. Stuck today. Everything else holds until its client’s turn.
The second is sizing. A client block is twenty to forty minutes of mail. If clearing a client takes three hours, what’s in there is delivery work that arrived in the mailbox. It belongs in a delivery slot rather than in a morning pass with four other clients queuing behind it.
The line you keep on each engagement
Working by client pays off when you can load a client quickly. Loading runs slow because the state of an engagement lives scattered across its own threads. So write it down once, per engagement, and keep the lines together.
The update you send the client is a separate thing. That one is outbound, written for them, and this collection takes its shape and its length separately. What belongs here is a private note, four or five lines. Its job is to get you from cold to working in about ten seconds.
What earns its place:
Where it stands, in one clause. Keep it to the length of this. Draft with the steering group, readout on the fourteenth.
What you owe them next, and the date you gave. The date matters more than the deliverable. It’s the thing you’ll otherwise misremember in a way that flatters you.
What you’re waiting on, from whom, since when. One line each. A decision sitting inside somebody else’s organization stays silent in your inbox, so write it down the moment you ask. This collection takes the stalled approval as a subject of its own.
When they next hear from you. Give every engagement a next contact date, including the weeks when nothing is due. That date is your defense against the drift described further down.
The two or three facts you’d otherwise reconstruct. Who the sponsor is. Who’s difficult and about what. What you’ve quietly absorbed and left off the invoice. A recorded free half day is worth something to you three weeks later, when something larger has to be priced.
The last of those is the one people leave out and the one that pays. Your client-facing record and your own commercial position are two different documents, and only one of them belongs in a note you could forward.
What matters is that all of them live in the same place, side by side, on one screen. Keep them in one file rather than one per client. The whole return on this habit is reading five engagements next to each other and seeing that two of them have their heavy two weeks in November. Write it at the end of each client’s block. It costs about thirty seconds, and it’s the difference between a Monday morning that starts with a plan and one that starts with an hour of reading.
When two clients want the same Tuesday
Ranking inside one client is easy, because everything measures against the same piece of work. Ranking across clients is genuinely hard, and it’s hard for a real reason. You’re missing a common unit. Hartley’s workshop pack and Renwick’s board paper sit on different scales, and staring at the inbox leaves them there.
Three questions produce a comparison, asked in this order.
Who is blocked. A person stuck on their own work until you answer outranks work that’s sitting there quietly, however important that second thing is. Being the blocker is the most expensive position available to you. The cost lands on somebody else’s day, and it gets talked about in rooms you’re absent from.
Whose date is it. A date set by the client’s own machinery holds for you and for everybody. A board sitting on the ninth, a regulatory return, a system going live. A date you invented can move, at a cost you can calculate and explain in one sentence. When two dates collide, move yours. That feels like the wrong way round, and your date was always the flexible one. Being flexible is what made it useful.
Is it recoverable. A draft a day late is repaired by a sentence sent in advance. A missed monthly committee is repaired in four weeks. Weight the unrecoverable thing even when it’s smaller.
Three things stay off the list. How loudly the client is asking, since the one who writes four times a day has trained you and the training carries no information about which work matters. How much you like them. And, on any given Tuesday, the size of the fee, because the largest client usually has the most internal slack.
When both genuinely have to give, one of them hears from you today. Doing both badly is the expensive alternative. Pick the client whose date is yours rather than the one you mind least, and send a new date rather than an apology. That’s a scheduling fact and clients absorb it easily. The same information arriving on the morning the thing was due is something else entirely, and it costs you a great deal more than the day did.
How many you can actually hold
Hours are the wrong unit, which is why the arithmetic people do in a spreadsheet always says yes to one more.
The binding constraint is the number of engagements with a live decision front. Those are the clients with meetings on the calendar, stakeholders with opinions, and something waiting on a yes. An engagement in that phase takes a meeting or two a week, an update, and a handful of unpredictable interruptions. It takes a share of your attention on the days you spend elsewhere, too. An engagement in a drafting phase takes long quiet blocks and almost no mail. An engagement in its final month takes hardly anything until the last two weeks, when it takes everything.
So count contact days rather than fee days. Most independents find the ceiling at two or three engagements at full intensity, or one heavy alongside three light ones. The honest test is the number of separate client meetings in a normal week. Past about six, your unbroken blocks are gone, and the thinking a client is actually paying for needs more than the forty minutes between two calls.
The failure mode is collision. Heavy phases land on top of each other. Two engagements sold three weeks apart will want their kickoff, their stakeholder round and their final readout in more or less the same two weeks. Engagements share a shape, and the shape is what stacks. Control that at the sale rather than in delivery, and the only variable you hold is the start date. Pushing a start by two weeks is an ordinary professional request. Clients accept it far more readily than a deliverable arriving late from a consultant who said yes to everything. What the calendar does in the gaps between engagements is a separate question, and another guide here answers it.
One number worth keeping honestly: how many clients you’ve promised same day replies to. That promise is cheap to make with two live engagements and expensive with five. Revisit it when you take on the fourth, rather than on the day it breaks.
The quiet client is the one to check
Attention goes to whoever asks for it, so the engagement sending the least mail gets the least of you. That’s exactly backwards. A client who has gone quiet usually has something to say.
Silence from an engagement usually means one of five things. Their sponsor has lost interest or lost an argument. Somebody internal is unhappy and has taken it to your contact rather than to you. The work has stalled on their side, and reporting that is a job everybody is avoiding. The people you need got pulled onto something else. Or these two weeks are genuinely quiet, which is fine, and which you’d still rather know than assume.
Only the last of those is harmless, and all five stay quiet by nature. Meanwhile the practical effect compounds, because a quiet client is also the one you stop writing to. Two months of thin contact is how an engagement loses the second phase it was heading for.
The habit that catches it takes ten seconds a week, and it asks a different question from the one you normally ask. Instead of which client needs me, ask which client have I not thought about. Whichever name you have to work at remembering is the one to open.
There’s a sharper version of the same check, and it’s the most useful mechanical trick in this guide. Look at your sent items rather than your inbox. The inbox tells you who’s chasing you, which you already knew. The sent folder tells you who you’ve stopped talking to, and a mailbox reports arrivals rather than absences. Sorted by recipient across two weeks, it shows you a client you last wrote to on the eleventh. That fact lives nowhere else.
Keeping them from bleeding into each other
The mistakes that actually happen are mechanical rather than conceptual. Take them in order of what they cost.
The wrong recipient. Autocomplete offers you the Dan you wrote to yesterday rather than the Dan you meant, and a client’s material lands at another company. This one has no repair, because a message already delivered to another company’s server stays there. A habit fixes it rather than a warning. Write the message first and fill in the recipient last, so addressing is a deliberate act rather than the thing you did before you started thinking. Then read the To line rather than the display name on anything carrying an attachment.
The forwarded chain. You forward a genuinely useful thread and everything beneath it travels too. The fee, a paragraph about another client, a candid line about somebody’s boss. People read to the top of what they forward and send the rest blind. The rule is simple and absolute. Where a thread would need trimming, paste the part that matters into a new message and send that instead.
The wrong attachment. Three files called report v4 final in a downloads folder is a matter of time. Put the client’s name first in every file name you create, always, including drafts. It’s free, and it’s the one naming convention that survives being in a hurry.
Reply all on a thread that gained a person. New names appear on client threads quietly, and a new name often means a director, procurement, or somebody’s counterpart at another supplier is reading now. Check the recipient list before you reply into any thread you’ve left alone for a week.
The example. Using one client’s situation to illustrate a point in another client’s room is the one deliberate item here, and it’s the one that costs a reference. Dropping the name does very little, since sector plus rough size plus the specific problem identifies a company to anybody working in that market. The test is whether they’d recognize themselves.
Underneath the mechanics sits an obligation most consultants have actually signed. A confidentiality agreement usually goes further than telling people, and says something about who else may hold the material. That becomes a live question the moment any software reads your mailbox on your behalf. That’s worth settling deliberately rather than at four o’clock on a Thursday, and what a confidentiality obligation means for an AI inbox sets out the questions worth putting to a supplier in writing.
It’s also worth being straight about what separation software gives you, because the marketing in this category tends to overstate it. What genuinely exists is separation between whole businesses that you run, which is a line in a different place. A wall between one client and another inside a single working life is the thing no product on the market provides, and a product promising you that is describing something else. Day to day, the five habits above are what prevents these errors, along with working one client at a time rather than jumping between them.
A week with five clients in it
Five engagements need one week with a shape, and four decisions make it.
Give each client an anchor day. Renwick on Wednesday, Hartley on Tuesday and Thursday. Anything urgent still crosses, so the day stays soft. When Renwick’s mail lands on Monday you know exactly when it’s answered, which settles the small decision you were otherwise making twelve times a day about whether now is the moment. Tell the client the day, too. A client who knows Wednesday is theirs stops wondering on Monday.
Keep a short pass across everything, daily. Ten minutes, reading only, and open as little as you can. One question: is there anything here that has to break today’s plan. Nine mornings in ten the answer is no, and the value is that you now know it rather than suspect it. Skimming a full inbox in minutes is the skill this pass runs on.
Spread the updates. The case for Thursday, and for sending on the same day whether or not anything happened, is made properly in this collection’s guide to the weekly update. With five clients the constraint changes shape. Five updates written on one afternoon is a bad afternoon. Worse than that, five sets of requests leave at once and their answers all come back inside the same day. That’s the day you have least room to act on them. Spread them across Tuesday to Thursday, two, two and one. Then each client’s replies arrive in a week that still has space in it.
Defend one unbroken block. With several engagements the first thing to disappear is the long stretch. Every client can make a reasonable case for forty minutes, and each of them is asking for forty minutes rather than for your Tuesday morning. The deliverable gets written well in the long stretch and nowhere else. Put it on the calendar with a name on it and treat it like a client appointment, since that’s what it is.
Two smaller things. Leave a gap between two different clients booked back to back. The ten minutes after a client meeting belong to the meeting, which is argued in this collection’s guide to follow up notes, and with several clients that gap is doing a second job as well, which is unloading one engagement before you load the next. Fifteen minutes is enough for both.
And find a quiet slot at the end of the week to read the engagement lines side by side. Fifteen minutes, all five at once. This is where the quiet client shows up. It’s where you notice two heavy two-week stretches about to land on top of each other. And it’s where next week’s anchor days get adjusted while adjusting them is still free.
What Point holds when there are six
The judgment here stays exactly where it is. Which client comes first on a colliding Tuesday. How many engagements you can carry. What you’ll absorb and leave off the invoice. What you tell a client whose date has to move. Those are the job, and they stay yours. What moves is the reloading, which is where the day actually went.
The reading comes first, because with several clients it’s the largest cost. Each thread turns up with a line saying what it is already on it. A pass across a morning tells you which engagement each thread belongs to and roughly what it wants. You learn that before you open anything and have to become that part of your business. That’s what makes the short daily pass across five clients a ten minute job rather than an hour.
Everything is also weighed before it reaches you, and weighed twice. What a thing is worth is scored separately from how soon it needs an answer. Treating those as two measurements rather than one keeps a loud client’s volume off the top of a quiet client’s genuinely blocking question. You can mark the people who count as well, so a message rises on who sent it rather than on how it happens to be worded.
Then the separation you actually use day to day. Mail is placed into the part of your working life it belongs to. Turn the weight up on the area that needs you these two weeks, and its threads rise while the rest wait quietly. You can also look at one area on its own, which is the closest thing there is to sitting down with a single client and a clear desk. The stricter line, where one thing genuinely stays invisible to another, follows a business you operate rather than a client inside one, and that’s deliberate. A fair part of the value here is seeing that Hartley has been in touch three times since Monday, and a per client wall would take that away.
The engagement lines are the part you stop having to remember. When a message asks something of you, it becomes a dated item with its conversation still attached. The questions you sent out are held the same way, as things owed to you, returning on a date you set rather than whenever they next cross your mind. Those gather into a single list that spans every conversation and every business you run. That’s the twelve item register from the start of this guide, assembled while you were doing something else. You can leave a standing request in plain words too, one per engagement. Tell me when Hartley’s signed order arrives. Tell me when anyone at Renwick replies on the phasing note. A standing watch reaches you once, on the morning it fires, and stays quiet on the mornings it doesn’t.
Some of the rest is small and adds up across five clients. A short briefing gathers what needs you today. You decide what’s worth an interruption and what waits for it, which is how a talkative client stops setting the pace of your afternoon. Replies arrive already in your own way of putting things, ready to adjust or send. Where a session has to go on the calendar, Point runs the offer and counter offer itself, working from calendars already reconciled. So five clients wanting time in the same two weeks stays one piece of work rather than five threads of proposed windows. Search works off what you remember about a thing rather than its exact wording, which is what you have when the client is right and the phrasing is nine months old. And duplicate contacts are merged, so the two entries for the same person at the same client stop feeding autocomplete the wrong one.
How far Point goes on its own is a setting held per kind of action. It runs from suggest only, through the position where something is prepared and then waits, up to Point handling that kind of task by itself. Review is where each of them starts. Acknowledging a client and offering two times is a reasonable candidate for moving up, once you’ve watched it happen enough. Keep a substantive reply to a client on review. Anything done on your behalf appears in a log, timed, and most of those entries can be reversed from where they’re recorded. The one exception is the one this whole subject keeps running into. A message already sitting on another company’s server stays there.
Everything stays where it is. Whatever mailbox the practice runs on now, Google or Microsoft 365, is the one Point sits over. The address five clients already write to is the address they keep writing to.
Point works on the mailbox rather than on the portfolio. Point has never seen your fees or your schedule, so a plan, a utilization figure, a view of which engagement is more profitable and a warning that two heavy phases are three weeks from colliding all live somewhere else. If the question you’re stuck on is whether there’s room for a sixth client in November, buy project and resource software, because that’s the question it was built for. If the question is which of five clients needs something before lunch and what you last promised the other four, the answer is in the mailbox, and the mailbox is what this guide has been about. Everything Point does is listed on the benefits page, Point for consultants argues it through a practice, and Point sets out the product.
Common questions
How many clients can one consultant manage at once?
Count engagements with a live decision front rather than counting clients or hours. A client with meetings on the calendar, stakeholders with views and something waiting on a yes takes a meeting or two a week, an update, and unpredictable interruptions. That’s all before any of the work you’re paid for happens. A client in a drafting phase takes long quiet blocks and almost no mail. Most independents find the ceiling at two or three at full intensity, or one heavy alongside three light ones. The practical test is the number of separate client meetings in a normal week. Past about six your unbroken blocks are gone, and the thinking has nowhere to happen.
Should I use a separate email address or inbox for each client?
One inbox usually serves you better, and it’s worth knowing why before you set up four. Separate mailboxes move the switching cost rather than removing it. You check four places instead of one. A reply can still reach the wrong company, because the mailbox you wrote it in has no say in where it lands. Four mailboxes also give up the one genuine advantage of a single queue, which is seeing across all five engagements at once and spotting which of them has gone quiet. Two exceptions are real. A client who requires you to work from an account on their own domain, which is their decision rather than a filing choice. And a genuinely separate business you run, which is a different line entirely and the one place where hard separation belongs.
How do I stop mixing up clients in emails?
Five habits do nearly all of it, and every one of them is a habit rather than a setting. Write the message before you fill in the recipient, so addressing is deliberate. Read the To line on anything with an attachment. Where a chain would need trimming, paste the useful part into a new message and send that instead. Put the client’s name first in every file name. And check the recipient list on any thread you’ve left alone for a week, since names get added quietly. Working one client at a time rather than jumping between them removes most of the remaining risk, because almost every mix up happens in the second or third switch of a morning.
One client is taking all my attention. What should I do?
Separate two questions that feel like one. The first is whether this client is genuinely heavier than the others right now. If so, the fix is scheduling. Give the others fixed days that survive, and protect one unbroken block for delivery. The second is whether the work has grown beyond what you agreed, which is usually what turns out to be true when one engagement swallows a practice. That’s a different repair entirely. Spotting a change to the agreed work and putting a price on it the same day, instead of quietly absorbing it, has a guide to itself in this collection. Either way, the client worth looking at is probably one of the others. It’s whichever of them you last thought about two weeks ago.
Two clients need me on the same day. Who comes first?
Ask three questions in order. Is anybody blocked, meaning somebody is stuck on their own work today until you answer. Whose date is it, since a date the client’s own machinery set holds and a date you invented moves. And is it recoverable, because a draft a day late is repaired by a sentence and a missed monthly committee is repaired in four weeks. Then, having decided, tell the other client today with a new date attached, so it reaches them ahead of the morning the thing was due. Early, that information is cheap. Late, it costs you a great deal, and the difference is the whole of what a client means when they say somebody is easy to work with.
The short version
Several engagements at once is a switching problem rather than a volume problem. The expensive part is rebuilding a client’s situation in your head, and arrival order makes you do it on every line. Group the writing by client and finish one before you open the next, letting only genuinely blocking work cross. Keep four or five private lines per engagement, all of them on one screen. They hold where it stands, what you owe and when, what you’re waiting on, when they next hear from you, and the commercial facts you’d keep out of a client note. When two clients collide, decide on who is blocked, whose date it is and what is recoverable. Then tell the loser today, with a new date. Count contact days rather than hours when you decide whether to take a sixth, and control the collisions at the start date rather than in delivery. Check the client you last thought about two weeks ago, using your sent items rather than your inbox, because a mailbox reports arrivals rather than absences. Give each client an anchor day, spread the updates across the week, and defend one unbroken block. The inquiry that started all this, the scope quietly growing inside one of them, the approval nobody will give and the hours disappearing into the whole arrangement are each taken up on their own by the other guides here. And the piece at the front of this collection takes the practice as a whole.