Running a Company While Finishing Your Final Year: What Actually Has to Give

Nobody tells you which hours disappear first. You assume it's sleep, and it is, at first, but sleep isn't actually the resource that runs out. What runs out is the slack in your schedule: the buffer that used to absorb a bad day without consequence. Once that's gone, everything downstream gets more fragile, and that's the real cost of running a company through final year, not the raw hours.

A final year of a BTech program and an early-stage software company both behave like they deserve full-time attention. Coursework has deadlines that don't move for your business, and clients don't pause because exams are coming. Treating both as full priorities at once isn't actually possible, something gets explicitly deprioritized, or it gets deprioritized by default in a way you didn't choose.

What worked was picking, in advance, which category of task gets protected time no matter what, instead of relitigating priority every time a conflict landed in my inbox. For me that meant protecting deep technical work, the actual building, and letting lower-stakes academic tasks absorb the schedule pressure instead. That only works if you're honest about which tasks are genuinely high-stakes versus which just feel urgent in the moment; a deadline-driven assignment and a client bug report both feel urgent the second they arrive, and treating them as equally important by default is how a schedule quietly erodes.

Spontaneity went first, saying yes to something unplanned stopped being free, because there was no slack left to absorb it. Breadth of academic engagement shrank too, I stayed on top of what actually mattered for grades and core understanding, and stopped going beyond that the way I might have otherwise. Social bandwidth got rationed, though not eliminated; community leadership work stayed protected specifically because it doubled as genuine commitment and professional network, while purely social time was what quietly gave way.

If I were starting over, I'd protect the same thing again: real building time over academic breadth. A degree measures whether you cleared a bar. A product measures whether something real actually works. Under time pressure, evidence that something works has compounded far more than a few extra points on a module that was never going to change my trajectory either way.