I run three companies. I am twenty-one years old. I have not slept through an alarm in four years because I set four of them. I have missed events, cancelled plans, and explained myself poorly in meetings with people twice my age who were deciding whether to trust me with their business. I have made exactly the mistakes you would expect someone my age to make, plus several I didn't expect at all.
I am writing this not because I have figured it out — I haven't — but because I wish someone had written it honestly for me when I was eighteen and making my first real business decisions with no frame of reference except optimism.
The thing nobody tells you about starting young
Everyone talks about the advantages of starting young. You have energy. You have time to recover from failure. You have nothing to lose. These are all true.
What nobody mentions is the credibility gap. You walk into a room and people are doing the math: how old is this person, how long have they been doing this, can I trust them with my money or my infrastructure or my data?
The answer, for a twenty-one-year-old running a fiber ISP, is often: not yet. You spend a disproportionate amount of time earning the right to be taken seriously. The work has to be better. The follow-through has to be faster. The communication has to be clearer. Because you don't have twenty years of professional reputation to borrow against.
This is not unfair. It is just the situation. I would rather know it clearly than be surprised by it at every sales meeting.
On running three things at once
This is not as heroic as it sounds. The honest version is that ViberNet, OpenLoop, and StarterHost share significant infrastructure — literal infrastructure in some cases, but mostly the more valuable kind: trust networks, vendor relationships, technical know-how, operating procedures. Running three companies is more efficient than running one, then restarting from zero on the second, then restarting again on the third.
But it is also harder in ways I underestimated. Context switching is expensive. Moving from a RADIUS configuration problem at ViberNet to a client delivery discussion at OpenLoop to a support escalation at StarterHost, all in the same morning, degrades the quality of thinking applied to each. I've learned to batch by context — network operations in the morning when I'm fresh, calls and decisions in the afternoon, writing at night.
I've also learned that most things that feel urgent are not. The escalation that arrives at 10pm is almost never as bad as the notification suggests. I check it, triage it, and if it isn't actively on fire, I handle it in the morning. I was not good at this at nineteen. I am marginally better at it now.
What I've actually learned
Discipline matters more than motivation. Motivation is a feeling, and feelings change. On the days when it's raining in Srinagar and three things need fixing and no one is going to handle them except me — motivation is not present. Discipline is a system that runs whether the feeling shows up or not.
Specificity is everything. Vague promises are easy to make and impossible to keep. "We'll get this to you soon" is a sentence that has created more problems for me than any technical failure. Specific commitments — "by Thursday at 3pm, I'll send you the configuration file" — are harder to make but actually deliverable.
Most problems are communication problems. The router that's supposedly broken is usually a miscommunicated expectation. The client who seems angry is usually a client who feels uninformed. I solve more problems with a well-written message than with an hour of debugging.
Read the actual documentation. Not the tutorial. Not the StackOverflow answer. The documentation. This has saved me more time than any other single habit, and it took me embarrassingly long to develop.
The part I'm still figuring out
I don't know yet how to grow beyond what I can personally oversee. The companies are at a size where I can still touch most decisions. At some point that stops working, and the question of who to trust with what becomes critical. I've hired wrong before — not dishonest people, just people whose working style didn't fit what the role actually required. That's an expensive mistake when you're small.
I also don't know how to rest. I take this seriously as a problem to solve because I've watched the compounding effects of sustained exhaustion on decision quality, and they are not good. I'm still figuring out what recovery actually looks like when you own the companies.
I'm twenty-one. I have time to figure it out. That's the real advantage of starting young — not the energy, not the risk tolerance, but the fact that the mistakes I'm making now, I'm making while there's still room to correct them.
Still learning. Still here.