In partnership with
Your inbox is full. Slack is piling up. Client messages need a response yesterday. Typing thoughtful replies to all of it takes hours you don't have.
Wispr Flow turns your voice into clean, professional text you can send the moment you stop talking. Speak like you would to a colleague — tangents and all — and get polished output. Emails, Slack, LinkedIn, WhatsApp, whatever's open.
89% of messages sent with zero edits. Used by teams at OpenAI, Vercel, and Clay. Works on Mac, Windows, and iPhone.
A client of mine ran a creative agency. Doing about fifty thousand a month. Forty-five hour weeks. He was a yes person. He admitted it freely. He said yes to coffee meetings, to LinkedIn DMs, to scope additions on client work, to favors from his network, to internal team requests for his time, and to the small extra deliverables that clients always think of after the statement of work is signed.
He did not understand why he could not get his own work done. He worked all the time. He was always responsive. He felt like he was being a great partner to everyone in his orbit. And his business had been stuck at the same revenue level for fourteen straight months.
I asked him to do one exercise. For the next two weeks, every time he said yes to something, he wrote it down. Just a one-line note. What he said yes to, when, and roughly how long it would take.
Two weeks later he sent me the list. There were two hundred and thirty-one items on it. Two hundred and thirty-one yeses in fourteen days.
That averages out to sixteen and a half yeses per day. Some of them were two-minute things. Some were two-hour things. The total time he estimated he had committed across those two hundred and thirty-one yeses was just over fifty-three hours per week of work he had agreed to do for other people.
He was working forty-five hours. He was committing fifty-three hours of new work every single week. The gap was eight hours per week of incomplete obligations, compounding, going somewhere into the future where he was already going to be behind before the week started.
He was not undisciplined. He was not lazy. He was being eaten alive by the small yes.
This is the article about how to stop doing that.
Why Saying Yes Feels Free
The small yes feels free because the cost is invisible at the moment of decision.
Somebody asks you for fifteen minutes of your time. Fifteen minutes is nothing. You say yes. Three days later somebody asks you to review a deck. Twenty minutes max. You say yes. A client asks if you can squeeze in one additional revision. Quick edit. You say yes. A team member asks if you can sit in on a meeting where they need your perspective. Half hour. You say yes.
None of these individual moments feel like decisions. They feel like courtesies. They feel like the small social currency that keeps a working life functional. And they are. The problem is not the existence of small yeses. The problem is that you have lost track of how many of them are stacking up, and the cumulative weight of them is breaking the back of your week.
Here is the math that nobody does in the moment.
A fifteen minute coffee meeting is not fifteen minutes. It is fifteen minutes for the meeting, plus ten minutes to walk to the venue or fire up the video call, plus twenty minutes of context switching on either side because your brain cannot just snap from deep work to chatting and back. Total real cost. Fifty-five minutes. Almost an hour.
A twenty minute deck review is not twenty minutes. It is the time to find the deck, the time to read it carefully enough to give useful feedback, the time to write the feedback, plus the inevitable follow-up where they want to discuss your feedback. Total real cost. Forty-five minutes minimum.
A "quick edit" on a client project is the edit, plus the email back, plus the re-review when they come back with a question, plus the small recalibration of the rest of your client work because this one bit moved.
The pattern repeats. Every small yes is a real yes plus a hidden tax. The tax is usually two to three times the size of the original ask. And nobody factors the tax in when they say yes, because the tax is paid later, in fragments, in the time you keep thinking you should have for your own work but somehow never do.
The Three Categories Of Yes That Are Costing You The Most
Not all yeses are equal. Some are genuinely worth saying. Some are catastrophically expensive. The trick is being able to tell them apart in the moment. There are three categories that, in my experience, account for most of the damage.
Category one. The networking yes.
Coffees. Lunches. Quick chats. Phone calls with somebody a mutual connection introduced you to. Podcast guest invitations. Conference panel slots. Industry meetups. The yeses that fall under the umbrella of "building relationships."
Some of these are real. Most of them are not. Most networking yeses, looked at in cold daylight, are people you do not actually want to spend time with, having conversations that will not produce business, in a window of your day that was supposed to be for the work that actually matters.
The honest test is this. If the relationship in question were already strong, would you have invited this person to coffee on your own initiative? If yes, take the meeting. If no, you are not building a relationship, you are being polite. Stop being polite at the expense of your business.
Category two. The favor yes.
Somebody you know asks for an introduction. A friend asks you to review their pitch deck. A former colleague wants your thoughts on a contract. A peer asks you to refer them to a vendor. None of these are bad asks. Many of them are appropriate. But the volume is the problem.
If you do five favors a week at thirty minutes each, you are spending two and a half hours per week on other people's businesses. That is one full afternoon every month, and three full work weeks every year. Free.
Some of those favors are worth it because they build the kind of relationships that come back around. Most are not. The honest test for favor yeses is whether you would be genuinely upset if the favor were never returned. If you would, ask yourself why you are doing it. Probably guilt. Probably some inherited belief that being generous is the same as being useful. It is not.
Category three. The scope yes.
This is the most expensive of the three. A client asks if you can squeeze in one more thing. A team member asks if you can take on one more responsibility. A vendor asks if you can handle one more piece of the process on their behalf. Each one of these is a tiny expansion of the work you have committed to do, and each one comes without additional compensation.
I see service businesses lose entire margins to scope yeses they never tracked. The original engagement was profitable. By the end of the quarter, after twelve scope yeses, the engagement is barely breakeven, and the founder cannot figure out why the cash got tight.
Scope yeses need their own filter, which I will get to in a minute, because they are the category most likely to come back and eat you alive.
The Single Question That Filters Most Of This Out
There are a lot of frameworks for deciding when to say no. Most of them are too complicated to use in real time. The one I have found that actually works is a single question, asked silently before answering.
The question is this. If I had to do this right now, would I want to?
The reason this works is that most of us say yes because the cost is in the future. We are agreeing to do something that future-us will have to do, and future-us is not in the room to push back. When you replace future-us with present-us, the calculus changes.
If somebody asks for a coffee three weeks from now, and you imagine doing that coffee in the next ten minutes, would you do it? If yes, take the meeting. If no, the future version of you is going to feel exactly the same way when the meeting actually arrives. Three weeks of distance does not make the obligation lighter. It only makes the saying-no harder.
This single mental move probably eliminates half the yeses that are killing your week.
For the harder cases, where the answer is not obvious, there is a second question. What am I trading?
Everything you say yes to is something you are saying no to. The hour you spend on a coffee is an hour you are not spending on client work, content, family, sleep, or your own strategic thinking. Make the trade explicit. If the trade is acceptable, take the meeting. If the trade is not, decline.
You will notice, when you make trades explicit, that most of the yeses you have been giving away are not trades you would consciously make. You would not trade an hour of focused work on your highest-leverage initiative for an hour of "catching up" with somebody you barely know. But you have been doing exactly that, several times a week, for years.
The Specific Scripts For Saying No
The hardest part of saying no is the social discomfort. You feel like a jerk. You feel like you are letting somebody down. You feel like your reputation will suffer.
It will not. People who run good businesses respect people who protect their time. The ones who do not respect it were not people you needed in your life anyway.
Here are the actual sentences I use, in case you want to steal them.
For networking asks. "Thank you for the offer. I am keeping my calendar tight this quarter so I can focus on a few specific projects. Let me check back in once that wraps up if it still seems useful."
For favor asks where you would normally say yes out of guilt. "I would love to help. My honest answer is that I am running tight on bandwidth this month. Can I point you to a resource that might be even better than my fifteen minutes?"
For scope creep on client work. "Good catch on that. That falls outside the original scope. I am happy to add it as a separate engagement. Want me to send you what that would look like?"
For team members asking for your time on things they could decide themselves. "Let me push this back to you. What do you think the right answer is? If you can write up your recommendation in three sentences, I will review it tomorrow morning."
None of these are rude. None of these burn bridges. All of them protect the most important asset you have, which is the time and attention you can put into the work that grows the business.
The Tools That Take The Volume Of Decisions Down
The honest truth is that even with the best filters, you are still going to face fifty or sixty asks a week. That is a lot of decisions. Most founders make those decisions in the cracks of their day, which means they are making them tired, distracted, and inclined to default to yes.
There are three operational moves that take the volume down to something manageable.
First, structure your calendar so the asks have less room to land. I keep a fixed set of "open" hours each week where I will take ad hoc requests. Outside those hours, the answer is automatically a "let me check my schedule and get back to you," which gives me time to evaluate properly. This shifted my decision-making from real-time, where I always defaulted to yes, to batched, where I default to no unless there is a reason.
Second, route as much of the volume as possible through automation. Calendar requests go through a booking page with qualification questions. Inquiry emails get auto-responses that surface intent. Vendor or partner requests get filtered through a form before anybody on my side spends a minute on them. I run most of this through Make scenarios that classify and triage incoming requests before they ever hit my inbox. You can grab Make here.
Third, give somebody else the authority to say no on your behalf. This is the single biggest unlock for founders past about forty grand a month. You hire or designate somebody whose job, among other things, is to gracefully decline asks that do not pass your filter. They are not lying for you. They are applying a filter you have already designed. The volume of asks that ever reach you drops by seventy or eighty percent.
What Happens When You Actually Do This
The first two weeks of saying no more often are uncomfortable. You will feel like you are becoming a worse person. You will worry that you are damaging relationships. You will catch yourself wanting to walk back declines.
Resist the urge. The discomfort is data. It is telling you how much of your previous yes pattern was driven by anxiety rather than judgment.
By week four, the volume of asks coming in actually starts to decline. People learn what you do and do not take on. The casual takers move on to easier targets. The genuine relationships get stronger because you have more time to invest in them.
By week eight, you are running an entirely different operating week. Your calendar has gaps in it. Your inbox is quieter. You are getting more done. You feel less reactive and more deliberate. The business starts to move in ways it had not been moving.
This is what most founders actually want when they say they want more freedom or more focus or more leverage. They do not need a better project management system. They need a better filter on what they let into their week in the first place.
Your Move This Friday
If you have read this far, your homework is small but specific.
For the next seven days, every time you say yes to something, write it down. One line. What it was, when you committed, how long it will take. Do not change your behavior. Just measure.
At the end of the seven days, look at the list. Categorize each yes into the three buckets above. Add up the time. Compare it to what you actually want your week to look like.
Most founders find a gap of fifteen to twenty-five hours per week between what they have agreed to do and what they would consciously choose to do if asked all at once. That gap is your bottleneck. That gap is why you cannot get your own work done.
Once you can see the gap, you can close it. The closing happens one no at a time.
If you want to install the operational structure that protects your time at the system level, the DSG Sprint is the program where we build it in thirty days alongside the rest of your operating backbone. Reply SPRINT and I will get you the details.
The yes is not generosity. The yes is just the easier option in the moment, and you have been paying for that easier option in chunks of your future for a long time now.
Start saying no.
Want my help installing this in your business? Reply SPRINT to this email and I will send you the rundown.
Talk Soon,
Dan
Dan Kaufman, Founder, Dead Simple Growth & Pinnacle Masters
2026 State of AEO Report
A year ago, most marketers weren't thinking about AI search. Now it's one of the fastest moving channels in the industry and nobody has a playbook yet.
So we built one. We surveyed hundreds of marketers to find out how they're approaching answer engine optimization, where they're investing, what's actually working, and what isn't.
The result is the 2026 State of AEO Report. Real data. Real strategies. A clear picture of where AI search is headed and how to get ahead of it.