When to Quit Your Job for Your Side Project
Concrete trigger points around runway, revenue, and growth rate to help you decide when leaving your job makes sense.
Most advice on this topic is either reckless ("follow your passion") or paralysing ("wait until you replace your salary three times over"). Neither is useful. The real question is simpler: at what point does staying at your job cost you more than it gives you? This post offers concrete things to measure before you make the call.
The Three Numbers That Actually Matter
Quitting is a financial event before it is anything else. Get these three numbers right and you have a rational basis for the decision. Get them wrong and you are guessing.
1. Runway
Runway is the number of months you can cover your personal expenses without new income. Calculate it honestly. Include rent, food, health cover, debt payments, and a buffer for the unexpected.
Twelve months is a reasonable floor. Less than that and a slow month, a failed product pivot, or a personal emergency can force you back into employment before the project has had a fair run. More than eighteen months and you may be waiting longer than you need to, depending on your growth rate.
To build runway, you have two levers: spend less before you quit, or generate revenue before you quit. Both work. Most people underestimate how much the first lever matters.
2. Monthly Recurring Revenue
MRR matters, but it is not the whole picture. A single month of strong revenue can come from a launch spike, a Product Hunt bump, or one enterprise deal that may not repeat. What you want is a baseline: the MRR you could replicate without a special event.
A useful target is covering a meaningful fraction of your monthly expenses from the project before you leave. That fraction depends on your personal risk tolerance. Some builders wait until MRR covers all fixed costs. Others leave earlier and treat the gap as acceptable because their runway covers it.
One number to avoid anchoring on: your current salary. Your salary includes taxes, benefits, and a premium for showing up reliably. Your personal burn rate is almost always lower. Compare MRR to burn, not to gross pay.
3. Growth Rate
A flat MRR of any size is a warning sign. Growing MRR, even at a modest level, tells a different story. It suggests the market is responding, word is spreading, and the trajectory is real.
Look at the last three months. If you see consistent month-over-month growth, that is more valuable information than any single month's figure. Consistent growth means the project has a mechanism working, not just a moment of luck.
If growth has stalled, that is worth understanding before you quit. Stalled growth with a job is a puzzle to solve. Stalled growth without a job is a source of pressure that makes clear thinking harder.
Softer Signals That Also Count
Numbers give you a floor. They do not give you the ceiling. These signals matter too.
You Are Losing More Time Than the Job Is Worth
Some jobs take forty hours a week. Some take sixty, plus the cognitive overhead of worrying about your inbox on weekends. If the job is consuming time you could spend on the project, and the project is showing real signs of life, the calculus shifts.
Be honest about this. A demanding job is not an excuse to quit before the numbers are ready. But if the project is gaining traction and the job is genuinely the bottleneck, that is a real cost to account for.
Customers Are Pulling You Forward
Organic inbound, referrals, unsolicited feedback asking for features you have not built yet: these are signals that the market wants what you are making. If you are pushing every new customer uphill, the product still needs work. If customers are arriving and staying without heroic effort on your part, that is a different situation.
You Have a Co-founder or Advisor Who Has Done This
Someone who has made the leap is worth more than any article, including this one. They can tell you what the first six months actually looked like. They can pressure-test your numbers and spot the things you are telling yourself that are not quite true.
Common Mistakes People Make
Quitting on a Peak
A launch goes well. Revenue spikes. Excitement is high. This is the worst time to make a permanent decision. Wait at least two or three months after a spike to see where the baseline settles. Quit on the baseline, not the peak.
Treating the Job as the Problem
The job is rarely the reason the project is not growing. More often it is a distribution problem, a pricing problem, or a positioning problem. Quitting does not fix those. If you quit and the underlying problem remains, you now have the same problem plus financial pressure.
Solve the distribution or retention problem first. Then quit.
Underestimating the Psychological Shift
Having a salary is a form of insurance. Losing it changes how you make decisions. Some builders find this motivating. Others find it makes them risk-averse at exactly the moment they need to experiment. Know which one you are before you make the call.
There is no shame in needing the stability of employment while you build. Some of the most durable indie businesses were built entirely on evenings and weekends.
Overestimating How Much Time You Will Gain
Quitting gives you time. It does not give you clarity. Many builders quit and immediately fill the new hours with busywork: redesigning the landing page, refactoring code that works fine, attending every community call. Protect your time before you quit, and you will protect it after.
A Simple Framework for the Decision
If you want a single structure to pressure-test your readiness, use this.
Step one: Calculate your personal monthly burn rate. Include everything.
Step two: Calculate your current runway in months (savings divided by burn).
Step three: Look at your MRR and what fraction of burn it covers.
Step four: Look at your three-month growth rate. Is it consistent?
Step five: Estimate how long it would take for MRR to cover full burn, given that growth rate.
If runway covers the gap between now and MRR covering full burn, with a buffer of a few months for the unexpected, the numbers say you can go. Whether you should still depends on the softer signals.
What Goodspeed Changes About This Calculation
One of the reasons builders stay in their jobs longer than they want to is the cost of building. If you spend six months and a significant amount of money getting to a first version, your runway shrinks and your risk goes up.
Goodspeed compresses that part of the timeline. It scores your idea against public signal before you write a line of code. It then plans the app with you and generates a React Native and Expo codebase. From there, it checks the must-have features against the screens and gives you a live web version. Finally, it prepares a signed release under your own developer accounts. You review and approve the release before anything goes live.
That matters for the quit-your-job calculation because it changes how much runway you need to burn before you know whether you have something worth pursuing. Getting to a testable version faster means you find out sooner. Finding out sooner means you can make the financial decision with more information and less time pressure.
It does not change the fundamentals. You still need runway. You still need to see growth. You still need to solve distribution. But the part of the equation where you are spending months and significant money just to reach a first version can be shorter.
The Decision Is Yours, Not Anyone Else's
No framework makes this easy. Obligations differ. Risk tolerance differs. Some builders have dependents, mortgages, or health conditions that make the leap genuinely dangerous below certain thresholds. Others are single, low-cost, and can absorb more variance.
The numbers in this post are starting points, not rules. Use them to structure your thinking, not to replace it.
The one thing that is almost universally true: builders who quit too early and run out of runway rarely get a clean second attempt. The ones who wait until the signals are real, build their runway deliberately, and solve distribution before they leave tend to have a better experience on the other side.
If your numbers are close but not quite there, the most useful thing you can do right now is keep building, grow MRR, reduce burn, and revisit the calculation in ninety days. The project will either be stronger by then, which makes the decision easier, or it will have stalled, which is information you also needed.
Either way, you will know more. That is worth three more months.
Subscribe to The Signal
The top 5 scored app ideas, delivered fresh.