When 60–80-Hour Weeks Feel Unrealistic: A Founder’s Guide to Working Enough

You do not need to copy someone else’s working week

If you hear founders talking about 60-, 70-, or 80-hour weeks and wonder how that is possible, you are not failing a test of commitment. You are noticing that time and energy have limits.

There is no universal number of hours a startup founder should work. Your available capacity, business model, funding, stage, health, and responsibilities outside work all matter. So does what someone counts as work: focused execution, travel, networking, or checking messages throughout the evening.

The useful question is not, “How do I reach 80 hours?” It is, “What working rhythm gives this business a credible chance without depending on a pace I cannot maintain?”

Set a realistic baseline, not an aspirational maximum

Start with the hours you can reliably work across an ordinary month—not the most you could survive during an emergency.

If that is roughly 40 hours a week, use 40 as your planning baseline. This is an example, not a guarantee that every startup can achieve every goal within that schedule. A limited schedule may require narrower scope, a longer timeline, more support, or a different business approach.

Build your baseline around:

• Sleep, meals, movement, and essential personal responsibilities.
• Your actual capacity for concentrated work.
• Time for administration, team support, and unexpected problems.
• A clear end to most working days.

Do not allocate every available hour in advance. A calendar with no room for surprises is already overcommitted.

If you have a co-founder, discuss this explicitly. Different working hours are not automatically unfair, but unspoken assumptions about availability often create resentment.

Plan around outcomes before adding hours

A long week can contain substantial effort without moving the business forward. Before expanding your schedule, identify what your current stage actually requires.

Ask three questions:

1. What must become true in the next four weeks? This might be validating demand, delivering a paid pilot, or resolving a cash-flow problem.
2. What is the main constraint? Is progress limited by customer access, product reliability, a hiring gap, or slow decisions?
3. Which work genuinely requires me? Separate founder judgment from tasks someone else could own, simplify, or stop.

Choose one to three weekly outcomes connected to that constraint. “Spend more time on sales” is vague. “Complete five customer discovery conversations and decide which problem to test next” gives the week a purpose.

If those priorities cannot fit your available hours, make the trade-off visible. Reduce scope, change the deadline, or secure help where feasible. Do not quietly make your evenings the solution to every planning problem.

Audit your week without turning it into another performance test

For one ordinary week, record your working time in rough categories. Fifteen-minute precision is unnecessary.

Use four categories:

• Progress: Work directly supporting the current business priority.
• Maintenance: Necessary operations, administration, and team coordination.
• Rework: Fixing unclear decisions, incomplete handoffs, or avoidable mistakes.
• Drift: Unfocused browsing, repeated inbox checking, or meetings without a clear purpose.

Review the pattern with curiosity rather than self-criticism. Some maintenance is essential, and not every conversation produces an immediate deliverable.

Then choose one practical change: remove a recurring meeting, batch administrative work, clarify a teammate’s decision authority, or protect a daily focus block. The goal is not to squeeze more output from every minute. It is to stop spending scarce capacity on preventable friction.

Treat intense periods as exceptions with an exit

Some startup situations genuinely demand additional work. A critical outage, a time-sensitive financing process, or a major launch may disrupt your normal rhythm.

Before accepting a longer week, define:

• The reason: What specific outcome requires additional effort?
• The endpoint: When will this sprint stop or be reassessed?
• The trade-off: What other work will pause?
• The recovery: What lighter commitments will follow?

Protect essential rest even during a sprint. If every week is exceptional, investigate the underlying operating model: scope, staffing, promises, pricing, or decision bottlenecks. Recurring overload is not solved simply by calling it ambition.

Review whether the pace is working

At the end of each week, assess both business progress and personal capacity:

• Did the most important outcome move forward?
• What remained undone, and does it still matter?
• Am I recovering between working days?
• Is this schedule creating repeated mistakes, irritability, or conflict at home?

A manageable week does not guarantee business success, just as an exhausting week does not prove effectiveness. Use what you learn to adjust both the workload and the business plan. Persistent exhaustion or sleep problems deserve attention from a qualified healthcare professional, not just a productivity reset.

You can take your company seriously without making extreme hours your identity. Your responsibility is to make deliberate choices about what the business needs—and what you can realistically provide.

For practical reflection and clearer ownership, explore Jessica Hill Holm’s workbook Lead Lagom (Scaling with trust, clarity and responsibility.). If you want personal support shaping a realistic founder working rhythm, consider a coaching call with Jessica.