Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.patchline.ai/llms.txt

Use this file to discover all available pages before exploring further.

A pitch kit is the per-track package of DSP-curator-facing copy — the message you send when submitting to editorial playlists, pitching to an independent curator, or applying for a Spotify Marquee. Aria generates these grounded in real audio features, artist history, and the specific curator’s context.   Generation costs 2 credits per pitch.

What’s in a pitch kit

For one track, Aria generates:
VariantLengthUse
Short280 charsTwitter, DM, in-app message
Medium~150 wordsEditorial submission form, generic pitch
Long~400 wordsCold email to curator, detailed positioning
Personalized per curatorvariesReferences curator’s recent adds + style
Plus:
  • One-line hook — for subject lines, headers
  • Sonic positioning statement — “between [artist A] and [artist B]”
  • Three social proof points — relevant numbers (streams, playlists, growth)
  • One-paragraph artist bio — concise, recent, accurate
  • Asset references — links to streaming, smart link, cover art

Why it matters

Generic pitches get ignored. Pitches grounded in the curator’s actual recent adds plus your track’s actual sonic profile get heard. Aria’s pitch kit closes the gap between “I have a track” and “here’s why this curator should care.”

How to generate

1

Pick a track

Track must be in your catalog with sonic analysis complete.
2

Ask Aria

Or sidebar → Releases → project → Pitch kit tab → Generate.
3

Pick a curator (optional)

For personalized pitches:Aria fetches the curator’s recent adds via inspect_playlist and references them.
4

Edit + send

Pitch is markdown. Edit anything that doesn’t sound like you. Send via your usual channel (email, DM, S4A, SubmitHub).

Example: long-form personalized pitch

Subject: Sleeper — for Lush Sounds curators

Hi Anders,

I saw you added Tessa's "Long Way" to Lush Sounds 11 days ago — I
mention it because Mira (whose track I'm sharing) shares Tessa's mixer
and tends to sit sonically adjacent to her work.

Sleeper is Mira's third single this year. It's a 76 BPM F# minor
dreampop ballad with high acousticness (0.78), low valence (0.21), and
prominent reverb-soaked guitar. Closest sonic peers are Mazzy Star and
late-period Beach House.

A few proof points:
  • Her last release ("Late Bloom") hit 8.2k streams in week 1 and was
    added to "Bedroom Vibes" within 4 days of release.
  • Editorial adds on Mint Friday and Lush Sounds (CA) this year.
  • 1,247 active fan-list subscribers, 28% open rate.

Sleeper releases July 15. Pre-save: patchline.ai/store/mira/sleeper.
Lossless version available if you'd prefer that for the playlist.

Happy to send the artwork pack or a longer write-up — just ask.

— Mira

Tone control

Aria can rewrite in different tones:

Where pitches get used

ChannelHow
Spotify for Artists (S4A)Copy the medium variant into the editorial pitch form
SubmitHubUse the long form, attach the track
Curator DMs (IG, Twitter, email)Use the personalized variant
Submission portals (Daily Playlists, etc.)Use the long form
Spotify Marquee / ShowcaseUse the medium + budget block (Aria can add the budget rationale)

Pricing

ActionCredit cost
Generate pitch kit (all 3 variants)2 credits
Personalized variant for a specific curator2 credits
Tone rewrite1 credit
Translation1 credit

FAQ

Yes — Aria varies wording across regenerations. The factual content (BPM, key, sonic peers, social proof) stays consistent because those are pulled from your real data.
No. There’s no public submission API for S4A editorial. You copy the pitch into the S4A form yourself. Aria reminds you when the submission window opens (in the release plan).
Run sonic analysis first. Pitches without audio features default to generic genre descriptors — much weaker.
Yes — same flow. Released tracks can still be added to playlists. Some curators prefer 30-90 days post-release for “we already validated it” reasons.
Pitch-response tracking is on the roadmap. v1 you manually log it in the project anchor activity feed.