A three-day work week is a design outcome, not a productivity hack
A three-day week is what happens when a consulting business is built to hold at lower volume. It is not a reward for getting faster, batching your emails or finding the right app.
That distinction matters, because most advice on working less is really advice on working the same amount in less time. Compress the calendar, automate the admin, wake up earlier. That approach can buy you back a few hours. It cannot buy you back two days, because the two days are being consumed by decisions you made about pricing, clients and scope — often years ago, often without noticing.
So the honest version of this article is not a productivity list. It is a design brief. If you want a three-day delivery week in a consulting or advisory practice, four things have to be true at once:
- Your pricing holds at lower volume.
- Your client base fits the shape of the week you want.
- Your boundaries are set at the start of an engagement, not defended in the middle of one.
- Your systems carry the days you are not working.
Miss one and the week collapses back. Most people who try this and fail did not lack discipline. They had three of the four.
What a three-day work week actually asks of consultants
Start with the arithmetic, because it is the part people skip.
A three-day week is not 60% of a five-day week. Delivery days are not interchangeable units. In a five-day practice, days four and five are usually where the invisible work lives — proposals, follow-ups, admin, the client who needs a quick call, the half-finished thing you meant to systemise. Cut those days without moving that work somewhere else and it simply migrates into your three days, pushing delivery out, which pushes revenue out, which pulls you back to five days by the end of the quarter.
This is why the three-day week is a structural question. You are not removing two days of work. You are removing two days of capacity and then deciding, deliberately, what no longer happens.
The Company of One philosophy we work from at The IC starts from the same place: growth is a choice, not a default. Before you add headcount, add hours or add another retainer, you ask whether it moves you closer to the business you actually want. Sometimes the answer is yes. Often it is not — and the businesses that stay small on purpose are the ones with the most room to design their weeks.
A three-day week also asks you to be specific about what the three days are for. "Three days of work" is vague enough to be meaningless. Three days of client-facing delivery, with everything else fitted inside them, is a constraint you can build against. Say you run a two-day-a-week advisory practice with a third day for your own business: that is a different design problem to three delivery days and no internal day at all. Name which one you are building.
Condition one: pricing that holds at lower volume
If your pricing only works at full capacity, you do not have a pricing model. You have a treadmill.
The test is simple. Take the annual figure your household and business genuinely need — your enough number, not your aspirational number. Divide it by the number of delivery weeks you will actually work once you account for leave, sick days, quiet periods and the weeks that get eaten by a launch or a family event. Then divide again by the days you are willing to deliver in a week.
That gives you a required day rate or, better, a required value per engagement. Compare it to what you charge now. For most consultants the gap is uncomfortable, and the gap is the work.
A few things tend to close it:
- Pricing the outcome, not the hours. Day rates cap your income at your capacity and punish you for getting better. If you are being paid for the result, three days of your time is a delivery decision rather than a revenue ceiling.
- Fewer, deeper engagements. Six clients at a meaningful scope is a three-day week. Eighteen clients at a small scope is a five-day week with worse margins and more context-switching.
- A minimum engagement size you will not go under. Not a preference. A floor.
- Removing the work that is priced as though it were free. Scoping calls, revisions, "quick reviews", the extra stakeholder who joined in week three.
This is Design pillar territory — pricing, packaging, positioning and pipeline — and it is the pillar that most often blocks Sustain. You cannot boundary your way out of underpricing. Run your numbers properly, and take the tax and structure questions to your accountant rather than working them out alone.
One warning. Raising your prices without changing anything else usually produces a short, sharp improvement followed by the same overload at a higher rate. Price is a condition, not the whole design.
Condition two: a client base that fits the shape of your week
Some clients are structurally incompatible with a three-day week. Not difficult, not unpleasant — incompatible.
The organisation that runs on same-day responses. The founder who thinks out loud at 9pm and expects a reply. The programme that requires you in three different workshops a week for six weeks. None of that is a character flaw on their part. It is a mismatch, and mismatches show up in your calendar, not in your feelings.
So audit the base you have. For each current client, ask:
- How many separate days does this engagement touch in a typical week?
- How much of the work is scheduled versus reactive?
- Does the value I deliver depend on my availability, or on my thinking?
- Would this client accept a two-day response window in writing?
That last question is the most revealing one, and you can usually answer it without asking. You already know.
Work that depends on availability is hard to fit into three days. Work that depends on judgement, design, analysis or facilitation is far easier, because it can be scheduled. Moving your practice from the first category to the second is often the single biggest structural shift available to a consultant who wants a shorter week — and it is usually a positioning change, not a pricing one.
There is a values dimension here too. A client base that fits your week is not just about logistics. Purpose-led consultants tend to accumulate work they took on because it mattered, at terms that do not hold. Both things can be true: the work is worth doing, and the arrangement is unsustainable. The point of our impact practice is to make the mattering deliberate rather than accidental — chosen against the Sustainable Development Goals you have decided to serve, priced properly, and scoped so you are still doing it in three years.
Condition three: boundaries set up front, not defended later
Boundaries that arrive in the middle of an engagement read as a problem. The same boundaries, stated in the proposal, read as professionalism.
This is the cheapest change on the list and the one most people put off, because saying it early feels risky. It is far riskier not to. Every unstated expectation becomes the client's assumption, and you will be renegotiating from behind.
What belongs in writing before the work starts:
- Which days you work. Named. "I deliver Tuesday to Thursday" is a fact, not a negotiation.
- Response times. Two business days is normal in professional services. Say it.
- Channels. Where work happens and where it does not. If you are not on their internal chat tool, say so in week zero, not week five.
- What a revision is, how many are included, and what happens after that.
- Scope change process. Not "we'll figure it out" — an actual mechanism, even if it is one sentence.
- Meeting load. How many, how long, and who prepares what.
- Escalation. What genuinely urgent looks like, and how it reaches you.
Most clients accept all of it without comment. The ones who push back are giving you information, early, at no cost. Take it.
The internal boundary matters as much as the external one. A three-day week that fills its non-working days with business admin is a five-day week with worse record-keeping. Decide when your own business gets attention, and protect that block with the same seriousness you would protect a client workshop.
Condition four: systems that carry the other four days
On the days you are not working, your business still has to function. Not grow — function. Enquiries need a response. Invoices need to go out. Someone who found you on a Sunday needs to be able to book a call.
This is what systems are for, and it is a narrower job than the word suggests. You do not need a technology stack. You need a small number of things that run without you:
- An enquiry path. A clear way for someone to get from interest to a booked conversation without a back-and-forth thread.
- A proposal template you can adapt in under an hour, with your boundaries and terms already in it.
- Onboarding that runs itself. Welcome, scope confirmation, access, first meeting booked, expectations restated.
- Financial hygiene on a schedule. Invoicing on fixed dates. Automated reminders. You should never be chasing money on a delivery day.
- A single place your work lives so you can pick a project up cold after four days away.
- A decision log or client notes habit so you are not rebuilding context every Tuesday morning.
The test for each of these is not elegance. It is whether the business embarrasses you when you are not in it.
Systems also protect the fifth pillar — Wellbeing — in a way willpower does not. If the only thing standing between you and a Sunday of admin is your intention, the admin wins. If the invoicing runs on a schedule and the enquiry form does the qualifying, the Sunday is yours by default.
The order matters
The four conditions are not independent, and there is a sequence.
Pricing first, because it sets what is possible. Client fit second, because it determines whether the pricing can hold. Boundaries third, because they are how the client fit is maintained. Systems fourth, because systems built before the other three just automate a business you do not want.
This is why the five-pillar diagnostic we run at onboarding is a diagnostic rather than a curriculum. You rate yourself 1–10 across Product Design, Visibility, Impact, Systems and Wellbeing, and the low score tells you where the constraint actually is. Plenty of members arrive certain their problem is systems and find out it was pricing. Sustain is usually downstream of Design.
It is also why the shorter week is rarely a single decision. It is a sequence of decisions made over two or three quarters — a repriced offer, two clients not renewed, a proposal template rewritten, an invoicing schedule automated — and then one day the calendar has room in it.
What the three-day week is not
A few honest caveats, because this gets oversold.
It is not a stage of business you graduate to. Some practices are structurally suited to it and some are not, at least not yet. If you are two years in and building a pipeline, a compressed week may cost you more than it gives you. Know which season you are in.
It is not the same for everyone. For some people the goal is fewer days. For others it is the same days with far less noise in them, or a week that flexes around care responsibilities. The underlying design work is identical; the output is personal.
It is not a guarantee of anything. Reducing your delivery days changes your capacity, not your market. What it does reliably is force clarity — you find out very quickly which parts of your business were carried by extra hours rather than by good design.
And it is not permanent. A launch quarter, a major bid, a client crisis: there will be weeks that are not three days. The difference is that you return to the design instead of drifting away from it.
Where to start this quarter
Pick one condition. Not all four.
If you do not know your enough number, that is the start. If you know it and your pricing does not reach it, that is the start. If your pricing is fine and your calendar is still shredded, look at client fit and at what you never put in writing.
Then make the change on the next engagement rather than trying to retrofit everything at once. New proposal, new terms, new response window. The existing work can transition at renewal.
This is slow, unglamorous structural work, and it is much easier with other people who are doing it at the same time. Our Foundation Pods run one masterclass per pillar each month and are recorded for members; Expert Pods put three or four members with an expert guide for small-group work you apply to get into and that stays off the record so people can be honest. The Impact Collab is capped at 150 members for exactly that reason — the conversations only work at that scale.
The IC is not where you summit. It is the base camp: the place you sort out your pricing, your terms and your systems so the climb is survivable.
If you are designing a practice that pays you properly and does not consume your week, join the Community Waitlist. We open places as they come up, and we would rather have the right 150 than a bigger number.