The release planner turns a finished track (or EP, or album) into a structured rollout: milestones, launch windows, marketing tasks, DSP pitches, smart links, fan messaging — all grounded in your catalog, your audience, and what’s actually working for artists like you. Free tier sees basic release planning (manual checklist). Starter+ unlocks the AI-generated plan with project anchors.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.
What it does
A release plan is a living document. Aria generates the structure; you edit, approve, and mark off tasks as you ship them. Every plan includes:| Section | What it contains |
|---|---|
| Pre-release timeline (Week -6 to Week 0) | Artwork, pitch copy, DSP submissions, smart link, pre-save, teasers |
| Release day | DM list, post copy, storefront update, fan-facing announcement |
| Post-release (Week +1 to +4) | TikTok/ads, follow-up pitches, performance review, momentum capture |
| Project anchor | The persistent project record that holds your campaign state, track list, and conflict-safe edits |
| Tasks | Discrete checkable items, each tied to a date and (optionally) an Aria action |
When to use it
- You’ve finished a track and don’t know where to start. Open the planner and ask Aria. You’ll have a draft plan in 60 seconds.
- You’re managing 5 artists with overlapping release schedules. Project anchors let you track multiple campaigns without losing state.
- Your last release flopped and you want to know why. Aria can compare the new plan against historical performance — “the dreampop releases that worked all had X in week -4, yours didn’t.”
Where it lives
- Web: Sidebar → Releases → + New project
- Aria: “Plan a release for [track]” — generates the plan, asks if you want to commit it as a project anchor.
- Claude plugin: Same flow, native to Claude. The plugin includes a progressive interview that walks the planner with you step by step.
Quick start
Pick a track
Already in your catalog? Skip to step 2. If not,
import or upload it first —
the planner is much better when it has sonic analysis
available.
Open the planner or ask Aria
Easiest path:Or sidebar → Releases → + New project, pick the track,
set the target date, click Generate plan.
Review & edit
Aria returns a 6-week rollout. Edit anything that doesn’t fit. The
plan is markdown — change task names, dates, owners, descriptions.
Commit as a project anchor
Click Save as project (or tell Aria “yes, commit it”). The
rollout is now a persistent project at
/dashboard/projects/[id] with concurrent-write-safe storage and
daily task reminders.What a generated plan looks like
A typical 6-week rollout for a dreampop single (Mira’s “Sleeper”):Prerequisites
- A track in your catalog with sonic analysis complete.
- Starter+ for the AI-generated plan. Free tier sees a manual checklist.
- (Optional) Gmail connected for Aria to draft and send curator outreach.
- (Optional) A smart link plan if you want Aria to wire the pre-save automatically.
How it works
- The release-planner UI calls Aria with the track, target date, and optional constraints.
- Aria assembles the rollout from:
- The track’s sonic features (genre cluster, energy profile).
- Your historical release performance.
- Your roster’s audience data (Audience).
- A baseline 6-week template that adjusts based on tier (Pro/Scale unlock more granular timelines).
- The plan is rendered in markdown in the chat. If you commit it, the project anchor saves the campaign state with conflict-safe updates (see project anchors).
- Once committed, Aria can adjust the plan based on early signals such as playlist adds, social engagement, and missed tasks.
Examples
Example 1 — Generate a fresh plan
Example 2 — Adjust mid-flight
Example 3 — Roster-level view
Pricing
| Tier | Release planner access | AI plan generation |
|---|---|---|
| Basic (manual checklist) | — | |
| Full (AI-generated plan, 1 active project) | 10 credits/plan | |
| Full + multi-artist (5 active projects) | 10 credits/plan | |
| Full + roster view (20 active projects) | 10 credits/plan | |
| Full + API access | 10 credits/plan |
Related features
- Project anchors — the persistent state
- AI campaign planner — deeper marketing
- Pitch kit — the pitches Aria generates for the plan
- Playlist matching — the curator targeting
- Smart links — auto-wired pre-saves
- Gmail integration — for Aria to send pitches
FAQ
Can I edit the plan after Aria generates it?
Can I edit the plan after Aria generates it?
Yes. The plan is editable markdown. Click any task to rename, change
date, add description, mark complete. You can also ask Aria to revise
— “move week -2 stuff earlier”, “drop the TikTok ad”, “add a
storefront launch task in week 0”.
What if my release is in 3 weeks, not 6?
What if my release is in 3 weeks, not 6?
Aria compresses the plan. Editorial submission moves to ASAP, fewer
pre-release weeks, more weight on release-day and post-release. The
template adjusts to the timeline you give it.
Can multiple people work on the same plan?
Can multiple people work on the same plan?
Yes on Pro+ (3+ seats). Pro adds 3 team seats, Scale adds 10. The
project anchor uses concurrent-safe writes — your edits and your
teammate’s edits won’t overwrite each other.
Does Aria actually submit to Spotify editorial?
Does Aria actually submit to Spotify editorial?
No. Spotify for Artists doesn’t have a public submission API. Aria
drafts the pitch copy and reminds you when the window opens; you
submit in S4A yourself.
What if I miss a deadline?
What if I miss a deadline?
Ask Aria “what’s overdue” and it flags them and suggests
recovery actions. If you miss the editorial window, Aria suggests
alternative paths (DM curators directly, lean harder on playlist
matching, etc.).
Can I have multiple campaigns running at once?
Can I have multiple campaigns running at once?
Starter: 1 active project. Pro: 5. Scale: 20. Enterprise: unlimited.