Four clients in one day: what the switches cost in hours

An unpaid hour. You billed eight hours at 90. You sat down four times. Three of those sits were twenty minutes of closing the last file and finding the next one. That hour was never on a calendar, and it is the whole gap between 90 and an 80 floor. Four clients in one day is not a full day of work. It is eight billed hours plus the hops nobody booked.

What is a client switch, counted in hours?

It is the sitting between one client’s work and the next client’s work.

You save the file. You find the other project. You remember where you were: the open thread, the last comment, the password that expired since Tuesday. Then you start.

Your own minutes will differ. The shape will not. The minutes do not shrink when the block is two hours instead of eight, and they do not disappear because the billed total for the day still says 8. A day with one client has zero of them. A day with four clients, in four blocks, has three.

This is not the hour around a small job. That hour is brief, reopen, handover, invoice, and it happens even if you only have one client that day. A switch is a hop inside a day of otherwise full-size work. You would happily bill each block. Nobody billed the corridor between them.

It is also not the sentence in the day-rate guide that a focused day for one client is worth a premium because eight focused hours beat eight scattered ones. That sentence is true and it is never multiplied. This page is the division.

Why does a four-client day land on the floor?

Because the day’s fee does not move when the sitting does. The arithmetic is the same division as always: what the day paid, over every hour it took.

Take 8 billed hours at 90, a floor of 80, and 20 minutes per switch. Twenty minutes is an example you replace with your own, not an average.

Clients	Switches	Sitting	Effective rate
1	0	8.0	90
2	1	8.3	86
4	3	9.0	80
6	5	9.7	74

Every invoice in that table says 90, and every invoice is correct. Nothing about the work went wrong. The gap is entirely the sitting between clients, and those minutes are invisible unless you write them down.

Call the number a switch tax: minutes to close one client and open the next, times the switches in the day. Four clients, three switches, 20 minutes each: 720 over 9 hours is 80. The fourth client is the one that lands you on the floor.

Is batching the same four clients enough?

It is the whole difference between 80 and 70.

A day with four clients is not one number. It depends on how often you hop.

Four blocks, one per client: three switches. 720 over 9 hours is 80.

The same four clients, a different one every hour: seven switches. 7 × 20 minutes is 140 minutes. 720 over 10.3 hours is 70.

The clients did not change. The hops did. This is why “I had four clients today” is the wrong count. Count the switches. A calendar that names four clients and jumps seven times is not a four-client day.

Batching does not require turning anyone down. It requires finishing one block before opening the next. Slack still arrives. The rule is that Slack from client B waits until the block for client B, or it becomes a switch you chose.

If the day is sold as presence for one client, that is a day rate, and the premium is exactly this: zero switches. Mixing a day rate with three other clients in the gaps is how you sell the premium and then spend it.

What to do with tomorrow’s calendar

Count the hops, not the names. Open tomorrow. Every time the client changes is a switch, including the hop back to someone you already touched. Four names and seven hops is seven.

One block per client. The same four clients in four blocks cost three switches. That is the cheapest version of a four-client day, and it is usually available. Ping-ponging them is a choice that looks like being responsive and pays 70.

Stop the timer when you leave. If it keeps running, the next client pays for the last one’s leftover context, and which client is profitable is reading a lie. The sitting still happened. It just landed on the wrong person.

Log the gap as sitting, not as admin. A general admin bucket spreads the hour across every client until nobody can see it. Non-billable time on an overhead project, or on the day, keeps it in utilization where it belongs. Your own 20 minutes may be 12, or 35. Time the next three hops and replace the example.

The multi-client tracking habit of starting a timer when you start and stopping it when you switch is the mechanical half of this. The arithmetic half is dividing the day’s fee by billed hours plus the sitting those stops created.

Where CronLoom comes in

CronLoom has no context-switch feature and no day as a unit of sale. What it has is the division.

Stop the timer when you leave a client so the next block starts clean. Log the gap as non-billable time. Per-client effective rate in analytics is billed revenue over every completed hour, billable or not, drawn against the floor you set. Utilization is the billed share of the sitting. A day that billed 8 and sat 9 shows up in both places, which is the point.

The effective hourly rate calculator does the single division by hand: what the day billed, over the hours you sat. If you want the number running per client while the hops happen, join the waiting list.

Open tomorrow

Count the times the client changes. Multiply by the minutes a hop actually takes you. Add that to the hours you already plan to bill, and divide the day’s fee by the total.

That is what a four-client day pays you right now. The names on the calendar do not decide it. The hops do.