Building on the Side: The Double Life of a Job and a Startup

Your actual workday ends at 6:30. Your real day starts around 9, once dinner's done and the house has gone quiet, two, sometimes three hours before you're too tired to think straight, building something nobody at your office knows exists. You've gotten good at the specific exhaustion of doing this, showing up focused for a job that pays your rent while your actual attention is somewhere else entirely, then showing up half-depleted for the thing you actually care about, because the job took the version of you that had real energy left. Nobody's told you to stop. Nobody's told you to jump either. You're just doing both, badly, and calling it progress.

The Math Nobody Says Out Loud

Here's the honest version of what's happening: you're not actually working two jobs at full capacity, you're splitting a finite amount of daily energy across two demands and calling the result "building on the side," when what's really happening is that neither the job nor the startup is getting your best hours, because your best hours went to whichever one came first that day. That isn't a personal failing. It's simple arithmetic. A day only has so many genuinely high-focus hours in it, and a full-time job claims most of them before the startup ever gets a turn.

Naming that honestly matters, because a lot of the guilt in this situation comes from believing you should be able to give both things 100%, when the actual, achievable version of doing this well is closer to giving the job what it needs to stay stable and giving the startup whatever real focus is left, on purpose, rather than by accident at 11pm.

Why This Path Is So Common and So Rarely Talked About Honestly

Building something on the side while employed isn't a fringe choice, it's closer to the default path for most Indian founders who don't have significant savings or investor backing before they start, since the alternative, quitting first and building second, requires a runway most first-time founders simply don't have yet. This is happening against the backdrop of a genuinely large ecosystem, India remains the world's third-largest startup ecosystem, with over 110 unicorns as of the most recent government figures, which means the pool of people quietly building something on the side, right now, around a day job, is considerably larger than the visible, funded founders it eventually produces. The version of founder life that gets talked about publicly, the clean, dramatic "I quit my job to build my dream" story, is a small, visible minority. The much larger, quieter reality is people building in the gaps around a day job, for months or years, before anything is stable enough to jump into fully.

That quieter version doesn't get discussed as openly, partly because it doesn't photograph well for a LinkedIn post, and partly because it involves a genuine tension a lot of employers don't love hearing about directly, an employee's real ambition sitting somewhere other than the job that pays them. Forums where people actually discuss this candidly tend to be places like Teamblind rather than public platforms, precisely because the honest version of "I'm building something on the side and not sure my company would be thrilled to know" isn't something most people want attached to their name.

The Specific Exhaustion of Doing Both Half-Well

This is a different kind of tired than either pursuit alone would produce. It isn't the clean exhaustion of a hard day's real work. It's the more corrosive kind that comes from context-switching between two demands that each want your full attention and getting neither, spending office hours partially distracted by the startup, then spending startup hours too depleted from the job to do your best thinking.

There's also a specific guilt that compounds the exhaustion, the sense of being a slightly worse employee than you'd be if the job were your whole focus, and a slightly worse founder than you'd be if the startup were. Both of those feelings can be true simultaneously without either one meaning you're doing this wrong. It's simply the honest cost of building two things at once with one set of hours, a cost worth naming rather than pretending away.

How This Actually Plays Out for Different People

For some, this phase has a relatively clear endpoint, a specific revenue number, a specific runway saved, a specific validation milestone, after which the job gets left behind deliberately. Having that concrete marker tends to make the double life feel more bearable, since it's a phase with a defined exit rather than an indefinite grind.

For others, the phase drags on without a clear endpoint, the startup never quite reaching the threshold that would justify leaving, the job never quite becoming unbearable enough to force the decision either. This is often the most draining version, not because the workload is necessarily heavier, but because the uncertainty itself, not knowing how much longer this specific exhaustion needs to be sustained, adds its own weight on top of the actual hours worked.

For a third group, the side-building phase eventually reveals something honest about the startup idea itself, that it either genuinely can't get the attention it needs in stolen evening hours and needs a real full-time push to actually test properly, or that the founder's honest energy and interest were never quite where they told themselves it was. Both discoveries are valuable, even when neither feels good to arrive at. A fourth, quieter outcome is worth naming too: some founders discover, through the sheer exhaustion of trying to do both, that the idea itself wasn't actually strong enough to survive the double life, and that shutting it down while still employed is a far less costly way to learn that than discovering it after quitting entirely.

What Actually Helps During This Phase

Setting a genuinely honest weekly time budget for the startup, and treating it as a real commitment rather than "whatever's left over," tends to produce more actual progress than an open-ended, guilt-driven approach where the startup gets attention only when energy happens to be available. A defined two hours most evenings, protected on the calendar, usually beats an aspirational but unenforced "whenever I can."

Being honest with yourself about which of the two, the job or the startup, is actually draining more of your genuine enthusiasm lately is worth revisiting periodically, since that balance shifts over time and the answer at month two isn't necessarily the answer at month eight. What felt sustainable at the start can quietly stop being sustainable without a clear single moment marking the change.

Protecting some actual rest, not startup time, not job time, just genuine downtime, is easy to sacrifice first when both demands feel urgent, but doing so consistently tends to produce worse decisions in both domains rather than more overall output. Indian workforce data more broadly backs up how widespread this exhaustion has become, with recent research finding employee engagement in India at a multi-year low even among people with only one job to focus on, let alone two.

What tends not to help is treating this phase as a test of willpower alone. The people who sustain it longest usually aren't the ones grinding hardest without boundaries, they're the ones who've built some actual structure around a genuinely unsustainable-feeling situation, rather than trying to out-discipline the basic math of finite hours.

Where Artha Fits In

This is exactly the kind of double life that's hard to talk about honestly with people close to you, because your family may not fully know about the startup yet, and colleagues definitely shouldn't. Artha's Founders' Room exists for this specific gap, an anonymous space to say the real thing, "I'm exhausted doing both and I don't know when, or if, I get to just do one," with other founders who are in the exact same stretched position, or who've already made it through to the other side of taking the full leap.

A Small Thing Worth Saying Honestly

Artha itself started this way, built in the hours around CA prep rather than instead of it, and the specific exhaustion described here is one I know from the inside, not from a distance. What helped most wasn't finding more energy from somewhere. It was getting honest about how much there actually was, and building around that real number instead of an imagined one, the same honesty that matters when deciding whether a startup idea can even survive being shared in the small pockets of time you actually have for it.

You were never really failing at either the job or the startup. You were just trying to run two full-time efforts on the hours of one, and calling the resulting tiredness a character flaw instead of what it actually was, simple arithmetic.

If you tracked, honestly, how many real hours the startup got this week, not the hours you meant to give it, would that number tell you it's time to change something, or that the pace is actually fine?