AI for Booking Agents, Managers & PromotersVenue outreach that doesn’t get flagged as spam, multi-act roster ops, contract drafting, lineup research, and post-show settlement: the operational layer for the people who book

Who this is for

This post is for the people behind the artists:

• Booking agents: managing 5–50 acts, pitching venues, negotiating fees, routing tours. Your week is 40% email, 30% phone, 30% strategy. AI cuts the email layer in half.
• Artist managers, wearing every hat: bookings, PR, socials, merch, release strategy. You don’t have a team; you have Claude Pro and 18 hours a day. This post reclaims 10 of those hours.
• Promoters: programming 4–20 events a month, coordinating multiple acts per bill, settling on the night or within 7 days. The multi-act ops layer from the festivals post applies; this one adds the pitching and roster management you do before and after the event.

If you’re a solo artist managing your own bookings, the earlier posts in this cluster cover you better, especially the release campaign automation and 12 ChatGPT prompts. This post assumes you’re booking for other people, not just yourself.

What this costs, and the maths that justifies it

Claude Pro or ChatGPT Plus: £18–20/month. That’s the entire stack. No automation tier needed. Agents run these prompts manually because every output needs review before sending.

The value maths: standard UK booking agent commission is 15–20% of gross fees (Musicians’ Union recommended rates). On a roster averaging £400/gig, one additional gig booked per week from AI-assisted pitching is £60–80/week in commission (£240–320/month). The subscription pays for itself on the first gig of the month. The 12 hours/week you save goes into the relationship work that actually moves fee negotiations upward, which is where agents build long-term income, not in typing faster.

If you’re HMRC self-employed (which most UK booking agents are), the subscription is an allowable business expense under “office and administrative costs.”

Prompt 1: Personalised venue outreach

The cardinal sin of agent outreach is the mail-merge pitch: same email, venue name swapped, sent to 50 bookers who all recognise the template. AI fixes this by writing a genuinely different pitch for each venue, drawing on the venue’s specific programming, capacity, and genre focus.

You are a UK booking agent pitching an act to a venue. Write a
personalised pitch email.

