📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Newport takes Graham's idea and turns it into a schedule you can actually run. He lays out the moderate version (block Monday/Wednesday/Friday as meeting-free deep-work days, hold email and Slack to the end of the day) that maps straight onto your build-day / people-day / sales-day split. His point that almost no team runs this way despite everyone agreeing it works is exactly why a founder has to impose it on themselves, no one will hand you the blocks.
From
calnewport.com
by Cal Newport
8 min read
- Slack and email cause the same fragmentation as meetings; protecting whole days means silencing the pings, not just declining calls
- A concrete dual-schedule template: alternate no-meeting maker days with open manager days rather than mixing both every day
- The reason maker schedules are rare is cultural convenience, so the discipline to batch modes has to come from the founder, not the org
Open
calnewport.com →
📖 Book
✓ Link checked
Paid
Beginner
Why we picked it
Built around picking one Highlight per day and defending it, which maps cleanly onto shipping one small thing in every build block. The tactics are small and practical, like closing notification loops and designing your environment so distraction is harder. It is less about grand productivity systems and more about winning one day at a time, which is what solo shipping actually is.
From
Jake Knapp and John Zeratsky
by Jake Knapp and John Zeratsky
Book, ~300 pages
- Choose one daily Highlight and protect the time for it
- Remove distraction triggers rather than relying on willpower
- Design each day so the important build happens before the noise starts
Open
jakeknapp.com →
📄 Article
✓ Link checked
Freemium
Intermediate
Why we picked it
A collection of what founders and operators actually do to protect time, including treating the calendar as a strategy document and blocking the important work before the week fills up. You will find specific, copyable rhythms like mornings for building and afternoons for calls. Concrete enough to redesign your own week the same day you read it.
From
Lenny's Newsletter
by Lenny Rachitsky
Long-form newsletter post
- Block the work that matters before meetings claim the calendar
- Separate days or halves into build time versus reactive time
- Audit recurring commitments and kill the ones with no reason to exist
Open
lennysnewsletter.com →
📖 Book
✓ Link checked
Paid
Intermediate
Why we picked it
The definitive manifesto for building a 'calm company', remote-friendly, sustainable, and free of chronic overwork, from a team that's lived it for two decades. Essential for founders designing culture and operations.
From
37signals
by Jason Fried & David Heinemeier Hansson
~232 pages
- Sustained output comes from calm and focus, not permanent crunch
- Default to async, protect deep work, and kill the always-on expectation
- Reasonable hours and a livable pace are a competitive advantage, not a weakness
Open
amazon.com →
📖 Book
✓ Link checked
Free
Intermediate
Why we picked it
Basecamp's battle-tested, opinionated system for shipping meaningful work in fixed cycles without endless backlogs, a primary source, free in full. The antidote to over-planning your roadmap.
From
Basecamp / 37signals
by Ryan Singer
free online book
- Work in short cycles with a cool-down between them.
- Fix time, vary scope, use 'appetites,' not estimates.
- Make bets, not plans; no runaway backlog.
Open
basecamp.com →
📖 Book
✓ Link checked
Paid
Beginner
Why we picked it
The single best thing ever written on customer conversations. It teaches you to ask about the customer's life and past behaviour, not your idea, so you can't be lied to. If a founder reads one thing before talking to a single customer, it's this.
From
momtestbook.com
by Rob Fitzpatrick
~130 pages
- Talk about their life, not your idea.
- Ask about specifics in the past, not opinions about the future.
- 'That's so cool, I'd totally buy it' is a compliment, not data, dig for commitment and evidence.
Open
momtestbook.com →
📖 Book
✓ Link checked
Paid
Beginner
Why we picked it
Lavingia's whole thesis is the one you need as a part-time founder: start with a community you already know and belong to, then build the smallest thing that solves a real problem for them. He built Gumroad this way and argues you should charge before you build, which is exactly how you validate a beachhead without quitting your job. It is a calm, anti-hype read that respects the fact that you have limited hours and no appetite to raise money.
From
Penguin Random House
by Sahil Lavingia
288 pages
- Pick a community you already have access to, so your first customers are people you can actually reach.
- Solve one specific problem for that group instead of chasing a broad market.
- Charge early and stay profitable, so the business survives on the hours you can spare.
Open
penguinrandomhouse.com →
✍️ Essay
✓ Link checked
Free
Beginner
Why we picked it
Barry built his career on a daily writing streak, and his story is the clearest argument for shipping one small thing every day rather than waiting for a clear week. It shows how tiny consistent output compounds into something that would have felt impossible as one big project. Motivating and specific about how the chain of daily shipping actually works.
From
Nathan Barry
by Nathan Barry
~1,200 words
- Small daily output compounds into results big pushes cannot match
- A daily streak removes the wait for the perfect uninterrupted week
- Consistency, not intensity, is what carries a solo builder
Open
nathanbarry.com →
✍️ Essay
✓ Link checked
Free
Beginner
Why we picked it
Solo weekly shipping is a long game, and this short essay makes the case that endurance, showing up week after week, is what eventually gets your work seen. Useful on the low weeks when a support fire ate your afternoon and shipping felt pointless. A quick read to reset your expectations toward the long arc.
From
Nathan Barry
by Nathan Barry
~1,000 words
- Most results come from enduring past the point others quit
- Keep shipping through slow, invisible stretches
- The compounding only pays off if you stay in the game
Open
nathanbarry.com →
📖 Book
✓ Link checked
Paid
Beginner
Why we picked it
A punchy, contrarian classic on building a lean, sane, profitable company from the founders of Basecamp. It's the antidote to hustle-culture folklore about how startups must operate.
From
37signals
by Jason Fried & David Heinemeier Hansson
~288 pages
- Small teams, less process, and shipping beat planning theatre
- Say no to most things and protect focus
- You can build a great company without following the standard playbook
Open
amazon.com →
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.
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 →
Why we picked it
The definitive case that undistracted, focused work is both increasingly rare and increasingly valuable, a direct competitive advantage for founders drowning in shallow busywork.
From
calnewport.com
by Cal Newport
long
- Deep work, cognitively demanding, distraction-free focus, is a rare and valuable skill
- Schedule long uninterrupted blocks and ruthlessly eliminate context-switching
- Shallow work feels productive but rarely creates real value
- Rituals and boundaries (fixed hours, notification cutoffs) make depth repeatable
Open
calnewport.com →
