Release plans & lifetime fans

What it is

A release plan is a structured launch roadmap attached to a single track. It's generated from a short questionnaire about your release — budget, timeline, marketing goals — and comes back with a checklist of milestones, todos, and draft social posts you can start working through right away.

Lifetime fans are people who subscribe once to your artist profile and then automatically have every future release saved to their Spotify library the moment it goes public. They also get an email notification. You collect fans through your public profile page or from a presave link attached to a specific track.

Using it

Creating a release plan

1. Open a track and go to the Release plans tab.
2. Click New plan and answer the questionnaire (release date, budget, platforms, marketing goals, social accounts).
3. Aden generates a set of milestones, per-milestone todos, and draft social posts based on your answers. Review and confirm.
4. The plan is saved in draft status. Move it to active when you're working it, completed when the launch is done, or archived to shelve it.
5. Market-wakeup posts from the questionnaire are materialised immediately as draft posts in your Posts dashboard, wired to the connected accounts you selected — ready to review and schedule.

Working a plan

• Each milestone has a due date, an optional budget, and a list of todos.
• Check off todos as you complete them. Milestones track progress across the team.
• When writing a todo, type @ to mention anyone who can work the track — its collaborators, the owning team's members, and members of any organisation the team belongs to (the same people you can @mention on media and asset comments).
• You can share the plan with an external contact (label, manager) via a read-only share link — they see the milestones and status without needing an Aden account.
• You can delete a plan from either the plans list or the plan header. When the plan has milestones and tasks, you choose whether to also delete all linked data (milestones and tasks are permanently removed) or keep it (the milestones and tasks stay on the track and are only unlinked from the plan).

Collecting lifetime fans

1. Share your public profile link (/@<team>/fans) or embed it on your website.
2. Visitors enter their email. They can optionally connect their Spotify account to get new releases auto-saved to their library.
3. Confirmed fans appear in your Fans dashboard under Teams → [team] → Fans.

What fans receive

When you release a track (status moves to released), every active lifetime fan automatically gets:

• The track saved to their Spotify Liked Songs (if they connected Spotify).
• An email notification about the new release.

This happens on the release date — fans who signed up after the fact are not back-filled.

The label release schedule (organisations)

Organisations (labels, distributors, managers) get a roster-wide Releases page at Org → Planning → Releases. It aggregates every upcoming track and album across the artist teams the org has release access to:

• Schedule by month — upcoming releases grouped by calendar month, each with cover art, artist team, single/album badge, release date and countdown.
• Release readiness — each upcoming release shows what's still missing for release day: artwork, audio, ISRC (tracks), UPC (albums), a release plan, and distribution (a distributor on the track/album or an active submission to the org). Complete releases show a Ready badge.
• Ready, not scheduled — content marked ready_to_be_released that has no release date yet, so the label can slot it into the calendar.
• Recently released — the last 60 days, for follow-up.

An Upcoming releases widget with the same data (next 8 releases) is on the org dashboard by default. Access is scope-gated: only teams that granted the release scope appear.

Reflect after the release. Once a track is released, leave an optional release retrospective: a 0–5 star rating (half stars allowed) plus what went well, what didn't, and what to do differently next time — about the milestones, the release plan, the content, anything. Retrospectives are visible to the whole team. One click saves the written learnings as a team skill, so the AI assistant automatically applies them the next time it drafts a release plan or milestones — the team stops repeating the same mistakes.