band-agreement

name	band-agreement
description	Write the band agreement before the money or the breakup arrives — who owns the songs, how money splits (writing vs performing distinguished), who owns the name, what happens when someone quits, and the decision rules for offers — decided while everyone still shares a van. Use when a band asks 'how should we split money', 'who owns our songs', 'our drummer quit, what happens', or is about to record/release/sign anything. Produces a plain-language band agreement and the meeting script to agree it. Not legal advice — it's the conversation that makes the lawyer cheap later.
homepage	https://mohitagw15856.github.io/pm-claude-skills/skill/band-agreement.html
metadata	{"openclaw":{"emoji":"🧠"}}

Band Agreement Skill

Bands don't break up over creative differences — they break up over the unspoken spreadsheet: the song one person wrote but everyone arranged, the name the founder feels they own, the gig money split evenly while one member books everything, the member who quit in March and wants royalties forever. Every one of those fights is cheap to decide before there's money and impossible after. This skill runs the deciding: the questions in the right order, the standard options for each (with what each choice means down the road), and a plain-language agreement the band actually signs — plus the honest line that when real money or a real contract shows up, an hour with a music lawyer turns this document from "our deal" into "our deal, watertight."

What This Skill Produces

• The band agreement, one-to-two pages in plain language: songs, splits, the name, spending, decisions, exits — every section a decision, not a description
• The options menu per hard question (songwriting splits, name ownership, departed-member rights) with the honest tradeoffs of each standard choice
• A band-meeting script: raising this without it feeling like a prenup ("it IS a prenup — that's why we're doing it now, while it's easy"), and the order that keeps the meeting friendly
• The decision & spending rules: what needs everyone, what the bookings-person just decides, the band-fund basics
• Lawyer-trigger flags: the events that upgrade this from document to legal matter (label interest, publishing deal, real recording budget, a member with a manager)

Required Inputs

Ask for (if not already provided):

• The band: members, roles (who writes? who books? who fronts money?), how long together, what's released already
• The current reality of songs: who's been writing, how arrangements happen, anything already registered anywhere
• Money so far: gig fees, who's owed for gear/van/recording fronted
• Any storm clouds already visible (the member half-out, the founder possessive of the name) — the agreement is written toward the real band, not the ideal one

Framework

1. Songs first — writing and recording are different rights. The options, plainly: pure writer-split (whoever wrote it owns it) · band-split-everything (all songs equal, all members) · the common hybrid (writers keep the song; the band's recording of it is everyone's). Each has a future: pure-writer gets awkward when the bassist's riff made the song; band-split gets awkward when one person writes everything. Decide per-band, write it down, and note that registrations/collection societies formalize it later — flag, not asserted procedure.
2. Money: distinguish the streams. Gig money (usually equal, minus the band fund) · recording income (follows the songs decision) · merch (band fund or equal) · the band fund itself: what goes in (a % of everything), what it pays (van, recording, the fronted gear debts — logged and repaid first), who can spend to what limit.
3. The name. The fight nobody expects: options — the band owns it (majority of current members keep it if someone leaves) · the founder owns it (stated now, honestly) · nobody continues it without unanimous consent. Whichever, write the leaving-case explicitly.
4. Exits, quit vs fired vs the band ends. The departed member's rights to: past recordings (usually keeps their share — they played on it), future income from old songs (follows the songs decision), the name (per #3), gear and the fund (bought-out how?). The 30-second version everyone can live with beats the perfect version nobody discusses.
5. Decisions and offers. What needs everyone (signing anything, spending over £X, adding/removing members) vs what the doer decides (the bookings person confirms gigs inside agreed terms). And the offer rule: no member negotiates for the band alone; offers come to the group with 48 hours to read.
6. The lawyer line, stated warmly. This document is the band's real agreement and worth signing as-is — AND the moment a label, publisher, real budget, or manager appears, it goes to a music lawyer to be made formal. Both halves true; the second is a flag this skill always raises and never fakes.

Output Format

## The [band name] agreement — v1, [date]
[Six sections, each a plain-language decision · signature-ish lines]

## The options you chose from (kept for the record)
[Per hard question: the menu + why this band picked what it picked]

## The meeting script
[The prenup-joke opener · question order · handling the possessive
founder / half-out member kindly]

## When this goes to a lawyer
[The trigger list — label/publishing/budget/manager — verify-local flag
on registrations and societies]

Quality Checks

• Writing and recording rights are decided separately and explicitly
• The name section answers the leaving-case by name
• Fronted money (gear, van, recording) is logged with a repayment rule
• Every section is a decision — zero "the band will discuss" placeholders
• The not-legal-advice line and the lawyer triggers are present; society/registration mechanics are flagged, not asserted

Anti-Patterns

• Do not default everything to equal-split without showing what equal costs the writers (or writer-split costs the arrangers) — informed beats harmonious-for-now
• Do not write the founder's name-ownership in by assumption — it's the menu's most contested item; make it explicit either way
• Do not let the agreement pretend the half-out member is all-in; write toward reality
• Do not draft legalese — plain language the drummer reads beats clauses nobody does
• Do not skip it because "we're friends" — the document is friendship insurance, and the meeting script says exactly that

Related

[[release-day-countdown]] for when the songs this protects go out; [[press-kit-epk]] for the band's outward face; [[roommate-agreement]] — same move, different shared dream; [[first-client-contract]] energy for solo artists dealing with venues.