Scope creep on a custom song order rarely arrives as one big unreasonable ask. It shows up as a series of small, individually reasonable requests that add up to a completely different (and more time-consuming) order than the one you priced.
The usual pattern
A customer orders a standard song. Partway through, they ask if you could also do a shorter version for social media. Then a second cover art option. Then a slightly different mix "just to compare." None of these feel like a big deal in isolation, and saying no to any single one feels petty — but three small additions can easily double your time on an order that was priced for one deliverable.
Define the deliverable explicitly upfront
The clearest defense against scope creep is stating exactly what's included before the order starts: one song, one cover art image, one lyric card, delivered as specific file formats. When a request falls outside that list, it's not an argument — it's just outside what was agreed, the same way asking a bakery for a second cake "while they're at it" would be.
The fastest-growing scope creep: "just a small tweak"
Small requests are the hardest to push back on because each one really is small. The trap is treating every "just a quick thing" individually instead of noticing the pattern. If you're three "quick things" into an order, that's a revision round, not a series of favors — treat it as one, even if no single request felt big enough to say no to on its own.
How to respond without sounding difficult
"That's outside what's included in this order, but I'd be happy to add it for [price]" is a complete, professional answer that doesn't require justifying yourself further. Most customers accept an add-on price without pushback; the ones who don't were unlikely to be a good long-term customer regardless, and holding your scope protects the orders you have queued up behind theirs.
Where a review link helps
A lot of scope creep happens because a customer wasn't sure what "final" meant until they saw it, and kept requesting adjustments as a way of participating in the process. Sending a review link with your selected version — where they explicitly approve or request specific changes — gives customers a clear, bounded moment to weigh in, which tends to reduce the drip-feed of small requests that show up when there's no defined checkpoint.
