Saying no to a custom request without losing the relationship

A customer sends you a thoughtful message asking for something your product does not include. They want a private version of your course, a few hours of one-to-one help, or a custom template shaped around their business. They are interested, polite and possibly ready to pay. You still know that saying yes would pull your work in a direction you did not choose.

Separate the person from the request

The awkwardness usually comes from treating the request as a test of the relationship. If you decline, you fear the person will feel rejected. That can make you over-explain, apologise repeatedly or offer a smaller version of the work you meant to avoid.

Instead, separate two things: your view of the customer and your decision about the work. You can value their interest while deciding that this particular service is not part of your business. A request is evidence that someone has a problem. It is not proof that you should solve it in the requested format.

This distinction also protects the buyer. If you accept work that does not fit your process, you may deliver slowly, price it badly or resent the revisions. A clear no is kinder than a yes followed by a confusing experience.

Decide what kind of no this is

Before replying, identify the boundary you are protecting. The request may be outside your subject, outside your delivery model or simply too labour-intensive for the price the customer expects. Those are different decisions, even if the reply is short.

You do not need to make every decision in the same message. If the request might reveal a useful product idea, ask one clarifying question, note the answer and still decline the custom work for now. Curiosity does not require a commitment.

Use a reply with four parts

A dependable response has four parts: thank them, state the boundary, offer the closest fit and leave the relationship open. Keeping the structure consistent makes it less likely that you negotiate against yourself while writing.

1. 1Thank them for explaining what they are looking for. This acknowledges the effort they made without agreeing to the request.
2. 2Say what you do not offer in plain language. For example: “I do not take on bespoke versions of this template.”
3. 3Name the closest available option and say what it includes. Link directly to the product, course, call or membership rather than making the buyer search.
4. 4Close warmly without creating a false promise. “I hope the standard version helps, and I would be glad to have you join if it is the right fit.”

A complete reply could read: “Thanks for explaining what you need. I do not create bespoke versions of this template, because the offer is designed as a self-serve product. The closest fit is the existing template, which you can adapt to your own project. If you need help applying it, a coaching call may be a better option. I hope one of those works for you.”

Make the alternative real, not decorative

“Have a look at my other products” is not much of an alternative. It transfers the work of matching the need to the customer. A better option has a name, a defined outcome and a clear boundary.

For example, if you sell a workbook but do not provide individual implementation, a coaching call might be the right alternative if you already offer calls. If the buyer wants structured teaching rather than a private build, point them to your online course. If they only need the original files, link to the relevant digital download.

Your storefront can support this boundary. On store.fan, you can place the standard offer in a simple path from your profile or link in bio, then direct the customer to the exact page in your reply. A named offer is easier to choose than an open-ended promise that you might make something later.

Turn repeated requests into evidence

One request should not automatically change your offer. It may be a one-off preference, or the buyer may not have understood what you sell. Several similar requests are more useful: they show a repeated gap between the problem people have and the format you currently provide.

Keep a short record with the date, the request, the existing offer that came closest and the reason you declined. After a set period, review the list. You might find that people repeatedly want the same add-on, a smaller entry product or help using the product. You can then test one defined change, with a price and scope, rather than quietly adding bespoke work to every sale.

The same record can show that no change is needed. If requests are varied and difficult to group, customisation may be a feature of the buyer's situation rather than a viable product category for you. In that case, keep the boundary and improve the wording around your existing offer.

Build the boundary into your sales process

A private reply is useful, but your product pages should do some of the boundary-setting first. State who the product is for, what it contains and what it does not include. If there is no personal feedback, say so. If updates are not included, say that too. Clear scope reduces the number of disappointed buyers and gives you language to reuse.

For creators using store.fan, the paid plans start with a 14-day trial, and store.fan takes 0% of sales while Stripe's own processing fee still applies. Money goes straight to your Stripe account. That can make a defined alternative easier to sell without adding a separate manual payment process. The free plan is link-in-bio only, so selling the alternative requires the relevant paid setup.

You can also watch for which replies lead to a purchase, not just which requests sound persuasive. If customers commonly move from a custom request to a call, that is a useful signal. If they rarely choose the alternative, the offer may not solve the same problem, or your reply may need a clearer explanation.

A clear boundary is easier to keep when the next step is visible. Use store.fan to give each offer a proper home, then send the customer to the option that matches what you are actually prepared to deliver.