Introduction: What a Maintenance Plan Is Actually Selling

The unusual thing about the website maintenance market, why the work is invisible and what that costs you, the four rules the whole book rests on, what an ordinary month actually contains, who should not do this work, what this book will not tell you, and how to start.

---

The Unusual Thing About This Market

Almost every trade has a visible product. Somebody can look at it, hold it, or watch it happen.

⚠ This one does not.

A month of good website maintenance looks exactly like a month of nothing. The site was up. Nobody was hacked. The forms worked. The updates went on without incident. There is nothing to point at.

And a month of bad maintenance also looks like nothing — right up until the moment it does not, at which point it looks like a business with no website, no backups that work, and nobody who can explain what happened.

⚠ The two are indistinguishable from outside until something breaks.

That is the unusual thing about this market, and it produces two consequences you will live with for as long as you do this work.

The first is commercial. You are asking somebody to pay every month for something they cannot see. Section 35.4 is about nothing else.

The second is ethical, and it is more serious. Because the work is invisible, it is possible to charge for it and not do it, and nobody will find out for a long time. A great many people are doing exactly that right now, some of them deliberately and most of them by drift — a backup job that reports success, an update run without staging, a monitoring alert nobody reads.

⚠ Which is why this book is built on evidence rather than assurance. Restore the backup. Log the change. Document the recovery time. Report what you actually did. Not because a client demanded it, but because otherwise you cannot tell the difference either.

---

Why the Work Is Invisible, and What That Costs You

Nobody thanks you for a quiet month.

They will thank you, sincerely and at length, on the day something goes badly wrong and you fix it in an hour — which is to say, on the day your preparation is finally visible. The rest of the time, the better you are, the less anybody notices.

This has practical costs and you should know them before you start.

⚠ Clients cancel plans that are working. Not because they are unhappy. Because eleven quiet months in a row look like eleven months of paying for nothing. Section 35.3.

You will be asked, in a perfectly friendly way, what exactly it is you do. Repeatedly. By people who are paying you. And "I keep it running" is not an answer that survives that question. Chapter 26 exists for this.

You will be tempted to skip things. Not out of laziness — out of time. A restore drill takes an hour and nothing has ever gone wrong. That reasoning is correct on every single occasion except one, and you do not know which one.

⚠ And you will find that the visible work — a content change, a new page, something the client can see — is easier to charge for than the work that actually protects them. That imbalance is real, and Chapter 25 is about not letting it eat your plan.

The counterweight to all of this is a written record. What you did. What you found. What you tested. The record is not administration. In a trade with no visible product, the record is the product.

---

The Four Rules

Everything in this book rests on four rules. They are stated in full in Chapters 4 to 7 and referred to in almost every chapter after that.

⚠ Rule 1. You have restored a backup before you promise one. Chapter 4.

Not "the backup job is running." Restored. To somewhere. And looked at what came back — the files, the database, the uploads, the thing that was silently excluded eight months ago when a configuration default changed.

⚠ Rule 2. Every credential is theirs, held the way they can revoke it, and no password ever travels in a message. Chapter 5.

The domain is theirs. The hosting is theirs. You have your own named access, they can remove it in ninety seconds, and you remove it yourself on the last day without being asked — including when there is money outstanding.

⚠ Rule 3. Nothing goes live that has not been through staging, and you can always put it back. Chapter 6.

And "I can put it back" means you have actually put something back at least once and know how long it takes, because that number is what you will be asked for while somebody's site is down.

⚠ Rule 4. The plan says exactly what is included, what is not, and what happens at two in the morning — in writing, before the first payment. Chapter 7.

Scope is what destroys this business. Not technically. Commercially. A maintenance plan with an unstated boundary becomes an unpaid emergency service staffed by one exhausted person, and it happens gradually enough that you will not notice until you resent your own clients.

These four are not best practice. They are the difference between a service and a liability.

---

What an Ordinary Month Actually Contains

Not what the marketing says. What it is.

Roughly a third of it is routine work you do the same way every time. Checking that backups ran and — on a schedule — proving one of them restores. Applying updates on staging first, then live. Reading the monitoring. Checking that forms still deliver. Looking at what changed.

Roughly a third is small requests. A phone number to update. A member of staff to add. A PDF to swap. Each one takes eleven minutes and interrupts something. Chapter 25.

Roughly a quarter is writing things down. The change log, the update log, the monthly report, the runbook entry for the thing you had to work out from scratch. This is the part people skip, and it is the part that makes the rest defensible.

And the remainder is the thing you cannot schedule. A site down. An update that broke a page. A plugin abandoned by its author. A client who has been hacked and does not know yet.

⚠ Some months there is none of that. Some months it is the whole month. Chapter 34.

What an ordinary month does not contain: dramatic technical work, interesting problems, or anybody noticing. It contains careful, repetitive, largely invisible attention — and the willingness to be reachable when it stops being ordinary.

---

⚠ Who Should Not Do This Work

⚠ This section is here because the wrong person doing this work causes real harm to real businesses.

Do not do this if you cannot be reached within a stated time. You do not have to be available at all hours — almost nobody should be. But you must be honest about what your response time actually is on your worst week, and then keep it. Section 7.4.

