agentleFS
guerrilla2799guerrilla2799/event-and-scale-os/skills/sponsorship-negotiation/SKILL.md

sponsorship-negotiation

Skill2 starsChanged 3 months agoMITView on GitHub

Use before signing any event sponsorship, or when the user says "they sent a sponsorship package", "what should we negotiate", "review this event contract", "what do we get for our money". Runs the five pre-signature diligence questions, scores the package on stage and transferable seats, and audits the onboarding pack against the contract after signature. Writes workspace/events/<event>/contract.md. Owns the terms and the contract. Not the go or no-go itself, which is `event-selection` and should run first.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    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
  1. Distinctive:

    All three clear: defensible at a serious price.

    line 30
  2. Distinctive:

    When does the matchmaking platform open, exactly?: If pre-booked meetings are the metric, this date decides the entire outreach schedule.

    line 37
  3. Distinctive:

    What is the expected attendance and title mix?: Never model a meeting target without it, and net out sponsor and exhibitor staff

    line 41
  4. Distinctive:

    Add three more when they apply:

    line 43
  5. Distinctive:

    When does booth position selection open, and how does priority work?

    line 44
  6. Distinctive:

    Do speakers we bring from a partner or customer consume our transferable passes, or are they comped?

    line 46
  7. Distinctive:

    Write down, while it is fresh, what you would need next time to sign again.

    line 75
  8. Distinctive:

    No invented attendance figures: If the organizer will not give a number, that is itself a finding

    line 87

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Sponsorship Negotiation

What to buy, what to refuse, and the questions to ask before signing. After signature you have no leverage, so almost all the value in this skill is in using it early.

When to use

  • A sponsorship package is under consideration, at any price
  • Renewing last year's sponsorship, which is when nobody re-examines anything
  • The onboarding pack has arrived and needs auditing against what was sold
  • Deciding between tiers

Inputs

  • Reads: workspace/events/<event>/decision.md, workspace/program/charter.md
  • Needs from user: the sponsorship prospectus, the contract if drafted, the organizer's contacts, and what the salesperson has said verbally

Workflow

1. Score the package on three things

Everything else is decoration.

  1. Does a senior person from our company get a speaking surface? A main-stage slot, a panel, a moderated session, a workshop. Not a "sponsor spotlight" in a side room during lunch
  2. Do we control at least five transferable passes we can hand to named prospects and customers?
  3. Is the primary metric pre-booked executive meetings rather than badge scans?

All three clear: defensible at a serious price. Missing the first two: it is a booth and a logo, and that is a no at any price.

Transferable passes are the most under-negotiated line in event contracts. They read as a nice extra and they are frequently the highest-return item in the deal, because a comped pass is a reason to call a prospect that has nothing to do with your product.

2. Ask the five diligence questions, in writing, before signature

Send these to the organizer's customer success or marketing contact rather than the salesperson. They are usually pleased to be asked, and every answer changes the plan.

  1. When does the matchmaking platform open, exactly? If pre-booked meetings are the metric, this date decides the entire outreach schedule. Onboarding booklets are frequently out of date. Get it from a human
  2. What are the literal booth or stand dimensions, and what is supplied? Get feet and inches, the height cap, and the list of what comes with it: table, chairs, power, wifi, lead scanner, monitor. "Premium position" can mean a table-sized footprint, which changes the production budget by thousands
  3. Does the speaking slot include Q&A, and are decks merged into one master file? A twenty-minute slot including Q&A is a fifteen-minute talk. A merged master file kills custom fonts, animation, embedded video, and live demo
  4. What insurance does the venue require? Sample certificate, exact additional-insured entity names, coverage limits, deadline, and recipient. This is a broker request with a lead time
  5. What is the expected attendance and title mix? Never model a meeting target without it, and net out sponsor and exhibitor staff

Add three more when they apply:

  • When does booth position selection open, and how does priority work?
  • How many staff passes are included, and what is the registration cutoff?
  • Do speakers we bring from a partner or customer consume our transferable passes, or are they comped?

3. Negotiate in this order

Priorities, highest value first:

AskWhy it mattersTypical flexibility
A speaking surface, or a better oneMakes the whole thing defensibleModerate. Producers control this, not sales
More transferable passesHighest return per dollarHigh. They cost the organizer very little
Attendee list access, in any formTurns the event into a list-building asset tooModerate. Frequently "names and titles, no emails"
Better matchmaking placementDirectly drives the primary metricModerate
Priority booth positionReal advantage at a busy showUsually tier-based
Push notifications, newsletter features, bag insertsReach you do not pay for againHigh. Frequently thrown in
PriceThe thing everyone negotiates first and gains least fromLow to moderate

Ask for the assets they produce about you. Most organizers create a set of promotional graphics: sponsor announcements, speaker announcements, countdown posts. Request all of them for your own channels, and tell them to tag your speakers rather than the contract signatory.

4. After signature, audit the onboarding pack

The day it arrives, line by line against the contract. Deliverables go missing between the two, and the ones that go missing are the promotional items with real reach. Ask about every absent item by name.

Also confirm the timing of each one. A newsletter feature scheduled after the event is amplification rather than promotion, which changes what it should contain.

5. Write the deliverables register

| # | Deliverable | Contracted | In the pack | Confirmed | Value | Owner | Deadline |

Rank by value. This register is what run-of-show and event-logistics build from.

6. Set the renewal note now

Write down, while it is fresh, what you would need next time to sign again. Renewal conversations happen when the memory has faded and the number looks familiar.

Output

  • Writes: workspace/events/<event>/contract.md with the score, the diligence answers, the deliverables register, and the renewal note
  • Prints: the three-part score with a verdict, the unanswered diligence questions, and the negotiation asks in priority order

Rules & quality bar

  • All five diligence questions answered in writing before signature. They are conditions, not follow-ups
  • A booth and a logo is a no at any price
  • Negotiate passes and stage before price
  • Audit the onboarding pack line by line and chase missing items by name
  • Never accept a verbal answer on a date that drives the schedule. Matchmaking open dates in particular
  • No invented attendance figures. If the organizer will not give a number, that is itself a finding

Related skills

  • Reads: event-selection
  • Hands off to: event-budget, conference-activation, meeting-engine, event-logistics
  • See also: docs/operations-runbook.md sections 4, 7, and 8

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.