A couple weeks ago I accepted a 17-minute “Quick Chat” with three people I’d just met.

I can see the meeting title on my calendar. I can see the time.

I cannot tell you what we talked about.

No follow-up shipped. No intro mattered. No customer moved closer. No bug got fixed. No product decision got clearer.

Seventeen minutes disappeared, then took more with it: a little prep, a little context switch, a tab left open in my brain for the rest of the morning.

And that’s the trap.

Yeses That Leave No Mark

There are yeses that move a company forward.

A customer willing to pay.
A design partner with a real workflow.
A technical conversation that unlocks a hard product decision.
A founder who has seen the same problem up close and can help you avoid a hole.

Those are the yeses I live for.

The dangerous ones are smaller.

A quick chat. A quick intro. A quick coffee. A quick question. An intimate founder dinner with 200 people and Costco pizza.

Each one is easy to justify.

Networking matters and loose connections compound. You never know where something will lead. This is all true. And also how you lose a week.

The problem with a tiny yes is that it feels almost free. Fifteen minutes sounds harmless. A calendar invite looks contained. A coffee feels human.

But a quick chat rarely costs what the invite says.

It costs the 10 minutes before. The 20 minutes after. The energy of remembering who they are. The vague guilt of deciding to follow up or not.

Founders do not usually get derailed by one giant bad decision.

It’s death by a thousand cuts.

A Quick Way To Be Distracted

I did not expect quick to be the most expensive word in my inbox.

Quick Chat. Quick Meeting. Quick Question. Quick Intro.

A genuinely quick ask has a shape. It’s specific: “Can you intro me to Joan?” “Do you support Teams?” “Can I send this customer your way?” Great. Those are real asks. They can be answered in a minute.

The dangerous quick is really an opening volley. The ask is not the ask. The ask is permission to enter your calendar.

“Can we do a quick chat?”  → “Can I have a low-friction way to see if there is something useful for me here?”

Sometimes the answer should be yes. A lot of the time, especially at a tiny startup, the honest answer is: not this week.

Because a founder’s calendar is part of the product roadmap.

Every vague meeting competes with a concrete piece of work. The email parser. The onboarding flow. The prospect who already asked for pricing. The customer waiting for the thing you said you would ship.

That is the part a calendar invite hides.

Why Founders Fall for It

Leaving a big company for a startup does weird things to your dopamine.

Inside a large company, attention is everywhere: syncs, threads, reviews, status updates. Somebody always needs something.

Then you start a company and the room goes…quiet.

No calendar making you feel important. No inbox full of internal threads. No giant brand opening doors. No team absorbing asks.

At first the silence is liberating. Then it gets weird.

You start to overvalue attention that you used to ignore. A warm intro feels like momentum. A podcast invite feels like validation. Any investor interest even if it’s just a “curious what you’re building” call? Jackpot. A coffee with another founder feels like work because it’s part of the work day and uses work words.

Therein lies the danger.

No carries an imagined cost: what if this person becomes important? What if this is the one? Will this dinner lead to the customer? Yes carries real cost: forty-five minutes. A burned morning. A step you never wanted. Less focus for building.

I’ve learned to be suspicious of imagined costs more than real ones.

Taking Back Yes

That 17-minute call from two weeks ago? Fine.

The 200-person “intimate” dinner with the Costco pizza? Also fine.

And that’s what makes this hard.

These things are rarely bad. Bad is easy. You can reject bad.

Fine is pleasant enough to keep accepting. Fine is polite enough to feel harmless. Fine makes you busy without making you better.

As a founder, that’s the danger zone.

Especially now. Coding agents can fill every spare second with something to check, review, fix, merge, rerun, or contemplate. We now have an unlimited supply of plausible work.

People are one of the best parts of building a company. You learn so much from talking to customers, founders, operators, and experts.

The point isn’t to eliminate human connection, but to make Yes earn its spot.

My New Rule

Before committing to a meeting or event, I ask myself one question:

If I can't answer it, I don't accept. If the other person can't, it can probably be handled in writing.

Quick chat → What would make the call useful?
Want to meet up? → Is there something specific we should decide or compare notes on?

Sometimes it may sound colder than I want it to be. That is the skill.

Saying no to people who are nice is so much harder than ignoring spam. But that’s just it. The nice people are the trap. The interesting people are the trap. The flattering opportunities are the trap.

Every no gets you an hour of extra flow. Every hour moves you closer to the only thing that matters at this stage.

Millions of developers use Wispr Flow to dictate code, write docs, and give coding agents better context. 89% of messages sent with zero edits. 4x faster than typing. Free on Mac, Windows, and iPhone. Try Wispr Flow free.