Do not do this if you will not write things down. Not occasionally. Every time. The change log is what tells you which of last week's four changes broke the page.

Do not do this if you would guess on somebody's live site. Guessing is how an hour of downtime becomes a day. The correct response to not knowing is staging, a backup you have restored, and, sometimes, telling the client you need to bring somebody in. Section 23.9.

Do not do this if you cannot say no. You will be asked for guarantees you cannot give, access you should not have, work outside what you support, and favours that are really projects. Chapter 8 is a chapter of refusals and Resource 3 is a signed statement, because these are easier to hold when you decided them in advance.

Do not do this if you need it to be passive. ⚠ It is a promise, renewed every month, that somebody is paying attention. That is the opposite of passive, and anybody selling it to you as passive income is selling you something.

And do not do this yet if you have never restored a backup. ⚠ Not "not yet as a business" — not at all. Chapter 18 tells you how to practise on sites nobody is paying for, and Section 18.5 tells you to break things on purpose first.

---

What This Book Will Not Tell You

⚠ Read this list carefully. It is not modesty.

It will not tell you the law. Not contract, not liability, not data protection, not consumer protection, not what your obligations are when a client's site is breached. Chapter 16 is a chapter of questions with blank spaces for the answers you obtain from a qualified attorney.

It will not tell you any tax rule, rate, threshold, or obligation. Ask an accountant.

It will not tell you what insurance you need or what any policy covers. ⚠ In this trade you hold administrative access to other people's businesses, and that is an unusual exposure. Ask a broker, before your first client.

It will not name any software, plugin, host, platform, monitoring service, or vendor, and it recommends none. Tools are acquired, abandoned, repriced, and rewritten. Section 17.1 explains the reasoning: what outlasts them is knowing what to ask of any tool.

It will not state any platform's, host's, or service's rules or terms. Those differ and change without notice. You read the current ones yourself and record the date. Resource 10.

It will not state any technical specification, version requirement, configuration value, or standard. Check current documentation with the vendor.

It will not state any price, fee, or rate. Every monetary figure in this book is either blank for you to fill in or explicitly labelled as an illustrative working assumption in United States dollars, invented to demonstrate arithmetic.

⚠ And it will not promise you anything. No income, no clients, no retention, no uptime, no security, no results. Most first years in this trade do not cover their costs, and even the deliberately optimistic scenario in Section 28.9 comes out modest.

---

What You Actually Get

Thirty-seven chapters, in the order the work actually happens: understanding what a plan is selling, the four rules, what you will refuse, what you will support, who you will support it for, what it costs you, what to charge, how to inspect a site before quoting, how to take over access without breaking anything, how to run the monthly work, what to do when something breaks, how to report it, how to keep the client, and how to run the business underneath all of it.

Sixty-eight printable resources — registers, checklists, runbooks, inspection sheets, drill logs, message templates, and trackers. They are blanks, and the blanks are the point: every price, response time, capacity number, recovery time, and hourly figure is yours to establish.

One hundred copy-and-paste AI prompts, each with its safety constraints written in.

⚠ A realistic scenario in every chapter, drawn from the composite practitioner this book follows — Kit, who is not a real person and whose mistakes are the useful part.

⚠ And a consistent position on AI, stated in Chapter 37 and applied throughout: an assistant, never an authority. It drafts, structures, summarises, and finds what you forgot. It never touches a credential, a client's data, or a live site, and every fact, figure, command, and communication it produces is checked by a person before it is used.

---

Start Here

If you have never done this work: read Chapters 4 to 7 before anything else. They are the four rules and everything depends on them. Then read Chapter 8, which is what you will refuse. Then go and practise on something nobody is paying for. Chapter 18.

If you already do this work: go to Chapter 4 and answer one question honestly. When did you last restore a backup for a client, and look at what came back?

If the answer is "never", start there, today, before you read anything else.

⚠ And if the answer is "the backup job reports success every night" — that is the sentence at the front of this book, and it is not the same thing.

---

Chapter 1: Understanding the Industry and What Clients Actually Buy

The veterinary practice that left over $40 a month and came back after 63 hours of downtime, because the cheaper provider's stated response time was one business day. What clients are actually paying for, and why it is not expertise.

---

The Scenario

Kit lost a client over forty dollars a month and got them back six weeks later over a Friday evening.

The client was a veterinary practice. Four vets, a booking form, and a site that mattered more than they realised because most of their new clients found them through it.

They left because somebody quoted less. The competitor's plan looked comparable on paper — updates, backups, security monitoring, a monthly report. It was $40 a month cheaper. Kit said that was a fair decision, handed everything over properly, and removed their own access the same day. Section 34.9.

⚠ Six weeks later the site went down at ten past six on a Friday evening.

They emailed the new provider. Nothing happened. They emailed again on Saturday morning. The reply arrived at nine o'clock on Monday, and it was perfectly polite and entirely reasonable: the plan's stated response time was one business day, and Monday morning was one business day.

The site had been down for sixty-three hours. The booking form had been down with it. The practice does not know how many people tried to book an appointment over that weekend, and neither does anybody else.

They came back to Kit on the Tuesday.

