A founder's handbook

The Complete Guide to Building and Launching a Software Startup

From having no idea, to a live product, to a business. Product-agnostic: the sequence is the same whether you're building a SaaS, a marketplace, a consumer app or a developer tool.

54/54chapters written

117,060words

10parts

9sections each

The business before the build

The work that decides whether anything you build matters.

01How Software Businesses Actually WorkBefore you choose what to build, understand what you're choosing between. The business model you pick determines your pricing, your sales motion, your metrics, your funding options, your tea 02Finding and Generating IdeasIdeas are not scarce and they are not valuable. What's scarce is the discipline to kill the bad ones quickly. This chapter is about generating candidates systematically and then trying very 03Market Research and Competitive AnalysisDon't research the market. Research the hole in it. A market size tells you how big the room is; a hole tells you where to stand.04Talking to UsersEveryone tells you to talk to users. Almost nobody tells you that most founder interviews are worthless, because they're designed, unconsciously, to collect compliments.05Validating Demand Before You BuildYou cannot prove your product will make money before you build it. You can prove that money already flows to products shaped like yours, for your customer, and you can make strangers pay you 06Positioning and Product StrategyStrategy is mostly a list of things you refuse to do. Positioning is deciding who you're for, and, unavoidably, who you're not for. Founders who won't make that second decision end up buildi

Defining the product

What you're building, and what you refuse to build.

07Scoping the MVP"Build an MVP" is the most repeated and most misapplied advice in startups. The right question is not "what's the smallest thing I can build?" It's "what's the smallest thing that tests the 08Requirements and RoadmappingWriting down what you're building sounds like bureaucracy until the third time you rebuild the same screen because you changed your mind halfway and forgot why. Requirements are not paperwor 09The Core Loop: Designing for RetentionEverything else in your product is decoration around one question: why does the user come back tomorrow? Get the loop right and mediocre features still work. Get it wrong and no amount of po 10Onboarding and ActivationOnboarding is not a tutorial. It is a sales process wearing a friendly hat, and its only job is to get a stranger to the moment where they understand why your product matters, before they lo

III

Design

How it looks, feels, and behaves.

11UX FundamentalsUsers can't tell you why a product feels cheap, but they know within seconds. It's almost never the colours. It's structure, states, and whether the thing does what they expected.12UI Design and Design SystemsYou do not need to be a designer to ship an interface that looks designed. You need a small set of constraints, applied without exception. Most amateur UI isn't ugly because of bad taste, it 13Branding and Visual IdentityBranding is treated as decoration applied at the end. In a crowded category it's a competitive strategy, it's the first thing a customer perceives and the only thing they can judge before th 14Behavioral Design and EthicsEvery product shapes behaviour whether you intend it or not. The only question is whether you're doing it deliberately, and whose interest you're optimising for. This chapter covers both the

Building

The engineering, and every bug that cost more than an hour.

15Choosing Your Tech StackFounders lose weeks to this decision and it barely affects the outcome. The one criterion that matters: minimise the distance between noticing a problem and having it fixed. Everything else,16Project Architecture and Working PracticesArchitecture isn't only how the code is organised. It's the set of invariants that hold when you're tired, and the only ones that hold are the ones a machine enforces. A convention you have 17Frontend and Web DevelopmentThe frontend is where users experience every other decision you've made. It's also where a small number of specific mistakes, a rendering model that doesn't match your content, an uncached f 18Mobile Development"Feels native" is not a vague quality. It's about six specific details, five of which are cheap. The sixth is where you lose two days to a platform behaviour that operates below your code an 19Backend ArchitectureThe backend question isn't "which framework." It's "what promise am I making to the user, and what has to be true on a server for that promise to hold?" Build it when a promise requires it, 20Databases and Data ModelingYour data model outlives your code. You'll rewrite the UI three times and refactor the backend twice, and the schema decisions you made in week one will still be shaping what's easy and what 21Authentication and IdentityAuth is the most over-built and most under-tested part of a consumer product. Over-built because founders reach for a login screen on launch. Under-tested because everyone tests "sign up" an 22APIs and Third-Party IntegrationsEvery integration is a dependency on someone else's uptime, pricing, roadmap and judgement. That trade is almost always worth making, but it should be a decision you made, not one you drifte 23AI IntegrationAn AI feature is the first thing most founders build that has a variable cost per user. That single property changes your unit economics, your abuse surface, your latency budget, and what "c 24Prompt EngineeringA prompt is production code. It has inputs, outputs, failure modes and a version history, and unlike your other code, changing one word can silently alter behaviour for every user. Treat it

Money

What you charge, and how you collect it.

25Monetization ModelsChapter 01 covered which business you're in. This is the mechanics: what you gate, what you give away, how someone becomes a customer, and why most freemium products are charities with a pai 26Pricing StrategyYou are not inventing a number. Your market has already trained your customer what this costs. Your job is choosing a defensible position on an existing scale, and then making the annual pla 27Payments, Billing and SubscriptionsPayment code is the only code where a bug costs you money directly, and it's uniquely hard to test, the path that matters most is the one you can least easily exercise. The most dangerous ve

