Most business rules waste time—stay small and ship incomplete

1

Plans are expensive fiction

Multi-year business plans are guesses whose accuracy collapses the further out they reach, so time is better spent on a working version than on locking early assumptions.

Fried and Heinemeier Hansson open by attacking the demand for a detailed plan before a serious business can start. A plan dresses guesses as a document; markets and customers move faster than the paper can. The further the horizon, the less the projection is worth.

They also dismantle the excuse that an idea will not work in the real world. Every product that exists was once dismissed that way by people comfortable with the status quo. Real world, in their telling, is other people’s limits, not a fixed law.

Instead they recommend deciding at the last responsible moment, when information is richest. Certainty about the future is an illusion consultants get paid to manufacture. Money and hours go further on something that runs than on a description of what might run.

In practice: 37signals never wrote a formal business plan for Basecamp; it began as an internal tool for the founders’ own scheduling mess while they ran a design consultancy, and real usage showed what mattered.

2

Stay small on purpose

Chasing rapid growth and long hours makes companies fragile and judgment worse; deliberate smallness protects speed, focus, and profit as the real health metric.

Growth and overwork are habits adopted without asking whether they serve the goal. Workaholism often signals bad workflow disguised as virtue—midnight hours usually fix problems that should not exist. Long days also crowd out the rest that produces good judgment, so a tired team makes more bad decisions while working harder.

Bigger is not automatically better. A small company can move faster, skip layers of managers, and stay profitable on a smaller base because profit—not headcount or valuation—is the measure. Outside investment imports someone else’s priorities, usually a faster exit or growth path than founders would choose.

Most pressure to scale and grind comes from imitating other firms, not from evidence of better outcomes. Staying small is presented as strategy that defends the qualities that made the company worth running.

In practice: 37signals kept staff under twenty for years even as revenue grew, serving existing customers well instead of chasing new lines or acquisition.

3

Build from your own pain

The surest product ideas come from founders solving a problem they personally feel, because firsthand depth beats surveys and gives an instant test of one.

After rejecting distant plans, the authors argue the best source of an idea is a problem you already have. You already know which annoyances matter. No focus group matches that depth, and you are a built-in test group of one—you can tell almost immediately whether a change helps or hurts.

Customers describe symptoms, not solutions. Acting on every request bloats the product until it serves no one well. Founders should trust informed judgment checked against real usage, not every voiced opinion.

The claim is narrow: it works best for tools and problems the founders are close to, and says little about products for populations unlike the builders. Still, it reframes know your customer as be your customer wherever possible.

In practice: Basecamp exists because 37signals, then a design consultancy, was drowning in email and spreadsheets managing client projects; they built for themselves first and later saw other small companies had the same mess.

4

Half a product, finished

Cutting scope beats adding features; a smaller complete thing ships faster and keeps a clear identity that a cluttered tool loses.

Once the problem is clear, resist solving every adjacent one. The authors want half a product, not a half-finished one—smaller and whole rather than larger and incomplete. Every feature request meets a default no, because isolated yeses collectively turn focus into clutter.

Constraints of time, team, and budget are forcing functions, not obstacles. They make you choose what matters instead of doing everything adequately. Scarcity is useful pressure; more hiring or funding is not the automatic fix.

A product’s boundaries, not its feature count, give it identity. The corrective is aimed at the instinct that better always means more.

In practice: Early Basecamp shipped without file attachments, time tracking, or dozens of features rivals like Microsoft Project treated as standard; fewer options meant less to learn and less to maintain.

5

Launch before it feels ready

An imperfect live product teaches more, faster, than endless internal debate; good enough beats polishing that avoids the real test of demand.

After building something small and incomplete, launch before it feels ready. A live product generates real feedback; a hypothetical one only generates more opinions. Good enough is a legitimate standard. Perfectionism is reframed as procrastination that dodges finding out whether anyone wants the thing.

