Starting a business, in the order the work actually happens

Most business advice arrives out of order. You read about pricing before you know what you sell, about scaling before anyone has paid you, about culture before there is anyone to have a culture with. Then you do the work in that order, and it does not compound: each piece sits there waiting on something you have not built yet.

This guide is for people building something small and real: a service business, a product, a one-person shop that might one day be a five-person one. It assumes no funding, no co-founder, and no team to delegate to yet. If you are raising a seed round or running a company with a finance function, the sequencing here will feel remedial: you have specialists for these stages and you should use them. And if you already have paying customers and a working offer, most of the first half is behind you; start at the numbers.

What follows is the whole territory in one view, in dependency order, with the sixteen kits in the pack attached to the stage they actually belong to.

The map: six stages, and what each one is waiting on

The work breaks into six stages: deciding what to build, building the smallest testable version, launching it, giving people somewhere to land, measuring what happened, and getting yourself out of the middle. The order is not arbitrary. Each stage produces the input the next one needs.

Validation comes first because everything downstream inherits its answer. Building before validating is not faster: it is the same amount of building, done on a worse brief. Validate Business Ideas is blunt about the trade: the point of the research is to spend a week finding out what a year would have taught you.

Building comes second and should be smaller than feels dignified. The reason is mechanical, not motivational: a prototype answers a question, and questions asked early are cheap. A prototype asked to also be a finished product answers nothing and costs six months.

Launch is third, and it is a distribution problem rather than a product one. The most common launch failure is not a bad product but a product with no route to anyone, which is why the launching material in this pack spends more of its length on the founder's stamina than on the mechanics.

The website sits fourth in sequence, not first, and this is the ordering claim people fight hardest. A site built before the offer is settled has to be rebuilt when it settles. A site built after is a two-day job.

Measurement comes fifth. Instrumenting a business that has not shipped is theatre; instrumenting one that has is how you find out which of the previous four stages is leaking.

And getting out of the middle comes last, because it is the only stage that requires the others to already work. You cannot systematise a business whose value still lives entirely in your head: you can only write down what already happens twice the same way.

Deciding what to build

The first stage has one job: reduce the number of things you are wrong about before they get expensive.

SWOT Analysis Simplified opens by attacking the version of strategy most people have seen. It calls it the laundry list trap: a room shouting items at a whiteboard until the grid contains "dedicated team", "good service", and "broken printer on 2nd floor" side by side, which it correctly labels as too vague, subjective, and a maintenance ticket. Its replacement is a decision engine: write a specific challenge question first, then apply what it calls the Control Test, drawing a hard line between what you control and what merely happens to you. Category errors here are the expensive ones: you end up trying to fix a market trend or capitalise on an internal habit.

Its last move is the useful one. Every option you generate goes onto an Impact/Effort matrix, where impact is defined strictly by that challenge question, not by whether something is generally good for the business. The matrix is not for organising ideas. It is for killing them.

Your Business Plan Playbook handles the document, and is honest that the document is optional. Its most transferable chapter is on planning pitfalls, starting with analysis paralysis: it recommends a hard deadline of thirty to sixty days on the planning phase on the grounds that the plan needs to be actionable, not perfect. It also covers the Lean Startup method and the Business Model Canvas as lighter alternatives when a full plan is the wrong shape.

The evidence-gathering itself is covered in the Validate Business Ideas Ebook post; the strategy grid and how to stop it becoming a brain dump in Swot Analysis Simplified; the plan-or-canvas decision in Your Business Plan Playbook Ebook.

The smallest version that teaches you something

Everyone agrees an MVP should be minimal. Almost nobody can say which features get cut, which is where the arguments happen.

The MVP Playbook gives four prioritisation tools and the one worth learning first is MoSCoW. Every candidate feature is sorted into four buckets:

• Must-have: critical features without which the product does not work.
• Should-have: important, not vital, add significant value.
• Could-have: nice to have, small impact if left out.
• Won't-have: not a priority for this release.

The book's instruction is to build the must-haves and perhaps a few high-impact should-haves, and nothing else. The discipline is in the fourth bucket. A "won't-have" list you actually write down is what stops the release date moving.

The Power of Prototypes covers the step before the MVP, and its worked example is the Dropbox one: a demo video standing in for a product that did not exist yet, used to measure demand rather than to demonstrate a build. It also works through Spotify's feedback loops, and is unusually careful about the pitfalls: a prototype polished past the point of answering its question has stopped being a prototype.

Create Micro Products is the fastest path for anyone selling knowledge rather than software. Its 4-D method (draft, design, develop, deliver) treats creation as a continuous flow instead of four phases each demanding perfection. Draft means timed ninety-minute sprints, voice dictation allowed, formatting deferred entirely. Design comes after, using templates specifically to remove design decisions rather than to make them.

Feature triage is covered in The Mvp Playbook Ebook; the cheaper test that comes before it in The Power Of Prototypes Ebook; and the small paid product you can finish in a week in Create Micro Products.

Launching it, and the part nobody plans for

A launch is where most first-time founders discover that building was the easy half.

