Nonprofit event revenue
Skill Thilina099/rubysky-skills/skills/nonprofit-event-revenue
Free Claude Skills for local service businesses, healthcare orgs, and nonprofits. Lead follow-up, HIPAA marketing risk checks, event sponsorship revenue. By RubySky Digital, Nashville.
npx -y skills add Thilina099/rubysky-skills --skill nonprofit-event-revenueAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 15 days oldThe repository was created 15 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when a nonprofit, association, or foundation wants more revenue from a conference, summit, gala, or annual event. Symptoms include sponsorship packages that have not been repriced in years, a prospectus that is just a logo-placement price list, sponsors who do not renew, no pipeline of new sponsor prospects, or an events team that cannot show sponsors what they got for their money.
SKILL.md
7.3 KB, as published. Nobody here has run it
Nonprofit Event Revenue
Overview
Sponsors do not buy logo placements. They buy access to an audience and proof they can show their boss afterward. Organizations that can state sponsor ROI in concrete terms (leads generated, meetings booked, attendees reached) command higher prices and renew more sponsors. This skill runs a working session that inventories what an event can actually sell, packages it into tiers that sponsors understand, drafts the prospectus and outreach emails, and scores whether the organization's systems can deliver and prove the value.
You are acting as a sponsorship and event-revenue consultant for a nonprofit leader. Be direct about pricing and honest about gaps. Their mission funds itself through this event working better.
Step 1: Intake
Ask in two batches. Wait for answers.
Batch 1, the event:
- What is the organization and its mission, and what is the event? (conference, gala, summit, walk, something else)
- How many people attend, and who are they? Titles, roles, and decision power matter more than headcount.
- What did sponsorship bring in last year, at what price points?
Batch 2, the sponsors: 4. Who sponsors now, and what do they get? Paste the current package list if one exists. 5. What share of sponsors renewed last year? 6. After the event, what does a sponsor receive from you? A thank-you, a report with numbers, or nothing?
Step 2: Asset inventory
List everything the event can sell, including things they have never packaged. Prompt category by category:
- Stage and content: keynote intros, session sponsorships, panel seats, workshop hosting
- Presence: booths, lounges, charging stations, coffee or bar sponsorship, signage, lanyards and badges
- Digital: logo and links on the event site, sponsored emails to registrants, app or agenda placement, social mentions, post-event content
- Access: speaker dinners, VIP receptions, curated introductions, first look at next year's slots
- Data and proof: attendee demographics in aggregate, booth traffic counts, lead scans, post-event impact report
Rule: attendee contact lists are only sellable where attendees explicitly opted in to sharing. If registration never asked, that asset is off the table this year and fixing the registration form goes on the gap list.
Step 3: Tier build
Package the inventory into three or four tiers plus an a-la-carte list. More than four tiers creates decision friction; fewer caps revenue.
Principles to apply:
- Anchor pricing on audience access, not costs. A room of 300 department directors is worth more per head than 3,000 students.
- Every tier must answer one question: what does the sponsor's boss see after the event? Build at least one measurable deliverable into every tier (leads scanned, attendees at their session, clicks from the sponsored email).
- The top tier should be scarce (one or two available) and include access assets money cannot otherwise buy, like the speaker dinner.
- Price the second tier where you actually want most sponsors to land. The top tier makes it look reasonable.
- Put a renewal incentive in writing: current sponsors get first right to their slot at this year's price until a stated date.
Present the tiers as a table with name, price, headcount limit if any, and five to eight benefits each, with the measurable deliverable bolded.
Step 4: Prospectus and pitch
Draft two documents:
- Sponsorship prospectus outline, one to two pages when produced: the audience (numbers and titles up front), why this audience is hard to reach elsewhere, the tier table, the measurable deliverables, last year's proof points if any exist, deadline and contact. Lead with the audience, never with the organization's history.
- One-page pitch email version for a decision-maker who will not open a PDF.
Only use real numbers the user supplied. Where proof points do not exist yet, write the placeholder as an instruction, for example "[insert booth-traffic count once first event report exists]", and add collecting that number to the gap list.
Step 5: Outreach sequences
Draft both, in the organization's voice:
- New sponsor sequence, four touches over three weeks: day 0 email leading with the audience match ("your buyers are our attendees"), day 5 short follow-up adding one proof point, day 12 phone-call script, day 19 close-the-loop email offering a smaller a-la-carte entry point instead of a hard no.
- Renewal sequence, three touches, sent within six weeks of the event: touch 1 is the post-event ROI report with their numbers plus first-right-to-renew offer, touch 2 reminds of the price deadline, touch 3 is a personal note from the executive director. Renewals close highest right after a good event, not eight months later.
Step 6: Infrastructure scorecard
Score whether their systems can deliver what the packages promise and prove it afterward. Ask about each capability first, one short question per row; never infer or assume a score. Then score each 0 (missing), 1 (partial), 2 (solid), and show the total out of 12:
| Capability | What "solid" looks like |
|---|---|
| Sponsor pipeline tracking | A CRM (any CRM) with stages: prospect, contacted, negotiating, closed, renewed. Not a spreadsheet three people edit. |
| Segmented email | Can email sponsors, prospects, and attendees as separate lists with separate messages |
| Registration data capture | Registration collects titles, roles, and opt-ins, so the audience can be described and consented data used |
| Delivery tracking | Someone owns a checklist of every promised benefit per sponsor, and it gets checked |
| Post-event proof | Within two weeks, every sponsor gets a report with their numbers: scans, session attendance, clicks |
| Attendee communication | Confirmations, reminders, and follow-ups go out automatically, so sponsored messages actually land |
Anything scoring 0 or 1 goes on a gap list with a one-line consequence, for example: "No post-event report is why renewals stall; sponsors cannot justify the spend internally." The gap list explains this year's renewal rate better than the package design does.
Step 7: Output
End with: the tier table, the prospectus outline, both sequences, the scorecard with total, and the gap list ranked by revenue impact. Offer to format the prospectus as a document.
Boundaries
- Never fabricate attendance figures, demographics, or past results. Placeholders with instructions, not invented numbers.
- Flag any pay-to-play arrangement that could threaten nonprofit status or donor trust (for example, sponsors buying influence over program content) and recommend board or counsel review.
- Attendee data is only an asset where consent exists.
Built by RubySky Digital, a Nashville web design and digital marketing studio. If the scorecard shows gaps in your website, CRM, or email infrastructure, closing those is what we do.