Music promotion for independent labels
An independent label promotes a roster by running each release as its own campaign, with its own list segment, sender and timing, while sharing infrastructure: authenticated mailboxes, verification, templates and reporting. Never push the whole roster through one mailbox in one day, and report replies per artist rather than a single vanity total.
Updated 2026-10-26. Written by the team that operates this platform; no rankings, placements or listener numbers are promised anywhere on this page.
The roster is not one campaign
The most common label mistake is treating promotion as a shared pot: one list, one mailbox, every artist batched into the same week. It produces three problems at once. The mailbox reputation absorbs the whole roster’s volume, the press and curators receive near-identical emails from the same label, and nobody can tell which artist’s campaign actually worked.
Separate the campaigns, then share the plumbing. Each release gets its own contact segment, its own sender name matching the artist, its own send dates and its own reporting. The label shares the domain, the verification discipline and the templates. That structure is also what makes a small label look professional: a curator receiving three pitches from three artists over three months, each written for them, remembers the label.
- One campaign per release, never one campaign per quarter.
- A sender name that matches the artist, on a stable label domain.
- Segments by genre and outlet type, not one undifferentiated list.
- Reporting per artist, so the next release is planned with evidence.
Shared infrastructure, without shared damage
A label needs more than one mailbox. If every artist sends from the same address, a bad list for one release contaminates deliverability for the rest. Use enough sending identities that volume is spread and a problem can be isolated, and keep each identity’s volume steady rather than spiking on release day.
Verification is the other shared discipline: every address checked before it enters a segment, and every hard bounce removed after a send. Allowances should match the roster’s realistic monthly output, not its ambitions. On this platform the tiers scale managed mailboxes from 1 to 15 and email allowances from 2,000 to 500,000, which maps to a roster size rather than a single artist. The published per-tier numbers are on the pricing page, and the release timeline guide covers how to sequence the campaign around them.
Segmentation that a curator can feel
Press and curators do not want the label’s catalogue; they want the one record that fits what they cover. Build segments by genre, outlet type and region, and record the last time each contact heard from the label. If two artists on the roster fit the same outlet, space the pitches out and give each one a different angle rather than sending both in the same week.
Keep a shared suppression list at label level: anyone who has asked not to be contacted again, hard bounces, and addresses that generated a complaint. That list is the single most valuable asset a small label builds, because it is the only thing standing between a growing roster and a blocked domain.
What to report, and to whom
Report per release: contacts attempted, delivered, replies, positive replies, pieces of coverage and playlist additions you can verify. Do not report open rates as success; opens are affected by privacy features and say little about whether a curator cared. Positive replies per hundred contacts is the number that tells a label whether the list or the pitch needs work.
Artists on the roster deserve the same numbers, including the unflattering ones. A label that reports "campaign sent" and nothing else trains its artists to expect magic. A label that reports 40 contacts and two replies teaches them what promotion actually costs in effort, which is also how you justify the next campaign.
Published plans
These are the plans this platform publishes today, in US dollars per month. Every paid plan includes managed domain SMTP sending and email verification; the tiers differ in allowances.
| Plan | USD / month | Emails | Contacts | Managed mailboxes |
|---|---|---|---|---|
| Starter Outreach | $49 | 2,000 / month | 1,000 | 1 |
| Pro Industry | $99 | 10,000 / month | 10,000 | 3 |
| Artist Plus | $199 | 50,000 / month | 50,000 | 5 |
| Label | $399 | 100,000 / month | 100,000 | 7 |
| Agency | $699 | 250,000 / month | 250,000 | 10 |
| Enterprise | $1000 | 500,000 / month | 500,000 | 15 |
Allowances reset on the first day of each UTC month. Prices are read from this site's own plan data, not estimated. See the pricing page for the exact feature list per plan.
Three ways a small label can run outreach
Each option below is a real structure, not a marketing claim. Costs other than ours are not quoted because they vary by market.
| Approach | What the label does | Main risk |
|---|---|---|
| In-house, one mailbox | One person sends everything from one address | Deliverability damage affects the whole roster |
| In-house, per-release campaigns | Separate segments and senders per artist, shared templates | Needs planning discipline and a written process |
| Outsourced to a freelancer | A publicist or plugger runs each campaign | Knowledge and contacts leave with the freelancer |
Worked example: four releases in a quarter
A small label has four releases in a quarter and a Pro Industry plan: 3 managed mailboxes, 10,000 emails a month and up to 10,000 contacts. Each release gets one mailbox and one segment of 250 contacts, matched by genre. That is 1,000 first emails across the quarter plus follow-ups, comfortably inside the allowance and spread across three sending identities.
Week one of each release is list preparation and verification. Week two is the first wave. Week three is follow-ups with one new asset. The label reviews positive replies per 100 contacts at the end of each release and changes the segment or the first line for the next one. Nobody sends more than 250 emails in a day, and no campaign shares a mailbox with another release in the same week.
- 1Map the quarter: which release, which genre, which outlet segments.
- 2Assign one sending identity per release and keep daily volume steady.
- 3Verify every contact and remove label-level suppressions before building the segment.
- 4Run first wave, then one follow-up per non-reply with a new asset.
- 5Report contacts, replies, coverage and verified additions per artist.
The numbers in this example are arithmetic on the plan allowances, not observed results.
Label campaign checklist
One checklist per release, signed off before the first send.
- The release has its own campaign, segment and send dates.
- The sender name matches the artist, not the label catalogue.
- The mailbox has not absorbed another release’s volume this week.
- Contacts are verified and label-level suppressions are removed.
- Press and curator segments are separated by genre and outlet type.
- A follow-up is scheduled with a specific new asset.
- Reporting is defined per artist before the campaign starts.
- A hard-bounce clean-up is booked after the campaign closes.
What this structure will not do
It will not make a weak release work. Promotion multiplies what exists: a record with a clear identity and a real audience responds, and a record without either produces polite noes. It also will not let a label scale contacts faster than it can personalise them; a roster with ten artists and one writer still has one writer’s capacity for research.
It will not protect an artist from a label-level reputation problem if the shared domain is abused. Sharing infrastructure is efficient, and it is also shared risk, which is why suppressions, verification and volume discipline are not optional. And it will not replace the parts of label work that are not email: release operations, artwork, metadata and the live plan.
- No guaranteed coverage, playlist adds, streams or sales.
- No shared mailbox used to blast a whole roster in one day.
- No claims about other labels’ methods or results.
Questions people ask
- Should each artist have a separate sending mailbox?
- For a roster, generally yes — or at least enough identities that one release cannot sink another’s deliverability. The sender name should match the artist either way, and no single mailbox should carry the whole roster’s monthly volume.
- How many contacts should a small label email per release?
- A segmented wave of 150 to 300 per release is a realistic starting point for a small roster, personalised by outlet type. The ceiling should be the time available to research and answer, not the plan allowance.
- Do we need separate lists for each artist?
- Separate segments, yes. You can keep one master contact database at label level with shared suppressions, but each campaign should build its own segment from it so a curator is not emailed about three artists in one week.
- How should a label report campaign results to artists?
- Contacts attempted, delivered, replies, positive replies, coverage and verified playlist additions, per artist. Include the misses. Reporting only the wins makes the next campaign impossible to plan.
Tools we build for this work
Spotify Monthly Listenersthis site
Spotify Monthly ListenersDirect outreach to playlist curators, radio, press and industry contacts with managed sending.
LocalSMTP
SMTP accounts with DNS set upInbox-ready SMTP accounts with the domain, mailbox and DNS work handled for you.
Mail Pro
Mail ProCold email campaigns: sequences, senders, replies and reporting in one workspace.
AI Sales Agent
AI sales email workspaceAI-written cold email with campaign workspaces, pooled sending and reply handling.
Scrape.Email
lead finder and email verifierVerified B2B lead discovery and email verification before you send.
United States Marketing
WhatsApp, SMS and social outreachWhatsApp, SMS and social outreach in one marketing workspace.
Help Me Teach Me
Help Me Teach MeA patient AI teacher that shows you how to do a task, or does it with you.
How To Unblock Website
unblock a website or appProxies and VPS access for websites and tools that block your region or network.
Software Programmer
custom software developmentCustom software built for a specific workflow, integration or internal tool.