Decisions inside the company are intentionally temporary. A choice this month can reverse next month once usage replaces guesswork. An early flawed release is not failure but the fastest information, cheaper than any focus group.

This loops back to the planning critique: if plans are guesses, shipping quickly tests the guess against reality instead of refining it in isolation. The accepted tradeoff is that some early customers see bugs a cautious firm would have caught; the bet is that goodwill lost to roughness is smaller than time saved learning early. The claim holds best for software where updates are cheap.

In practice: The authors treat early roughness at 37signals as cheaper than conference-room guessing, fixing problems real users report rather than imagined ones.

6

Honesty is the marketing

Effective marketing is transparency and generosity in daily operations—selling byproducts, showing personality, and underdoing rivals—not a budget line after launch.

Marketing is not a department. The whole company does it by how it operates. Selling byproducts means turning writing, code, and expertise the firm already produces into public material that builds an audience before there is anything to sell.

Decommoditize by putting a visible point of view into the product. A tool indistinguishable from rivals competes only on price; one with a distinct voice earns loyalty. Underdoing the competition means winning by doing less, more clearly, for customers who find simplicity a relief.

Openness about pricing, decisions, and mistakes is an asset on the theory that customers reward companies they understand. The approach fits firms selling trust and expertise more than pure commodities.

In practice: 37signals published thinking on Signal v. Noise and gave away Ruby on Rails as open source; both built trust and visibility no ad could buy because they demonstrated competence.

7

Guard unbroken attention

Sustained concentration, not longer hours or more meetings, is the scarce resource that produces good work; interruption is a structural cost to cut by default.

Most workplaces destroy unbroken attention. A one-hour meeting with ten people burns ten collective hours for a decision two people could often make in ten minutes. Meetings multiply because they are easy to schedule and feel like progress even when they produce none.

Open offices and constant messaging break focus every few minutes and force restarts. The fix is structural: quiet stretches where interruption is simply not allowed beat asking people to concentrate harder inside noise.

This links to the rejection of workaholism. Long hours often compensate for a day shredded by interruptions, so the cure for overwork is fewer disruptions in the hours already worked. Some coordination still needs live talk; blanket suspicion can underserve highly collaborative work.

In practice: 37signals instituted no-talk afternoons so interruption was forbidden rather than merely discouraged.

8

Hire only after real pain

Add people only when understaffing is acute and sustained; do the job yourself first, prefer clear writers and trial work, and treat culture as daily rewards not wall statements.

Most firms hire too early, adding cost and complexity before extra capacity is proven necessary. Urgency clarifies the actual missing skill better than a generic title. Doing the work yourself first, even badly, grounds the job description and the evaluation in real tasks.

Clear writing signals clear thinking across roles. A short paid trial reveals how someone works better than interviews or résumés. Culture is the pattern of what the company actually rewards and tolerates; new hires absorb that immediately, whatever onboarding claims.

The advice assumes a firm flexible enough to delay hiring without losing the market—harder in winner-take-most or capital-heavy settings.

In practice: The authors’ rule is wait until the pain of not having someone is genuine and lasting, then hire for that specific hurt rather than anticipated growth.

9

Fail in public on purpose

Admitting fault quickly and over-communicating during problems builds more loyalty than hiding errors or delivering scripted vagueness.

Even solid products eventually fail someone. The instinct to minimize or hide a mistake is backward. Customers forgive outages and bugs more readily than darkness or evasive technical language.

Over-communicate: post updates before customers ask, explain plainly what broke and why, take visible responsibility. Answer support personally rather than with templates; a specific human reply builds more trust than a fast generic one.

This closes the loop with shipping early. A company that iterates in public will break things, so honesty is structural, not optional politeness. Trust is compounding capital spent quickly by one cover-up. The chapter rests mainly on the authors’ own downtime anecdotes and says little about legal or regulatory constraints larger firms face.

In practice: At 37signals, handling downtime with plain public explanation and personal support replies was treated as trust-building rather than reputation risk.