Navigating the Startup Hustle: Lessons from the Tech Trenches
When I joined Enerjazz as employee #5, I thought I was joining a startup. What I actually joined was controlled chaos with a pitch deck.
There was no onboarding document. No department to slot into. On my first week, I was simultaneously drafting job descriptions, sitting in on a sales call I had no business being on, and helping the CTO Pratik figure out why a particular API integration kept timing out under load. I had signed up as a marketing consultant. The role description became irrelevant by day three.
That’s the startup hustle nobody talks about honestly. It’s not the glamorised version — late nights fuelled by passion and cold brew. It’s the version where you’re debugging a vendor contract at 11pm because the person who was supposed to do it left two weeks ago and the institutional knowledge left with them.
What Employee #5 Actually Means
Being one of the first five people at a company means you are, functionally, every department. CEO Ravi Bharihoke ran a lean operation by design — not because they couldn’t hire, but because the right people hadn’t been found yet. In the meantime, whoever was closest to a problem owned it.
I touched HR because nobody else was writing job descriptions. I touched finance because someone had to reconcile the vendor invoices before the founder’s quarterly review. I touched sales because a warm intro came in and the pipeline needed to move. And through all of it, I was supposed to be building the marketing function from scratch.
What this taught me: in a seed-stage startup, your job title is aspirational. Your actual job is whatever the company needs most urgently today.
The Specific Things That Break You Down
People talk about startup resilience in abstract terms. Let me be specific about what actually tests it.
The first is context-switching cost. Every time you pivot from writing a performance brief to debugging a broken Zapier workflow, you lose about 20 minutes of deep focus. Multiply that by six context switches a day and you’ve lost two hours of your most productive thinking — every single day — to the overhead of being a generalist.
The second is the invisible work. At a large company, processes exist because someone spent years documenting institutional knowledge. At a five-person startup, that documentation doesn’t exist. You create it while you’re doing the work, which means every new task takes three times as long because you’re building the system and executing it simultaneously.
The third — and this one caught me off guard — is the emotional weight of proximity. When there are only five of you, every win lands harder and every setback lands harder. A churned customer isn’t a number in a dashboard; it’s a conversation you had last week with a real person who was genuinely excited. That intimacy is powerful. It’s also exhausting if you don’t learn to manage it.
The Small Wins That Actually Matter
At Enerjazz, I learned to find signal in small wins. Not because positivity is good for morale, but because small wins are the only leading indicators you have when lagging indicators (revenue, growth) are still months from materialising.
The first time a piece of content I wrote brought in an inbound inquiry — that mattered. Not because of the revenue it might eventually represent, but because it was proof that the thing I built worked. It validated the direction. In an environment where you’re making decisions with incomplete data constantly, any validation is navigational.
I’ve since carried this into how I evaluate startups at Delhi Angels. When I’m sitting across from a founder, I’m not just looking at their numbers. I’m looking at whether they can identify their leading indicators — the small wins that tell them they’re moving in the right direction before the big metrics confirm it. Founders who can do this tend to navigate the hustle without losing themselves in it.
What I’d Tell Someone Starting Out
Don’t optimise for comfort. The periods of maximum discomfort at Enerjazz — the weeks where I had no idea what I was doing and no one to ask — produced the most compressed learning of my career. The chaos was the curriculum.
Build systems obsessively, even when you think it’s too early. The cost of not having a system compounds fast. A 15-minute daily standup note saved us hours of alignment meetings. A shared doc with vendor contact details saved repeated Slack threads. These feel trivial when you set them up. They feel essential six weeks later when someone new joins and can get up to speed in an afternoon instead of a week.
And lastly: the hustle is real, but it has a direction. Make sure you know what direction you’re hustling toward. Effort without clarity is just exhaustion.
Related reading: How I Evaluate Early-Stage Startups — the framework I developed after moving from operator to ecosystem builder and reviewing 100+ startups at Delhi Angels. Or: Inside Delhi NCR’s Startup Ecosystem — the broader landscape of events, capital, and founders in the region.