sponsor-outreach-and-close
Skill0 starsChanged 25 days agoMITView on GitHub
Finds, prioritizes, pitches, follows up, and closes brand partners for an artist-led athletic event, from warm relationships first to cold category outreach, with honest proof, a one-page proposal, and a partner agreement checklist. Use for "find sponsors for this event", "draft the sponsor email", "follow up with [brand]", "who should we pitch first", or "what goes in the partner agreement". Drafts only; a human approves every send and signature.
In this repository13 other files it gives its agents.
- artist-deal-termsSkill
- artist-fit-and-conceptSkill
- content-capture-and-rightsSkill
- event-budget-pnlSkill
- event-producerSkill
- launch-campaignSkill
- permits-insurance-and-riskSkill
- press-and-mediaSkill
- recap-and-sponsor-reportSkill
- registration-and-capacitySkill
- run-of-show-and-staffingSkill
- sponsor-inventory-and-pricingSkill
- sport-format-designSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 52
Never say the artist is confirmed unless the term sheet shows it.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Sponsor Outreach and Close
Step 1: Build the list in rings
- Warm: people who already know you or the artist. Existing partners, former colleagues at brands, local businesses you're a customer of.
- Local fit: businesses in the event's city that would genuinely be useful on the day.
- Endemic national: brands in the sport's natural partner categories (see the sport reference) with an active grassroots, club, or creator program. Look for public application forms and named community or grassroots owners.
- Artist-adjacent: brands the artist's audience loves, after the conflict check.
For each prospect record: category, why them, the specific inventory you'd offer, contact path (named person beats generic inbox), relationship strength, conflict check status, and next action.
Work warm first. One warm yes becomes proof for every cold ask.
Step 2: Write the proposal
One page (assets/one-page-proposal.md):
- The event in two sentences.
- Who will be there, with honest numbers and labels.
- The specific ask: one inventory option and one price. Offer the menu only if they ask.
- What they get, as deliverables with dates.
- Proof: past events and their verified results. If this is a first event, say so and offer a smaller pilot price.
- The deadline and why it's real (production lead time, print date).
Step 3: The email
Short. From a real person's inbox, not a marketing tool, for first touches.
Subject: [Artist] x [Brand]: [one-line event]
Hi [Name],
[One sentence on why them, specific to their brand or program.]
[Artist] is [doing the hard thing] with [who] in [city] on [date]. We're producing it: [what we handle].
We'd love [Brand] to [specific useful role], [price or "covered with product"]. That gets you [two concrete deliverables].
Worth a 15-minute call this week? One-pager attached.
[Name]Never say the artist is confirmed unless the term sheet shows it. Never imply other partners have signed if they haven't.
Step 4: Follow up
- Day 4 to 5: one line, add one new useful detail (venue confirmed, registration opened).
- Day 10 to 12: last note, offer a smaller option or a later event.
- Then stop and log it. Silence isn't a no forever, but it's not a pipeline either.
Step 5: Close
A yes in email is a start. Before any logo appears:
- Signed agreement or written order covering the checklist in
assets/partner-agreement-checklist.md. - Invoice issued with payment terms. Track paid, not just signed.
- Final conflict check against the artist's deals.
Pipeline honesty
Track stages: Researched → Contacted → Replied → Call held → Proposal sent → Verbal yes → Signed → Invoiced → Paid. Report each stage count separately. Pipeline dollars are never revenue.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

