← Back to the book

Free preview

Look inside The AI-Powered Small-Business Website Development Side Hustle

This is the introduction and the opening chapter in full — the same text you get in the bundle, not a rewritten sample. The complete book runs to 44 sections.

See what's included

Introduction: Why Small-Business Website Development Works as a Side Hustle

Why small businesses buy websites, why the window is open, the four rules the whole book rests on, what an ordinary week actually contains, who should not do this work, and what the book will not tell you.


The Scenario

Row's first client rang in a genuine panic, two years after the site was finished, about something Row had done right without realising how much it would matter.

The business was a family bakery. Row had built them a five-page site — opening hours, a menu, some photographs, a contact form. It had taken about three weeks around a full-time job.

The panic was not about the site. Their previous developer, from years before Row, had registered their domain in his own name. He had since stopped answering emails, and their email had stopped working on a Tuesday morning. Orders, suppliers, everything.

They rang Row because Row was the only person they knew who did "computer things."

Row could not fix it — it was not Row's domain to fix, and getting it back took the bakery weeks and an attorney's letter.

But somewhere in that conversation the owner said something Row has thought about ever since:

"When you set ours up, you made me sit down with my own card and do it myself. I remember being slightly annoyed. I'm not annoyed now."

Row had done that because it seemed obviously correct, not because Row understood the alternative.

This book exists so that you understand the alternative before somebody teaches it to you.


What Small Businesses Are Actually Buying

Almost nobody wants a website. They want the thing the website is for.

To be findable. Somebody searches, and they exist, and the information is right.

To look like a real business. A site that is old, broken on a phone, or obviously abandoned costs them work they never hear about.

To stop answering the same questions. Opening hours. Whether you do that. Where you are. What it costs, roughly.

To get enquiries. A form that works, going to an inbox somebody reads.

And, quietly, to stop worrying about it. A great many small business owners have a site they are slightly embarrassed by and have been meaning to sort out for two years.

Notice what is not on that list: design. Design matters enormously to how the first four are achieved, and it is almost never what the client is actually buying. Selling design to somebody who wants enquiries produces a project where nobody is satisfied.


⚠ The Four Rules the Whole Business Rests On

=================================================================
  ⚠ 1. THE CLIENT OWNS THEIR DOMAIN, THEIR HOSTING
       ACCOUNT, AND THEIR CONTENT.

     ⚠ Registered in their name, on their card,
       under their control — ⚠ FROM THE FIRST DAY,
       NOT AT HANDOVER.
     ⚠ ⚠ THE DOMAIN IS FREQUENTLY THE MOST VALUABLE
       DIGITAL ASSET A SMALL BUSINESS OWNS, ⚠ AND IT
       IS THE THING MOST CASUALLY MISHANDLED IN
       THIS INDUSTRY.
     ⚠ Chapter 4. ⚠ Row's bakery.

  ⚠ 2. NOTHING GOES ON A SITE THAT YOU DO NOT HAVE
       THE RIGHT TO USE.

     ⚠ Images, fonts, icons, video, themes,
       plugins, code, and text.
     ⚠ ⚠ "I FOUND IT ONLINE" IS NOT A LICENCE, ⚠ AND
       THE DEMAND LETTER ARRIVES AT THE CLIENT.
     ⚠ Chapter 5.

  ⚠ 3. ACCESSIBILITY IS A DESIGN DECISION, NOT AN
       ADD-ON — ⚠ AND YOU DO NOT CERTIFY COMPLIANCE.

     ⚠ Decisions made at wireframe stage cannot be
       retrofitted cheaply.
     ⚠ ⚠ YOU BUILD TO A STANDARD, ⚠ DOCUMENT WHAT YOU
       DID AND TESTED, ⚠ AND TELL THE CLIENT THAT
       WHETHER IT MEETS ANY LEGAL REQUIREMENT IS A
       QUESTION FOR THEIR OWN ADVISER.
     ⚠ Chapter 6.

  ⚠ 4. A SITE YOU BUILT IS A RESPONSIBILITY YOU
       CREATED.

     ⚠ Software you did not write needs updating.
       ⚠ Certificates expire. ⚠ Backups that were
       never tested are not backups.
     ⚠ ⚠ AND THE CLIENT MUST BE TOLD, IN WRITING,
       WHAT HAPPENS IF NOBODY MAINTAINS IT.
     ⚠ Chapters 22 and 24.
=================================================================

Everything else in this book is method built on top of those four.


What the Work Actually Looks Like

A brochure site for a local business, from first call to handover:

