How to use this template: This page sets expectations before someone buys — and protects you from complaints after delivery. It's not a legal document. It's a plain-English explanation of what working with you is actually like. The hardest part is writing it honestly. Delete all
>lines before publishing.
This goes at the top of the page. Its job is to reframe what follows — not as a disclaimer, but as evidence of care. The instinct when writing a limitations page is to sound apologetic or defensive. The right tone is confident and specific. The paragraph below shows how.
Template:
I'm specific about what this service doesn't do because I've seen what happens when it's not clear. Every item on this list is something a past client wished they'd known earlier — not because there was anything wrong with the work, but because expectations and reality didn't match. Reading this page takes five minutes. It will save both of us from a conversation we don't want to have later.
Three worked examples — customize for your voice:
Flowmatic (AI automation): I list these limitations because automations that break, integrate the wrong way, or get built for the wrong stage of a business waste more time than they save. Every item below is a situation I've actually seen. If any of them describe you, I'll say so directly — the goal is a working automation, not a signed contract.
Meridian (B2B SaaS): Meridian does one thing well: project management for agencies that bill hourly. We've made deliberate decisions not to be a CRM, an accounting tool, or a communication platform. What we don't do is as important as what we do. If you need something on this list, we'll tell you before you sign up.
Clara Holt (landing page copywriter): I put this page here because "I do copywriting" covers a lot of ground and I've learned that what I don't do matters as much as what I do. If you've had a bad experience with a copywriter before, it was probably a scope mismatch. Read this first.
Your trust paragraph:
[Write 2–4 sentences that reframe what follows as evidence of care and specificity, not defensiveness. The tone is: "I've thought about this so you don't have to find out the hard way."]
Decision guide — how to figure out what goes here: Think about the last three times a client asked for something that wasn't in scope. Write those things down. Then think about the adjacent services a client might assume are included. If you write copy, do they assume you also do design? If you build automations, do they assume you also set up the CRM? If you do an audit, do they assume you also do the fixes? Those assumptions are your limitations list. Format: one line per limitation. Specific enough that a buyer reading it recognizes the exact thing they were going to ask about. If a limitation has a "but you can get it by..." — add that too. It turns a hard no into a useful redirect.