carl-gustav.dev

Notes on systems, language, and craft.

Building & Leading

Why I Check Email Only on Tuesdays and Fridays

In 2011, I set an autoresponder limiting email to two days per week. Not as a productivity stunt — because my operational setup made it possible. Here is how it works, why it works, and who it frustrates.

Three weeks ago I turned on an autoresponder on my work email. It reads:

In order to increase my efficiency and productivity, I check my e-mail only on Tuesdays and Fridays. If you need immediate assistance, please call our office switchboard or reach me on Skype/mobile for urgent matters.

People have had reactions. Some positive, mostly from other founders who secretly wish they could do the same. Some confused, from people who assume it means I am on vacation. A few irritated, from prospects who sent an inquiry on a Wednesday and got what felt like a brush-off.

I want to explain why I did this, why it actually works, and what makes it possible — because the last part is the one that most email-batching advice leaves out.

The problem with email

I run an SEO agency with offices in Gothenburg and Stockholm. On a normal week, I receive somewhere between 80 and 150 emails that are not automated notifications. Most of them require some form of response. Maybe half require thinking — not just a yes/no, but actual consideration of what is being asked.

Before the autoresponder, my day looked like this: check email at 8:00 when I arrive. Respond to the urgent-looking ones. Start working on the hard problem of the day — a client strategy, a technical audit, a proposal. Thirty minutes in, check email again because something might have come in. Respond to two things. Try to pick up the hard problem where I left it. Fail to find the thread. Start over. Repeat until 17:00, having accomplished maybe three hours of real work in a nine-hour day.

I am not exaggerating. When I tracked it over two weeks in June, the average context-switching cost was close to 15 minutes per interruption. With 8-12 email checks per day, that is two to three hours spent just getting back into whatever I was doing before I opened my inbox.

Why this is not just “turn off notifications”

The standard productivity advice is to turn off email notifications and check email at set times — maybe three times a day. I tried that. It helps a little, but it does not solve the underlying problem, which is that email presence creates a psychological pull. If I know that there is email waiting, some part of my brain is processing that instead of the work in front of me.

The autoresponder solves this differently. It eliminates the pull entirely for five days out of seven. On Monday, Wednesday, Thursday, Saturday, and Sunday, my email does not exist as a communication channel. People who need me use other channels. The email sits there accumulating, and I deal with it in two concentrated sessions.

What makes this implementable

Here is the part that matters: I can do this because of specific operational conditions, not because of willpower.

BBO has a staffed office. When a client calls, someone answers. That someone is not me — it is whoever is at the front desk or, for our Stockholm operations, one of our team there. Urgent client matters get routed to the right person without requiring my inbox.

For truly urgent situations — the kind where a client’s website has been deindexed or a campaign is malfunctioning — people can reach me on Skype or my mobile. These channels exist specifically for things that cannot wait until Tuesday or Friday. In three weeks, this has been used maybe four times.

This is the key point: email batching works when you have a functioning triage infrastructure. The autoresponder is not a wall between me and the outside world. It is a sorting mechanism. Things that need me personally reach me immediately through faster channels. Things that can wait, wait. Things that do not need me at all get handled by the team without my involvement.

Without the switchboard, without the team handling first-line client contact, without the mobile/Skype escape valve — this system would not function. I would just be an unreachable founder, which is a different thing entirely.

What it has freed up

The numbers from the first six weeks: I estimate I have recovered 6-8 hours per week. Not through heroic productivity, but through the simple elimination of context-switching overhead.

On my non-email days, I work on the genuinely hard problems — the client engagements that require deep technical analysis, the business development work that requires sustained thinking, the strategic planning that cannot happen in 20-minute fragments. The quality of this work has improved noticeably, and the throughput has roughly doubled.

On Tuesdays and Fridays, I spend the first two to three hours processing the accumulated email. Because I am doing it in batch, I make faster decisions. There is no “I will come back to this later” — later is next Tuesday, which is too far away, so I deal with it now. Response quality has actually improved because I am giving each email my full attention during a dedicated session rather than squeezing replies between other tasks.

What it has not solved

Cold outreach is a problem. If someone emails me on a Wednesday with a business inquiry and gets an autoresponder, some percentage of them will move on to the next agency on their list before Friday. I know this is happening. I have accepted it as a trade-off, but it is a real cost.

There is also a perception issue. Some people interpret the autoresponder as arrogance — “this person thinks they are too important for email.” That is not the intent, but I understand the reading. I have tried to word the autoresponder as matter-of-factly as possible to minimize this, but it is unavoidable for some recipients.

The honest part

I do not know how long this will last. The conditions that make it work — a small enough organization that I can redirect urgent channels, a team that handles the day-to-day without my constant involvement, a work portfolio that benefits from concentration over availability — these conditions might change. BBO is growing. We are expanding into new service areas. I am running a second company alongside this one. At some point the volume or the nature of the work might outgrow this particular discipline.

For now, it works. And the lesson I take from it is not “batch your email” — that is surface-level advice. The lesson is: before you can protect your attention, you need to build the infrastructure that makes protection possible. The autoresponder is the visible part. The switchboard, the team, the alternative channels — that is the actual system.

Anyone else running something similar? I am genuinely curious whether this holds up at larger scale or whether it is a window that only exists at a particular company size.

Written by Carl-Gustav Öberg

I'm Carl-Gustav Öberg, founder of Forge Nord. I build AI systems, run infrastructure, and write about what I learn along the way.

More inBuilding & Leading See all in Building & Leading →