Unlimited releases, 1200+ platforms. Create account

Testing a song before release and getting useful feedback

Whom to ask, which questions get honest answers, how to test on real devices and short videos, and how to stop tweaking a song that is already done.

4 min read

"Sounds great" is the least useful thing anyone can say about your unreleased song. Good feedback is specific, comes from the right people and arrives while you can still act on it. Here is how to get it without turning the song into a never-ending project.

Decide what you are testing

Before you send the track to anyone, write down what you actually want to learn. Feedback on a rough demo and feedback on a final master are different jobs.

  • The song itself: is the hook strong, does the structure hold attention, is the second verse needed?
  • The arrangement and mix: is the vocal clear, is the low end too heavy, does the chorus lift?
  • The choice: which of three finished songs should be the single?

If you mix these up, you get a bit of everything and nothing you can use. Test one question at a time. Asking at the demo stage is cheaper: changing the structure after the mix costs both time and money.

Choose the right people

Different people hear different things, so ask a small mix:

  • Two or three listeners who fit your audience but do not know you well. They react like strangers on a playlist, which is what you need.
  • One or two musicians or engineers whose own work you respect, for technical points.
  • One person who knows your music well and will tell you if you are drifting away from your sound.

Family and close friends mostly want to support you. That is kind but not useful for this. Large group chats are also a poor fit: people repeat whatever the first person said.

Ask questions that get real answers

"Do you like it?" invites a polite yes. Ask questions that force a concrete answer:

  • At what moment did your attention drift?
  • Which line or sound stuck with you after it ended?
  • Was there a part you wanted to skip?
  • Describe the song in three words.
  • What kind of playlist or situation would you put it in?

Send a private file or link, ask people to listen once without pausing, and to answer before they listen again. First impressions are what a stranger on a streaming platform will have. Write down the time codes people mention; if three people drift at the same second, that is information.

When the answers come in, do not argue or rush to explain. Say thank you, write it down and, if needed, ask one follow-up: "Why there?" People who feel they have to defend their opinion will be less honest next time.

Listen where your listeners listen

Most people will not hear your song on studio monitors. Before you call the mix finished, play it on:

  • a phone speaker
  • cheap earbuds and decent headphones
  • a car
  • a small Bluetooth speaker
  • a laptop at low volume

Compare it with two or three released songs in the same genre at a similar loudness. You are not trying to copy them, only checking that nothing is badly off: a vocal that disappears on a phone, a bass that vanishes in earbuds, a hi-hat that hurts in the car. Most platforms even out playback loudness, so simply making the mix louder will not make it sound stronger to the listener.

Try short-video tests, carefully

Short videos are a quick way to see which part of a song catches people. Say Noah Field is unsure whether to open his single with the chorus or with a quieter verse line. He posts two similar clips on different days, each with a different section, and compares how long people watch, how many replay and what they write in the comments.

Treat these results as hints, not proof. Small numbers are noisy, and a clip can do well because of the picture rather than the sound. Post short excerpts only, keep the same style of video for both versions, and do not change five things at once. Run the test a few weeks before release, so you still have time to act on what you learn.

Know when to stop

Endless tweaking is the most common way good songs never come out. A few rules help:

  1. Set a deadline for feedback and a date to lock the master.
  2. Change something only if more than one person points to it, or if you already suspected it yourself.
  3. Keep every version, named clearly, so you can go back if a change made things worse.
  4. After two rounds of feedback, stop asking about the same song.
  5. Before the final decision, leave the song alone for a few days and come back with fresh ears.

At some point the song is as good as you can make it right now. The next one will benefit from everything you learned here, and that only happens if this one goes out.

Unlimited releases, 1200+ platforms

Create an account, pick a plan and upload your music. Every plan includes unlimited releases, and your rights stay yours.

Create account