Skip to main content

How to use Apollo as a manager or label

Apollo works with the artist's context - their Vision, Identity, and projects. As a manager or label rep, you don't need to explain who the artist is. Apollo already knows. You just need to ask the right questions.

Written by JC Sanchez
Updated over 2 months ago

๐Ÿ”ฎ How it works

When you're inside an artist's workspace, Apollo draws from:

  • Their Vision board - visual identity and aesthetic

  • Their Identity - why they make music, who it's for

  • Their Context - how they work, content preferences, tools

  • Their Projects - releases, mood boards, timelines

Every recommendation Apollo gives is filtered through the artist's creative identity. You're not getting generic advice - you're getting advice tailored to them.


๐Ÿ“‹ Release planning

Help artists map out their next drop:

"Build a 6-week release timeline for [artist]'s upcoming single"

"What should [artist] prioritize in the 2 weeks before release?"

"Create a launch day checklist for this project"

"Compare the rollout strategy for a single vs an EP for this artist"

"We only have 3 weeks before release - what's the minimum viable plan?"


๐Ÿ’ฌ Content strategy

Get recommendations for what to post and when:

"What content should [artist] post this week?"

"Give me 5 content ideas that align with their current project mood board"

"What's working on their TikTok and what should they do more of?"

"Suggest content themes for the next month leading into release"

"They hate being on camera - what content formats would work for them?"

Apollo factors in their content preferences from Context, so suggestions fit how they actually like to show up.


๐Ÿค Meeting prep

Walk into artist meetings with clarity:

"Summarize where [artist] is in their release prep"

"What are the top 3 things we should discuss in our check-in?"

"Based on their progress, what's the biggest risk to this release?"

"Generate talking points for our quarterly planning session"

"What questions should I ask to understand their creative direction better?"


๐Ÿ” Roster insights (for multi-artist teams)

If you manage multiple artists, use Apollo in each workspace:

"How does this artist's release timeline compare to best practices?"

"What's unique about this artist's positioning that we should lean into?"

"Where is this artist underinvesting in their career?"

"What opportunities is this artist not seeing?"

Switch workspaces using the selector (top left) - Apollo adapts to each artist's context.


๐ŸŒ Market research and opportunities

Explore strategic angles:

"What brands might be a good partnership fit for this artist?"

"What sync or licensing opportunities align with their sound?"

"How could this artist break into the UK market?"

"What collaborations would make sense given their aesthetic?"

"What's an unexpected angle for this release that fits their identity?"

Apollo draws from the artist's Mythos to suggest opportunities that actually make sense for them, not generic industry plays.


๐ŸŽจ Helping artists articulate their vision

Sometimes artists know what they want but struggle to express it:

"Based on their mood board, how would you describe their visual direction?"

"Help me write a one-paragraph artist bio based on their Identity"

"What's the core emotion this project is trying to convey?"

"How should we pitch this artist to DSPs?"

Apollo can translate what's in the workspace into language you can use externally.


โš ๏ธ Remember: Apollo reflects the artist

Apollo's recommendations are grounded in what the artist has shared. If the Mythos is incomplete, Apollo has less to work with.

If recommendations feel generic:

  • Check if the artist has completed their Vision board, Identity, and Context

  • Ask them to fill in more details or update outdated information

  • The richer their Mythos, the better Apollo serves both of you


๐Ÿ’ก Pro Tip

Start your week by asking Apollo:

"What should I focus on with [artist] this week?"

It's a fast way to get oriented across your roster without digging through each workspace manually.

Did this answer your question?