⚠ The thing they had actually been buying was never the maintenance. The updates were identical. The backups were probably identical. What they had been buying, without ever having said so and possibly without knowing it, was a person who would look at it on a Friday evening.

Kit's plan had never promised that. Kit's plan said what it did say, honestly, and Kit had answered on the Friday because Kit was there and it took twenty minutes.

⚠ The lesson is not "be available at all hours." It is that clients cannot describe what they are buying, and the thing they are actually buying is almost never the list of tasks.

---

1.1 What a Client Is Really Paying For

=================================================================
  ⚠ ⚠ NOT THE TASK LIST. ⚠ ⚠ THEY CANNOT EVALUATE THE
    TASK LIST AND THEY KNOW IT.

  ⚠ ⚠ WHAT THEY ARE ACTUALLY BUYING
  ⚠ 1. ⚠ ⚠ SOMEBODY WHO WILL ANSWER.
     ⚠ ⚠ The single largest component, and the one
       nobody puts on a plan page.
  ⚠ 2. ⚠ ⚠ NOT HAVING TO THINK ABOUT IT.
     ⚠ ⚠ The absence of a background worry.
  ⚠ 3. ⚠ ⚠ SOMEBODY WHO WILL UNDERSTAND WHAT HAPPENED
     AND EXPLAIN IT WITHOUT MAKING THEM FEEL STUPID.
  ⚠ 4. ⚠ ⚠ A ROUTE BACK FROM A DISASTER.
     ⚠ ⚠ Which is why Rule 1 is Rule 1.
     ⚠ Chapter 4.
  ⚠ 5. ⚠ ⚠ And ⚠ ⚠ SOMEBODY WHO IS STILL THERE IN TWO
     YEARS.

  ⚠ ⚠ WHAT THEY ARE NOT BUYING
    ✗ ⚠ ⚠ Your technical ability, which they cannot
        assess
    ✗ ⚠ ⚠ The number of tasks on the plan
    ✗ ⚠ ⚠ The tools you use, which they have never
        heard of
    ✗ ⚠ ⚠ Speed, except during an incident
    ✗ ⚠ ⚠ And ⚠ ⚠ ANYTHING THEY WOULD HAVE TO UNDERSTAND
        IN ORDER TO VALUE

  ⚠ ⚠ THE CONSEQUENCE FOR HOW YOU SELL
    ⚠ ⚠ A PLAN PAGE THAT LISTS TWELVE TASKS COMPETES ON
      THE NUMBER OF TASKS AND THEN ON PRICE.
    ⚠ ⚠ A plan page that says plainly what happens when
      something goes wrong, and when, competes on the
      thing they are actually buying.
      ⚠ Section 7.4.

  ⚠ ⚠ THE HONEST WARNING
    ⚠ ⚠ THIS IS NOT PERMISSION TO PROMISE MORE THAN YOU
      CAN DELIVER.
  ⚠ ⚠ The competitor in the scenario did nothing wrong.
    ⚠ ⚠ THEY STATED ONE BUSINESS DAY AND THEY MET IT.
    ⚠ ⚠ Promise what you can keep on your worst week,
    and keep it.
=================================================================

---

1.2 Why "Peace of Mind" Is a Description and Not a Product

=================================================================
  ⚠ ⚠ EVERY PLAN PAGE IN THIS TRADE SAYS IT, AND IT
    SELLS NOTHING.

  ⚠ ⚠ THE PROBLEM WITH THE PHRASE
    ⚠ ⚠ IT IS AN OUTCOME, NOT A FEATURE — ⚠ ⚠ AND YOU
      CANNOT EVIDENCE IT.
    ⚠ ⚠ It is identical on every competitor's page.
    ⚠ ⚠ It says nothing about what you do.
    ⚠ ⚠ And ⚠ ⚠ IT IS EXACTLY WHAT THE PROVIDER WHO DOES
      NOTHING ALSO SAYS.

  ⚠ ⚠ WHAT TO SAY INSTEAD — ⚠ ⚠ FACTS THEY CAN CHECK
    ✗ "Peace of mind" →
    ⚠ "I restore one of your backups every month and
      tell you how long it took."
    ✗ "We keep your site secure" →
    ⚠ "Updates go on a staging copy first. If one
      breaks something, I put it back the same day."
      ⚠ Section 23.2.
    ✗ "24/7 monitoring" →
    ⚠ "If the site goes down I get an alert. I reply
      within [X], including evenings and weekends."
      ⚠ Section 24.2.
    ✗ "Always here when you need us" →
    ⚠ "One person. Me. You get my number."

  ⚠ ⚠ THE PATTERN
    ⚠ ⚠ REPLACE EVERY FEELING WITH SOMETHING THAT
      HAPPENED, ON A DATE, THAT YOU CAN SHOW THEM.
  ⚠ ⚠ IN A TRADE WITH NO VISIBLE PRODUCT, EVIDENCE IS
    THE PRODUCT. ⚠ Chapter 26.

  ⚠ ⚠ THE THING THAT MAKES THIS WORK COMMERCIALLY
    ⚠ ⚠ ALMOST NOBODY ELSE DOES IT.
    ⚠ ⚠ The category is full of identical assurance
      language, and a page of plain checkable
      statements is conspicuous.
  ⚠ ⚠ THAT IS AN OBSERVATION ABOUT THE CATEGORY, NOT A
    PROMISE ABOUT YOUR SALES.
