How to Build a Music Industry CRM That Prevents Missed Follow-Ups

A music industry CRM is a system for recording every industry contact, what was said, and what happens next, so a follow-up never depends on memory. The three parts that make it work are a contact taxonomy (who these people are), a small set of follow-up states (where each relationship stands), and one next-action rule (what makes a contact overdue). Below is a working version of all three, a fictional sample pipeline, and a free tracker template.

Who this is for

This is for artist managers and self-managed artists holding relationships with promoters, venues, press, playlist curators, labels, and vendors across one or more active campaigns. The trigger is not a magic contact count. You need a system when you can no longer answer three questions from one trusted record: who spoke to this person last, what was agreed, and when is the next action due? A promoter who replied last week, a playlist curator waiting on a final single, and a label contact who went quiet after a promising call may not look urgent separately. Together, they are the relationships that quietly stall a campaign.

A CRM — customer relationship management system — does not need marketing automation, lead scoring, or an enterprise sales pipeline to be useful here. It needs three things: a place to log who the contact is, a place to log what happened, and a rule that surfaces who to contact next. The Music Managers Forum's role framework describes management work as spanning strategy, business affairs, live activity, recording, publishing, marketing, and team coordination. A music-industry CRM makes the relationship work across those areas visible instead of remembered.

The contact taxonomy

Group every industry contact into one of these categories. The category determines what "good" looks like for that relationship, not just who to file it under.

1. Venues and promoters — the people who book and run shows. Track capacity, typical deal terms, and past show history alongside contact details.
2. Booking agents — routing partners, usually managed in parallel across multiple markets.
3. Press and media — journalists, blogs, and podcasts who cover the artist or the scene around them.
4. Playlist curators and DSP contacts — editorial and independent curators, tracked separately from press because their follow-up cadence runs on release dates, not news cycles.
5. Labels and publishers — A&R, sync, and publishing contacts, often the slowest-moving and highest-stakes category.
6. Legal and business — lawyers, business managers, accountants; typically fewer contacts but higher-consequence follow-ups.
7. Vendors and collaborators — producers, engineers, photographers, videographers; project-based relationships that open and close.
8. Brand and sponsorship — partnership and marketing contacts, usually slower and more speculative than the rest.

A category with no current open item is not wasted effort — it's the reason the next opportunity in that category starts with a name instead of a cold outreach.

Follow-up states

Every contact needs exactly one relationship state and one factual last-interaction date. Keep the two separate: the state is a judgment call, the date is not.

• New — first contact made; no reply yet.
• Warm — an active, responsive back-and-forth; something is genuinely in motion.
• Follow-up Due — no logged interaction inside your follow-up window (see below), regardless of how warm the relationship felt last time.
• Cold — missed the follow-up window more than once with no response; deprioritized until a new reason to reach out exists.
• Closed — the specific ask is resolved, won, declined, or no longer relevant. Closed is not the same as deleted; keep the contact on file.

These are operating states for the template below, not universal CRM labels. Their job is to prevent "Warm" from becoming permanent. A contact can still be strategically valuable while an agreed action is overdue; mark the action due without rewriting the history of the relationship.

The next-action rule

A contact becomes Follow-up Due when either condition is true:

1. A specific next action was written down with a due date, and that date has passed; or
2. There is no dated commitment, and the contact has crossed the review interval your team chose for that category.

Set due dates from the actual commitment first: the date somebody promised feedback, the asset delivery date, the release date, the option deadline, or the date your team agreed to check back. Use a category interval only as a fallback, and treat it as a house rule rather than an industry standard. A fast-moving press pitch may need a shorter review interval than a contract discussion, but the right number depends on the ask, the campaign, and the recipient's expectations.

The rule only works if every logged interaction ends with one written next action and a due date — even if the action is "wait two weeks, then review." Without that field, the record explains the past but does not tell the team what to do next.

A fictional sample pipeline

Here is a fictional manager's contact-list excerpt as of 4 August 2026, showing the states in practice. Every person and organization in the downloadable file is invented.

Two contacts in this six-row excerpt are overdue by the next-action rule — Marcus Webb and Amara Osei — even though both conversations felt positive at the time. That is the point of the rule: it uses the written commitment and date, not how the conversation felt. Copy the full contact follow-up tracker CSV, which includes ten fictional contacts across every state, with the columns below.

Fields every contact needs

• Contact — full name.
• Role — one of the eight taxonomy categories.
• Organization — venue, label, publication, or agency.
• City — useful for routing and travel-adjacent outreach.
• Relationship State — New, Warm, Follow-up Due, Cold, or Closed.
• Last Interaction Date — the actual date of the last logged contact, not an estimate.
• Next Action — one sentence, written down at the end of the last interaction.
• Next Action Due — the date that turns the next action into an overdue item.
• Notes — enough context that anyone on the team could pick up the relationship cold.

Store only the information you have a legitimate operational reason to keep, restrict access to the people who need it, and correct or remove stale personal data. The UK's Information Commissioner's Office describes data minimisation as keeping personal data adequate, relevant, and limited to what is necessary. Privacy and outreach rules vary by location and channel, so this template is an operating record, not permission to scrape personal details or send unsolicited bulk messages.

Where contact tracking breaks down

• The state gets set once and never revisited. A contact marked Warm in March is still marked Warm in July because nobody built a habit of reviewing the list. Review relationship states on a fixed schedule — weekly is enough for an active roster.
• Notes exist, but there's no next action. "Had a good call with Marcus" is a record, not a plan. Every note needs a next action and a due date, or the interaction was logged but not actioned.
• Everything lives in email search. Searching a name in an inbox finds messages, not necessarily the relationship state or the next-action queue. Email can remain where the conversation happens, but it should not be the only place the team records who needs a reply.
• One category dominates the list. A manager focused on release week often lets label and legal follow-ups go cold because they don't feel urgent day to day — until the option deadline arrives and there is no current answer on file.
• The follow-up window is the same for every contact. A playlist curator waiting on a release date needs a shorter window than a publisher reviewing a multi-week licensing draft. Set the window by category, not as one global number.

How MNGR supports this, and where it stops

MNGR's implemented contacts module stores contact details, role, tags, notes, last-contacted date, and a relationship score of Hot, Warm, Neutral, or Cold. It also keeps a dated interaction history and can link a contact to artists, releases, and shows. That gives a small-roster manager one relationship record alongside the work the contact affects. The artist-managers workspace is designed around that connected view.

MNGR does not currently provide dedicated next-action or due-date fields on a contact, automatically calculate the five template states above, or surface an overdue-contact queue on the dashboard. It is not a fan CRM, email marketing platform, or SMS campaign tool, and it does not run automated outreach sequences. Use the CSV's Next Action and Next Action Due columns — or another dated task system — for that part of the method today. MNGR is the relationship record; the downloadable rule is the review discipline.

Next action

Copy the contact follow-up tracker CSV, load your current contacts into the eight categories, and set one relationship state and one next action per contact. Then set the follow-up windows for each category and mark today's overdue contacts before you add a single new name to the list.

Sources: HubSpot, "What is CRM?"; Music Managers Forum, "Code of Practice and Framework for Training"; Information Commissioner's Office, "Data minimisation". Reviewed and current as of 4 August 2026.

Sources

1. HubSpot — What is CRM? A Guide to Customer Relationship Management
2. Music Managers Forum — Code of Practice and Framework for Training
3. Information Commissioner's Office — Data minimisation