=================================================================
  ⚠ ROUGHLY. ⚠ YOURS WILL DIFFER.

  ⚠ DISCOVERY — ⚠ a proper call, not a chat.
    ⚠ What the site is for. ⚠ Who decides. ⚠ What
      content exists. ⚠ ⚠ WHO OWNS THE DOMAIN.
    ⚠ Chapter 17.

  ⚠ SITE MAP AND CONTENT PLAN — ⚠ what pages, and
    ⚠ WHO IS WRITING WHAT, BY WHEN.
    ⚠ ⚠ THIS IS WHERE PROJECTS STALL. Chapter 18.

  ⚠ WIREFRAMES — ⚠ structure before decoration, ⚠ with
    the accessibility decisions made here.
    Chapter 19.

  ⚠ DESIGN AND BUILD — ⚠ frequently the shortest
    stage, which surprises everybody.
    Chapter 20.

  ⚠ TESTING — ⚠ real devices, ⚠ accessibility checks,
    ⚠ and every form tested end to end.
    Chapters 20, 21, 6.

  ⚠ LAUNCH — ⚠ a procedure with a checklist and a
    rollback plan, ⚠ never a moment.
    Chapter 23.

  ⚠ HANDOFF — ⚠ assets confirmed in their name,
    ⚠ training, documentation, ⚠ and an honest
    conversation about maintenance. Chapter 24.

  ⚠ ⚠ AND THE UNBILLED HOURS AROUND ALL OF IT —
    ⚠ the enquiry, the proposal, the waiting for
    content, the chasing, the invoicing.
    ⚠ Section 27.2 — ⚠ THEY ARE LARGER THAN YOU
    THINK.
=================================================================

If you imagined this work as mostly designing, adjust that now. Design and build is perhaps a third of it. Discovery, content wrangling, testing, launching, and explaining are the rest — and they are what a professional is actually paid for, whether or not the client realises it.


Who Should Not Do This Work

Plainly, because it is kinder said now.

Anybody who would register a client's domain in their own name — for convenience, for control, or because it is easier. If that sounds reasonable to you, this trade will eventually make somebody's business stop working.

Anybody who takes images from search results. The demand letter arrives at the client, and the client remembers who put it there.

Anybody who cannot chase content politely for six weeks. Content is the reason projects stall, and it is a relationship skill rather than a technical one.

Anybody who will not get approvals in writing. "You said you liked it" is not a defence at revision seven.

Anybody who thinks accessibility is a nice-to-have. It is a set of decisions made early that cannot be retrofitted cheaply — and it affects real people.

Anybody who wants to be finished with a client. You are building something that needs maintaining. If you disappear, it degrades, and somebody's business degrades with it.

And anybody who would rather make something beautiful than something that works on a five-year-old phone in poor light. Both is the goal. One of the two is the job.


The Honest State of This Market

You are competing against free.

Small businesses can build something themselves on a website builder for the price of a subscription. Many do. Some of the results are perfectly adequate for what that business needs.

Pretending otherwise is how people end up bitter about this trade.

What you are actually selling, against that:

Time. They have not got around to it in three years and will not next year either.

Judgement. What pages, what order, what to say, what to leave out.

The parts they do not know exist. Accessibility, forms that actually deliver, redirects, backups, updates, ownership.

And somebody to ring.

Which means: never compete on price against a subscription, and never sell "a website." Sell the parts of the job the builder does not do — and tell them honestly when the builder is the right answer. Section 15.10.

No volume of work, income, or timescale is promised by this book. What is true is that the things above are free, are entirely within your control, and are almost never offered.


What Has to Be in Place Before Your First Paid Project

=================================================================
  [ ] ⚠ Insurance discussed with a broker, with your
      written scope sent first, and the exclusions
      read. ⚠ Section 14.3.

  [ ] ⚠ A client agreement reviewed by a qualified
      professional — including ownership, IP,
      revisions, acceptance, warranty, and
      limitation of liability. ⚠ Chapter 28.

  [ ] ⚠ Answers from an accountant on structure, tax
      set-aside, and records. ⚠ Section 14.11.

  [ ] ⚠ A written position on domain and hosting
      ownership — ⚠ THE CLIENT'S NAME, THE CLIENT'S
      CARD. Chapter 4.

  [ ] ⚠ A licence register and a habit of keeping
      receipts. ⚠ Resource 22.

  [ ] ⚠ An accessibility standard you build to, and
      the wording of what you will and will not
      claim. ⚠ Chapter 6.

  [ ] ⚠ A backup and update position, and what you
      tell a client who declines a care plan.
      ⚠ Chapter 22.

  [ ] ⚠ Your own security in order — password
      manager, multi-factor, backups.

  [ ] Three sites built that you can show.
      ⚠ Section 16.4.

  [ ] A discovery process you charge for.
      ⚠ Section 17.12.

  ⚠ ⚠ THE FIRST EIGHT ARE NOT OPTIONAL, AND SEVERAL
    REQUIRE SOMEBODY QUALIFIED TO ANSWER A QUESTION
    THIS BOOK DELIBERATELY DOES NOT ANSWER.
=================================================================

Three Worked Examples

Every figure below is a blank. Fill them in from your own researched costs and your own market. No income, client, or outcome is promised anywhere in this book.

