Academy › Build › Describe your business
They break your rule and you want to say yes: use judgment, not your gut
You'll know when an exception to your rule deserves a yes, what condition to set on it, and when that same request, repeated, is telling you the rule needs to change, not be broken.
By Yodai · Published September 6, 2026 · Updated October 12, 2026
No matter what condition you set before saying yes, besides the price, sooner or later someone's going to ask you to break it. You wrote the rule a month ago: no orders with less than 48 hours' notice. You wrote it calmly, with nobody pressuring you, thinking about the nights you ended up decorating a cake at eleven at night because someone needed it the next day. Now the phone rings. It's a customer who's already bought from you twice, asking for a cake for the day after tomorrow, and she adds a $20 tip if you make it happen anyway. The rule says no. Your gut says yes.
That same moment repeats with any limit you've set: your delivery area, your minimum order size, the day you don't work. Someone breaks it with an offer that sounds reasonable, and you decide on the spot, based on how you feel that day. If it's a Monday and you're in a good mood, you say yes. If it's a Friday and you're exhausted, you say no to something almost identical. The real problem is deciding every exception without a criterion.
What the rule was protecting, and whether this exception respects it
A rule doesn't exist for no reason. It protects something specific: your work time, the quality of the result, or simply having your head clear on a Sunday. Before deciding if this exception is worth it, ask yourself what the rule was protecting and whether the case in front of you respects that or breaks it anyway.
The 48-hour notice isn't just a whim: an elaborate fondant design takes time, between making the pieces, letting them dry, and putting it all together. If you take on a cake like that for the day after tomorrow, you're handing over a lower-quality product with your name on it, no matter how small the exception seems. But if the customer asks for a simple cake, just sponge and frosting, that doesn't need all that work, the rule isn't protecting anything in that specific case. That's where there's room to say yes.
The question isn't whether the money is worth it. It's whether this exception breaks what the rule was protecting, or whether it's a case that, by its very nature, doesn't need that protection.
An exception that costs nothing and isn't named as an exception gets learned as the new normal
It's not just what's being asked, it's who's asking
A rule doesn't get broken in a vacuum: a specific person breaks it, and who that person is matters just as much as what they're asking for. The point here is to look at who's asking before you give anything. A customer who's been buying from you for two years and has never haggled isn't the same as someone who already pushed you to lower your price once and is now back with another impossible request. The first one has earned the benefit of the doubt; the second already showed you how she operates, and you don't need to learn that lesson twice.
This doesn't contradict the earlier criterion: it completes it. First you ask whether the case respects what the rule was protecting. Then you ask whether the person making the request is the type who asks once and appreciates it, or the type who asks once and already expects it next time. The same cake for the day after tomorrow, requested by two different customers, can deserve two different answers, and that makes sense: the criterion includes their history, not just the order.
You don't need a perfect memory to know who's who: just check your last WhatsApp conversation or your order notebook before you answer. If she already asked for something similar last time and you gave it to her for free, you already know what's going to happen if you say yes again with no conditions: she's going to ask again, and this time with even less room to negotiate, because by now it's just normal to her.
The criterion: two questions before you say yes
With that, you already have half the criterion. The other half is this question: if you said yes today, would you be okay with the same thing happening again next month under the same conditions? If the answer is yes, the rule was set wrong from the start, and it's time to change it, which is what the next lesson covers. If the answer is no, then this really is a genuine exception, and a genuine exception gets accepted with a condition attached, not handed over as is.
The trap that catches almost everyone is thinking, 'it's just this once.' That phrase is exactly what erases the criterion: it turns any exception into a special case you don't have to justify or charge for, because it's just this once. The problem is that 'this once' keeps happening, under a different name and a different excuse, every few weeks, and before long the rule turns into a suggestion that folds under enough pressure.
The condition can be a rush fee, a different delivery time, or the order itself being simpler than usual. What it can't be is free and silent. If you accept the same service, within the same off-limits timeframe, without charging anything for the extra effort, you've changed the rule without telling anyone, not even yourself.
- It happens under the same terms as if the rule didn't exist
- No one pays for the extra effort or the risk you're taking on
- The customer doesn't see it as a favor: she thinks that's just how it always works
- You charge a rush fee or simplify the order
- It's made clear that it's an exception, not the norm
- If it gets asked for again the same way, you already know the rule was set wrong
Which one I'd pick: Choose the conditional yes when the case doesn't come up every week and the surcharge makes up for the risk you're taking on. Say no outright when it's already the third time this month: at that point there's no exception worth making, there's a rule that no longer fits what your business needs.
- Before you say yes, you know what the rule was protecting and whether this case respects it
- You look at who's asking, not just what they're asking for: their history counts as much as the order
- You have the question that separates a real exception from a rule change in disguise: would you be okay with this happening again next month?
- The exception you accept comes with a condition attached (a surcharge, a different deadline, or a simpler order) and is stated as an exception, not as a new rule.
- You have the exact words to offer it without it sounding like a free favor
Test yourself
Answer before opening each one. If one gives you trouble, go back to the section that explains it.
1. A regular customer, one of the ones who always pays on time, asks you for exactly what your rule forbids: a rush order with less notice than you require. It's the first time they've asked in two years. What do you decide?
You accept it, and you accept it with a condition: either a rush fee or a simpler order that doesn't need the buffer you were protecting. It's the first time in two years, so there's no risk of it becoming a habit, but it's not free either: you call it out as an exception.
2. This is the third time this month someone has asked for delivery outside your delivery area, each time with a different, seemingly valid reason. What do you decide?
You turn down this request and review the rule with a clear head, without a customer waiting on the phone. Three times in a month is already a pattern: the area you set no longer matches where your business actually stands, and handling it case by case only puts off the decision to move the line.
3. Two weeks ago, you agreed once to make a cake on short notice without charging a rush fee because you liked the customer. Now she's asking for the same thing again, with the same timeline, and assumes you'll do it the same way. What do you decide?
You explain that last time was an exception, not the rule, and that this time it comes with the rush fee or the design change that avoids the timing problem. The mistake is already made, you didn't say it the first time, but you fix it now, before it happens a third time.
Yodai builds the site from what you tell it, with a store, bookings or quote requests depending on what you do. See what the website for your business looks like.
NextWhat the exception costs