Time Management for Indie Hackers: Deep Work & Focus

Deep work for solo founders

Deep work is uninterrupted, focused time dedicated to cognitively demanding tasks that require your full mental capacity. Cal Newport, author of Deep Work: Rules for Focused Success in a Distracted World, defines it as “professional activity performed in a state of undistracted concentration that pushes your cognitive abilities to their limit.”

For indie hackers, deep work is the most valuable use of time—it’s when you build product features, design architecture, solve complex bugs, and create meaningful progress. Unlike shallow work (emails, meetings, admin tasks), deep work produces measurable output and compounds over time. The challenge: deep work is fragile. A single Slack notification or context switch can derail your focus for 15–25 minutes.

Why deep work matters for solo founders:

You have limited time; every hour counts
Complex technical work requires sustained focus to avoid mistakes
Shipping features faster = validating ideas sooner
Deep work sessions build momentum and confidence

Why context switching kills productivity

Context switching—jumping between tasks, tools, or projects—is the #1 productivity killer for developers. Research shows it takes an average of 23 minutes to regain full focus after an interruption.

Example: You’re 30 minutes into debugging a payment integration (deep work). A Slack message pings. You respond (5 minutes). You return to the code, but now you’ve lost the mental model. You spend 20 minutes re-reading your notes. You’ve lost 25+ minutes of deep work to a 5-minute distraction.

Types of context switches to avoid:

Notifications: Slack, email, phone, social media
Meetings: Especially unscheduled or back-to-back calls
Task switching: Jumping between feature development, support, and admin work
Tool switching: Moving between code editor, documentation, browser tabs

Techniques for deep work

Time blocking

Time blocking is scheduling specific blocks of time for specific types of work. You treat these blocks like immovable calendar events.

How to implement:

Identify your peak energy hours (usually 8 AM–12 PM for most people)
Block 90-minute sessions for your most important work
Schedule meetings, async work, and breaks around these blocks
Use calendar visibility to protect these blocks from others

Example: Your calendar shows “Deep Work: Feature Building 9:00 AM–10:30 AM” (visible to team) so no one schedules over it.

Pomodoro & 90-minute focus cycles

The Pomodoro Technique (invented by Francesco Cirillo) breaks work into 25-minute focused intervals, followed by 5-minute breaks. However, many developers find 90-minute deep work cycles more natural, based on research by Kleitman’s ultradian rhythms.

90-minute cycle structure:

90 minutes: Uninterrupted deep work
5–10 minutes: Break (stretch, water, walk)
90 minutes: Another cycle
15–20 minutes: Longer break (lunch, admin tasks)

Why 90 minutes? Your brain naturally operates in ~90-minute cycles of high focus followed by a dip in energy. Working with this rhythm (not against it) maximizes flow and minimizes burnout.

Tools for time tracking:

Toggl Track – Simple, free time tracking
Pomodone.io – Combines Pomodoro with task management
Be Focused – iOS/macOS timer

“Do Not Disturb” & app blockers

DND (Do Not Disturb) modes silence notifications while you work. Most modern operating systems and communication tools support this.

Setup across tools:

Slack: Set status to “In Deep Work” with DND until a specific time
macOS/iOS: Enable Focus mode (e.g., “Work Focus” that allows only calls from favorites)
Gmail: Enable “Scheduled send” so you don’t respond impulsively
Calendaring: Block “Focus Time” on your calendar so others see you’re unavailable

App blockers prevent access to distracting websites and apps during work sessions.

Popular blockers:

Freedom – Cross-platform (Mac, Windows, iOS, Android)
Cold Turkey – Aggressive blocker; hard to override
FocusMe – Website + app blocking with app limits
LeechBlock NG – Free, open-source browser extension

Sample weekly schedule for indie hackers

This schedule maximizes deep work while accommodating necessary meetings, marketing, and admin tasks.

Day	Morning	Afternoon	Notes
Monday	90 min deep work (feature building)	60 min meeting block, admin	Ease into the week
Tuesday	90 min deep work (feature) + 90 min deep work (design/architecture)	30 min async sync, light tasks	Highest productivity day
Wednesday	90 min deep work (bugfix + polish)	90 min marketing block (content, social, outreach)	Balance shipping + visibility
Thursday	90 min deep work (documentation, refactoring)	90 min outreach (emails, partnerships, community)	Prepare for Friday review
Friday	Review, analytics, retrospective, light dev	Flexible / buffer time	Reflect and plan next week

Total deep work: ~540 minutes (~9 hours/week) of focused, uninterrupted feature development and architecture work.

Customize for your rhythm:

If you’re a night owl, reverse the schedule
If you work 4-day weeks, compress this into Mon–Thu
If you have support duties, add a 1-hour “support block” daily (e.g., 3–4 PM)

Tools to use

Calendar & time blocking

Google Calendar – Free, integrates with Gmail, easy sharing
Fantastical (macOS/iOS) – Faster calendar entry with natural language
Notion Calendar – Free Notion integration
Calendly – Let others book meeting slots (vs. endless back-and-forth)

Distraction blockers

Freedom – Block websites, apps, and the entire internet
Cold Turkey – Nuclear option; once started, can’t be disabled
FocusMe – App limits and internet blocking for accountability
LeechBlock NG – Free browser extension for website blocking

Work timers & time tracking

Toggl Track – Free time tracking; see where your time goes
Be Focused – Pomodoro timer with task management
Forest – Gamified focus timer (stay focused, grow a virtual forest)
Clockify – Free unlimited time tracking

Communication & async work

Slack – Use status + DND; set “working hours”
Loom – Record quick video walkthroughs instead of meetings
Async Agile – Async standup + updates (no sync meetings required)

Implementation roadmap

Week 1: Foundation

Audit your current schedule; identify your peak energy hours
Block three 90-minute deep work sessions on your calendar (protect them like meetings)
Turn on DND/Focus mode across Slack, email, and your phone during deep work
Pick one app blocker and install it (e.g., Freedom, Cold Turkey)

Week 2–4: Optimize

Track time with Toggl to see where hours actually go
Batch your meetings into 1–2 days (e.g., all calls on Tue & Thu)
Move all notifications out of your default view (Slack sidebar hidden, email notifications off)
Experiment with 90-minute vs. Pomodoro cycles; pick your rhythm

Month 2: Scale & protect

Communicate your deep work schedule to your team (e.g., “I’m focused 9 AM–10:30 AM; async only”)
Set up a second “support/admin” calendar so people book around your deep work blocks
Build accountability: track features shipped, bugs fixed, or PRs merged per week
Review weekly: Did your deep work sessions produce output? Adjust accordingly.

Action items

This week: Schedule three 90-minute deep work sessions and track output:
- Features shipped or PRs merged
- Bugs fixed
- Architecture designed
- Prototype completed
Next week: Measure your focus:
- Use Toggl to log time per task
- Note interruptions (how many Slack messages, etc.?)
- Assess quality of work (fewer bugs? Faster code?)
Ongoing: Weekly retrospective (Friday):
- How many deep work sessions did you complete?
- What blocked you (meetings, notifications, energy)?
- What will you change next week?