=================================================================
  ⚠ EXAMPLE A — A FIVE-PAGE LOCAL BUSINESS SITE

  Discovery                     $________
  Site map and content plan     $________
  Wireframes and design         $________
  Build and testing             $________
  Launch and handoff            $________
  ⚠ TOTAL                        $________
  ⚠ Client pays directly: ⚠ domain, hosting,
    any licensed images or fonts.

  Your hours: discovery ____ · planning ____ ·
  design ____ · build ____ · testing ____ ·
  launch ____ · handoff ____
  ⚠ ⚠ UNBILLED: ⚠ enquiry, proposal, ⚠ WAITING FOR
    CONTENT, chasing, invoicing ____
  ⚠ TOTAL HOURS ____
  ⚠ ⚠ REVENUE PER WORKING HOUR $________
  ⚠ ⚠ THIS IS THE HONEST NUMBER. Section 35.6.
=================================================================
  ⚠ EXAMPLE B — A CARE PLAN

  Monthly fee                   $________
  Includes: ⚠ updates, ⚠ backups verified, ⚠ uptime
  checks, ⚠ ____ hours of small changes, ⚠ a
  quarterly review.
  ⚠ Excludes: ⚠ new pages, ⚠ redesigns, ⚠ content
  writing, ⚠ anything on sites I did not build.
  Your monthly hours            ____
  ⚠ REVENUE PER WORKING HOUR    $________
  ⚠ ⚠ Watch month seven. Section 27.6.
=================================================================
  ⚠ EXAMPLE C — THE TWELVE-MONTH VIEW, THREE CASES

                  CONSERVATIVE  MODERATE   GROWTH
  Sites/year        ______      ______     ______
  Avg site value    $_____      $_____     $_____
  Care plans by Dec ______      ______     ______
  Revenue           $_____      $_____     $_____
  Costs             $_____      $_____     $_____
  Tax set-aside     $_____      $_____     $_____
  Left over         $_____      $_____     $_____
  ⚠ Rev/working hour $_____      $_____     $_____

  ⚠ ⚠ BUILD ALL THREE. ⚠ PLAN AGAINST THE
    CONSERVATIVE ONE. ⚠ NO CASE IS A PREDICTION.
    Section 27.10.
=================================================================

What This Book Assumes About You

That you can build a basic website, or are willing to learn one platform properly. That you would rather ask an awkward question at the discovery call than discover the answer at launch. That you will get approvals in writing even when the client is lovely. And that when this book says ask a qualified professional, you will actually ring somebody rather than asking an AI tool and treating the answer as settled.

That last habit is the difference between a business and a liability.


Chapter Summary

Row's bakery client rang two years later about a domain a previous developer had registered in his own name — and remembered being made to sit down with their own card, which had seemed slightly annoying at the time.

Almost nobody buys a website. They buy being findable, looking like a real business, stopping the same questions, getting enquiries, and no longer worrying about it. Design is how those happen, and it is almost never what is being bought.

Four rules carry the whole book: the client owns their domain, hosting, and content from day one; nothing goes on a site you do not have the right to use; accessibility is a design decision and you never certify compliance; and a site you built is a responsibility you created.

Design and build is perhaps a third of the work. Discovery, content wrangling, testing, launching, and explaining are the rest.

You are competing against free, and pretending otherwise is how people become bitter about this trade. What you actually sell is time, judgement, the parts they do not know exist, and somebody to ring — and telling them honestly when a builder is the right answer is part of it.

Do not take a paid project until insurance, a reviewed agreement, an accountant's answers, a written ownership position, a licence register, an accessibility standard, a backup position, and your own security are all in place.


Chapter 1: Understanding the Industry and What Clients Actually Buy

What a small business is really purchasing when it buys a website, why accountability beats design, how they choose, and the seven page titles on paper that beat three mock-ups.


The Scenario

Row lost a project by showing three beautiful designs, and won the next one by showing a list of pages on a piece of paper.

The first was an accountancy practice. Row spent a weekend producing three homepage designs — different typography, different colour, genuinely good work — and presented them.

The senior partner looked at them politely for about ninety seconds and said:

"They're all very nice. Which one gets us more of the right sort of enquiry?"

Row did not have an answer, because Row had been solving a different problem than the one the practice had.

The second was a plumbing company. Row asked what happened when somebody found them online, and the owner said:

"They ring and ask if we do commercial work. We do, but you'd never know from the website. Then they ring somebody else."

Row wrote seven page titles on a sheet of paper — one of them being Commercial Work — and a sentence about what each page would say.

The plumber said yes in that meeting. Nothing had been designed at all.

The accountancy practice was not being difficult. They were asking the only question that mattered, and Row had spent a weekend answering a different one.


1.1 Nobody Buys a Website