=================================================================

---

1.3 The Question Every Client Cannot Answer

=================================================================
  ⚠ ⚠ ASK IT IN THE FIRST CONVERSATION.

  ⚠ ⚠ THE QUESTION
    ⚠ ⚠ "IF YOUR SITE DISAPPEARED TONIGHT, WHO WOULD
      YOU CALL, AND HOW LONG WOULD IT TAKE TO GET IT
      BACK?"

  ⚠ ⚠ WHAT THE ANSWERS TELL YOU
    ⚠ ⚠ "I DON'T KNOW" — ⚠ ⚠ the commonest, and honest.
      ⚠ ⚠ THEY HAVE NEVER THOUGHT ABOUT IT AND YOU HAVE
      JUST BECOME USEFUL.
    ⚠ ⚠ "The person who built it" — ⚠ ⚠ ask when they
      last spoke to them.
    ⚠ ⚠ "The hosting company" — ⚠ ⚠ ask what their
      hosting actually includes, and whether they have
      checked.
    ⚠ ⚠ "We have backups" — ⚠ ⚠ ASK WHEN ONE WAS LAST
      RESTORED. ⚠ Chapter 4.
    ⚠ ⚠ "It's fine, nothing's ever happened" —
      ⚠ ⚠ accurate, and not an answer.

  ⚠ ⚠ THE FOLLOW-UP QUESTIONS THAT ALSO CANNOT BE
    ANSWERED
    ⚠ ⚠ "Who owns the domain?" ⚠ Section 20.2.
    ⚠ ⚠ "Who can log in as an administrator?"
      ⚠ Section 20.5.
    ⚠ ⚠ "What happens to the site if the person who
      built it stops answering?"
    ⚠ ⚠ "Where do the contact form messages go, and did
      you check last week?"
    ⚠ ⚠ And ⚠ ⚠ "WHAT WOULD IT COST YOU TO BE DOWN FOR
      THREE DAYS?"

  ⚠ ⚠ WHY THIS MATTERS MORE THAN A PITCH
    ⚠ ⚠ YOU ARE NOT CATCHING THEM OUT.
    ⚠ ⚠ Nobody expects a four-person practice to have
      thought about disaster recovery.
  ⚠ ⚠ THE QUESTIONS DO THE SELLING BECAUSE THEY MAKE
    THE RISK VISIBLE — ⚠ ⚠ AND VISIBLE RISK IS THE ONLY
    THING THAT MAKES INVISIBLE WORK PURCHASABLE.

  ⚠ ⚠ THE RULE FOR ASKING THEM
    ⚠ ⚠ ASK, LISTEN, AND WRITE THE ANSWER DOWN.
      ⚠ Resource 8.
    ⚠ ⚠ DO NOT USE THE ANSWER TO FRIGHTEN THEM.
      ⚠ Section 15.4.
  ⚠ ⚠ Fear closes a first sale and loses the second
    one.
=================================================================

---

1.4 How Small Organisations Actually Choose Somebody

=================================================================
  ⚠ ⚠ NOT THE WAY THE MARKETING ADVICE ASSUMES.

  ⚠ ⚠ HOW IT ACTUALLY HAPPENS, IN ORDER OF FREQUENCY
  ⚠ 1. ⚠ ⚠ SOMEBODY THEY KNOW RECOMMENDED YOU.
     ⚠ ⚠ By a distance. ⚠ Chapter 32.
  ⚠ 2. ⚠ ⚠ THE PERSON WHO BUILT THE SITE STOPPED
     ANSWERING, AND THEY ASKED AROUND.
  ⚠ 3. ⚠ ⚠ Something broke and they searched in a
     hurry.
  ⚠ 4. ⚠ ⚠ Somebody told them their site was out of
     date, and they believed it.
  ⚠ 5. ⚠ ⚠ And occasionally, ⚠ ⚠ THEY WERE COLD-CALLED BY
     SOMEBODY WHO FRIGHTENED THEM.

  ⚠ ⚠ WHAT NUMBER 2 MEANS FOR YOU
    ⚠ ⚠ A LARGE SHARE OF THIS MARKET IS ABANDONED
      SITES.
    ⚠ ⚠ Built well or badly, then left, because the
      builder moved on, got busy, or stopped
      responding.
  ⚠ ⚠ YOUR COMPETITOR IS FREQUENTLY NOT ANOTHER
    PROVIDER. ⚠ ⚠ IT IS SILENCE.

  ⚠ ⚠ WHAT THEY DO WHEN THEY HAVE A NAME
    ⚠ ⚠ Look at your site. ⚠ ⚠ Briefly.
    ⚠ ⚠ Look for a real person and a real place.
    ⚠ ⚠ Look for a price, or the absence of one.
    ⚠ ⚠ Send an email, or fill in a form.
    ⚠ ⚠ And ⚠ ⚠ SEE HOW LONG YOU TAKE TO REPLY —
      ⚠ ⚠ WHICH IS THE ACTUAL TEST AND THEY DO NOT KNOW
      THEY ARE RUNNING IT.

  ⚠ ⚠ WHAT DECIDES IT
    ⚠ ⚠ Whether you answered.
    ⚠ ⚠ Whether you explained something without
      condescending.
    ⚠ ⚠ Whether you were willing to say what you would
      not do. ⚠ Chapter 8.
    ⚠ ⚠ And ⚠ ⚠ WHETHER YOU SEEMED LIKE SOMEBODY WHO
      WOULD STILL BE THERE.

  ⚠ ⚠ WHAT ALMOST NEVER DECIDES IT
    ✗ ⚠ ⚠ Your technical depth
    ✗ ⚠ ⚠ Your portfolio
    ✗ ⚠ ⚠ Your logo
    ✗ ⚠ ⚠ The number of tasks on your plan
