Why this exists
Most startup advice on the internet is written for traffic, not for the founder who is actually stuck on a specific decision at 11pm. It is fast, shallow, and keeps recycling the same three frameworks.
StartupBook is built the other way around. Each guide is long enough to be useful, narrow enough to actually answer the question in its title, and written for people who have already read the obvious things and want a real answer.
The test we apply to every piece is simple: would a thoughtful founder who already knows the basics still get something out of this? If the answer is no, we don’t publish it.
What you’ll find here
Guides
Long-form pieces on the questions early-stage founders actually get stuck on: how to validate an idea, how to split equity, how to structure a deck, how to read your own metrics. Each guide is written to be the last thing you need to read on that topic before making a decision.
Bookshelf
A short list, not a catalog. The books we keep on the shelf are the ones founders we trust keep returning to a second and third time. Each one comes with a note on when in your journey it is worth reading — and when it isn’t.
Resources
A directory of tools, templates, and communities we have either used ourselves or seen used well by other founders. We pass on most of the things we look at; what stays on this page is what actually held up in practice.
Who this is for
The pieces here are written with a particular reader in mind:
- First-time founders at the pre-seed or seed stage, deciding what to build and how to fund it.
- Technical founders who want to understand the parts of a company they didn’t train for — sales, fundraising, hiring, pricing.
- Solo founders and small teams building durable, profitable businesses rather than chasing a Series A.
- Early employees who want to see the company they joined the way the founders see it.
If you are looking for hustle quotes, daily motivation, or a newsletter that summarizes someone else’s tweets, this is probably the wrong site.
How we write
A few rules we hold ourselves to:
Answer the question in the title
If a guide is called “How co-founders should split equity,” it has to actually take a position on the question by the end. We try not to publish pieces that hide behind “it depends.”
Long is fine; padded is not
Some topics deserve 3,000 words. None deserve filler. If a section isn’t earning its place, it gets cut, even if it took a day to write.
Name the tradeoff
Every interesting decision in a startup has a cost on the other side. Guides here try to name the tradeoff explicitly — what you give up when you pick A over B — rather than pretending one path is obviously right.
Update, don’t republish
When the world changes, we edit the existing guide rather than ship a new “[Year] update.” The URL stays stable; the content stays current.
How the site is built
StartupBook is a plain static site: hand-written HTML, one stylesheet, no build pipeline, no comment system, no popups. A few consequences of that:
- It loads fast, on any connection, without a framework getting in the way.
- There is almost nothing to track you with — analytics is limited to anonymous traffic counts.
- Nothing breaks on a phone, in a slow browser, or behind a corporate proxy.
- Pages stay readable for years. The URL you bookmark today should still work in 2030.
Want to send something in?
A few things we always read:
- A topic you wish someone wrote a real guide on.
- A correction, a stale link, or a number that’s out of date.
- A book that has held up for you over multiple re-reads.