=================================================================
  ⚠ THE SENTENCE THIS CHAPTER RESTS ON.

  ⚠ WHAT PEOPLE ACTUALLY HAVE
    ⚠ A site that is old and slightly embarrassing.
    ⚠ Enquiries they suspect they are losing.
    ⚠ The same six questions, answered on the phone,
      every day.
    ⚠ Something that looks broken on a phone.
    ⚠ ⚠ Or a service they offer that nobody knows
      about. ⚠ Row's plumber.

  ⚠ WHAT THIS MEANS FOR HOW YOU SELL
  ⚠ ⚠ NEVER LEAD WITH DESIGN.
  ⚠ Lead with the problem, described in their words,
    more precisely than they described it.

  ⚠ THE TEST FOR ANY PROPOSAL
  ⚠ ⚠ COULD THE CLIENT HAVE WRITTEN THE FIRST
    PARAGRAPH THEMSELVES?
  ⚠ If not, you are selling a design project, ⚠ and
    design projects get "they're all very nice."

  ⚠ AND THE PRACTICAL VERSION
    ⚠ A LIST OF PAGES WITH A SENTENCE EACH IS
      FREQUENTLY MORE PERSUASIVE THAN THREE
      HOMEPAGE DESIGNS.
  ⚠ ⚠ It shows you understood the business. ⚠ Design
    shows you understood design.
=================================================================

1.2 The Five Things Clients Are Really Buying

=================================================================
  ⚠ 1. BEING FINDABLE, ⚠ WITH THE RIGHT INFORMATION
     ⚠ Hours, location, what they actually do.
     ⚠ ⚠ Frequently the current site is simply WRONG —
       old hours, old prices, a service they dropped.

  ⚠ 2. LOOKING LIKE A REAL BUSINESS
     ⚠ A broken or abandoned-looking site costs work
       they never hear about.
     ⚠ ⚠ This is the one owners feel most and mention
       least.

  ⚠ 3. NOT ANSWERING THE SAME QUESTIONS
     ⚠ Do you do X? ⚠ Where are you? ⚠ How much,
       roughly? ⚠ Do you cover my area?
     ⚠ ⚠ Every one of those is a page.

  ⚠ 4. GETTING ENQUIRIES
     ⚠ A form that works, ⚠ reaching an inbox somebody
       reads. ⚠ Chapter 21.
     ⚠ ⚠ AND YOU WOULD BE ASTONISHED HOW OFTEN THE
       EXISTING FORM GOES NOWHERE.

  ⚠ 5. NOT WORRYING ABOUT IT
     ⚠ Many owners have been meaning to sort the site
       out for two or three years.
     ⚠ ⚠ Relief is a genuine product, ⚠ and it is why
       care plans sell. Chapter 34.

  ⚠ ⚠ WHAT IS NOT ON THE LIST
    ⚠ AWARDS, ANIMATION, CLEVERNESS, OR BEING
      "MODERN".
  ⚠ ⚠ Sell those and you attract clients who judge on
    taste, ⚠ which is a project with no finish line.
=================================================================

1.3 The Four Reasons a Small Business Finally Calls Somebody

=================================================================
  ⚠ THEY HAVE BEEN MEANING TO FOR YEARS. ⚠ SOMETHING
    CHANGED.

  ⚠ 1. SOMETHING BROKE OR EXPIRED.
     ⚠ The site went down. ⚠ The domain nearly lapsed.
       ⚠ The old developer vanished. ⚠ A browser
       started warning about it.
     ⚠ ⚠ URGENT, ⚠ AND FREQUENTLY ARRIVES AS A RESCUE.
       Section 8.5.

  ⚠ 2. THE BUSINESS CHANGED.
     ⚠ New service. ⚠ New premises. ⚠ New partner.
       ⚠ A rebrand. ⚠ Someone left who used to update
       it.

  ⚠ 3. SOMEBODY EMBARRASSED THEM.
     ⚠ A customer said "I couldn't find you." ⚠ A
       competitor's site looks better. ⚠ Their own
       child told them it looks terrible on a phone.

  ⚠ 4. THEY ARE TRYING TO GROW.
     ⚠ The most enjoyable clients, ⚠ and the ones who
       ask "which one gets us more of the right sort
       of enquiry?" ⚠ Row's accountants.

  ⚠ WHY KNOWING WHICH ONE MATTERS
    ⚠ 1 buys speed and reassurance.
    ⚠ 2 buys accuracy and completeness.
    ⚠ 3 buys credibility.
    ⚠ 4 buys judgement — ⚠ and pays best.
  ⚠ ⚠ ASK IN THE FIRST FIVE MINUTES: ⚠ "WHY NOW?"
    Section 17.4.
=================================================================

1.4 Why "We Just Need a Simple Site" Is Never Simple

=================================================================
  ⚠ THE SENTENCE THAT PRECEDES MOST UNDERQUOTED
    PROJECTS.

  ⚠ WHAT THEY MEAN
    ⚠ "Not many pages."
  ⚠ ⚠ WHAT THEY DO NOT MEAN
    ⚠ Not much work.

  ⚠ WHAT A "SIMPLE" FIVE-PAGE SITE STILL REQUIRES
    [ ] A discovery conversation. ⚠ Chapter 17.
    [ ] ⚠ Establishing who owns the domain — ⚠ and
        frequently untangling it. Chapter 4.
    [ ] A site map and a content plan
    [ ] ⚠ CONTENT THAT DOES NOT EXIST YET.
        ⚠ Section 18.4.
    [ ] Photographs, ⚠ licensed or taken.
        Chapter 5.
    [ ] Wireframes and design approval
    [ ] ⚠ Accessibility decisions. Chapter 6.
    [ ] Responsive testing on real devices
    [ ] ⚠ A form that actually delivers, tested end to
        end. Chapter 21.
    [ ] ⚠ Hosting, certificates, DNS, and email that
        must not break. Section 23.6.
    [ ] Redirects from the old site.
        Section 23.7.
    [ ] Analytics and search tools
    [ ] Backups
    [ ] ⚠ Handoff and training. Chapter 24.

  ⚠ ⚠ THE PAGE COUNT IS ALMOST IRRELEVANT TO THE
    EFFORT.
  ⚠ Section 27.4 prices from the work, ⚠ not the
    pages.

  ⚠ THE SENTENCE TO SAY EARLY
  ⚠ "Five pages is a sensible size. Most of the work
    isn't the pages though — it's working out what
    they should say, getting the content together,
    and making sure everything still works
    afterwards. Shall I walk you through what's
    involved?"