Quality

How to know it actually works.

28Testing and Verification"It looked fine" is not verification. A screenshot is a picture of a cache. Verification is a measurement that could have come back negative, and if yours couldn't have, you didn't run one.29Debugging: A Systematic MethodLoud bugs are cheap, a stack trace is a gift. The expensive ones produce no error at all: they return success, render something plausible, exit zero, and quietly do the wrong thing. Learn to 30Security and Code ReviewFinding vulnerabilities is easy and getting cheaper every year. Fixing them requires a mechanism, and that's the part almost everyone skips. A review that doesn't become tracked work produce 31Performance, Cost and ScalingYour architecture sets your cost curve before you have a single user. Scale doesn't create the curve, it only reveals it. And the free tier that carries you to launch will fail on your best

VII

Shipping

The unglamorous gauntlet nobody blogs about.

32Content and Asset Production at ScaleWhen content is the product, lessons, listings, templates, images, questions, it's not "the writing part" you do at the end. It's an engineering problem wearing a writing costume, and it nee 33Build Pipelines, CI/CD and DeploymentYour build pipeline is invisible infrastructure until the day it lies to you, reports success over a failure, ships a stale artifact, or deploys the wrong branch. Then it costs you a day of 34Web Infrastructure and Landing PagesYour website isn't marketing you get to defer to launch week. For a mobile app it's a submission dependency, two of its pages are required before a store will accept you. Build it early, and 35Domains, Email and DeliverabilitySending email from your own domain is not typing an address into a "from" field. Modern mail providers silently discard unauthenticated mail, not bounce, discard, with no error and nothing i 36App Store PreparationYou can have a perfect app and be rejected, for a missing disclosure line, a promise you can't keep, or a health claim you didn't realise you made. Rejection is more often a wording problem 37Google Play PreparationCheaper to enter, slower to launch. The rule that catches everyone is a testing requirement that adds two weeks to your first release, so if Android is anywhere in your plan, start the clock 38Analytics, Crash Reporting and ObservabilityAnalytics feel like they can wait, because they don't change the product. They can't wait, because without them, every decision after launch is a guess. Install them before you have users. D

VIII

The company

Entity, legal, tax, support.

39Company Formation and Legal BasicsYou do not need a company to start building, and you do need one before you take money, hire, or sign anything. This chapter is the map of what the pieces are and which questions to take to 40Privacy, Terms and CompliancePrivacy is not a document you generate at the end. It's a set of promises your product must actually keep, and the fastest way to break one is to add a feature or an SDK that collects data y 41Taxes and Financial AdminThe single decision that saves a global software business the most pain is who acts as merchant of record, because it decides whether sales tax in dozens of countries is your problem or some 42Customer SupportSupport is not a cost centre to minimise. Early on it's your highest-bandwidth product-research channel, every ticket is a user telling you exactly where your product confused, failed, or di

Go to market

Getting anyone to see it.

43Messaging and CopywritingThe gap between a product people want and a product people buy is usually words. Say what it is, for whom, in the language they already use, not the language you invented. Your best copy is 44Pre-launch: Audience and WaitlistsLaunch day is quiet for almost everyone, because they built the product first and thought about the audience second. The founders who launch to something built the audience while they built 45LaunchLaunch is not an event; it's a switch you flip after the work is done, and for almost everyone it's quiet. The mistake is treating one day as the moment that decides everything, pouring mont 46Content Marketing and SEOContent is the channel you own, compounding, that keeps working while you sleep. It's also the channel with the longest lag, you plant for months before you harvest, which is exactly why mos 47Social, Short-form and CommunitySocial media creates demand from people who weren't looking for you, and community turns strangers into a group that markets for you. Both run on the same currency: you have to give before y 48Paid AcquisitionPaid acquisition is the only channel where you can turn money directly into users, which is exactly why it's dangerous. It amplifies whatever it's pointed at. Point it at a product that does

Growth and beyond

Retention, experimentation, team, and the long game.

49Metrics That MatterMost dashboards measure what's easy, not what's true. Signups, pageviews, and downloads feel like progress and predict almost nothing. The numbers that actually matter are the ones that tell 50Retention and LifecycleAcquisition gets the applause; retention pays the bills. A product nobody comes back to isn't a business, it's a leak with a marketing budget. Retention is the only growth that compounds, an 51Growth Loops and ExperimentationFunnels leak; loops compound. A funnel pours users in the top and loses them out the sides, and when you stop pouring, growth stops. A loop uses the output of one cycle as the fuel for the n 52Hiring, Contractors and Working with AIThe first question isn't "who do I hire?", it's "does this need a person at all?" A great deal of what used to require a first hire is now a contractor, a tool, or an AI workflow. Bring on p 53The Founder's Operating SystemThe hardest part of building a company isn't any single decision, it's making thousands of them, in the right order, without running out of money, focus, or yourself. A founder's operating s 54ResourcesThe tools matter far less than the founder using them. Every stack in this chapter can build a great company or an abandoned one, the difference is judgment, focus, and the will to ship, non