Drop your business development to its smallest sustainable level rather than switching it off, tell people your dates before you go, and accept that a live opportunity moving two weeks later is normal. Two weeks feels enormous to you and is close to nothing in client time.
Go into your smallest business development setting for the weeks around the trip instead of stopping entirely.
A floor you keep means the quiet stretch that follows a break never arrives, because nothing dropped to zero.
Pick your dates, then look at what has to happen in the three weeks before them.
Client time and our time are different.
Leah Neaderthal, Smart Gets Paid
Two weeks away stalls a consulting business only if you also stop the activity that feeds it, and the stall that consultants remember came from the stopping. The trip is not the problem. The month of nothing wrapped around it is.
Two things are true at once here:
So the fix isn't working through your holiday. It's not letting the floor hit zero for the weeks around it. Why the quiet arrives months after the decision that caused it is the fuller version of that argument.
Keep the smallest version of what you normally do, which is what simmer mode is for. I built that setting specifically for the weeks when you're traveling, dealing with something personal, or simply out, and the point of it is that it's small enough to survive a week you aren't in.
What it looks like in practice, from consultants who've done it:
| Normal setting | Simmer setting |
|---|---|
| Ten to twelve outreach emails a week | Three to five, sent before you go |
| One original post a week | One repurposed post, scheduled |
| Weekly newsletter | Continues, written ahead or paused for one issue |
| Stretch projects and new experiments | Nothing. Simmer has no stretch row |
The rule underneath: minimum viable showing up, enough that you don't recede into the distance. Scheduling ahead is legitimate, and so is doing less. What isn't recoverable is the month where nothing happened at all, because that one bills you in the autumn.
Tell them your dates before you go, in a plain sentence, and say when you'll be back in touch. A stated absence is a professional norm that nobody questions. An unexplained silence is the thing that gets interpreted.
The three messages worth sending in the week before:
Notice that all three are about certainty rather than availability. You aren't asking permission and you aren't apologizing. And when you get back, follow-up on things that went quiet across the break is ordinary rather than awkward, which restarting a conversation that's gone quiet covers properly.
Decide in advance what you will and won't do while you're away, and then hold it, because the alternative is checking email on a beach and calling it a compromise. This is a decision rather than a discipline problem, and the deciding has to happen before you leave.
The mindset I'd bring is one I use constantly: make it so. Whatever you decide about how you work is how you work, starting now. Your clients don't know you were reachable at eleven at night last summer, and it doesn't matter to them. They see what you show them today. Whether that's sustainable at your current workload is a bigger question, and the warning signs are worth knowing before you answer it.
I want to name the thing underneath this question, which is usually not logistics.
Most consultants I talk to can arrange the practical parts fine. What they can't do is give themselves permission, so the question comes out as "how do I take a vacation" when what's being asked is "am I allowed to." The logistics are the acceptable version of a question about permission.
Here's the reframe I'd offer. You didn't leave a job to build something that gives you less freedom than the job did. If your business can't survive two weeks without you, that's information about the business rather than a reason to stay. And it's fixable information: it usually means everything depends on one opportunity, or that nothing is running unless you're pushing it that day.
The other thing I'd say is about client time, because it's the piece that surprises people every time. You are agonizing over two weeks. On the client's side, someone looked up three weeks after your last conversation and thought it was last Tuesday. I've been that client. I lost three weeks of my life and had no idea.
So take the two weeks. Set the floor, send the three messages, and go.
Three to four weeks of runway is usually enough for the practical side, and the business development side wants longer. Because activity takes months to become income, a break planned a quarter ahead lets you keep the floor steady through the run-up rather than scrambling in the fortnight before. Booking the dates first and working backwards is what stops the trip getting postponed.
Real emergencies are rarer than the anticipation of them, and naming a contact for urgent matters before you go resolves most of what does arrive. Deciding in advance what counts as urgent is the part worth doing before you go, because in the moment everything feels urgent. Write down the two or three situations that would warrant reaching you, and let the rest wait.
Saying you're away on vacation is normal and it costs you nothing. Vagueness reads as evasive and invites people to test the boundary, while a specific date is easy to plan around and easy to respect. Consultants worry this signals a lack of commitment. Clients read a person with clear dates as a person who runs an organized business.
Send the proposal before you go, or tell them the date it's coming and hold that date. What creates the problem is going quiet with something pending, since silence on an open proposal reads as a change of mind. A note saying when you're back and when you'll follow up keeps the opportunity in the same place you left it.