=================================================================

1.5 ⚠ The Single Biggest Cause of Failed Projects

=================================================================
  ⚠ ⚠ IT IS NOT DESIGN. ⚠ IT IS CONTENT.

  ⚠ WHAT ACTUALLY HAPPENS
    ⚠ The site map is agreed. ⚠ The design is
      approved. ⚠ The build is essentially done.
    ⚠ ⚠ AND THEN NOTHING HAPPENS FOR FOURTEEN WEEKS,
      BECAUSE NOBODY HAS WRITTEN THE ABOUT PAGE.

  ⚠ WHY IT HAPPENS, ⚠ AND IT IS NOT LAZINESS
    ⚠ Writing about your own business is genuinely
      hard.
    ⚠ It is nobody's job.
    ⚠ It is never urgent compared with actual work.
    ⚠ ⚠ And frequently the person who must write it
      was never in the meeting.

  ⚠ WHAT THIS COSTS YOU
    ⚠ A project that should take five weeks takes
      five months.
    ⚠ ⚠ Your final invoice waits with it.
      Section 35.8.
    ⚠ You cannot start the next project properly.
    ⚠ And the client eventually feels the delay is
      yours.

  ⚠ WHAT TO DO ABOUT IT — ⚠ AND CHAPTER 18 IS BUILT
    AROUND THIS
  ⚠ 1. ⚠ Establish at discovery what content exists
     and ⚠ WHO WILL WRITE THE REST, BY NAME.
     Section 17.6.
  ⚠ 2. ⚠ Put content deadlines in the proposal as
     DEPENDENCIES. Section 28.4.
  ⚠ 3. ⚠ Price content writing as a real service and
     offer it. Section 26.8.
  ⚠ 4. ⚠ Stage payments so a stall does not strand
     your cash. Section 28.10.
  ⚠ 5. ⚠ And have a written stalled-project procedure.
     Section 33.4.

  ⚠ ⚠ A CONSULTANT WHO SOLVES THE CONTENT PROBLEM IS
    WORTH MORE THAN ONE WHO DESIGNS BETTER.
=================================================================

1.6 The Three Kinds of Buyer

=================================================================
  ⚠ 1. THE OWNER-OPERATOR
     ⚠ Decides alone, fast. ⚠ Trades, salons, cafés,
       single-practitioner services.
     ⚠ CARES ABOUT: ⚠ cost, ⚠ whether it will actually
       work, ⚠ and whether they will be stuck with
       you.
     ⚠ ⚠ SELL: ⚠ a fixed price, a clear finish, and the
       fact that they will own everything.

  ⚠ 2. THE OFFICE MANAGER OR MARKETING PERSON
     ⚠ Recommends upwards. ⚠ Professional firms,
       larger trades, nonprofits.
     ⚠ CARES ABOUT: ⚠ not being blamed, ⚠ approvals,
       ⚠ documentation, ⚠ and what happens when you are
       unavailable.
     ⚠ ⚠ SELL: ⚠ process, ⚠ written approvals, ⚠ handoff
       documentation, ⚠ and a care plan.
     ⚠ ⚠ THIS BUYER GIVES YOU RECURRING WORK.

  ⚠ 3. THE COMMITTEE
     ⚠ Nonprofits, partnerships, membership bodies.
     ⚠ CARES ABOUT: ⚠ everybody having been consulted.
     ⚠ ⚠ SELL: ⚠ a decision-making process — ⚠ WHO SIGNS
       OFF, ⚠ HOW MANY ROUNDS, ⚠ AND WHAT HAPPENS IF
       THEY DISAGREE. Section 19.5.
     ⚠ ⚠ AND PRICE IT HIGHER, ⚠ BECAUSE IT WILL TAKE
       LONGER. Section 27.4.

  ⚠ ⚠ IDENTIFY WHICH IN THE FIRST FIVE MINUTES.
    ⚠ AND FOR ALL THREE, ⚠ ASK WHO ACTUALLY APPROVES.
    Section 17.5.
=================================================================

1.7 What Makes a Business a Good Client