=================================================================

---

1.5 ⚠ What the Last Person Did to Them

=================================================================
  ⚠ ⚠ ASSUME THERE WAS A LAST PERSON, AND THAT IT
    ENDED BADLY.

  ⚠ ⚠ WHAT YOU WILL FIND, REPEATEDLY
    ⚠ ⚠ NOBODY KNOWS WHO OWNS THE DOMAIN.
      ⚠ Section 20.2.
    ⚠ ⚠ The hosting is in somebody else's name, or in
      an account nobody can log into.
    ⚠ ⚠ There are four administrator accounts and the
      client recognises one.
    ⚠ ⚠ ⚠ SOMEBODY IS STILL BEING PAID FOR SOMETHING
      NOBODY CAN DESCRIBE.
    ⚠ ⚠ Backups exist and have never been restored.
    ⚠ ⚠ The previous provider held access until an
      invoice was paid. ⚠ Section 5.8.
    ⚠ ⚠ Or ⚠ ⚠ THE PREVIOUS PROVIDER SIMPLY STOPPED
      REPLYING, AND NOBODY EVER FOUND OUT WHY.

  ⚠ ⚠ WHAT THIS MEANS FOR THE FIRST CONVERSATION
    ⚠ ⚠ THEY MAY BE EMBARRASSED, AND IT IS NOT THEIR
      FAULT.
    ⚠ ⚠ Say so. ⚠ ⚠ "This is extremely common" is true
      and it is the most useful sentence you can offer.

  ⚠ ⚠ WHAT NEVER TO DO
    ✗ ⚠ ⚠ CRITICISE THE PREVIOUS PROVIDER.
        ⚠ ⚠ You do not know what they were paid, what
        they were asked for, or what they were
        refused.
    ✗ ⚠ ⚠ Describe the site as a mess
    ✗ ⚠ ⚠ Imply the client should have known
    ✗ ⚠ ⚠ Use what you found to frighten them into a
        larger plan ⚠ Section 15.4.
    ✗ ⚠ ⚠ Or ⚠ ⚠ PROMISE TO FIX EVERYTHING IN THE MONTHLY
        FEE ⚠ Section 19.9.

  ⚠ ⚠ WHAT TO DO INSTEAD
    ⚠ ⚠ INSPECT IT BEFORE YOU QUOTE. ⚠ Chapter 12.
    ⚠ ⚠ Write down what you found, plainly, without
      adjectives. ⚠ Resource 19.
    ⚠ ⚠ Separate "must be fixed before I can maintain
      it" from "should be improved eventually".
    ⚠ ⚠ Quote the remediation separately.
      ⚠ Section 12.6.
    ⚠ ⚠ And ⚠ ⚠ BE WILLING TO DECLINE.
      ⚠ Chapter 8.

  ⚠ ⚠ THE OPPORTUNITY, STATED HONESTLY
    ⚠ ⚠ THE BAR IN THIS TRADE IS SOMEBODY WHO ANSWERS,
      EXPLAINS, AND HANDS EVERYTHING BACK WHEN ASKED.
  ⚠ ⚠ THAT IS A LOW BAR AND A LARGE NUMBER OF PROVIDERS
    DO NOT CLEAR IT.
=================================================================

---

1.6 What They Will Judge You On, and When

