Should I quit my well-paid job to start a startup?

Short answer: Keep your day job for now. Spend evenings and the odd Sunday hacking on the idea until you’re sure it has legs (and until you’re sure you actually enjoy the grind that comes with it).

Long answer: I still remember sitting on the Zürich S-Bahn, salary in my pocket, spreadsheet open, trying to decide whether to hand in my notice. I’d built a little prototype that maybe ten people cared about — exhilarating, but hardly “quit-tomorrow” traction. The question that kept looping in my head: am I bored enough at work to trade stable income for the privilege of eating stress for breakfast?

Your current gig is comfortable — decent pay, insurance, the luxury of paid holidays where Slack stops buzzing. Walking away means uncertainty on all three fronts. First customer revenue often arrives slower than founders expect (took me 3-4 months the first time, but I’ve seen friends wait half a year). Then comes the awkward stretch where revenue covers coffee and Heroku, but not rent — the so-called “ramen profitability” phase. I should be upfront: some products never crawl out of that zone.

Startup life, at least in my experience, is mostly unglamorous repetition: shipping half-finished features at 1 a.m., begging strangers on the internet to try them, fixing the bugs those strangers uncover, repeat. The highs are absurdly high — waking up to three new sign-ups can feel like Christmas — but the lows (silent inbox, churn you can’t explain) hit harder than any performance review ever did. I’m not entirely sure this scales beyond solo or two-person teams, yet here we are romanticising it.

Gauge your risk tolerance honestly. Can your savings cushion six to twelve months of patchy income? Are you OK telling friends you’re “still pre-revenue” at the next barbecue? If the very thought makes you queasy, keep iterating on nights and weekends a bit longer.

The upside, of course, can be life-changing, but not always in the billionaire-exit sense. Owning the roadmap, deciding which customer emails matter, building something that reflects your taste — that autonomy is hard to price. When a user says “this solved my problem,” you’ll grin like an idiot. Worth noting: the feeling fades if you’re sleep-deprived for months, so pace yourself.

What’s worked for me: build a runway before you jump. Save aggressively, yes, but also trim personal burn (cancel the streaming services you barely use, swap the fancy coworking space for your kitchen table). Use that freed-up time to crank on the product: evenings at first, then maybe negotiate one remote day per week, then spin up small consulting gigs to keep cash coming while you reduce employer hours. You’re aiming to transition from “salary” to “revenue that kind-of resembles a salary.” Messy, but doable, though it might not fully resolve all challenges.

Timing matters. If you’re child-free in your twenties, the downside is mostly bruised ego and a dent in savings — recoverable. Add a mortgage, kids, or visa constraints, and the calculus shifts. I could be wrong, but past thirty the opportunity cost feels steeper, which is why many founders in that bracket pursue calmer “indie” products or raise a seed round to offset personal risk.

One last thought (more note-to-self than advice): quitting shouldn’t be a grand gesture timed to a new moon. It’s usually a series of small choices — saying no to an internal promotion, shipping the V1 landing page, talking to ten real users. After enough of those, the decision to resign becomes almost obvious. If it still feels like a coin toss, keep collecting data until the odds nudge clearer.