The month I had to let my first hire go at $22K MRR: a founder diary (2026)

Quick answer (2026): There is no MRR number that automatically makes a first hire safe, and no number that automatically makes a layoff necessary. The honest trigger is trend plus fixed cost. A salary is a fixed cost you carry through good months and bad, so the real question is not "can I afford this person today," it is "can I still afford them if revenue keeps doing what it has done for the last three months." This is one founder's 2026 diary of hiring a first employee at $9,000 MRR, watching revenue slide from a $27,000 peak back to $22,000, and finally letting that person go about four months later than the numbers said to. The severance was not the expensive part. The waiting was.

For two years the hardest thing I had built was the product. In the spring of 2026 the hardest thing I had ever done was tell the one person I had hired that I could not keep paying them. I run a small B2B SaaS on plans between $29 and $149 a month. The figures here are my real numbers, rounded and told the way I tracked them at the time, and I have kept the product name and my employee's name out of it on purpose.

This is a diary about the gap between a decision the spreadsheet made months ago and the day I finally had the nerve to make it.

The hire I was genuinely proud of

I brought on my first employee at about $9,000 MRR. Call them R. A customer-support and onboarding generalist, part detective, part diplomat, the person who answered the tickets I had been answering at midnight for two years. I wrote about the leap and the fear of that first payroll run in the month I made my first hire at $9K MRR, and for about ten months it was the best decision I had made.

It worked. R. gave me back roughly twenty-five hours a week. Response times dropped, a few churned accounts came back, and I finally had time to sell instead of only support. MRR climbed from $9,000 to a peak of about $27,000. I remember thinking hiring was the cheat code nobody had told me about, and I started quietly planning the second hire.

Then the line bent the wrong way

Two things happened close together. One mid-size account got acquired and folded into their new parent's tooling. A second slashed its budget and dropped to a plan a third the size. And a price change I had made to lift my average revenue quietly pushed out a cohort of my oldest, most price-sensitive customers over the following two months.

None of it was a catastrophe on its own. Together, over one quarter, MRR went from about $27,000 to $24,000 to $22,000. The graph I had watched go up and to the right for two years was now, unmistakably, pointing down. And R.'s salary, of course, did not point anywhere. It was the same number every month, exactly as it should have been.

The math I kept not looking at

Here is the monthly picture the month I finally forced myself to add it up.

Nine thousand a month. If you stop there, it looks fine. It was not fine, and two numbers hidden inside it are why.

First, that $9,110 had been closer to $13,000 three months earlier. It was falling about $1,200 every month, because MRR was sliding while R.'s cost stayed flat. A fixed salary against a declining top line is a slow leak with a very predictable end date, and I could see mine.

Second, to keep R. paid on time and to avoid the conversation, I had quietly pulled about $14,000 out of my personal savings across four months. I told myself I was investing in the recovery. I was not investing. I was subsidizing a decision I had already made and refused to say.

Why I clung on for four months too long

I did not wait because the math was unclear. I waited for two reasons, and I think they are the two reasons most first-time founders wait.

The honest one: R. was good, and it was personal. This was not a headcount on a slide. It was a person who had trusted a tiny company, who was excellent at the job, and who had no idea the graph had turned. Every week I did not say anything, I got to keep pretending I would not have to.

The one I dressed up as strategy: I told myself that letting R. go was penny-wise, because if growth came back I would have to rehire, and rehiring is brutally expensive. That part is even true. Gallup's widely cited 2019 analysis puts the cost of replacing an employee at one-half to two times their annual salary once you count the hiring, the ramp, and the lost knowledge. I used that real number as a reason to hold on. But it is a trap when your revenue is shrinking: I was spending certain money now, out of my own savings, to avoid an uncertain, possibly-never cost later. The fear of an expensive rehire kept me making an expensive mistake.

The written trigger I did not have, and now always will

The root cause was not the churn. It was that I had hired on pure optimism, with no written condition for when the role would be at risk. I had a hiring bar. I had no un-hiring bar.

If I could do one thing differently, it is embarrassingly small: write the exit condition on the same day you write the offer.

1. Before the hire, write the number and the trend that put the role at risk. For me it should have read: "if MRR is under $24,000 for three straight months, this role is formally reviewed." That is it.
2. Track it somewhere you cannot avoid, next to the MRR cell you already look at every morning.
3. When the trigger fires, move in weeks, not quarters. The decision is already made by the rule. Your only job is to execute it like an adult instead of relitigating it every night.
4. Never fund a fixed salary out of personal savings for more than one month without a dated plan to either fix revenue or end the role. One month is a bridge. Four months is denial with a receipt.

Had that rule existed, the decision would have made itself in month two, when I had lost far less money and R. would have had a far better runway to land somewhere. The rule is not cold. The rule is the kindest thing, because it makes you act while you still have resources to be generous with.

How I actually did it

When I finally accepted it, I decided the one thing fully in my control was to do it well. The most useful guidance I found was Harvard Business Review's 2018 piece by Sandra Sucher and Shalene Gupta, a better, fairer approach to layoffs, whose core idea is simple and hard: treat the people leaving as adults who deserve the full truth and real help landing, not a scripted five-minute meeting.

So I did not hide behind a process, because there was no process, it was just the two of us. I told R. the whole financial picture, the same table you just read. I gave six weeks of severance, which was honestly all I could responsibly do and less than I wanted, and I said so. I kept their health coverage running through the notice period. I wrote a reference that was easy to write because it was all true, and I personally introduced R. to three founders I knew were hiring for exactly that skill set. Two of them replied the same day.

It was still the worst forty seconds of my time as a founder. Doing it decently did not make it not hurt. It just meant I could live with how it happened.

What it cost, and what it bought

I went back to answering the tickets myself, at midnight again, which is its own slow danger. Doing every job alone at a real revenue milestone is exactly the road into burnout at $15K MRR, and I felt the first pull of it within a month.

But the leak stopped. Reclaiming about $6,700 a month in fixed cost, my personal savings stopped draining the day R.'s last check cleared. At $22,000 MRR with only me to pay, the business was comfortably default alive again, just at a smaller and more honest shape than the one I had been pretending to run.

I still do not think hiring at $9,000 MRR was the mistake. Hiring for the growth I was only hoping for, with no written condition for what I would do if that growth did not come, was the mistake. The hire was a bet. The refusal to plan for losing the bet is what cost me four months of savings and a friendship that never fully recovered.

What I would tell you if you are standing here

If you are about to make your first hire, congratulations, it might be the best money you ever spend. On the same afternoon you write the offer letter, write two more sentences: the MRR level and the trend that would put this role at risk, and the maximum number of months you will ever cover this salary out of your own pocket. Put them where you will see them.

Then, if that day ever comes, believe your own rule. The layoff is one bad day you can do with decency. The waiting is a bad quarter you pay for out of your savings, your sleep, and eventually the other person's runway too. I waited four months to save one job, and all the waiting bought me was less money to be kind with when I finally had no choice.

Founder identity and figures in this diary are a composite drawn from several real founders, anonymized, rounded, and self-reported, shared this way to protect the people involved.