The 6:47am Slack check that’s costing you $40,000 a year

Why answering Slack before you put your feet is structural and the fix isn't where most founders look first.

You’re not out of bed yet.

The phone is in your hand because the alarm was on the phone, and now that you’re holding it you may as well look. There’s already a message in the team channel. Something needs a decision before the day starts, and the only person who can make it is you.

You make it. You put the phone down. You go make coffee.

By the time you sit at your desk, you’ve already worked.

I want to talk about what that actually costs.

Let me show you the math, because nobody wants to sit with the math on this one. If you’re running a $500K–$1M service business, your effective hourly rate as the founder is probably somewhere around $200. That’s a conservative number. For most of the founders I work with, it’s higher.

The pre-coffee Slack triage takes maybe fifteen minutes. Let’s say it happens five mornings a week, plus the weekend version, plus the lunchtime version that’s really just another triage in a different room. Add it up honestly and you’re at roughly two hours a week of founder time, spent answering questions that landed on your phone because no other path existed for them to land anywhere else.

Two hours a week at $200 an hour is $20,800 a year.

That’s the conservative version. It doesn’t count the cost of the attention you spend the rest of the morning recovering from having already worked before you wanted to be working. By the time you add the recovery cost — the mental tax of switching from “founder making coffee” to “founder triaging” and back again — the real number is closer to $40,000.

You are paying $40,000 a year to be your team’s first line of support.

I want to be clear about something. This is not a discipline problem. You are not failing at boundaries. You don’t need to delete Slack from your phone, or set up an autoresponder, or read a book about deep work.

The problem is structural. Every question routes to you because no other path has been built. There’s no decision framework the team can use. There’s no documented standard for the kind of call they’re asking you to make. There’s no second-in-command who’s been given the authority to handle it. So the question lands where it can land, which is on your phone, at 6:47am, before you’ve put your feet on the floor.

The instinct, when you notice this, is to tell the team to stop messaging you in the morning. That doesn’t work. They’re not messaging you because they don’t respect your time. They’re messaging you because the system you built, without realizing you were building it, taught them that the founder is where decisions happen.

What works is building a different path.

Here’s what that actually looks like. Not in theory. In the engagements I run.

We start by mapping every decision the team brought to you in the last two weeks. Every single one. Not the strategic ones — those are supposed to come to you. I mean the operational ones. Should I send this proposal at the standard rate or discount it. Should I push this deadline by a day. Should I respond to this client request with X or Y. The ones where you usually think, I shouldn’t be the person deciding this, but you decide it anyway because there’s nobody else to decide it and someone has to.

Then we sort that list. Some of those decisions need a written standard — a one-page document the team can reference. Some need a process. Some need a person other than you to own them. And a small handful actually do belong to you, and those stay with you, and you stop apologizing for them.

The work isn’t glamorous. Most of it is sitting with a client for an hour and asking, what did you decide last Tuesday at 2pm, and what did that decision cost you? The answers fill a document. The document becomes the path. The path is what the team uses instead of your phone.

I’ll tell you what changes when this is built.

The team gets faster. Not because they’re working harder. Because they’re not waiting on you. Decisions that used to queue up in your inbox now happen at the level they should have always happened at. The morning Slack ping doesn’t disappear, but the kind of ping changes. It’s no longer “what should I do here?” It’s “FYI, here’s what I did.”

The math on your time also changes. The $40,000 doesn’t show up as a check. It shows up as the hour you got back in the morning. The proposal you finished because you weren’t context-switching for ninety minutes after the school dropoff. The strategic thinking you used to push to Sunday night because the weekdays were already full.

If any of this sounds like you, I’d point you to one thing.

I built a two-week operational diagnostic for exactly this. Two weeks, fixed scope, fixed price. We map the decisions, find the bottlenecks, document what needs documenting, and you walk out with a roadmap for what to build first and what to stop doing yourself. It’s the engagement I run before any longer-term work, because I’ve stopped believing in strategy without inventory.

I’ll write more about the diagnostic next week. For now, the question I want you to sit with is this one.

What decision did your team route to you this morning that they shouldn’t have had to route to you?

If you can answer that, you’ve already done the first ten minutes of the work.

Reply and tell me! I read every one. And if you know a founder who reads Slack before they put their feet on the floor, send this to them. They probably need it more than they’d say.

— Nicki

Marlowe Strategies publishes every Tuesday. Subscribe at marlowestrategies.substack.comand Marlowe Strategies Website