MicroSaaS Success Blueprint is the software version and its sequencing is the good part: niche selection, then problem research, then testing the idea before development: landing page, targeted traffic, surveys, a manual MVP where you do by hand what the software will eventually do. It lists the warning signs to watch for during that testing, which is a rarer thing to publish than the encouragement. Its no-code and outsourcing chapters exist so that "I can't build it" stops being the blocker.

The Online Business Launching Strategies kit is the odd one in the pack, and worth flagging honestly: the bulk of its material is Mental Toughness, about the founder rather than the funnel. That is a defensible choice. Its chapters cover the entrepreneurial roller coaster, stress reduction, and building resilience through adversity, with an action plan attached to each. A launch fails more often from the founder quietly stopping than from any single tactical error.

The niche, validation and no-code build path are covered in Microsaas Success Blueprint Ebook; the stamina side, and why it belongs in a business pack at all, in Online Business Launching Strategies Ebook.

Where people land and decide

Two of the sixteen kits are about websites, and they split cleanly: one is the build, one is the business case.

How to Build a Website is the practical path: choosing a builder, the brand-consistency work, the pages every business site needs, publishing, and the search-engine basics after. It is written for someone who has never done this and does not want to learn to code, which is the correct audience for it.

Business Websites Mastery argues the other half: what being invisible costs, and why the psychology of digital trust decides whether a first-time visitor believes you exist as a real business. Its chapters on credibility elements and transparency are the ones to read if your site exists but nobody converts on it.

The Psychology of Conversions is the layer on top, and it is the kit that most needs translating down. It covers emotional triggers, social proof, visual hierarchy, colour, typography and whitespace, and also scarcity and urgency, which we would treat with more suspicion than the book does. Its own chapter on balancing them is the honest bit: manufactured urgency buys a short-term lift and spends trust you will want later. Take the social proof and first-impressions material; leave the countdown timers.

Podcast Launchpad is here because a show is the other owned channel a small business can start for near-nothing. Its five-part episode structure template is the reusable asset: most abandoned podcasts die from having to reinvent the format every week, not from bad audio.

The build itself is covered in How To Build A Website Ebook; the trust and credibility case in Business Websites Mastery Ebook; the persuasion layer, hedged, in The Psychology Of Conversions Ebook; and the audio channel in Podcast Launchpad.

The numbers that tell you which stage is leaking

Most small businesses track revenue and nothing else, which tells you that something is wrong without telling you where.

Understanding Business Metrics recommends starting with four and expanding only as you build the habit: monthly revenue growth, customer acquisition cost, satisfaction scores, and website conversion rate. Four is the right number because each one indicts a different stage. Acquisition cost rising is a launch and distribution problem. Conversion rate falling is a website problem. Satisfaction dropping is a product problem. Revenue flat while the other three are healthy usually means a pricing problem, which is a different guide.

The book's framing is that metrics are a navigation system rather than a report card: they tell you where you are and warn you when you are off course. The mistake that costs most is measuring monthly and reacting quarterly. A number you look at once a quarter is a historical record. The one you look at every Monday is a control.

Which metrics to start with, and the tracking system that keeps them current without a data team, are covered in Understanding Business Metrics Ebook.

Getting yourself out of the middle

The last stage only becomes possible once the first five work, and it is the one most people attempt too early.

Agency Growth Blueprint names the trap precisely: the difference between working in the business and on it, and the point at which you realise you have built yourself a very expensive, very demanding job rather than a company. If you approve every decision and review every piece of work, the business grows exactly as fast as you can work, and no faster. Its answer is unglamorous: mapping the operating system, writing SOPs, a strategic hiring sequence, and accountability that is not micromanagement.

How to Franchise Your Business is the extreme version of the same idea, and useful even if you never franchise anything. To license a business you must first make it fully replicable by someone who is not you, which is a brutally good test of how much still lives in your head. Its readiness audit and red-flags chapter are worth reading purely as a diagnostic.

The Safety Culture Shift That Transforms Teams is the people half, and applies well beyond regulated industries. Its five-minute conversation framework and its insistence on accountability without blame are the transferable parts: a team that reports problems early is the same asset whether the problem is a hazard or a client about to leave.

The operator-to-owner shift and the systems that make it possible are covered in Agency Growth Blueprint; replicability as a test in How To Franchise Your Business; and the leadership habits underneath it in The Safety Culture Shift That Transforms Teams.

How to start this week

Two hours, no budget, in this order:

1. Write your challenge question in one sentence. Not a goal: a specific decision you are trying to make in the next ninety days. Everything else in this guide gets filtered against it, and if you cannot write it, that is the finding.
2. Put your feature or scope list through MoSCoW. Four buckets, and force yourself to fill the won't-have column. Whatever survives as must-have is your next two weeks of work.
3. Start tracking the four numbers. A spreadsheet is fine. Monthly revenue growth, acquisition cost, a satisfaction proxy, conversion rate. You need a baseline more than you need accuracy.

Then do the smallest thing on the list: talk to one person who has the problem you think you are solving, and ask what they currently do instead. That conversation is worth more than the rest of the two hours combined.

Related guides

Pricing is the stage this guide deliberately hands off: if the numbers section suggested your problem is what you charge rather than how much you sell, the Money & Pricing guide is the one that deals with it. And once the systems work in the last section starts, the question becomes what to automate first, which the AI & Automation guide covers directly.