How to take a 30-day vacation as a business owner

Executive overview

Most founders believe they can't step away because the business will fall apart without them. That belief is the problem. The more indispensable you are, the less valuable your business is.

A 30-day vacation is a forcing function: it exposes bottlenecks, accelerates documentation, and hands off tasks that should never have stayed with you.

Removing yourself is the fastest way to build a business that scales without you.

Three core principles

• Rest is work — breakthroughs happen in the shower, on walks, on vacation, not at a desk
• Distance creates perspective — the longer you're stuck, the longer the break you need
• Vacations are forcing functions — announcing you're leaving galvanises the team to build systems

Seven rules for doing it right

• Block at least four consecutive weeks on the calendar
• Book three to nine months out (six months is the sweet spot)
• No meetings while away
• No email
• No Slack — remove it from your phone
• No special projects; don't commit to deliverables
• One named emergency contact for the whole company

Three vacation formats

1. 1-1 option (good): Work remotely week 1 → full off weeks 2–3 → ease back in week 4
2. Full 30 (better): Leave on day one, return on day 30, no exceptions
3. 1-for-1 option (best): Work part-time the week before → full four weeks off → ease back in for one week after (six weeks blocked total)

The vacation announcement email

• Send to the leadership team as soon as dates are set
• State clearly you won't attend meetings, check email, or log into Slack
• Name the emergency contact
• Ask each person to reply with what they think will break while you're gone
• Frame it as an opportunity: systems get built, team members get new responsibilities

The reply process surfaces every critical task that depends on you personally.

Processing the replies: three task types

• Do it ahead — tasks only you can do; batch them before you leave
• Stop test — tasks that simply won't happen; find out if anyone misses them
• Hand off — tasks that can and should belong to someone else permanently

How to document a handoff

• Perform the task and record it simultaneously (e.g. with Loom), five to ten steps
• Repeat the task following your own documentation to find gaps
• Have the new owner attempt it while you observe; ask what was missing
• Adjust, then hand it off before you leave
• If done well, many tasks never return to you when you're back