The hidden cost of being available to every customer
Calculate how instant replies and flexible exceptions quietly reduce your capacity and profit.

A customer sends a message at 10.47pm asking whether you can change the file, extend the deadline and make an exception to your usual refund policy. You answer before bed because it feels small. The next morning, another customer asks for something similar. By Friday, the offer you built to give you more freedom has filled your spare hours with tiny negotiations.
The cost is larger than the reply
An instant reply rarely takes only the time shown in your sent messages. There is the interruption, the context switch, the search for the customer’s order, the decision about what to offer and the follow-up you create by making a special arrangement. A five-minute answer can become fifteen minutes of scattered attention.
Start with a simple weekly calculation. Add the time spent answering questions, changing files, processing exceptions, checking whether a promise was completed and returning to unfinished work. If that comes to 6 hours a week, and your business needs to earn £40 for each hour of your working time, the capacity cost is £240 a week. Over four weeks, that is £960 of potential working capacity.
| Activity | Weekly time | Capacity cost at £40/hour |
|---|---|---|
| Customer messages | 3 hours | £120 |
| Custom changes and exceptions | 2 hours | £80 |
| Follow-up and admin | 1 hour | £40 |
| Total | 6 hours | £240 |
This is not a claim about lost revenue. You may not have sold another product with those six hours. It is a way to make the trade-off visible. The time is being used somewhere, so you can compare that use with creating a new product, improving an existing one, marketing, rest or paid work.
Flexible exceptions train the wrong expectation
One exception can be kind and sensible. The problem starts when an exception becomes the clearest description of how your offer works. If one customer receives a late delivery, a revised file and a refund outside your stated terms, future customers may ask for the same treatment. You have then created an informal service level without choosing its price.
Separate requests into three groups: information the product should answer, support your standard process can handle, and work that is genuinely bespoke. The first group belongs in the sales page, checkout notes or welcome email. The second needs a repeatable reply and a defined window. The third should be a different paid offer, not a quiet addition to the original one.
- 1List the last ten requests that interrupted your work.
- 2Mark each as information, standard support or bespoke work.
- 3Write down the time each one took, including follow-up.
- 4Create one rule for the most common request.
- 5Turn repeated bespoke work into a priced add-on, a coaching call or a separate service.
Design the buying experience to answer first
Boundaries are easier to keep when customers can see the answer before they need to ask. A clear product page can state what is included, the format, delivery timing, permitted use, support method and refund terms. For a downloadable product, a simple digital download storefront can deliver the same file and instructions without you sending it manually.
The same principle applies to teaching and access. If customers need a sequence of lessons, put the material in an online course rather than rebuilding the same explanation in private messages. If the value is your judgement in a live conversation, sell that deliberately as a coaching call. The format should match the kind of attention the customer is buying.
A storefront on store.fan can give each offer a defined place, delivery method and customer journey. With paid plans, you can also use email marketing to explain what happens after purchase and reduce questions that come from uncertainty. The point is not to hide from customers. It is to move predictable answers from your inbox into the offer itself.
Replace instant access with a reliable rhythm
You do not have to answer every message as it arrives. Choose a support rhythm you can maintain: for example, one daily reply window, two set days each week or a stated response period. The right choice depends on your product and promises. A cohort with a fixed start date needs a different rhythm from a self-serve template.
Tell customers the rhythm in three places: before purchase, immediately after purchase and in your first reply. Use a short message such as: “I answer support questions on Tuesdays and Thursdays. Please include your order email and the specific lesson or file you are referring to.” This reduces the back-and-forth because it tells the customer what useful information looks like.
Keep exceptions visible in the numbers
Track exceptions for one month rather than relying on your memory. Record the request, the time spent, whether it led to a sale or refund, and whether the same solution could be reused. Then calculate the monthly total. If ten exceptions take 45 minutes each, that is 7.5 hours. At £40 an hour, the capacity cost is £300.
You can then choose a response based on evidence. Keep the exception if it protects a valuable relationship and costs little. Add a fee if it is useful work that sits outside the product. Turn it into a standard feature if many customers need it. Or stop offering it if the work creates more obligation than value.
The same review can show where automation or structure is worth paying for. store.fan’s paid plans can send money straight to your Stripe account, and the platform takes 0% of sales, although Stripe’s own processing fee still applies. An iOS app can provide instant sale alerts without requiring you to keep checking messages. Those tools do not remove support, but they can reduce manual monitoring and make the customer path more consistent.
Make availability a product decision
There is no universal number of hours you should be available. Decide what access your offer requires, what it costs to provide and what you want your working week to contain. A low-priced download may need clear instructions and limited support. A membership may need regular community prompts. A coaching package may need reserved appointments and a defined number of questions between calls.
Write the boundary as part of the product, not as an apology. “This includes one 45-minute call and written preparation questions” is clearer than “I may not always be able to reply quickly.” “Support is available by email on Tuesdays and Thursdays” is a service description. Customers can decide whether it suits them, and you can deliver it without renegotiating every week.
No. Keep fast replies for urgent issues, active launches or offers where speed is part of what customers buy. The aim is to stop treating every message as urgent by default. State a response rhythm and use it consistently.
Acknowledge the request, point to the agreed terms and offer the closest available option. If the request needs bespoke work, price it separately. A boundary may lose a sale, but accepting every request can make the original offer unprofitable.
Compare support hours with sales, refunds and repeat purchases, then compare the time with other uses of your capacity. If support regularly exceeds what the price allows, reduce the scope, raise the price or create a higher-touch tier.
Give each offer a clearer buying and support path with your own store.fan storefront.
Start your storefrontTurn your knowledge into income
Launch your Store.Fan in minutes — sell digital products, courses, and calls straight from your bio. Free to start.



