Scope creep in bookkeeping is not usually one big overreach. It is a hundred small requests, each too minor to argue about, until you are effectively on call for a fixed monthly fee.

The cost nobody bills for: an interruption does not cost the five minutes it takes. It costs the five minutes plus the time to get back into what you were doing plus the schedule you now have to rearrange. Charging for every minute spent still undercharges for what it actually costs you.

Where boundaries come from

Not from confrontation. From having agreed something in advance that you can point at:

  • The engagement letter defines what is included, what is not, and how out-of-scope work gets quoted and approved.
  • A stated response time — "I reply to non-urgent queries within one business day" — sets an expectation that makes an unanswered evening email normal rather than rude.
  • A single channel. A client using email, text, WhatsApp and phone has four ways to interrupt you and no way to be tracked.
  • A predictable rhythm. Clients who know when they will hear from you ask fewer unscheduled questions.

The ad hoc request client

The most common difficult pattern: a client who has decided, silently, that you work for them, and sends requests throughout the month with no regard for your schedule.

Subject: How I'm structuring your work from {{date}}

Hi {{first name}},

I want to make sure you're getting the best of my time rather than the most fragmented version of it, so I'm tightening up how I schedule work.

From {{date}}: your regular monthly work runs on {{schedule}}. Anything outside that I'll handle in my {{day}} block, so if you send something on {{day}} you'll have it back by {{day}}.

If something is genuinely urgent, call rather than email and I'll deal with it — I'd just rather keep that for actual urgency so it means something.

Anything that falls outside our agreed scope I'll quote before starting, so there are no surprises on either side.

{{your name}}

Note what this does not do: complain, or ask permission. It states a new operating pattern and gives the client something better — predictability — in exchange.

The out-of-hours problem

Checking email after hours to catch a client's reply is how a boundary erodes without anyone deciding anything. If you answer at 9pm once, you have set the expectation.

  • Decide your hours and state them once, in your signature or onboarding note.
  • Do not reply outside them, even when it would be quicker. Schedule the send if you write it late.
  • Define what counts as genuinely urgent, and give a different channel for it.
  • Accept that the first few weeks feel uncomfortable and then stop feeling like anything.

Charging for the fragmentation

Time-based billing captures the minutes but not the disruption. Options that work better:

  • A minimum charge per ad hoc request. Fifteen or thirty minutes minimum makes the trivial request visible without an argument.
  • A priority or rush rate for anything needed outside the agreed cycle.
  • A retainer for on-call access, priced properly — if a client genuinely wants you available, that is a product you can sell rather than a leak.
  • An included allowance — "up to two ad hoc requests per month included, beyond that quoted separately". Clients self-regulate against a visible allowance surprisingly well.

When the client is a large share of your income

This is what makes boundaries hard in practice. A difficult client who represents a third of your revenue is not one you can simply push back on, and pretending otherwise is not useful advice.

The honest sequence: set the boundary anyway but implement it gradually; price the disruption into the next renewal rather than fighting each instance; and treat the concentration itself as the real problem. A client is only able to break your week because you cannot afford to lose them, and that is a business development issue rather than a communication one.

Take the document chasing out of the relationship

A large share of client friction is document-related — the reminders, the ad hoc "did you get that?", the arguments about what was sent when. ClientClose handles all of it automatically and keeps the record, so those exchanges stop being conversations you have to have.

Start your free week →