Buying Guide
CRM for Artist Booking Agents
How booking agencies keep promoter, venue and festival contacts clean across a team, stop double-pitching, and hold the history a roster runs on.
An artist booking agency has two contact problems, and they need two different answers. The first is shared and operational: one clean list of promoters, venues and festivals that the whole desk can see, so two agents never pitch the same buyer in the same week. The second is personal and invisible: what that buyer actually told you last time, which no shared database ever holds.
Agency software solves the first. Nothing solves the second by itself, which is why an agency can have a tidy CRM and still lose relationships when an agent leaves.
Start with the shared record
If your promoter and venue records live in spreadsheets and inboxes, fix that first. A shared system is the only thing that stops double-pitching, because double-pitching is a visibility problem rather than a memory problem.
What the shared layer has to do:
- One record per buyer, not one per agent, so there is a single current version
- Roles that are explicit: talent buyer, promoter rep, production, settlement contact
- Pitch history everyone can see: who offered what, when, and what came back
- Holds and offers attached to the buyer, not just to the show
- Ownership: whose relationship this is, so an intro goes through the right person
| Layer | Tools built for it | What it does not hold |
|---|---|---|
| Booking and touring software (Prism.fm, Master Tour, Muzeek) | Holds, offers, routing, advances, settlements | Why a buyer said no, and what they asked for instead |
| General shared CRM (HubSpot, Attio, folk) | Shared pipeline, deal stages, team visibility | Anything the agent did not think to type into a field |
| Spreadsheet plus email | Nothing durable | Everything, within about a quarter |
| Personal relationship memory (Intriq) | What a buyer told one agent, recallable before the call | Shared team state; it is a single-user tool by design |
Cleaning up promoter and venue records
If you are starting from spreadsheets, do it in this order. The order matters more than the tool.
- Pick the surviving system first. Merging into a destination you have not chosen creates a fourth spreadsheet.
- Deduplicate on the venue, then the person. Venues are stable, people move. A record keyed to a room survives the buyer changing jobs.
- Mark the current buyer explicitly. Most stale agency lists are not wrong about the venue, they are wrong about who books it now.
- Attach roles. A settlement contact and a talent buyer are not interchangeable, and treating them as one record is what produces awkward calls.
- Record ownership. One named agent per relationship, visible to everyone.
- Then import history. Past offers and results, even roughly, are what stop the new system feeling empty in week one.
Expect the first pass to be about the roster you are actively working, not the whole archive. A clean list of the two hundred buyers you pitch this year beats a complete list of four thousand you do not.
The part a shared CRM cannot hold
Here is the failure that surprises agencies who did everything right.
A shared record tells you the buyer at that theatre is Lena, that you offered a mid-size act in March, and that it came back a pass. It does not tell you that Lena said she was moving away from that genre for the autumn, that she asked whether your folk act tours in spring, that her programming budget resets in October, or that she prefers a phone call before an offer lands.
That second set is what makes the next pitch work, and it almost never gets typed into a CRM field, for a structural reason: fields ask closed questions, and conversations produce loose sentences. So the loose sentences stay in one agent’s head, and they leave the building when that agent does.
What each agent should capture
This is per-agent memory, written in seconds after a call, in plain language rather than fields:
- Programming direction: the genres and sizes a buyer is actually chasing this cycle
- Budget cycle: when their money resets, which decides when an offer lands well
- Pitch preference: email with an EPK, a call first, or through their assistant
- What they passed on and why, in their words rather than as a status
- Rooms and capacity notes: what actually sold there, not what the spec says
- Promises: an avail you owe them, an intro to another buyer, a hold you said you would release
A realistic captured note
After a call, an agent might write this in under a minute:
Lena Okafor, books the 900-cap theatre and the summer series. Passed on the March offer, said she is moving away from heavier guitar for autumn and wants folk and roots for the spring series. Budget resets in October, so offers before then get a soft no regardless. Prefers a call before anything formal, hates cold offers by email. Asked whether our Glasgow act tours in April. Owes nothing; I owe her an avail by end of month.
Six months later, that is the difference between an offer that lands and an offer that gets filed. The shared CRM would have recorded one word: passed.
Why the timing matters more than the pitch
Buyers work on cycles that are invisible from outside the building. A club books six to twelve weeks out, a theatre season three to six months, a festival six to nine months, and public-funded programmes often move on a fixed budget year.
Pitch outside the window and a good offer gets a polite no, which agents then misread as a relationship problem. It usually is not. It is a calendar problem, and the fix is to write down the window the first time a buyer mentions it, then have the reminder arrive inside it rather than at a round-numbered interval.
Where Intriq fits, and where it does not
Intriq is private relationship memory for one person. It is not a shared agency database, it does not dedupe your venue list, and it is not a substitute for booking software. An agency still needs a shared system for holds, offers and settlements.
What it holds is the layer above that: an individual agent writes a quick note, typed or spoken, right after a call, and it becomes searchable, person-centered memory. Before the next conversation, that agent can pull up what this buyer actually said, and ask for a briefing drawn only from notes they saved. It works from their own words rather than the web, and it says when it does not know.
It runs on iPhone and in any browser, so the note happens in the two minutes after the call rather than at the end of the week, which is the only time it reliably happens at all.
For the artist’s side of this same relationship, see best CRM for musicians. For the general category, see what is a personal CRM and the personal CRM hub.
Key takeaway: A booking agency needs both layers. Use booking or agency software for the shared record that stops double-pitching, and give each agent private relationship memory for what buyers actually say, because that half is what walks out of the door when an agent leaves.
FAQ
What is the best software for an artist booking agency?
For shared operations, a booking platform such as Prism.fm, Master Tour or Muzeek, because holds, offers and settlements need to be visible to the whole desk. For the relationship history behind those records, agents need a personal memory layer as well. Most agencies that only buy the first still lose context when staff change.
How do we stop two agents pitching the same buyer?
Make ownership explicit in the shared system and require pitch history to be logged against the buyer rather than the show. Double-pitching is a visibility failure, so it is fixed by a shared record, not by a better memory.
Should promoter records be keyed to the venue or the person?
The venue, with the current buyer marked on it. Venues persist and buyers move. Keying to the person means every job change silently orphans a record, which is the most common reason agency lists go stale.
Can a personal CRM be used by a whole agency?
Not as a shared workspace. Intriq is single-user by design, so each agent keeps their own memory. That is the right shape for conversation notes, which are personal and often candid, and the wrong shape for holds and offers, which belong in a system everyone can see.
How do we keep contacts current across the team?
Assign an owner per relationship and review the active roster quarterly rather than continuously. A buyer list is only ever current for the venues you are actively working, so scope the upkeep to those and let the long tail age.
What should an agent write down after a buyer call?
Programming direction, budget cycle, pitch preference, what they passed on and why in their own words, and anything you promised. Five lines, written before the next call starts, is enough to make the next pitch specific six months later.
Final recommendation
Fix the shared record first, because double-pitching costs you credibility with buyers and it is the cheaper problem to solve. Then give every agent somewhere private to put what buyers actually say, so the roster’s relationship history survives a resignation.
Use Intriq for that second layer: quick capture after a call, private per-agent profiles, and reminders that arrive with the buyer’s own words attached. For the habits that make it stick, read how to take better contact notes and how to send a cold reconnect message for the buyers who already went quiet.