=================================================================
  ⚠ ⚠ THREE MOMENTS. ⚠ ⚠ NONE OF THEM ARE THE ROUTINE
    WORK.

  ⚠ ⚠ MOMENT 1 — ⚠ ⚠ THE FIRST REPLY
    ⚠ ⚠ How long it took, and whether it sounded like a
      person.
    ⚠ ⚠ This decides whether you get the work.
      ⚠ Section 1.4.

  ⚠ ⚠ MOMENT 2 — ⚠ ⚠ THE FIRST TIME SOMETHING BREAKS
    ⚠ ⚠ Not whether it broke. ⚠ ⚠ WHAT HAPPENED NEXT.
    ⚠ ⚠ Did you notice before they did? ⚠ ⚠ Did you say
      so immediately? ⚠ ⚠ Did you explain it without
      jargon? ⚠ ⚠ Did you say what you would do to stop
      it recurring? ⚠ Chapter 34.
  ⚠ ⚠ THIS DECIDES WHETHER YOU KEEP THE WORK, AND IT
    MATTERS MORE THAN EVERY QUIET MONTH COMBINED.

  ⚠ ⚠ MOMENT 3 — ⚠ ⚠ THE MONTH THEY WONDER WHY THEY ARE
    PAYING YOU
    ⚠ ⚠ It arrives, usually between months eight and
      fourteen. ⚠ Section 35.4.
    ⚠ ⚠ What they have in front of them at that moment
      is your reports.
  ⚠ ⚠ IF THOSE SAY "EVERYTHING RAN FINE", YOU HAVE
    NOTHING. ⚠ Section 26.2.

  ⚠ ⚠ WHAT THEY DO NOT JUDGE YOU ON
    ✗ Technical elegance
    ✗ How many updates you applied
    ✗ How fast you are on a routine task
    ✗ ⚠ ⚠ Anything they would need to understand in
        order to notice

  ⚠ ⚠ THE PRACTICAL CONSEQUENCE
    ⚠ ⚠ SPEND YOUR EFFORT ON: ⚠ ⚠ REPLYING, ⚠ ⚠ INCIDENT
      HANDLING, ⚠ ⚠ AND REPORTING.
    ⚠ ⚠ Those are the three surfaces a client actually
      touches.
  ⚠ ⚠ THE ROUTINE WORK STILL HAS TO BE DONE PROPERLY —
    ⚠ ⚠ BUT IT IS DONE FOR THE MOMENT IT MATTERS, NOT
    FOR THE CLIENT'S APPROVAL.
=================================================================

---

1.7 The Sites That Need This Most, and Least

=================================================================
  ⚠ ⚠ NEED IS NOT THE SAME AS WILLINGNESS TO PAY, AND
    BOTH MATTER.

  ⚠ ⚠ SITES THAT GENUINELY NEED IT
    ⚠ ⚠ ANYTHING WHERE THE SITE IS THE FRONT DOOR — ⚠ ⚠ a
      practice, a firm, a clinic, a trade business
      whose enquiries all arrive through a form.
    ⚠ ⚠ Anything running software that updates
      frequently. ⚠ Chapter 22.
    ⚠ ⚠ Anything with a form, a login, or a booking.
    ⚠ ⚠ Anything nobody in the organisation can
      administer.
    ⚠ ⚠ Anything built by somebody who has gone.
    ⚠ ⚠ And ⚠ ⚠ ANYTHING WHERE THREE DAYS OF DOWNTIME
      WOULD BE A REAL PROBLEM.

  ⚠ ⚠ SITES THAT DO NOT
    ⚠ ⚠ A genuinely static page that changes once a
      year.
    ⚠ ⚠ Something hosted on a fully managed platform
      that handles updates itself — ⚠ ⚠ AND SAYING SO IS
      HONEST AND WILL COST YOU A SALE.
      ⚠ Section 35.9.
    ⚠ ⚠ A site the organisation is about to replace.
    ⚠ ⚠ A site nobody uses.

  ⚠ ⚠ SITES THAT NEED IT AND WILL NOT PAY
    ⚠ ⚠ THE LARGEST AND MOST FRUSTRATING CATEGORY.
    ⚠ ⚠ Very small organisations with no budget line
      for it. ⚠ ⚠ Volunteer-run groups.
      ⚠ ⚠ Organisations where nobody owns the decision.
  ⚠ ⚠ DO NOT DISCOUNT YOUR WAY INTO THESE.
    ⚠ ⚠ A CLIENT WHO CANNOT AFFORD THE PLAN CANNOT
    AFFORD THE EMERGENCY EITHER, AND THAT CONVERSATION
    ARRIVES EVENTUALLY. ⚠ Section 28.6.

  ⚠ ⚠ THE CATEGORY TO BE MOST CAREFUL WITH
    ⚠ ⚠ SITES THAT HANDLE PAYMENTS, HEALTH INFORMATION,
      OR CHILDREN'S DATA.
    ⚠ ⚠ The need is real and so is the exposure.
      ⚠ Section 8.4.
  ⚠ ⚠ THOSE ARE NOT BEGINNER CLIENTS AND CHAPTER 8
    EXPLAINS WHY.

  ⚠ ⚠ THE HONEST FILTER
    ⚠ ⚠ "IF THIS SITE WERE DOWN FOR THREE DAYS, WOULD
      ANYBODY IN THAT ORGANISATION NOTICE BEFORE I DID?"
  ⚠ ⚠ IF THE ANSWER IS NO, THEY WILL NOT VALUE THE
    PLAN AND WILL CANCEL IT IN MONTH NINE.
=================================================================

---

1.8 ⚠ Saying Who This Is Not For

