# Calmo — Full AI Corpus > Demo submission and contract platform for record labels, covering branded portals, A&R review, artist status pages, deliverables, catalog assets, and e-sign contracts. ## What Calmo is - Calmo is submission management software built for independent record labels and A&R teams. - Labels create public, branded submission portals that artists use to send demos — no artist account required. - Labels review submissions in a dashboard, leave notes, assign reviewers, and approve or reject demos. - Artists get automatic confirmation emails and a status page they can check without signing up. - Approved artists receive a secure link to upload deliverables (masters, artwork, metadata). - Contracts are sent and signed through the platform via Firma e-signing. - Labels can manage an approved catalog of tracks, releases, and artists (Label plan). - Artists can discover labels accepting submissions at https://calmo.ai/labels. ## What Calmo is not - Calmo is not a streaming or distribution platform — it does not distribute music to DSPs. - Calmo is not a payment or royalty platform — it does not handle licensing payouts. - Calmo is not a general-purpose CRM — it focuses on the demo-to-contract workflow. - Calmo is not a marketplace that charges artists to submit — labels run their own portals. ## Key links - Website: https://calmo.ai - Labels directory: https://calmo.ai/labels - Blog: https://calmo.ai/blog - Pricing: https://calmo.ai/#pricing - FAQ: https://calmo.ai/#faq - Sign up: https://calmo.ai/auth/register - Contact: contact@calmo.ai - Discord: https://discord.gg/PsWzTPRma6 - llms.txt: https://calmo.ai/llms.txt ## Pricing - Starter (€0/mo): 1 submission portal, 50 submissions/month, submission status page, email automation, unlimited team members, Calmo watermark on portal. - Pro (€19/mo, yearly = 2 months free): 3 portals, 500 submissions/month, 25 contracts/month, 3 contract templates, API access, remove watermark. 14-day trial, no card required. - Label (€29/mo, yearly = 2 months free): unlimited portals, 1,000 submissions/month, 100GB storage, WAV + artwork uploads, catalog management, 100 contracts/month, unlimited templates, custom portal domain, API access. 14-day trial, no card required. ## FAQ - Can I try Calmo before paying? Yes. Starter is free and does not require a credit card. - How do artists submit demos? Through your branded portal with a SoundCloud link. No Calmo account required. - Do artists get status updates? Yes — confirmation email + status page on submit; decision email on approve/reject. - Can I run multiple portals? Yes on Pro and Label. - Can I accept file uploads? Submissions are SoundCloud links; deliverables support WAV + artwork uploads. - Can we use our own branding? Yes — logo, colors, copy, and custom domain options by plan. - How do contracts work? Templates + deal details + signing link via Firma; managed in the dashboard. - Is Calmo only for demo submissions? No — also contracts, status updates, catalog assets, and API access. - Is there a yearly deal? Yes — yearly billing includes 2 months free. - What can I do with the API? Org-scoped API keys to read portal details and submission counts today; more endpoints planned. --- # Calmo vs email for demo submissions > Email is great for conversations. Calmo is for the intake, review, and artist-update workflow that inboxes were never designed to run. ## Short Answer Use email for introductions, A&R conversations, and deal talk. Use Calmo when demos become an operation: one public portal, one review queue, and automatic artist updates. If a single person can still hold the whole queue in their head, email can work. The moment a second teammate joins, or volume makes "did we answer this?" hard to answer, a dedicated submission portal is the better default. ## When Calmo Fits - You publish a public place for artists to send demos. - More than one person reviews music. - You want confirmations, status pages, and approve/reject emails without writing them by hand. - You want approved artists to upload masters and artwork, then move into contracts. - You want the track, artist details, and status on one object. ## When Email Still Fits - You only take warm intros and almost never open for unsolicited demos. - One person owns every reply and the volume stays tiny. - The channel is already a private conversation, not a public inbox. ## Product Difference Email knows messages and threads. It does not know whether a demo was heard, who owns the next listen, or whether the artist was told. Calmo treats each demo as a submission with state: received, in review, approved, or rejected. Artists submit without creating an account. Labels review in a dashboard. Decisions can trigger artist emails automatically. ## Bottom Line Keep email for human conversations. Move public demo intake into Calmo so the queue, the music, and the artist update live in one workflow. ## Sources - [Email is where demos go to die](https://calmo.ai/blog/alternatives-to-email-for-demo-submissions) - [What a demo submission portal actually changes](https://calmo.ai/blog/demo-submission-portal) - [Homepage](https://calmo.ai/) ## Last Updated 2026-07-18 --- # Calmo vs forms and spreadsheets > Generic forms collect responses. Spreadsheets track rows. Calmo connects intake, review, artist status, deliverables, and contracts in one label workflow. ## Short Answer A Typeform/Google Form plus a spreadsheet can collect demos. It usually falls apart after submit: listening state, teammate handoffs, artist updates, deliverables, and contracts live in separate tools. Calmo is for labels that want the public portal and the A&R queue to be the same system, with status pages for artists and a path from approval to deliverables and e-sign. ## When Calmo Fits - You need a branded portal artists can trust. - Submissions must stay reviewable as shared work items, not form rows. - Artists should get confirmation and a status page without making an account. - You want approve/reject notifications built in. - You later need masters, artwork, and contracts without exporting to another stack. ## When Forms + Spreadsheets May Be Enough - You are testing whether you want to be open for demos at all. - Volume is a handful of tracks and one person owns every step. - You do not need artist-facing status or contract signing. ## What Usually Gets Hard - "Has anyone listened?" is not a spreadsheet column people keep honest. - Artist follow-ups arrive in DMs and email while the source of truth is elsewhere. - Approved tracks still need a separate process for WAV, artwork, and contracts. - Branding, open/closed state, and guidelines drift across links and docs. ## Bottom Line Use a form and sheet to validate demand. Switch to Calmo when the admin around listening starts costing more attention than the music. ## Sources - [Most submission forms ask the wrong questions](https://calmo.ai/blog/record-label-submission-form) - [A&R is taste. The workflow around it shouldn't be.](https://calmo.ai/blog/a-and-r-submission-management) - [Pricing](https://calmo.ai/#pricing) ## Last Updated 2026-07-18 --- # Calmo vs music submission platforms > Some platforms optimize for artists shopping many labels. Calmo optimizes for a label running its own branded demo-to-contract workflow. ## Short Answer Marketplace-style submission platforms help artists discover many labels and sometimes charge artists to submit. Calmo is label software: you own the branded portal, the review queue, deliverables, and contracts. Choose a marketplace when your main problem is discovery volume from a shared network. Choose Calmo when your main problem is running a professional intake process on your own site, socials, and campaigns. ## When Calmo Fits - You want artists to experience your label brand, not a third-party marketplace. - Artists should submit free on your portal with no Calmo account. - Your team needs one dashboard for demos, notes, assignments, and decisions. - You want status pages, deliverables uploads, catalog assets, and e-sign after approval. - You care about owning the relationship and the workflow end to end. ## When a Marketplace Platform May Fit - You primarily want inbound from artists already browsing a multi-label network. - You are fine with a shared platform UX instead of a fully branded portal. - You do not need deliverables, catalog storage, or contract signing in the same tool. ## Product Difference Marketplace tools optimize matching and distribution of submissions across many labels. Calmo optimizes the operating system inside one label: portal → review → artist update → deliverables → contract. Calmo also publishes a public [labels directory](https://calmo.ai/labels) so artists can find labels with open portals, but each label still runs its own branded intake. ## Bottom Line If you need a network effect across many labels, evaluate marketplace platforms. If you need your own demo-to-contract workflow, Calmo is the clearer fit. ## Sources - [Explore Labels](https://calmo.ai/labels) - [So you want to open for demos](https://calmo.ai/blog/how-to-accept-music-demos) - [Homepage](https://calmo.ai/) ## Last Updated 2026-07-18 --- # What a demo submission portal actually changes > We built Calmo around a submission portal instead of an inbox. Here is the specific thing that changes when demos stop arriving as email. **TL;DR:** A demo submission portal splits public intake from the review queue. Artists get one branded place to send music; your team gets every demo as a track + context + status object — not another inbox thread. Most labels start taking demos with an email address. It is the fastest possible setup: put "demos to" in a bio, wait for links, listen when there is time. We are not here to tell you that is wrong. It works right up until the inbox becomes the queue, and then it quietly stops working. That is the moment we built Calmo for. ## The inbox is doing three jobs at once An email address that collects demos is secretly three tools stacked on top of each other: - the submission portal artists go to - the internal list your team works from - the record of who already got an answer None of those three jobs is visible in one place, and email is only good at the first one. So you end up reconstructing the other two in your head. Has this been heard? Is someone else on it? Did we already reply? Is this the same artist who wrote last month? When you are busy, those questions cost more than the listening does. A submission portal splits the public page away from the work behind it. Artists get one branded place to send music. You get a dashboard where the track, the artist's context, and the current status all live on the same object. ## What actually changes The point is not to make submitting feel more official. The point is to remove ambiguity on both sides. For the artist, a portal answers "where do I send this, and are you even open?" before they hit submit. You set your genres, add a description of what you are looking for, and put your logo, colors, and fonts on the page. That is not decoration. It tells an artist the link is real and the process is intentional, which means fewer submissions that were never a fit. For you, every demo enters as the same shape: a track, the details you asked for, and a status. You approve or reject it, and the artist gets an email either way. Approved artists move on to uploading their masters and artwork. You never leave the place you reviewed the track. ## What we deliberately did not do We think a lot of "submission tools" fail because they try to be a full CRM, or they force artists to make an account before they can send you a song. We did the opposite. Artists never sign up. They submit through your portal and get a status link they can check later, no account, no password. That one decision removes most of the friction that kills submissions, and it keeps the tool honest about what it is: a submission portal and a review queue, not another inbox to manage. ## Even a handful of demos is worth it Even a handful of demos a month is worth a portal. Artists get a real place to send music, you get a clean record of everything that came in, and nobody is digging through an inbox to find a link. That is exactly why the free plan exists: you can start the day you open for demos. And the moment your volume grows or your process starts leaning on memory, the same portal is already holding your intake together, instead of you scrambling to set one up under pressure. The goal was never to make demo intake feel corporate. It was to make sure good music has a fair shot at being heard, and that artists are not left guessing whether anyone listened. --- Source: https://calmo.ai/blog/demo-submission-portal Section: Blog Last updated: 2026-07-16 --- # Email is where demos go to die > Email is a great way to hear music and a tricky system for managing it. Here is why demo intake struggles in the inbox, and what to use instead. **TL;DR:** Keep email for conversations. Move public demo intake to a dedicated portal so listening state, teammate handoffs, and artist updates are not trapped in threads. Email is not bad at receiving music. It is bad at everything that happens after. That distinction matters, because we are not anti-email. You will have great conversations there, get trusted recommendations there, and use it every day for artist relationships. The question is only whether your inbox should also be the public destination for every unsolicited demo on the internet. The reason is simple: email has no idea what a demo review is. It knows about messages, threads, labels, and replies. It does not know whether a track arrived, whether anyone heard it, or whether the artist was ever told. You are the one keeping track of all of that by hand. ## Why inbox workflows get harder over time At low volume it feels fine, because one person remembers everything. The starred message is waiting for a listen. The forwarded thread needs a second opinion. It all lives in one brain. Add a second person and that memory gets harder to share: - A demo gets forwarded without the context it came with. - One person's reply is invisible to everyone else. - Newer submissions push promising older ones off the screen. - "Read" and "reviewed" start to look like the same thing. So teams patch it. Folders, stars, a shared address, a spreadsheet that tracks the inbox. Every one of those is an attempt to turn a communication tool into an intake system, and it rarely holds for long. ## The fix is a dedicated submission portal The first move is boring and effective: give artists one official link, and stop publishing a demo inbox. Put the link everywhere the email address used to be. Website, socials, contact page, replies to cold messages. This is not less accessible, it is more consistent. Every artist lands on the same page with the same expectations, and every submission arrives in the same queue. The second move is the one that actually changes your life: a demo should enter your workflow as a review item, not as an email you have to file later. That item keeps the track, the artist, their note, and the status together, and it can move from new to a decision without ever losing its link to the artist-facing page. This is why a mail rule is not enough. A rule can drop a message in a folder. It cannot tell an artist their demo is under review, or send them a decision when you make one. It has no relationship to the state of the submission, because email has no concept of state. ## Keep email for what it is great at Moving public intake out of email does not mean abandoning it. It puts email back in the role it earns: personal outreach, introductions, contract conversations, anything that deserves a human reply. That is roughly the split we designed Calmo around. Artists submit through your portal and get an automatic confirmation with a status link. You review in a dashboard. When you approve or reject, the decision email goes out on its own. Email still does the human parts, it just stops being the source of truth for a process it was never built to run. If you take one thing from this: the inbox is great for talking to artists. It is a hard place to run an operation. The moment your demos become an operation, give them a home of their own. --- Source: https://calmo.ai/blog/alternatives-to-email-for-demo-submissions Section: Blog Last updated: 2026-07-10 --- # 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. **TL;DR:** Opening for demos is easy. Define fit, publish one portal link, ask for little, keep review state shared, and tell artists when a decision lands — before you announce you are open. 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. --- Source: https://calmo.ai/blog/how-to-accept-music-demos Section: Blog Last updated: 2026-07-02 --- # Good submission guidelines are a filter, not fine print > A short, honest page beats a defensive policy every time. What to write, a template you can steal, and the promise you should not make. **TL;DR:** Good guidelines are a short filter: what you want, what format to use, and which portal to pick. Promise receipt and a decision path — not a reply deadline you cannot keep. Most submission guidelines are one of two things: too vague to help, or so defensive they scare off everyone including the artists you want. The useful version sits in the middle. It is a short note that helps an artist make a good decision before they submit, and it doubles as a filter so you get fewer bad-fit tracks. Think of it as a filter, not fine print. ## What the page has to do You do not need a policy document. You need to prevent the avoidable misunderstandings that create weak submissions and follow-up emails. After reading it, an artist should be able to answer three things: 1. Is my music likely to fit this label? 2. What should I check before I send? 3. Am I on the right portal? Answer those clearly and you are already ahead of a "demos welcome" line in a bio. ## Keep it short Look at real portals and the pattern is clear: the descriptions that work are usually one to three sentences. Labels are not writing essays. They are writing a filter. Common shapes: - A genre line: what you want, in plain words - A reference playlist: "listen to this before submitting" - A routing note: which portal is for which brand or style That is enough. The form already collects the track, the artist name, and the contact email. Your description does not need to restate the whole process. ## A template you can steal Adapt one of these to your voice and put it on your submission page. **Genre filter** > We are looking for [genres]. If it is not a clear fit with our recent releases, skip it. **Reference playlist** > Listen to this [reference playlist] before submitting. If your track would not sit next to those, it is probably not for us. **Multi-brand / multi-portal** > Use this portal for [genre or brand]. For [other genre or brand], submit [here] instead. **A little more specific** > [Label] — [genres]. Send only music in those lanes; anything else gets declined up front. And for when you are closed: > Demo submissions are closed right now. Follow us for updates when we reopen. Please do not send demos by email or DM while the portal is closed. ## Make it specific, not formal Swap the placeholders for details that actually affect review. Narrow style? Name it. Prefer a certain mood or energy? Point to a playlist. Running more than one brand? Tell artists which portal to use. The more useful the guidance, the less it needs to sound like a contract. Artists are not grading your prose. They are trying to work out whether sending you their music is worth anyone's time. ## The one promise to avoid It is tempting to write "we reply to every demo within two weeks." It sounds considerate right up until the queue grows or a release cycle eats your month, and then it is just a promise you are quietly breaking. Promise what the system can actually keep: we confirm receipt, we keep your demo in a queue, and we notify you when there is a decision. A status page an artist can check beats a deadline that slips in silence. ## Keep the rules where the submission happens Guidelines belong on the submission page, not in a separate doc an artist has to find. That keeps the rules next to the action and gives you one source of truth to link everywhere. That is how Calmo portals are set up: your branding, your genres, a short description of what you are looking for, and a closed message all live on the same page the artist submits from, so the expectations and the form are never more than one screen apart. --- Source: https://calmo.ai/blog/demo-submission-guidelines Section: Blog Last updated: 2026-06-24 --- # Most submission forms ask the wrong questions > A submission form is the start of a workflow, not the finish line. Ask for less, and make sure the thing you build survives past the submit button. **TL;DR:** A submission form is the front of a workflow, not the finish line. Ask only what the first listen needs, and make sure every submit lands in a shared review queue with artist confirmation. A submission form gets treated like a finish line. Add a few fields, collect a link, and the label is "open for demos." It is actually the start of the workflow. The second an artist hits submit, someone has to find the demo, listen, remember what happened, and eventually communicate a decision. A form that only fires off an email notification has solved the first second of that and none of the rest. So the question is not "what should the form ask." It is "does the thing this form creates still work an hour, a week, and three teammates later." ## Ask for less than you want to The temptation is to ask for everything: bio, socials, release history, live dates, influences, press, a paragraph about the track. More fields feel like more context. Usually they are more reading before the first listen. The right question is narrower: what does someone here need to decide whether this demo earns a next step? For most labels that is a working link, the artist name, a way to reach them, the genre, and a short note if it adds something. Everything else has to earn its slot. If a field does not change how a submission is routed, reviewed, or answered, it is probably costing you completed submissions for no reason. ## Set the rules before the first field The strongest submission pages do work before anything gets typed. They say what you are looking for, whether you are open, and what format you want, and they set expectations on timing without promising what you cannot keep. This is not fine print. It is a filter. An ambient artist should not have to guess whether a club label wants them. Someone with only an attached file should know you need a streaming link. Clear guidance lets people self-select, and a queue that starts with better context is a queue you can actually work. ## The missing layer is everything after submit Generic form tools are great at collecting responses and weak the moment a response becomes live A&R work. Look at the questions that show up right after a form is submitted: - Has anyone listened to this? - Is it waiting on a teammate? - Is this the same artist, or a new one? - Did we already send an update? If the answers live in separate places, the form is disconnected from the process it kicked off, and you rebuild a review queue in an inbox or a spreadsheet. That is the part we cared about most with Calmo: the public form feeds a review dashboard, and the submission stays the shared reference point from arrival to the artist update. ## What the artist should get back Submitting a demo is a small act of trust. Someone picked your label, prepared the music, and sent it into a process they cannot see. The floor is a confirmation that it arrived. Better is a place they can check their status without emailing you. Neither of those commits you to a personal reply for every track, they just make the process legible. In Calmo the artist gets a status link instead of an account, which keeps it light for them and consistent for you. ## A short checklist Before you publish a form, check it does five things: 1. Makes clear who you want to hear from. 2. Asks only for what an initial review needs. 3. Accepts music in a format you can review fast. 4. Sends every submission into one queue, wherever the artist found the link. 5. Confirms receipt and tells the artist what happens next. A form can be simple and still feel considered. The difference is whether you built an isolated page or the front of a real workflow. --- Source: https://calmo.ai/blog/record-label-submission-form Section: Blog Last updated: 2026-06-16 --- # A&R is taste. The workflow around it shouldn't be. > The judgment part of A&R should stay human and messy. The administrative part should be boring and reliable. Most teams mix the two up. **TL;DR:** Keep A&R taste human. Make the admin boring: one queue with explicit state, intake separate from discussion, music + context together, and artist status updates built into the system. A&R is taste, context, and conversation. That part should stay human. What should not depend on human memory is whether a demo was received, heard, and answered. That is the whole idea behind submission management, and it is worth being precise about it: it is not turning music discovery into a rigid pipeline. It is making the administrative layer reliable enough that the team can spend its attention on the only part that matters, which is listening. Most teams get into trouble by mixing those two up. They either let the boring part stay chaotic (the inbox), or they overbuild the creative part into a fifteen-stage CRM that nobody keeps current. ## The queue is not the inbox When demos arrive through a few channels, it is easy to treat the inbox as the queue. But an inbox is just where some messages happened to land. It does not show the state of the work. A message marked read might mean someone listened, someone forwarded it, or someone opened it between meetings. A reply might live in one person's account. A still-interesting demo slides down the page because there is no shared place to keep it active. A real queue makes state explicit. Each submission is new, being looked at, ready for a decision, or done. The exact labels matter far less than everyone seeing the same thing. ## Keep intake and review separate One of the easiest wins is to stop using the same channel for public intake and internal discussion. Public intake should be consistent: one link, clear expectations, a confirmation that the music arrived. Internal review can then happen against that submission as the source of context. Artists need clarity and a clean handoff. Your team needs fast access to the track, enough background to judge it, and a status that survives people handing work to each other. Those are different needs, and one inbox serves neither well. ## Design stages around decisions, not reporting Too many stages is not sophistication. It is usually a system asking people to report more than they can maintain. For most independent labels a small set is enough: received, in review, decision ready, closed. The value is not the reporting. It is that each stage implies a next action. New needs a first listen. Decision-ready needs a message. Closed should stop creating uncertainty for the artist and the team. If a stage does not tell someone what to do next, it is decoration, and decoration is what people stop updating first. ## Keep the music and its context together The fastest way to slow down review is to make people rebuild the submission every time they open it. Link in one place, note in another, last conversation buried somewhere else. The review item should carry what informed the decision to submit in the first place: the track, the artist, the fit, the current status. Then a five-minute listen is productive, because nobody has to do setup work first. It also makes decisions easy to revisit. When a track gets passed around internally, the next person starts from the same context instead of a stripped-down forward. This is roughly how we built Calmo: the track, the submitter's details, the status, and the ability to assign a reviewer all sit on one object, so review is about listening, not archaeology. ## Artist updates are part of the system Labels cannot give detailed feedback to every artist, and that is reasonable. Silence is still a poor default when a system can acknowledge receipt and share a status. The distinction is between a personal reply and a clear process. A status page and an automated notification do not pretend every demo gets a bespoke conversation. They show the label received the work and has a defined way to move it forward. The side effect is fewer "did you get it?" messages, which means fewer interruptions to the actual review. ## The standard to aim for A good A&R submission workflow passes one test: if a teammate opens the queue today, can they see what arrived, what needs listening, and what needs an artist update, without asking anyone? If yes, the workflow is doing its job. It gives the team a dependable base for the subjective part of A&R, which is deciding what deserves more attention. Keep the taste human. Let the admin be boring. --- Source: https://calmo.ai/blog/a-and-r-submission-management Section: Blog Last updated: 2026-06-05 --- # Why we give every artist a status page > A status page is not a promise of feedback. It is the smallest honest answer to the only question most artists have after submitting. **TL;DR:** A status page is not a promise of personal feedback. It answers whether the demo arrived, what state it is in, and whether a decision exists — without forcing artists to create an account. After sending a demo, most artists are not waiting on a verdict. They are trying to answer something much smaller: did the label even get it? From the label side that question feels trivial. The submission is somewhere in the queue, you will get to it. From the artist side there is no visible process at all. Their only options are to wait, follow up, or assume the link got missed. So we gave every submission a status page. Here is the thinking, including the objection we hear most. ## A status page is not a promise of feedback The common worry: if we make the process more visible, are we now on the hook for a personal response to every demo? No. Visibility and individual feedback are different things. A status page does not explain your internal decisions. It makes the process legible. The artist can see that the submission arrived, that it is still under review, or that you have made a decision. When you choose to send an update, the page gives that update a home. It says what is true without implying a timeline or an outcome you cannot guarantee. That is exactly why it works: it commits you to nothing except honesty about state. ## The confirmation email needs somewhere to lead Plenty of forms send an automatic "thanks, we got it." Good first step, but it usually dead-ends. The artist has no way to check back without writing again. A status link turns that confirmation into a reference they can return to, instead of digging up an old email or resubmitting the same track because they are not sure the first one worked. You benefit too: fewer messages that exist only to ask whether a demo was received, which means more of your attention on the review itself. ## What the page should say, and what it should not The best status pages are deliberately plain. Ours answers a few things and stops: - Did the submission arrive? - What is its current state? - Is there an update or a decision from the label? What it does not do is expose reviewer notes or make the artist navigate your internal workflow. It is for clarity, not for turning your review into a public dashboard. ## Keep it lightweight for the artist We made one specific call here: artists do not create an account. They submit through your branded portal, get a confirmation, and use their link to check back later. When you approve or reject, they get an email tied to the same submission. That matters more than it sounds. Asking an artist to register before they can check on a demo they already sent is the kind of small friction that makes the whole thing feel bureaucratic. A link they can open is enough. ## Why this is worth doing at all Even when you cannot sign a track, the submission experience becomes part of how artists talk about your label. An organized process signals that you respect the time it took to send music, and it quietly sets a boundary: submissions are reviewed through the portal, not through persistent DMs. For a small team that is the real win. A polished process does not require a support operation. It requires one system that acknowledges the artist and gives you a reliable way to update status when you are ready. It is a small piece of the product, but it changes the tone of the whole thing. The artist has an answer to "what happened to my demo," and you have one less thing to manage by hand. --- Source: https://calmo.ai/blog/artist-demo-status-page Section: Blog Last updated: 2026-05-27