Agent: [your name], [agency name].
Act: [artist name], [genre], [home city].
Act credentials: [e.g. "Spotify 12k monthly, last 6 gigs: O2 Academy
Sheffield (support), The Bodega Nottingham (headline 120 sold), Brudenell
Leeds (headline 85 sold)"].
Draw in target city: [realistic number].
Fee range: £[X]-£[Y] (based on GX Index data for [city] [capacity]-cap).
Available dates: [list].

Venue: [venue name], [capacity]-cap [genre focus] in [city].
Venue's recent programming: [e.g. "books indie/alt-rock Fri-Sat, recent
acts include Yard Act support, Squid support, The Orielles headline"].
Booker: [name if known, else "the booker"].

Write a 100-word pitch that:
1. Opens with why THIS act fits THIS venue (reference their programming)
2. States the act's credentials in one sentence
3. Gives realistic draw and fee expectation
4. Asks for specific dates
5. Doesn't use "we'd love to" or "amazing opportunity"

Subject line: [City] - [Act Name] - [Month] availability. British
English. No exclamation marks. Professional, direct, not desperate.

Run this once per venue-act pair. For a 15-act roster pitching 10 venues each, that’s 150 pitches. At 30 seconds per draft (vs 8 minutes manually), you save around 18 hours per pitch round. Even after review and editing time, the net saving is 10–12 hours.

The failure mode to watch for: AI-drafted pitches across 50 venues develop a sameness that’s invisible to you (you read them over 20 minutes) but obvious to a booker who gets 3 of them in a week from different agents all using Claude. The tells: identical sentence structure, the same “their sound would sit naturally alongside” phrase, and a suspiciously uniform 100-word length. The fix: after generating the batch, read 5 pitches back-to-back and rewrite the opening sentence of any that feel templated. Vary your sentence length. A booker who spots AI copy from an agent assumes the agent doesn’t know the venue well enough to write their own email, which kills the pitch harder than a bad opening line would.

Prompt 2: Roster availability & routing

The weekly ops check: who’s available, where are the routing opportunities, and what’s the pipeline looking like for next month?

Weekly roster ops check for [agency name]. Date: [today].

Roster (columns: act_name, genre, home_city, fee_range, confirmed_gigs
this month, holds/pencils, available_weekends_next_60_days):

[paste roster data]

Analyse:
1. Acts with no confirmed gigs in the next 30 days (flag as "needs
   pitching urgently")
2. Acts with 3+ available weekends in the same month (flag as
   "underbooked, pitch priority")
3. Routing opportunities: two or more acts with confirmed or held dates
   in the same region on adjacent days (e.g. Act A in Leeds Fri, Act B
   in Sheffield Sat, shared transport/tech opportunity)
4. Fee conflicts: any act whose confirmed fee is >20% below their
   stated range (flag for renegotiation next round)
5. Pipeline summary: total confirmed gigs, total holds, conversion rate
   (holds→confirmed) for rolling 90 days

Output as a 1-page ops brief. Lead with the urgent items, then routing
opportunities, then the pipeline numbers.

Prompt 3: Contract clause drafting

Not legal advice, a first draft. You or your solicitor reviews before anything gets signed. The Musicians’ Union contracts guidance is a useful baseline for what UK industry-standard terms look like. This prompt generates the variable clauses for a standard UK gig contract, personalised to the specific deal.

Draft the variable clauses for a UK gig contract.

Parties:
- Artist: [name], represented by [agent/manager name, agency]
- Venue: [venue name], [address], represented by [booker name]

Deal:
- Date: [date], doors [time], set time [time], set length [minutes]
- Fee: £[amount], type: [guarantee / door split / hybrid]
- If split: [artist]% / [venue]%, minimum guarantee £[amount]
- Deposit: £[amount], due [date], non-refundable if artist cancels
  within [X] days
- Settlement: [on the night / within 7 days / within 14 days]
- Payment method: [bank transfer / cash on night]

Technical:
- Backline provided by venue: [list or "none"]
- PA provided: [yes/no, spec if known]
- Sound engineer: [venue provides / artist provides]
- Load-in time: [time]
- Soundcheck: [time]

Draft these clauses in plain English (not legalese):
1. Fee and payment terms (including deposit, settlement timeline)
2. Cancellation terms (tiered: 30+ days = full refund minus admin,
   14-29 days = 50% fee, under 14 days = full fee)
3. Force majeure (pandemic, venue closure, severe weather: neither
   party liable, deposit refunded)
4. Technical rider summary
5. Exclusivity radius: [X] miles, [X] days either side of the date

Output as numbered clauses ready to paste into a contract template.
Flag any clause where the terms I've given create a conflict or gap.
NOT legal advice. This is a first draft for review.

For a full breakdown of what belongs in a UK gig contract, read what to include in a gig contract.

Prompt 4: Lineup research for festivals

When a festival opens submissions or you’re pitching multiple acts to a multi-stage event, you need to understand the existing lineup before you pitch. This prompt reverse-engineers the festival’s programming pattern from their announced lineup.

Analyse this UK festival's announced lineup to identify gaps I can
pitch into.

Festival: [name], [location], [dates], [capacity], [number of stages].

Announced lineup so far:
[paste act names, from the festival website, socials, or Ents24]

My roster acts available for this festival:
[list: act name, genre, Spotify monthly listeners, home city, fee range]

Analyse:
1. Genre breakdown of the announced lineup (what % rock, electronic,
   folk, hip-hop, etc.)
2. Geographic spread (how many acts from which regions)
3. Draw tier spread (headline / mid-tier / emerging based on Spotify)
4. Gaps: genres underrepresented vs the festival's historical profile
5. For each of my roster acts: which gap they fill, which stage fits,
   and a 1-sentence pitch angle

Output: a gap analysis table, then a ranked list of my roster acts by
fit strength. For each, include the specific pitch angle I should use
when emailing the festival booker.

Prompt 5: Multi-act settlement

Month-end settlement across a roster with mixed deal types. This is the prompt that catches the arithmetic error that costs you a relationship.

Monthly settlement for [agency name], [month] 2026.

Commission rate: [X]% on all gross fees.

Gigs completed this month (columns: date, act_name, venue, city,
fee_type, gross_fee, door_count, ticket_revenue, split_percentage,
minimum_guarantee, deposit_received, expenses):

[paste gig data]

For each gig, calculate:
1. Artist gross (based on fee_type: guarantee / split / hybrid)
2. Agent commission ([X]% of gross)
3. Artist net (gross minus commission minus any expenses recouped)
4. Amount already received (deposit)
5. Balance due to artist

Then group by act and produce an artist statement for each:
"[Act Name]: [Month] 2026 settlement. [X] gigs. Gross: £[Y].
Commission ([Z]%): £[A]. Expenses: £[B]. Deposits received: £[C].
Balance due: £[D]. Payment within [7] working days."

Output: per-gig table, per-artist summary, agency total (total
commission earned, total settled). Flag any gig where the split
calculation was less than the minimum guarantee (hybrid triggered)
or where a deposit exceeds the final settlement (overpayment).

Prompt 6: Quarterly roster review

The review that tells you which acts are earning their slot on your roster and which are costing you time without returning revenue.

Quarterly roster performance review for [agency name], [Q1/Q2/Q3/Q4]
2026. Commission rate: [X]%.

Roster data (columns: act_name, genre, gigs_booked, gigs_completed,
cancellations, total_gross_fee, total_commission, avg_fee, venues_pitched,
pitch_conversion_rate, avg_door_count):

[paste quarterly data]

Analyse per act:
1. Commission earned vs time invested (use gigs_completed as proxy)
2. Pitch conversion rate (venues pitched → gigs booked)
3. Average fee trend (rising, stable, falling vs previous quarter)
4. Cancellation rate (flag >10% as concern)
5. Revenue per hour estimate (commission ÷ estimated hours: around 2hrs
   per gig booked including pitching, contracting, settling)

Output:
- Ranked table by total commission descending
- "Keep" tier: top 30% by commission + conversion
- "Develop" tier: middle 40%, decent conversion but low fee or volume
- "Review" tier: bottom 30%, low commission, low conversion, or high
  cancellation
- 3 specific actions for next quarter (e.g. "raise Act X's floor by
  £50", "stop pitching Act Y to 200+ cap rooms, conversion is 0%")

Format as a 1-page briefing. Be direct. Name acts, name numbers.

What goes wrong: the 5 mistakes that cost agents real money

Every failure mode below has happened to agents using AI-assisted workflows in the UK. The UK Music “This Is Music” 2025 report identified relationship capital as the single most valuable currency in live music booking, and these mistakes burn it.

• The stale venue brief. AI pitches a 4-piece rock band to a venue that stopped booking live music 6 months ago, or pitches to a booker who left in January. AI doesn’t know what’s current. It works from whatever data you feed it. If your venue spreadsheet is 3 months old, your pitches are 3 months wrong. Check the venue’s socials for recent gig posters before every pitch round. 5 minutes of verification saves a week of silence.
• The inflated draw. AI will smooth “we brought 35 to The Bodega last time” into “strong draw across the Midlands” unless you pin it to a number. Bookers who’ve been in the industry for 10 years can smell an inflated draw claim from the subject line. Feed exact numbers into every pitch prompt. If the honest number is 20, say 20. A booker will respect that more than a vague “growing following.”
• The contract clause that doesn’t match UK norms. AI defaults to American contract language. A “liquidated damages” clause in a UK grassroots gig contract will make a 100-cap pub booker think you’re taking the piss. UK grassroots booking runs on trust and plain English, not legal architecture. Always review AI-drafted clauses against the tone of your previous signed contracts. If the AI output feels like it was written by a solicitor, it’s wrong for this tier of venue.
• The settlement rounding error. AI handles arithmetic well, but it handles interpretation badly. A hybrid deal (“£300 guarantee or 70% of door, whichever is higher”) with 60 tickets at £8 = £480 gross, 70% = £336, so the split wins. AI sometimes misreads “whichever is higher” as “whichever is first stated.” On a 15-act roster doing 40 gigs a month, one misinterpreted hybrid clause is £36–150 out of an artist’s pocket. Check every hybrid calculation by hand. The 2 minutes per gig is non-negotiable.
• The festival pitch that ignores the politics. The lineup research prompt identifies genre gaps objectively. What it can’t know: that the festival booker hates your act’s previous agent, that two of your roster acts have a personal feud, or that the “gap” it identified exists because the festival deliberately avoids that genre for licensing reasons. AI gives you the data layer. The politics layer is yours, and it matters more at festival scale than anywhere else in UK booking.

The lines AI doesn’t cross

• AI doesn’t negotiate. It drafts the opening pitch. The negotiation (reading the booker’s counter, knowing when to hold, when to fold, when to package two acts for a discount) is yours. That’s the 15% you earn.
• AI doesn’t manage relationships. Remembering that the Manchester promoter’s daughter plays violin and asking about it at the start of the call. That’s not promptable.
• AI doesn’t make roster decisions. Signing an act, dropping an act, deciding who gets the festival slot when two of your acts both fit, that’s judgement backed by market knowledge. The quarterly review prompt gives you data; the decision is yours.
• Settlement accuracy is on you. The AI does the maths. You check every number before it goes to an artist. A wrong settlement breaks trust that took 2 years to build.

For commission structures and what’s standard in the UK, read booking agent commission: 15–25% models explained. For pitching technique beyond the AI draft, see pitching acts to venues: 3 email templates. For building the roster itself, see managing an artist roster: 3 to 30 acts.

Where this fits in the cluster

This is post 9 of 9, the final post in the AI for UK Musicians cluster. The full series:

• Foundations: 12 ChatGPT prompts, AI for music marketing, the £25/month tool stack.
• Intermediate: fan growth, data analysis, release-to-gigs playbook.
• Advanced: release campaign automation, AI for video & artwork, agents, managers & promoters (you are here).

Both clusters, artists (9/9) and venues (9/9), are now complete. 18 posts, 200+ minutes of reading, 50+ copy-paste prompts. Start at whichever hub matches your role.

Annual refresh commitment

This guide was published on 15 May 2026 and is refreshed every May. We re-verify every reference, recommendation, and data point once a year. Next scheduled refresh: May 2027. If any claim is outdated before then, email support@gigxchange.app and we will update it within 24 hours.