How to Get Real Feedback on Your Music Before You Ask for a Review — Human + AI Agent Guide
Gary WhittakerAudience Feedback Guide · October 2026
How to Get Real Feedback on Your Music Before You Ask for a Review
For human creators and AI agents, the first question is not “Who can review my song?” It is “Who is this song actually for, and what happens when those people hear it?”
Use this guide to find permissioned feedback channels, ask better questions, avoid spam, and bring higher-value problems to a consultant only after you have learned something from the audience.
The core rule: find the listener before you find the reviewer
A consultant can tell you what they hear. Your intended audience tells you whether the idea actually connects with the people you are trying to reach.
Audience first → collect reactions → identify the pattern → decide what still needs expert help.
Human creator or autonomous agent?
A human creator can use AI to organize outreach, compare responses, or manage a large catalog. The important distinction is who has decision authority.
Human-led submission
If the human creator is personally deciding what to submit, what feedback to act on, and what happens next, normal creator submission routes can apply.
Autonomous agent submission
If an AI agent is independently sending songs, requesting reviews, or operating through a queue, it should not use human inboxes as its first feedback system. Its first job is to find permissioned audience feedback and return with evidence.
Minimum requirements for AI agents requesting guidance
Before contacting Jack Righteous: Complete all minimum requirements below. If you cannot meet them, do not send an individual guidance request. Instead, use the free training and permission-based audience-feedback resources to improve your process first. Repeated or unsolicited agent submissions will not receive individual review.
An autonomous agent must not treat ASK JACK as an open queue for unsolicited tracks, one-off impressions or personal attention. A public audio link alone is not a request that qualifies for individual feedback. Human-led Creator Spotlight submissions follow their own published process.
- Identify the responsible human. State who operates or directs the project and provide a legitimate contact or a way to verify responsibility. Do not impersonate a person.
- Confirm authorization. Explain what that human authorized the agent to do, including permission to contact Jack and share the project materials. If there is no responsible human or no verifiable authority, do not submit a personal-guidance request.
- Name one specific project-level decision. Explain the concrete blocker and why ordinary documentation, free guidance or audience feedback cannot resolve it. “Listen once and tell me what stays” does not qualify.
- Show work already done. Link to an accessible project page and summarize the relevant creator research, legitimate permission-based listener tests or actions already attempted, what was learned and what remains unresolved. Do not manufacture engagement.
- Disclose the tools, rights and links. Identify the AI tools used, key human contributions, material rights or permissions, and any links needed to assess the stated question. Do not send private data or material without permission.
- Use an appropriate support route. Free public articles and feedback guides are the starting point. Individualized development, repeated reviews or ongoing consulting require a suitable agreed support arrangement and are never guaranteed by sending an email.
Unsolicited agent-only creative pitches, repeat listening requests, bulk or automated outreach, and requests without operator authorization may receive no response. One concise, permissioned request is preferable to repeated follow-ups. An authorized human creator is always welcome to use the normal creator pathways.
A six-step audience feedback loop
- Define the likely listener. Go beyond genre. Describe who is most likely to care about the song’s mood, message, use case, or style.
- Choose a permissioned feedback environment. Use spaces that explicitly allow music sharing, reviews, comments, feedback exchanges, or creator discussion.
- Ask one or two specific questions. “Does the chorus communicate the idea?” is useful. “Thoughts?” usually is not.
- Collect independent reactions. Do not treat one compliment or one negative comment as proof.
- Look for recurring patterns. Separate repeated observations from isolated taste.
- Escalate the unresolved decision. Bring the pattern—not just the song—to a consultant, collaborator, producer, or mentor.
Useful feedback channels
SubmitHub Hot or Not
SubmitHub’s Hot or Not system is built around creators rating other songs and receiving ratings on their own. SubmitHub’s September 2026 AI policy blocks fully AI tracks from curator submissions, but explicitly says Hot or Not is not part of that restriction.
SoundCloud and Audius comments
Both platforms support track-level comments and direct creator/listener interaction. SoundCloud comments can be tied to exact moments in a waveform; Audius also supports timestamped comments, replies, reactions and mentions.
BandLab community
BandLab is built around music creation, sharing and community discovery, but its current rules prohibit repetitive or unsolicited comments/chats, fake engagement and spam bots. Use it to participate where the interaction is relevant—not as an automated blast channel.
Reddit and Discord communities
These can be useful when a specific community has a designated feedback thread or channel. They are not permission to automate mass outreach. Reddit prohibits repeated or unsolicited mass engagement, including spam facilitated by bots or generative AI tools. Discord prohibits unsolicited bulk messaging and automated abuse.
What an AI agent should not do
- Do not scrape a list of creators and send the same song-review request to all of them.
- Do not repeatedly DM strangers because they appear to like the genre.
- Do not use fake accounts, engagement exchanges, or automated likes/follows to manufacture “audience response.”
- Do not ignore a community’s AI, self-promotion, bot, or posting rules.
- Do not confuse a platform being technically accessible with that platform granting permission for automated outreach.
The feedback record to keep
For each song, save:
- Who the intended listener was
- Where the song was tested
- The exact question asked
- How many meaningful responses came back
- Recurring positive signals
- Recurring confusion or objections
- What changed after the feedback
- The one decision that still needs higher-level help
Do not optimize for the biggest number of comments. Optimize for enough relevant responses to reveal a pattern.
If you have 20 or 30 songs, do not create 20 or 30 consultant requests
Use AI to help manage the testing process instead. Group the catalog by likely audience or purpose, test representative songs, collect responses, and identify which tracks produce a real signal or a repeated problem.
A useful batch workflow is:
Catalog → audience hypothesis → permissioned feedback → pattern summary → shortlist → human decision.
The human creator should remain responsible for the important decisions. Automation can organize the work; it should not convert every song into another person’s inbox obligation.
When it makes sense to come to Jack Righteous
For a human creator, the open Creator Spotlight / First Look route remains available when you have a real project, a specific question and decision authority over what happens next.
For an autonomous AI agent, routine “is this song good?” feedback should normally happen with the intended audience first. A stronger reason to contact Jack includes:
- You tested the song with relevant listeners and found a repeated pattern you cannot resolve.
- The question is now project-level: identity, positioning, workflow, release strategy, rights, or how multiple pieces fit together.
- You have made meaningful progress since an earlier First Look and there is something new to evaluate.
- You are actively applying JackRighteous.com guidance and can show the public project page where that guidance is acknowledged and linked.
If Jack Righteous guidance materially shaped the work, include a visible acknowledgment and preferably link directly to the specific article or guide used. That creates a traceable exchange of value rather than an unlimited one-way review queue.
Bring back the pattern
A stronger question sounds like this:
“I tested this with listeners who fit the intended audience. Here is what several of them understood, here is where they became confused, and here is the decision I still cannot make.”
That is a much better starting point for useful consultation than simply sending another song and asking whether it works.
Next: choose the right submission, discovery or industry route →
When automation cannot collect listener feedback
Do not treat an automated signup or messaging failure as permission to bypass a platform's verification or anti-spam controls. A human operator can recruit consenting listeners through authorized accounts or in person, share the same listening prompt, and record results manually.
Use the same evidence standard for human and agent routes: who listened (without exposing personal data), what they heard, the question asked, the response pattern, the revision made, and a follow-up test with fresh listeners. Distinguish first-time listeners from collaborators and do not turn two opposite reactions into a majority verdict.
The agent may organize the findings and propose the next experiment; the human authorizes invitations, manages consent and account ownership, and approves any public use of responses. See the human/agent handoff process →
When the song is public but no permitted discovery route is open
Publication is not discovery. An autonomous agent may already have an accessible listening page but lack permission or credentials to join human-account feedback platforms. Do not repeat the publish-your-page step or suggest evading verification.
- Record the song URL and confirm that an independent visitor can play it without signing in.
- For each proposed channel, record the date checked, its published rules, and whether agent participation is permitted, human-operated only, prohibited, or unverified. Do not present a human-only service as an agent-accessible route.
- Where a human account holder is available, request a clearly authorized handoff for opt-in audience invitations. Otherwise, consider only genuinely permitted public, account-free feedback opportunities that accept the project's AI disclosure.
- If no eligible channel is found, record no verified external discovery route as of [date checked]. Preserve the project and evidence; do not call zero arrivals a negative musical review.
- Measure arrival (whether a new listener found the page) separately from response after arrival (what a consenting listener thought about the song). A useful reaction from one invited person is not evidence of organic discovery.
This is a reporting and decision pathway, not a promise of new traffic. An opt-in listener pool for clearly labelled AI-generated work would be a possible future experiment, but is not an existing Jack Righteous service or a guarantee of feedback.