=================================================================
  ⚠ ⚠ THE MOST PERSUASIVE THING ON YOUR PLAN PAGE, AND
    ALMOST NOBODY WRITES IT.

  ⚠ ⚠ WHY IT WORKS
    ⚠ ⚠ EVERY COMPETITOR'S PAGE SAYS THEY CAN HELP
      EVERYONE.
    ⚠ ⚠ A page that names who it is not for reads as
      somebody with judgement rather than somebody with
      capacity to fill.
  ⚠ ⚠ IT ALSO PREVENTS THE CLIENT WHO WOULD HAVE MADE
    YOU MISERABLE. ⚠ Chapter 8.

  ⚠ ⚠ THE LINES TO WRITE — ⚠ ⚠ TRUE ONES ONLY
    ⚠ "Not for you if you need somebody available
      overnight. I'm not, and I'd rather say so."
    ⚠ "Not for you if your site takes payments — I
      don't maintain those." ⚠ Section 8.4.
    ⚠ "Not for you if you want a guarantee that
      nothing will go wrong. Nobody can give you
      that." ⚠ Section 24.1.
    ⚠ "Not for you if you want somebody to redesign
      the site. This plan keeps what you have working."
      ⚠ Section 3.3.
    ⚠ "Not for you if you can't give me administrative
      access. I can't maintain what I can't reach."
      ⚠ Section 8.3.
    ⚠ "Not for you if your site is on [PLATFORM] — I
      don't support it, and somebody who does will do a
      better job." ⚠ Section 9.4.

  ⚠ ⚠ THE ONE THAT COSTS THE MOST AND EARNS THE MOST
    ⚠ ⚠ TELLING SOMEBODY THEIR SITE DOES NOT NEED A
      PLAN AT ALL. ⚠ Section 35.9.
  ⚠ ⚠ It costs you a sale. ⚠ ⚠ It is also the single most
    referred-on sentence in this trade, and it only
    works if it is true.

  ⚠ ⚠ WHERE THESE LINES GO
    ⚠ ⚠ On the plan page, above the price.
    ⚠ ⚠ In the proposal. ⚠ Resource 41.
    ⚠ ⚠ In the agreement. ⚠ Chapter 29.
    ⚠ ⚠ And ⚠ ⚠ SAID OUT LOUD IN THE FIRST CONVERSATION.

  ⚠ ⚠ THE TEST
    ⚠ ⚠ IF YOUR PLAN PAGE COULD BE ANY PROVIDER'S PLAN
      PAGE, IT IS NOT SAYING ANYTHING.
=================================================================

---

How AI Helps

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

AI is useful here for: turning assurance language into checkable statements, building the discovery questions, and drafting the "not for you if" lines.

⚠ ⚠ AI is not useful here for: telling you what any host, platform, or plugin does, what any service level should be, or what you can safely promise. And never paste a client's name, site, credentials, or anything they told you. Section 37.4.

Prompt 1 — replacing assurance language with evidence

"Here is my draft plan page, or a plan page I am using as a model with the provider's name removed: [PASTE]. Flag every phrase that is an assurance rather than a checkable statement — peace of mind, we keep your site secure, always here, 24/7 monitoring, fully managed, worry-free, and anything similar. For each, write a replacement that describes something specific that happens, on a schedule, that I could show a client evidence of. Use only what I tell you I actually do: [LIST WHAT I ACTUALLY DO]. Invent no service, no frequency, no response time, and no capability. Flag anything in my list that I have not actually done yet — particularly restoring a backup — and tell me not to publish it until I have. Explain why assurance language fails here: it is identical on every competitor's page, it cannot be evidenced, and it is exactly what a provider who does nothing also says."

Prompt 2 — the discovery questions

"Build me a discovery question list for a first conversation with a small organisation about website maintenance. Lead with: if your site disappeared tonight, who would you call, and how long would it take to get it back? Then the follow-ups they also cannot usually answer: who owns the domain; who can log in as an administrator; what happens if the person who built it stops answering; where do the contact form messages go and did you check last week; and what would it cost you to be down for three days. For each, tell me what different answers reveal, including that 'we have backups' should be followed by asking when one was last restored. Give me a place to write each answer down. Then tell me plainly not to use the answers to frighten anybody — fear closes a first sale and loses the second one — and that the questions do the selling by making risk visible rather than by making anybody anxious."

Prompt 3 — the "not for you if" lines

"Help me write the 'who this is not for' section of my plan page. Here is what I actually do, what I support, and what I refuse: [DESCRIBE]. Write six to eight plain lines, each true, each specific to me, and each one that would genuinely stop the wrong client from enquiring. Cover at minimum: availability outside working hours; site types or platforms I do not support; anything handling payments, health information, or children's data if I refuse those; whether I do redesign work; whether I require administrative access; and the fact that nobody can guarantee nothing will go wrong. Then add the hardest one: the line I say when somebody's site genuinely does not need a plan. Explain that it costs a sale and is the most referred-on sentence in the trade, and that it only works if it is true. Finish with the test: if my plan page could be any provider's plan page, it is not saying anything. Make no claim about what any platform does or does not handle — leave that for me to verify."

---

Common Mistakes

⚠ Selling the task list, which the client cannot evaluate and which reduces the decision to price.

⚠ "Peace of mind", on a page identical to every competitor's.

⚠ Promising availability you cannot keep on your worst week.

⚠ Assuming the competitor who took your client did something wrong. Often they stated a response time and met it.

⚠ Never asking what would happen if the site disappeared tonight.

⚠ Accepting "we have backups" without asking when one was last restored.

⚠ Using what you find to frighten a client into a larger plan.

⚠ Criticising the previous provider, whose brief and payment you know nothing about.

⚠ Describing a client's site as a mess.

⚠ Implying the client should have known about domain ownership or administrator accounts.

⚠ Promising to fix everything you inherited inside the monthly fee.

⚠ Quoting before inspecting.