=================================================================
  [ ] They can say what the site is for, in one
      sentence
  [ ] ⚠ ONE NAMED PERSON APPROVES THINGS
  [ ] ⚠ Content exists, or somebody is genuinely
      assigned to write it
  [ ] They own their own domain — ⚠ or are willing
      to. Chapter 4.
  [ ] Photographs exist, or they will pay for some
  [ ] There is a real deadline, ⚠ but not an
      impossible one
  [ ] They are willing to pay a deposit
  [ ] They can tell you what an enquiry is worth to
      them
  [ ] ⚠ And they answer emails within a few days

  ⚠ ⚠ THE STRONGEST SINGLE SIGNAL
    ⚠ ⚠ THEY CAN NAME THE ONE PERSON WHO APPROVES.
  ⚠ ⚠ A project with a named approver finishes.
    ⚠ A project with "we'll all have a look" does
    not. Section 19.6.

  ⚠ AND THE SECOND STRONGEST
    ⚠ ⚠ CONTENT ALREADY EXISTS IN SOME FORM.
  ⚠ Even badly written, even out of date — ⚠ editing
    something is a completely different problem from
    creating it from nothing. Section 18.4.
=================================================================

1.8 ⚠ What Makes a Business a Bad One

=================================================================
  ⚠ THE ONES TO DECLINE, ⚠ POLITELY AND EARLY.

  ✗ ⚠ ⚠ THEY WILL NOT OWN THEIR OWN DOMAIN.
      ⚠ Chapter 4. ⚠ ⚠ THIS ONE IS ABSOLUTE.
  ✗ ⚠ ⚠ Nobody will approve anything
  ✗ ⚠ "We'll all have a look and let you know"
  ✗ ⚠ ⚠ No content, and nobody assigned to write it
  ✗ ⚠ "Just make it look like [COMPETITOR]"
      ⚠ Section 19.9.
  ✗ ⚠ ⚠ Images they cannot show you a licence for.
      Chapter 5.
  ✗ ⚠ A budget that is a fraction of the work
  ✗ ⚠ ⚠ An expectation of rankings, traffic, or sales
      that nobody could promise. Section 25.8.
  ✗ ⚠ ⚠ Unlimited revisions expected. Section 19.5.
  ✗ ⚠ A previous developer still owed money
      ⚠ Section 7.6.
  ✗ ⚠ ⚠ Anything from Chapter 7
  ✗ ⚠ Anybody who has fallen out with two previous
      developers

  ⚠ ⚠ THE TWO THAT MATTER MOST
    ⚠ ⚠ A CLIENT WHO WILL NOT OWN THEIR DOMAIN IS
      ASKING YOU TO HOLD SOMETHING THAT SHOULD NEVER
      BE YOURS.
    ⚠ ⚠ AND A CLIENT WITH NO NAMED APPROVER WILL
      REVISE FOREVER, ⚠ BECAUSE THERE IS NOBODY WHO
      CAN SAY YES.
=================================================================

1.9 The Realistic Size of a First Project

=================================================================
  ⚠ SMALLER THAN YOU WANT. ⚠ DELIBERATELY.

  WHAT A GOOD FIRST PROJECT LOOKS LIKE
    ⚠ Four to six pages.
    ⚠ ⚠ CONTENT THAT MOSTLY EXISTS ALREADY.
    ⚠ One named approver.
    ⚠ No shop, no bookings, no logins, no payments.
      ⚠ Chapter 7.
    ⚠ A domain the client already owns, or is happy
      to register themselves.
    ⚠ A business you understand.
    ⚠ And a deadline that is real but not tight.

  ⚠ WHY SMALL IS STRATEGICALLY CORRECT
  ⚠ It proves you deliver, ⚠ which is the only thing a
    first client is actually buying.
  ⚠ It limits your exposure while you learn.
  ⚠ ⚠ It gets launched, ⚠ which a large project
    frequently does not.
  ⚠ ⚠ AND IT BECOMES A PORTFOLIO PIECE AND A CARE
    PLAN. Chapters 31 and 34.

  ⚠ WHAT TO SAY WHEN A FIRST CLIENT WANTS EVERYTHING
  ⚠ "Let's do the core site first and get it live.
    Everything else gets easier once there's
    something real to add to — and if we build it
    all at once, the shop is what stops it launching
    for four months."
  ⚠ ⚠ This wins work. ⚠ It sounds like experience,
    ⚠ because it is.
=================================================================

1.10 How This Differs From Graphic Design and Software Development

