I Hired Them. Then I Had to Let Them Go.

The night before, I rewrote the message four times.

Each version sounded reasonable. Each one was a small lie of omission. None of them said the thing I was actually doing — ending a paycheck for someone whose family I had met.

I went to bed at 11:30. I was awake by 3:14.

This is the part of being a founder that no LinkedIn thread will tell you about. Not the strategic decision. Not the cap-table math. The specific physiological signature of having to call someone you hired and tell them, with steady eye contact, that tomorrow morning isn't a thing they need to plan for.

I want to talk about what that does to your body. Because nobody else will.

The Morning I Couldn't Eat.

I made coffee. I didn't drink it.

The first time I had to let someone go, I couldn't function. Not for the whole day. Not into the night.

This was someone I had hired myself. We had talked — properly talked, more than once. I knew about his family. I knew the things he was working on outside of work. I knew the names of the people who depended on him. None of that mattered to the math. All of it mattered to me.

I sat at my desk with the Zoom invite pulled up, watching the seconds reload. My phone was face-down. I had told no one that morning what I was about to do.

The strange part wasn't the dread. I had expected the dread.

The strange part was how calm I sounded when the meeting started. The voice came out steady. The eye contact held. The right words arrived in roughly the right order.

Internally, my resting heart rate was somewhere around 110.

After the call ended, I closed the laptop and didn't move from my chair for an hour. I didn't cry. I didn't write. I just sat there with a kind of internal static I didn't have a name for.

That night I couldn't sleep — not in the way you can't fall asleep, but in the way you can't sleep when something is physically torn inside you. When the body has logged a thing the mind hasn't filed yet. At 2am I was scrolling through old Slack messages from him, looking for proof I had been a good manager. Looking for the version of myself I could still live with.

That's not anxiety. That's something else.

A Decision Isn't the Same as a Feeling.

Here's what I had to learn: making a decision and feeling okay about a decision are two completely separate systems.

The thinking brain runs the math. Runway. Role redundancy. The version of the company that survives the quarter. It signs the document. It writes the message. It does its job.

The body runs a different process entirely.

The body doesn't know about runway. The body knows that you just looked at someone's face on a screen and changed their next twelve months. It logs that. It stores it somewhere I haven't found yet.

Most founders I've talked to describe the same pattern. The decision feels clear. The action feels clean. The week after feels weird in a way that's hard to name.

It's not regret — the decision was right.

It's not depression — you're moving, eating, working.

It's the specific cost of being the person who delivers the news. Your nervous system was built for tribes of forty people, and it treats "I had to let someone go" the same way it treats being exiled — except you're standing on both sides of the goodbye.

You're the one leaving. You're the one staying. The body doesn't always know which.

I think this is the thing nobody warns you about when you start a company. You assume the hard part is making the call. You don't realize the hard part is what the call does to you for the next two weeks — and the next time you have to make one.

What the Watch Showed That Day.

I started looking at the data after the third one.

By then there had been more than three. There were days, later, with two of these on the same calendar — back to back, separated by a fifteen-minute coffee break I never actually drank. The first one is the one I still feel. But it was the later ones — the ones I thought I'd gotten used to — that made me start watching the numbers.

Not the company-wide layoffs. The individual ones. The "I hired you, and now I have to let you go" calls. Those are the ones the body remembers.

The pattern was always roughly the same:

• HRV dropped by about 32% in the twelve hours leading up to the call.

• Resting heart rate stayed elevated for 48–72 hours afterward, regardless of how well or badly the conversation went.

• Sleep latency — the time it takes to fall asleep — doubled for about a week.

What surprised me wasn't that my body was stressed. I had expected that.

What surprised me was how long the stress lasted after the decision was made and the meeting was done. The thinking brain had filed the event by lunch. The body hadn't filed it by Friday.

This is the data nobody collects on founders. We collect revenue, runway, churn, NPS, win rate, time-to-close. We don't collect what it costs to be the person making the calls.

If we did, I think we'd build very different tools for this part of the job.

The Recovery You Can't Schedule.

Here is the part nobody warns you about: as the founder, you don't get to grieve the layoff.

The person you let go has a clear identity. They were laid off. They get to feel angry, sad, betrayed, free. They get to call their friends. There's a story they can tell about it that has a shape.

You, as the founder, get nothing to feel.

You made the right call. You should be moving on. You have a board meeting tomorrow. You have fourteen other people whose paychecks depend on you not falling apart this week. So the body holds the rest.

And here's the part that compounds: it's not one call. Over the life of a company, it's a handful. Sometimes more. Each one leaves a small, specific residue in the nervous system — a low-grade signature that doesn't fully clear before the next one arrives. By year five, founders are walking around with a stress profile nobody in their life has the vocabulary to ask about. Not their team. Not their board. Sometimes not even their partner.

That's the part Momomoon was built for.

Not the obvious stress. Not the kind you can post about on Twitter. The quiet, accumulated kind that founders don't tell anyone about — the kind that pools in the nervous system across weeks of small, professional cuts nobody marked on a calendar.

The standard advice doesn't reach it. Journaling assumes you have words for the feeling. Meditation assumes you have twenty minutes between meetings. Therapy assumes you're not running a company that requires you to be functional by 9am tomorrow. None of those are wrong, exactly — but none of them are calibrated to the actual physiological state of having just ended someone's job.

What helps is what helps the body. Short. Repeated. In the moment. Sixty seconds of guided recovery, triggered before the loop compounds — not twenty-minute sessions you'll never make time for.

If you've ever made one of these calls, you already know what I mean.

The body remembers them.

Mine still does.

Momomoon is a stress intervention system, not a tracker. It runs on your wearable — detecting rising stress through HRV and context signals, then delivering a haptic nudge that guides a 1–2 minute recovery reset. No screen. No dashboard. Just an early signal and a brief reset, at the moment your nervous system needs it most.

Reserve Early Access for $1 →