Launching While Still in School Without Burning Out
Founders who launch their companies while still in school usually arrive at the launch in one of two states.
The first state is rested, intentional, and ready to handle whatever comes next, and this state is rare.
The second state is tired, overcommitted, and quietly worried that they will not survive the next semester, and this state is much more common, because most students who launch a company while in school have spent the months leading up to the launch carrying too much, sleeping too little, and accepting too many simultaneous demands on their time.
The launch then arrives as a moment that should be celebrated but feels instead like the start of a phase the founder is not sure they can endure.
This piece is about how to launch while still in school without arriving at the launch already burned out, and it is meant for founders in the months before launch as well as for founders in the early weeks after, because the patterns that produce burnout in this period are predictable and most of them can be addressed before they take hold.
The pattern that produces burnout
The pattern that produces burnout in student founders has three reinforcing parts.
The first is that the founder has not yet learned to say no to commitments that pre existed the company, since the demands of student life are constant and feel non negotiable.
The second is that the founder treats the company as an additional commitment layered on top of student life, rather than as a replacement for some of the things student life has already asked of them.
The third is that the founder relies on sleep, exercise, and unstructured time as the slack that absorbs the new load, and so the slack disappears first while the visible commitments remain intact.
The result is a schedule that looks reasonable from the outside, because all the visible activities are still happening, while the founder is privately running on insufficient sleep, no time to think, and no room to recover from any setback. By the time the launch arrives, the founder has often been operating in this state for months, and the launch consumes the last of the reserves rather than energizing the work.
The conversation worth having with yourself
The single most useful thing a student founder can do before launching is to have an honest conversation with themselves about what they will stop doing in order to make the launch possible.
The conversation is uncomfortable because it asks you to give up things that feel important, but it is necessary because the alternative is to give them up anyway, less deliberately, and at a higher cost.
The list of candidates for stopping usually includes some clubs or extracurriculars that no longer serve the work you actually care about, some social commitments that have become routine rather than meaningful, and some classes or academic activities that you can either drop, audit, or take in a lighter form. The list will be different for every founder, and the right choices depend on your specific obligations, but the principle is the same, which is that the time and energy for the launch has to come from somewhere, and choosing that somewhere deliberately is much better than letting your body choose it for you by collapsing the parts of your life that you cannot maintain.
The schedule that survives a launch
The schedule that survives a launch is not the one that maximizes hours of work, since longer hours do not produce better launches at the early stage, but the one that protects the small set of things that keep the founder functioning across months. The list of protected things is shorter than founders expect.
The first protected thing is a non negotiable bedtime four or five nights a week, since sleep is the resource that erodes most quietly and most expensively.
The second is at least one form of regular physical movement, whether a walk, a gym visit, or anything else, since physical activity is one of the cheaper interventions for cognitive function and mood, and most founders who skip it find that their thinking becomes brittle in ways they did not anticipate.
The third is at least one weekly social interaction that has nothing to do with the company, since complete absorption in the work produces a kind of isolation that quietly damages your judgment over time.
These three things, held loosely but consistently, are usually enough to keep a founder functional through a launch and the months after, and the founders who hold them tend to look back on the launch period as challenging but manageable rather than as a season they barely survived.
What to do about the academic side
The academic side of student life during a launch is often more flexible than founders assume, and the small adjustments available within most academic systems can make a meaningful difference. Reducing your course load by one class for the semester of the launch, choosing easier electives, taking incomplete(s) if your school allows them, or moving to a part time status for a single semester are all options that founders sometimes consider too late.
These options carry small costs in terms of graduation timing or transcript appearance, but the costs are almost always smaller than the cost of trying to maintain a full academic load through a launch and discovering, after the fact, that you damaged your health or your relationships or the launch itself in the process. The conversation with academic advisors about these options is usually less difficult than founders expect, since most advisors have seen students try to do too much and would rather help you make a deliberate adjustment than watch you collapse later.
The first six weeks after launch
The first six weeks after launch are a specific kind of vulnerable period, since the launch itself often produces enough adrenaline that the founder feels fine through the first week or two, only to crash in the third or fourth week when the adrenaline runs out and the actual work of running a live product begins. Founders who anticipate this dip can plan for it, either by reducing other commitments during this period, by scheduling small recovery activities in advance, or by simply expecting the dip rather than being surprised by it.
The work in the first six weeks is mostly about responding to early customers, fixing the small issues that show up only after launch, and resisting the temptation to add new features before you understand how the original ones are working. None of this requires heroic hours, and founders who maintain a reasonable rhythm during this period tend to learn more from the early users than founders who burn through the weeks on adrenaline and then have nothing left to apply what they learned.
A closing thought
Launching a company while still in school is one of the more rewarding things a curious person can do, and it is also one of the easier things to do badly, in the sense of producing a launch that consumes the founder rather than energizing them. The work to avoid that outcome is mostly done before the launch, in the form of honest conversations about what to stop doing, careful protection of the small set of things that keep you functional, and deliberate adjustments to the academic load. Founders who do this work tend to arrive at their launches steady and ready, while founders who skip it tend to arrive depleted, and the difference shows up not in the launch itself but in the six months that follow.
Comments