=================================================================
  ⚠ CLIENTS WILL CONFUSE YOU WITH BOTH. ⚠ CORRECT IT
    EARLY. Chapter 3.

  ⚠ GRAPHIC DESIGN
    ⚠ Produces something that is looked at. ⚠ Finished
      when approved. ⚠ Judged on taste.
  ⚠ ⚠ YOURS: ⚠ produces something USED, ⚠ on devices you
    do not own, ⚠ by people with needs you cannot
    see, ⚠ that must keep working afterwards.

  ⚠ SOFTWARE DEVELOPMENT
    ⚠ Builds systems from scratch. ⚠ Deep technical
      depth. ⚠ Long-term ownership of code.
  ⚠ ⚠ YOURS: ⚠ assembles a site from parts other people
    made, ⚠ and the valuable skill is judgement about
    what to include rather than what to code.
  ⚠ ⚠ AND ANYTHING THAT BECOMES REAL SOFTWARE — ⚠ a
    booking system, a members' area, a shop with
    unusual requirements — ⚠ IS A DIFFERENT PRODUCT
    WITH DIFFERENT RISK. Chapter 7.

  ⚠ THE ONE-SENTENCE VERSION FOR CLIENTS
  ⚠ "I build small business websites that work
    properly on a phone, that you own completely,
    and that somebody can still update in three
    years."
  ⚠ ⚠ Say it early. ⚠ It sets scope, ⚠ mentions
    ownership before they have to ask, ⚠ and promises
    the thing they did not know to want.
=================================================================

How AI Helps

Paste your standing context block first (Section 36.2) before any of these.

AI is useful here for: turning a client's own words into a problem statement, drafting the page list, and preparing discovery questions.

AI is not useful here for: telling you whether a business will buy, what anything costs locally, or anything about a real client. Never put a client's name, site, credentials, or documents into an AI tool. Section 36.5.

Prompt 1 — the page list that sells

"I am a small-business website developer. A prospective client described their situation like this, with all identifying details removed and replaced by [BRACKETS]: [PASTE A GENERIC DESCRIPTION — no business name, no domain, no location detail]. Produce two things. First, the problem written back in three forms: a single sentence the owner could have written themselves; a short paragraph naming what they are losing and how often; and the five questions I still need answered before I could quote — including who approves things, what content exists and who will write the rest, who owns the domain and hosting, what the site must legally do, and what an enquiry is worth to them. Second, a proposed page list — just titles, with one sentence each on what that page would say and who it is for — because a page list is frequently more persuasive than a design. Do not propose a design, do not name any platform, and do not estimate a price or a timescale."

Prompt 2 — the qualification check

"Act as a sceptical adviser to a small-business website developer. Here is an opportunity in general terms: [DESCRIBE THE BUSINESS TYPE, ROUGHLY WHAT THEY WANT, AND WHAT THEY SAID — no client identity]. Assess it against a good-client checklist: can they say what the site is for in one sentence; is there one named person who approves; does content exist or is somebody genuinely assigned to write it; do they own their own domain or will they; do photographs exist; is there a real but not impossible deadline; will they pay a deposit; and do they answer emails. Then against a bad-client list: they will not own their own domain, flagged as an absolute decline; nobody approves anything; no content and nobody assigned; 'just make it look like [COMPETITOR]'; images with no licence; a budget that is a fraction of the work; expectations of rankings or sales nobody could promise; unlimited revisions expected; a previous developer still owed money; and anything involving payments, bookings, logins, or health, financial, or children's data. Conclude with a clear recommendation to pursue, ask more questions, or decline — and give no revenue estimate."

Prompt 3 — the "why now" and content questions

"Write the opening five minutes of a discovery call for a small-business website developer, built around finding out why they are calling now, since the reason shapes everything: something broke or expired; the business changed; somebody embarrassed them; or they are trying to grow. Give the question, four follow-ups for each answer, and what each reason means for how I should scope and price. Then write the content conversation — the single biggest cause of stalled projects — covering what content exists today, what is out of date, what is missing entirely, who by name will write the missing pieces and by when, whether photographs exist and who owns them, and whether they would want me to quote for writing instead. Finish with the sentence I say when somebody says 'we just need a simple site', explaining that the page count is almost irrelevant to the effort. Make no promise about results, rankings, or timescales."


Common Mistakes

Presenting designs before understanding the problem. "They're all very nice" is the sound of having answered the wrong question.

Selling design to somebody who wants enquiries.

Not asking "why now?" The reason shapes the scope, the price, and the urgency.

Accepting "we just need a simple site" at face value. The page count is almost irrelevant to the effort.

Not establishing at discovery who will write the content, by name. It is the biggest single cause of failed projects.

Assuming content will arrive because somebody said it would.

Taking a project with no named approver. There is nobody who can say yes, so revisions never end.

Taking a project where the client will not own their own domain.

Not asking to see a licence for images the client supplied.

Quoting on page count rather than on the work.

Not noticing which of the three buyer types you are talking to. The same proposal wins with one and loses with the others.

Underquoting a committee. It will take longer, and that is not a criticism of them.

Competing on price against a website builder. Sell the parts the builder does not do.

Letting a client believe you are their IT support, their copywriter, or their SEO agency.


Safety, Legal, Ethical, and Professional Considerations

Decline any project where the client will not own their own domain and hosting account. Chapter 4.

Never agree to copy another business's site, layout, or content. Section 19.9 and Chapter 5.

Ask, at first contact, whether the client can show a licence for any images, fonts, or content they supply — and record the answer. Chapter 5.

Make no promise about rankings, traffic, enquiries, or sales, at any stage, including informally in a first conversation. Section 25.8.

Do not describe yourself as providing IT support, security services, accessibility auditing, SEO guarantees, or legal advice. Chapter 3.

