Almost every custom-song seller eventually gets some version of "this isn't quite what I had in mind." Because the product is inherently subjective — there's no objective bar for "does this feel personal enough" — how you respond to this feedback matters more than getting every order perfect on the first try.
First, figure out what kind of feedback it actually is
Vague dissatisfaction ("it's just not right") and specific dissatisfaction ("the tempo feels too slow for a birthday song" or "you didn't mention the part about the lake house") are different problems that need different responses. Specific feedback is straightforward — you have a clear, actionable change to make. Vague feedback needs a follow-up question before you touch anything: ask what specifically feels off, rather than guessing and generating a second version that might miss the same way the first one did.
Don't take it personally, and don't over-apologize
A defensive response ("I followed exactly what you told me") escalates a fixable situation into a conflict. An overly apologetic response can also backfire by implying the work was actually bad rather than just not yet matched to what the customer pictured. A neutral, solution-focused tone — "let's figure out what would make this feel right, here's what I can adjust" — tends to de-escalate faster than either extreme.
Some feedback isn't about the song
Occasionally, "this isn't right" reflects something other than the actual output — buyer's remorse, a last-minute change of plans about the gift, or unrelated stress. You're not obligated to solve problems outside the scope of what you were hired for, but recognizing when feedback isn't really about the lyric or the melody helps you respond appropriately instead of endlessly iterating on a song that was never really the issue.
Use the review step to catch this earlier
Most "this isn't what I wanted" conversations happen after final delivery, which is the worst time to have them — the customer feels like they're complaining about a finished purchase, and you feel like you're being asked to redo something you'd considered done. Sending a review link before delivery, where the customer explicitly approves or requests changes to a specific version, moves this conversation to a point where feedback is expected and welcomed rather than a surprise complaint.
When to hold your revision limit and when to bend
If a customer's request is within your stated revision policy, it's not really a judgment call — you make the change. If it's beyond what's included, and the underlying issue seems like a genuine miscommunication on your end (you missed something clearly stated in the intake form, for instance), it's often worth making a good-faith adjustment even if it's technically outside your policy, since the alternative — a public dispute or a bad review over an honest mistake — usually costs more than the extra ten minutes of work.
