The boundary that stops small client favours becoming unpaid work

A client messages at 4.47pm: “Could you just make one small change?” You can do it in ten minutes. Then there is a second change, a new version to check, and a request to explain something that was never part of the original agreement. By Friday, the favour has become an unpaid part of the job.

Find the point where the favour changes category

The problem is rarely one large request. It is the accumulation of little exceptions: one extra page, a second export, a call that runs over, or advice on a related project. Each request sounds too minor to price on its own, so you absorb it. The client experiences this as flexibility; you experience it as a growing list of unfinished obligations.

A useful boundary starts with a category change. If the request changes the deliverable, adds a new decision, requires another round of work or creates a new deadline, it is no longer a correction to the original job. It is an add-on or a new project. This rule does not depend on whether the task takes ten minutes or two hours. It depends on whether the agreed result has changed.

Describe the work before you price it

“Design support” and “a bit of help” leave too much room for interpretation. Describe the work as a result someone can inspect. For example: “one 12-page PDF, supplied as a final file, with one consolidated revision round” is easier to protect than “PDF design”. A coaching offer might say what the call covers, how long it lasts and what the client receives afterwards.

1. 1Name the finished item: a file, session, review, lesson or set of edits.
2. 2State the boundaries: format, length, deadline, meeting duration and revision limit.
3. 3List what the client must provide, such as copy, images, access or decisions.
4. 4State what happens when the request falls outside those boundaries.

This is not about writing a contract that anticipates every possible question. It is about removing the most common ambiguity before work starts. If you sell repeatable digital products alongside client work, the same principle applies: make the buyer’s entitlement visible. A storefront such as store.fan’s digital downloads can separate a fixed product from the custom help you may choose to offer alongside it.

Use a simple pricing rule for extras

You do not need a complicated rate card. You need a consistent answer to three questions: what has changed, how will you charge for it, and when must the client approve it? A small menu is often enough.

The exact amount is yours to set. What matters is that the price reflects the work and is communicated before you do it. If you normally sell a fixed offer, an add-on can be a separate product rather than a negotiation hidden inside a message. For instance, coaching calls on store.fan can give a client a clear route to buy time with you instead of treating an extra conversation as an invisible favour.

Make the choice visible

A boundary feels personal when it appears for the first time after a request. It feels ordinary when the client can see it in the offer, checkout page or welcome email. Write the rule in plain language: “The package includes one revision round. Further changes are available as an add-on.” Then repeat it calmly when needed.

A useful reply has three parts. First, acknowledge the request without promising it. Second, identify whether it is included. Third, offer the next available choice. For example: “I can see why you’d want that included. It is outside the agreed deliverable, so it would be an additional piece of work. I can quote it separately, or we can keep the current version as planned.”

This gives the client agency without making you responsible for deciding on their behalf. They can spend more, reduce the request or leave it for later. If you sell several formats, store.fan’s storefront tools can help you present those choices in one place, while the paid plans start with a 14-day trial. The free plan is link-in-bio only, so a selling setup requires a paid plan.

Protect the boundary after you set it

The first boundary is rarely the difficult part. The difficult part is keeping it when the client is pleased with the work, when you are already in the file, or when the extra seems quicker to do than to explain. Create a short pause between the request and the work. Put the request in writing, classify it, and get approval before starting anything outside scope.

• Keep a list of recurring extras. If the same request appears repeatedly, turn it into a named add-on.
• Use one place for approvals, so an informal message cannot quietly become a new commitment.
• Review your completed jobs and count the unpriced tasks. The list shows where your offer needs clearer wording.
• Do not apologise for the rule. Explain it, then give the client the available options.

Separate generosity from your business model

You can still be generous. The distinction is whether generosity is a choice you control or a service the client assumes they have bought. Add a bonus when it supports the relationship, make a small exception when the context genuinely calls for it, or give useful advice in a public resource that helps more than one person. None of these requires you to keep expanding a private job without agreement.

For a creator selling products, the same separation keeps your time from being attached to every purchase. A digital guide can answer the common question; a paid call can handle the buyer’s specific situation; a membership can define what ongoing access includes. On store.fan, money goes straight to your own Stripe account and store.fan takes 0% of sales, while Stripe’s own processing fee still applies. That makes the transaction visible, but you still need to define what the transaction buys.