Founder & Scenarios

How do I manage my own time and priorities with no boss, no team, and everything on fire at once?

A starting point

Give yourself the structure a manager would. Pick one needle-moving priority per day and protect a two to three hour deep-work block for it before you touch email or WhatsApp, because reactive founders drown in other people's urgency. Batch shallow work into fixed windows, say no to almost everything, and review weekly against goals so you notice when you are busy but not moving. Motion is not progress, and no one else will catch the difference for you.

Go deeper

Hand-picked from around the web, each with a note on why it earns your time.

3 resources 2 link-checked Listen Read

Listen

🎧 Podcast
✓ Link checked Free Intermediate

Why we picked it This is a founder who ran Gumroad down to literally one person (himself) after raising 8 million dollars, and talks candidly about what he did with his time when everything was on fire and he was alone. His answer is brutal prioritization: he made the company his last priority of the day, did 'the bare minimum' on purpose, and the business kept growing. It is the honest first-hand case that motion is not progress, and that saying no to most work is what lets a solo founder survive.

From Aspiring Billionaire to Indie Hacker with Sahil Lavingia of Gumroad

On Indie Hackers by Sahil Lavingia (with Courtland Allen) 1 hr listen

  • Running solo, Lavingia deliberately did the bare minimum on Gumroad and it still grew; frantic busyness was not what kept the business alive.
  • He picked one narrow focus (creators just getting started) and refused everything else, including tempting enterprise deals, so his limited hours went to one needle-moving thing.
  • Deprioritizing the startup on purpose (writing, gym, painting first) is what made the solo path sustainable rather than a slow burnout.
Open indiehackers.com

Read

✍️ Essay
✓ Link checked India Free Intermediate

Why we picked it India's most respected bootstrapped founder admits that until 2019 he was answering email at 3 AM, staying late, and working weekends, and then consciously rewired his own habits: going home early, dumping stray thoughts into Google Keep instead of firing off a 3 AM email to the team. It is the rare Indian founder writing honestly about defending his own pace, and it proves the point that structure is something you impose on yourself, not something the always-on default gives you.

Why 'a nice place to work' doesn't just happen

From Nithin Kamath (Zerodha) on Substack by Nithin Kamath 6 min read

  • Kamath ran on a 3 AM-email, weekends-at-the-office pattern for years before recognizing it as a real burnout risk and stopping it deliberately.
  • His concrete fix: capture stray thoughts in a note (Google Keep) instead of interrupting yourself and others in real time. A simple, copyable batching habit.
  • The pace you set is the pace everyone copies; as a solo founder that is only you, so changing your own habits is the whole intervention.
Open nithinkamath.substack.com
📄 Article
Free Beginner

Why we picked it The essay that explains why one badly-placed meeting can destroy a founder's entire day of building, and what to do about it. Essential mental model for anyone who both makes and manages.

Maker's Schedule, Manager's Schedule

From paulgraham.com by Paul Graham short

  • Makers need time in half-day units; managers slice time into one-hour appointments
  • A single meeting can wreck a maker's whole afternoon by fragmenting the block
  • Batch meetings into designated windows to protect long stretches of deep work
  • Founders who both build and manage must consciously switch between the two modes
Open paulgraham.com

People also ask