How to Build a DSP Pitch Brief Before Submitting
Build one accurate, platform-aware brief before submitting a music pitch to a DSP, with a fact check, ownership notes, and a constructed example.
The short answer
Build a DSP pitch brief before opening any platform form. Record the release and track identity, eligible artist roles, delivery status, date, rights and credits, listener-facing description, factual proof, platform-specific fields, submission owner, and follow-up plan. Then adapt only the fields each DSP actually requests. A brief improves consistency and exposes missing evidence; it cannot predict editorial decisions or promise a playlist outcome.
Three things to know
- 01
A DSP pitch brief is an internal source of truth, not a copy-and-paste pitch submitted unchanged to every platform.
- 02
Separate verified release facts from interpretation, campaign ideas, and claims that still need evidence.
- 03
Assign one accountable owner for each submission and preserve the final version, timestamp, and platform route used.
- 04
Use platform-specific eligibility and access rules as a gate before polishing language or choosing descriptive fields.
What belongs in a pre-submission DSP brief?
Use this as a handoff checklist. The sample values below describe fields, not a required platform form.
- 01
Release identity
Artist, title, version, contributors, label, territories, language, release date, and delivery status checked against the source record.
- 02
Eligibility and access
Platform route, account role, release-level and track-level artist roles, timing rule, and any documented exclusions.
- 03
Listener description
Accurate genre, mood, context, and audience language that explains the track without claiming a result or trend.
- 04
Evidence register
Approved credits, artist statement, release facts, campaign assets, and a source or owner for each material claim.
- 05
Submission control
One owner, one approver, final version, submission timestamp, confirmation record, and a named follow-up decision.
What is a DSP pitch brief for?
A DSP pitch brief is a controlled working document that gathers the facts a team may need before using a platform submission route. It prevents the release date, artist role, genre description, credits, and campaign details from drifting between people or forms. It is not a universal form and it is not a promise of selection. The existing guide on coordinating DSP pitches covers the wider cross-platform workflow; this page focuses on making the source packet accurate before that coordination begins.
What release facts belong in the brief?
Start with identifiers that can be checked against the distributor or label delivery record: artist and release name, track title, version, contributors, label, territory, language, release date, delivery status, and the destination profile or account. Add the recording and composition credits that the team is authorized to state. For Spotify, current support guidance describes an eligible upcoming unreleased song, a one-song pitching limit, and role-based restrictions, so the brief should record eligibility rather than assume every collaborator can submit.
From our networkMake music. Keep the business in tune.
Invoices, expenses, and music business accounting. Keep the paperwork together.
Meet ClefHow should a team separate facts from pitch language?
Use three columns: verified fact, evidence or source, and proposed wording. A verified fact might be a documented release date or an approved collaborator credit. Proposed wording might explain the song's mood, audience, or context. Keep those categories separate so a creative description does not quietly become a claim about popularity, trend status, audience size, or expected performance. If a sentence cannot be tied to a release record, artist statement, approved asset, or first-party platform guidance, shorten it or mark it for review.
What platform differences should the brief capture?
Create a small route matrix with the platform, official entry point, eligible account or team role, timing rule, required fields, owner, and last verification date. Spotify, Apple Music, Amazon Music, and Deezer do not need to be treated as one identical workflow. Each platform documents its own submission routes and account limits. When a platform does not document a direct route for the artist's situation, record that limitation plainly and route the release through the distributor or label process that is actually available.
How can an artist test the brief before submission?
Run a read-back with someone who did not write the first draft. Ask them to identify the focus release, eligible artist role, listener description, strongest evidence, submission owner, and unresolved risk. Compare every material field with the delivery record and approved credits. Then remove unsupported superlatives, paid-placement language, promises of streams, and claims that a platform favors a particular sound. The goal is a clear and defensible submission, not a more impressive-sounding one.
What should happen after the brief is approved?
Lock a version for each route, record who submitted it and when, and save any confirmation or status signal in the campaign folder. Do not treat submission as the end of the release plan. Keep the calendar, owned content, publicity, and post-release measurement separate from the platform pitch itself. If a fact changes, update the source record first, then decide whether the platform route allows an edit or requires a new instruction. Platform interfaces, eligibility, and reporting details can change, so verify the current first-party guidance before every campaign.
Frequently asked questions
- Is a DSP pitch brief the same as a pitch form?
- No. The brief is an internal source of truth. Each platform may request different fields, access, timing, or route details, so adapt the approved facts to the form that actually exists.
- Should every DSP receive the same pitch text?
- No. Keep the underlying facts consistent, but use only the fields and descriptions that the specific platform requests. Do not imply that one platform's process applies to another.
- Who should own a DSP pitch submission?
- Assign one accountable artist, manager, label, or distributor owner with the appropriate account access. Other collaborators can review facts and supply assets without creating conflicting submissions.
- Can a strong DSP brief secure playlist placement?
- No. A clear brief can reduce avoidable errors and unsupported claims, but editorial decisions and platform outcomes remain outside the team's control.
- What if the release facts change after the brief is approved?
- Update the underlying source record, note the change and time, then check whether the platform allows an edit or requires a new submission instruction. Preserve the audit trail.
- Can an artist use this brief for independent playlist curators?
- The structure can help organize accurate facts, but independent curator outreach is a separate route with different safety and relationship considerations. Do not present it as DSP editorial access.