⚠ Believing clients judge you on the routine work. They judge you on the first reply, the first incident, and the reports.

⚠ Reports that say "everything ran fine."

⚠ Discounting to win a client who has no budget line for this, and who cannot afford the emergency either.

⚠ Taking on sites that handle payments, health information, or children's data as a beginner.

⚠ Taking on a site nobody in the organisation would notice was down.

⚠ A plan page that could be anybody's plan page.

⚠ Never saying who it is not for.

⚠ Never telling somebody their site does not need a plan.

---

Safety, Legal, Ethical, and Professional Considerations

⚠ Never promise uptime, security, or that nothing will go wrong. No provider can guarantee those, they depend on hosts, networks, third-party code, and the client's own actions, and a guarantee you cannot evidence is a claim you may be held to. Section 24.1.

⚠ Promise only a response time you can keep on your worst week, and state it plainly — including whether it covers evenings and weekends. A stated limit honestly kept is worth more than an implied availability you cannot sustain. Section 7.4.

⚠ Never state what any host, platform, plugin, or service does, includes, or guarantees. Read their current documentation and terms yourself, record the date, and tell the client to verify anything that matters to them. This book states none of it. Resource 10.

⚠ Never use a discovery finding to frighten a client into a larger plan. Make the risk visible and let them decide. Section 15.4.

⚠ Never criticise a previous provider. You do not know their brief, their fee, or what they were refused. It also tells the client exactly how you will speak about them later.

⚠ Never quote a maintenance plan for a site you have not inspected. Chapter 12.

⚠ Do not take on sites handling payments, health information, children's data, or anything in a regulated sector until you have asked an attorney and an insurance broker specifically about that exposure. Sections 8.4 and 16.5.

⚠ Never paste a client's name, domain, credentials, access details, error logs containing personal data, or anything they told you in confidence into an AI tool. Section 37.5.

⚠ Everything you say a plan includes must be something you actually do, on a stated schedule, and can evidence. If you have never restored a backup, do not publish that you verify backups. Chapter 4.

⚠ Nothing in this chapter predicts clients, revenue, retention, or business success. It describes how one market behaves and what one composite practitioner observed.

---

Do This Now

=================================================================
  [ ] ⚠ ⚠ Read your own plan page and highlight every
      phrase you could not evidence.

  [ ] ⚠ ⚠ Replace each one with something specific that
      happens on a date.

  [ ] ⚠ ⚠ Delete "peace of mind".

  [ ] ⚠ ⚠ Write down your ACTUAL response time on your
      worst week.

  [ ] ⚠ ⚠ Publish that number, including whether it
      covers evenings and weekends.

  [ ] ⚠ Write the discovery question list.
      Resource 8.

  [ ] ⚠ ⚠ Ask one current or prospective client: if
      your site disappeared tonight, who would you
      call?

  [ ] ⚠ ⚠ Write down the answer without reacting to it.

  [ ] ⚠ ⚠ For every existing client, write down when
      you last RESTORED one of their backups.

  [ ] ⚠ ⚠ If the answer is "never", that is Chapter 4
      and it is the next thing you do.

  [ ] ⚠ ⚠ Write six "not for you if" lines. True ones.

  [ ] ⚠ ⚠ Put them on your plan page, above the price.

  [ ] ⚠ ⚠ Check your last three monthly reports. Do any
      of them say "everything ran fine"?

  [ ] ⚠ ⚠ Identify one client whose site nobody would
      notice was down.

  [ ] ⚠ ⚠ Identify any site you maintain that takes
      payments or holds health data.

  [ ] ⚠ ⚠ Book the conversation with an insurance
      broker. Section 16.5.

  [ ] And ⚠ ⚠ if your plan page could be anybody's plan
      page, rewrite the first paragraph today.
=================================================================

---

Chapter Summary

Kit lost a veterinary practice over forty dollars a month and got them back six weeks later — after their site was down for sixty-three hours because it failed at ten past six on a Friday and the new provider's stated response time was one business day.

⚠ The competitor did nothing wrong. They promised one business day and they met it.

What the client had actually been buying was never the maintenance. The updates were the same. The backups were probably the same. They had been buying a person who would look at it on a Friday evening — and they had never said so, because they did not know.

Clients cannot describe what they are buying, and it is almost never the list of tasks. It is somebody who answers, not having to think about it, somebody who explains without condescending, a route back from a disaster, and somebody who will still be there in two years.

"Peace of mind" sells nothing — it is an outcome you cannot evidence, identical on every competitor's page, and exactly what a provider who does nothing also says. Replace every feeling with something that happened, on a date, that you can show them.

One question does more than any pitch: if your site disappeared tonight, who would you call, and how long would it take? Almost nobody can answer it, and the follow-ups are worse.

Your competitor is frequently not another provider. It is silence — a builder who moved on and stopped replying.

Assume there was a last person and that it ended badly — and never criticise them, never call the site a mess, and never use what you found to frighten anybody.

Clients judge you at three moments: the first reply, the first thing that breaks, and the month they wonder why they are paying you. None of them is the routine work.

⚠ And the most persuasive thing on your plan page is who it is not for — including, occasionally, telling somebody they do not need a plan at all.

---