Never state that a site will be accessible, secure, or compliant. You can describe what you build and test; you cannot certify. Chapter 6.

Decline projects involving payment or card data, bookings that hold money, member logins, or health, financial, or children's information until you have experience and written confirmation of insurance cover. Chapter 7.

Never take on a rescue where a previous developer is still owed money without the client resolving that first. Section 7.6.

Do not put a client's name, domain, site content, credentials, or documents into an AI tool while assessing an opportunity. Section 36.5.

Verify anything AI tells you about your market, competitors, or pricing before acting on it. Section 10.8.

This book states no law, licence, platform rule, technical specification, price, professional standard, or tax obligation. Confirm all of them with qualified professionals, official agencies, and the platforms' own current documentation.


Do This Now

=================================================================
  [ ] Write your one-sentence description, including
      ownership. Section 1.10.

  [ ] ⚠ Add "why now?" to your first-contact
      questions.

  [ ] ⚠ Add "who approves things?" — and treat a
      missing answer as a warning.

  [ ] ⚠ Add "what content exists, and who is writing
      the rest?"

  [ ] ⚠ Add "who owns the domain?" to every first
      conversation. Chapter 4.

  [ ] Write the "five pages is a sensible size, but
      most of the work isn't the pages" sentence.

  [ ] Practise proposing a page list instead of a
      design.

  [ ] ⚠ Write your bad-client list and sign it.
      Resource 3.

  [ ] Decide, in writing, the maximum size of your
      first project.

  [ ] Write what you will say when somebody asks for
      a copy of a competitor's site.

  [ ] And ⚠ list every local business you already know
      whose site looks broken on a phone.
=================================================================

Chapter Summary

Row lost a project by showing three beautiful designs and won the next one with seven page titles on a sheet of paper. The accountancy partner was not being difficult — "which one gets us more of the right sort of enquiry?" was the only question that mattered.

Nobody buys a website. They buy being findable with correct information, looking like a real business, not answering the same six questions, getting enquiries that actually arrive, and stopping worrying about it.

Ask why they are calling now. Something broke, the business changed, somebody embarrassed them, or they are trying to grow — and each buys a different thing and pays differently.

"We just need a simple site" is never simple. The page count is almost irrelevant to the effort, and saying so early prevents an underquoted project.

Content is the single biggest cause of failed projects — not design. Establish at discovery what exists and who will write the rest, by name, and treat it as a dependency with dates.

Three buyer types: the owner-operator wants a fixed price and a clear finish; the office manager wants process and documentation and gives you recurring work; the committee needs a decision-making process and should be priced higher.

The strongest signal of a good client is that they can name the one person who approves. A project with a named approver finishes; a project with "we'll all have a look" does not.

Two absolute declines: a client who will not own their own domain, and a client with no named approver.

Take a first project smaller than you want — four to six pages, content that mostly exists, one approver, no shop or bookings or logins — because small projects get launched and large first projects frequently do not.

And correct the confusion with graphic design and software development early. You are not producing something looked at; you are producing something used, on devices you do not own, that must still work in three years.


That's where the preview ends

The rest of the book — 42 further sections — comes with your purchase, along with the worksheets, the resource library and the full set of AI prompts.

Everything in the book

  1. 01 Introduction Why Website Development Works — included above
  2. 02 What Clients Actually Buy — included above
  3. 03 The Four Business Models
  4. 04 What This Work Is Not
  5. 05 Domain Hosting And Ownership
  6. 06 Copyright And Licensing
  7. 07 Accessibility As A Design Decision
  8. 08 Work You Should Not Take
  9. 09 Choosing Your Services
  10. 10 Selecting A Profitable Niche
  11. 11 Researching The Market
  12. 12 One Page Business Plan
  13. 13 Startup Costs And Budget
  14. 14 Naming Branding And Positioning
  15. 15 Legal Insurance And Compliance
  16. 16 Choosing Platforms And Vendors
  17. 17 Skills And Practice Plan
  18. 18 The Discovery Call
  19. 19 Site Maps And Content Planning
  20. 20 Wireframes And Design Approval
  21. 21 Building The Site
  22. 22 Forms And Data
  23. 23 Security Updates And Backups
  24. 24 Launch
  25. 25 Client Handoff And Training
  26. 26 Analytics And What To Measure
  27. 27 Designing Offers And Packages
  28. 28 Setting Profitable Prices
  29. 29 Proposals And Agreements
  30. 30 Onboarding And Communication
  31. 31 Repeatable Delivery Workflow
  32. 32 Finding Your First Ten Customers
  33. 33 Your Own Website
  34. 34 Project Management And Difficult Situations
  35. 35 Care Plans And Recurring Revenue
  36. 36 Bookkeeping And Growing
  37. 37 Ai Tools And Your First Year
  38. 38 Resources Setup And Foundations
  39. 39 Resources Records And Registers
  40. 40 Resources Discovery And Build
  41. 41 Resources Offers And Agreements
  42. 42 Resources Communication And Trackers
  43. 43 Resources Plans And Prompts
  44. 44 Where To Go From Here