So you want to open for demos
Opening for demos is easy. Handling every demo that arrives is the actual decision. A practical, opinionated playbook.
Opening for demos looks like a one-line decision. Add a form, post about it, let artists send music. The real decision is the one nobody announces: what happens to every demo after it arrives?
Get that part right and the rest is easy. Get it wrong and you end up with an inbox you are afraid to open. Here is the version we would set up.
1. Decide what you are actually open to
"We accept demos" is not guidance. It leaves genre, project stage, format, and "are you even signing right now" all unanswered, so you get everything and none of it fits.
Start with a short statement of fit. Name the styles you want. Say whether you want unreleased music only. If there are stretches where you are not listening, make that visible too. Being specific reduces the pile, and that is the goal. You are not collecting the most music, you are giving the right artists a reason to send and everyone else a reason not to.
2. Give artists one place to submit
The destination should be easy to find and hard to misread. A dedicated page beats an email address scattered across profiles, because the page carries the rules with it.
Use the same link everywhere: site, bio, contact replies, any "we're open" announcement. Then artists never have to guess which channel you actually watch, and you never have to merge three queues later. In Calmo this is a branded portal you can shape with your logo, colors, fonts, genres, and a closed message for when intake is paused, so the page stays useful even when you are not listening.
3. Ask for enough, then get out of the way
Nobody should complete a biography to send you a song. Ask for what makes the first listen possible: who they are, how to reach them, the track link, and a short note if it helps.
Be clear about format. If you review streaming links, say so. If private links need permissions on, say that too. Small bits of guidance kill a surprising amount of back and forth. The same applies on your side: a submission should arrive with its context attached, so nobody is hunting for the artist's note after opening the track.
4. Make the review state visible to your team
The common failure is not losing one demo. It is losing the shared picture of the queue. One person listened, another meant to follow up, and no one can see the state without asking in a chat.
Keep the number of states small and tied to real handoffs. New, decided, and then whatever comes after a yes. Calmo keeps every incoming demo in one dashboard with the status sitting next to the music and the artist details, and you can assign a specific demo to the person responsible for it. That is the whole point: a shared surface, not a shared memory.
5. Tell artists what happens next
It is fine not to give personal feedback to every artist. It is not fine to leave them guessing whether the thing even worked.
Set the expectation on the page: we confirm your submission, we review on our own schedule, and we tell you when there is a decision. Do not invent a turnaround time to fill space. With Calmo the artist gets an automatic confirmation and a status page, and an email when you approve or reject, so you close the loop without writing the same message fifty times.
The test before you announce
Run the journey yourself. Can an artist tell whether they are a fit? Can they submit in a couple of minutes? Can a teammate open the queue tomorrow and know what needs a listen and what needs an answer?
If yes, you are ready to open. Everything else can evolve once you see what actually shows up.
Your label deserves better than email threads.
Set up your portal in minutes.
Free to start. No credit card required. Upgrade when your volume grows.