When you’re the only engineer, every Slack ping is also a business emergency. Without a schedule, support eats your best hours and deep work happens whenever it happens, which is rarely. Here’s a block structure that protects both.

The core problem

Support and sales are urgent but rarely important on any single day. Deep work is important but never urgent. Left unscheduled, urgent wins every time, and you end each week having shipped nothing but replied to everything.

The block structure

Split the day into three kinds of time, not just “work” and “not work”:

• Deep blocks (2-4 hours, morning): coding, writing, anything that needs your full brain and breaks if interrupted.
• Shallow blocks (1 hour, midday and late afternoon): email, support tickets, Slack, scheduling.
• Buffer (30 minutes, end of day): the stuff that spilled over, plus planning tomorrow’s deep block.

Two shallow blocks a day, at fixed times, is usually enough to keep support latency reasonable. Customers don’t need an instant reply. They need a reliable one.

Protect the deep block like a meeting

Put it on your calendar as “Focus, do not book.” Turn off notifications, not just mute them — a badge count you can see is still an interruption. If you use a support tool, close the tab. If a customer emails during your deep block, they get a reply in the next shallow block, not immediately.

Set an autoresponder expectation

“I reply to support within 4 business hours” costs you nothing and buys you the right to batch. Most solo founders never say this out loud and end up training customers to expect instant replies, which then feels mandatory.

Match the block to the work, not the clock

Deep work needs your highest-energy hours, whatever those are for you. If you’re sharpest at 6am, that’s your deep block, even if it feels antisocial. Don’t put deep work at 4pm because “that’s when the calendar was free” — it’ll get eaten by fatigue and Slack anyway.

What breaks this

• Ad hoc calls. Every unscheduled call is a deep block killed. Push scheduling to async, a form or a booking link, with hours that don’t overlap your deep block.
• “Quick” interruptions. There’s no such thing. A two-minute question costs you the 20 minutes it takes to get back into flow. Batch them, always.
• Guilt. You will feel like you should be reachable all day. You are not obligated to be. A four-hour response window is normal for a one-person company, and customers assume it even if you don’t tell them.

The weekly check

At the end of the week, look at how many deep blocks actually happened versus how many you scheduled. If it’s under 60%, something is overriding the calendar — usually a support habit that needs a harder boundary, not more willpower.

---