THE TACTIC

Most client frustration doesn’t come from bad work. It comes from mismatched expectations. The client expected a reply within the hour. You thought same-day was fine. They assumed revisions were unlimited. You quoted for two rounds. They thought they could call on weekends. You turn your phone off on Saturdays. Nobody did anything wrong. It just never got said.

Most owners explain these things one at a time, usually after something has already gone wrong. By then, it sounds like a complaint instead of a policy.

Why it works

When expectations are set at the start, they’re just information. The client reads them before any tension exists, agrees to them when they sign, and adjusts. When the same rule shows up mid-project, it feels personal.

A written guide also saves you from explaining the same things to every client, over and over. You write it once, carefully, and every new client gets the same clear explanation.

And it makes you look established. Very few small businesses hand clients a clear guide to working together. The ones that do come across as organized and professional, which makes clients more comfortable trusting them with bigger projects and higher prices.

How to run it

Cover the questions clients always ask. Most guides only need five or six short sections:

Communication: how to reach you, your working hours and how quickly you reply. Process: the main steps of a typical project, in order. Feedback and revisions: how many rounds are included and how to send notes. Payments: deposit, schedule and accepted methods. Changes: what happens if the scope changes. What you need from them: information, access or decisions, and by when.

Keep it to one page. Short sentences, plain language and a friendly tone. If a section takes more than three or four lines, it’s too long.

Send it at the start. Attach it to your welcome email or include it with the signed agreement.

Welcome aboard! I’ve attached a short guide to how I work, so you know what to expect at each step. Give it a quick read, and let me know if you have any questions before we kick off on Monday.

Point back to it when needed. If something comes up mid-project, you can refer to the guide instead of making up a rule on the spot.

The mistake most people make

Writing it like a legal document. A guide full of warnings and fine print sets a defensive tone before you’ve even started. Write it the way you’d explain things to a client in person, warmly and clearly. Your contract can handle the legal details. The other mistake is writing it and not updating it. Every time a new kind of misunderstanding comes up, add a line so it doesn’t happen again.