Chapter 3: Business Model
How does this event get paid for?
Running a great event costs money. Even a scrappy, no-frills hackathon has costs — platform fees, maybe some food, prizes, marketing. Before you get deep into planning, figure out the money side. Not because it's glamorous, but because running out of budget halfway through planning is a miserable experience.
This chapter helps you think through whether your event is for-profit or community-driven, where the money comes from, and how to make the numbers work.
For-profit vs. community-driven
These aren't moral categories — they're business models. Both are valid. What matters is being honest about which one you're running, because it shapes your pricing, your sponsor relationships, and participant expectations.
Community-driven (non-profit):
The event exists to serve a community. Revenue covers costs, not margins.
Funding comes from sponsors, grants, institutional budgets, or small registration fees.
Participants expect the event to be cheap or free.
Success is measured in community impact, not revenue.
Examples: civic hackathons, university events, open-source sprints, community build days.
For-profit:
The event is a business activity. It might be a product in itself, a marketing tool, or a lead-generation engine.
Revenue comes from registration fees, sponsor packages, or the value created (talent pipeline, product integrations).
Participants accept higher fees if the quality justifies it.
Success includes financial sustainability alongside impact.
Examples: corporate innovation challenges, API hackathons, industry conferences with hacking tracks.
The middle ground — Many events are somewhere in between. A startup running a community hackathon that also generates leads. A non-profit charging a small fee to reduce no-shows. That's fine. Just be clear internally about what you're optimising for.
Where does the money come from?
Most events combine multiple revenue sources. Here are the main ones:
Sponsorship
This is the big one for most hackathons. Companies pay to be associated with your event in exchange for visibility, recruiting access, or product promotion. We'll cover this in depth in Chapter 5, but for now:
Sponsorship typically accounts for 50–80% of a hackathon's budget
Create tiered packages (Platinum/Gold/Silver/Bronze) with clear benefits at each level
Think about what sponsors actually want — it's usually recruiting, brand visibility, or product adoption
Don't give sponsors so much stage time that they hijack the event's energy
Registration fees
Free events get more registrations but ~65% show-up rate
Even a small fee ($10–25) dramatically improves show-up rates and signals commitment
Higher fees ($50–200+) work for professional/corporate events but require proportional quality
Consider "pay what you can" or scholarship options to keep events accessible
Some organisers charge a deposit that's refunded upon attendance — clever hack for reducing no-shows
Internal/institutional budget
If you're a company running an internal hackathon, this is your corporate budget
Universities may have department budgets, student activity funds, or grants
Non-profits may have programme budgets earmarked for community engagement
Grants & prizes from third parties
Tech companies often offer cloud credits (AWS, Google Cloud, Azure) as in-kind sponsorship
Government innovation programmes sometimes fund civic hackathons
Foundations and accelerators may sponsor events aligned with their mission
The BuilderBase model
Here's how it works when you run your event on BuilderBase:
Organiser fee: A flat fee per event that gives you access to the full platform (event page, registration, team formation, judging, analytics — everything)
Sponsor marketplace fee: When you bring sponsors onto the platform, BuilderBase takes a percentage of the sponsor fee. This means BuilderBase's incentives are aligned with yours — we do better when your sponsors do better.
This model means you can start planning without a huge upfront platform cost, and the sponsor-side fees only kick in when you're actually generating sponsor revenue.
What does an event actually cost?
Here's a rough breakdown of where money goes. Your numbers will vary, but this gives you a starting framework:
On-site event (per person, per day):
Venue: $10–30
Food & beverages: $7–15
Prizes: varies wildly ($0 for experience-only events to $10,000+ for corporate competitions)
Marketing & promotion: $2–5
Swag (t-shirts, stickers): $5–15 (optional — honestly, spend the money on better food instead)
Technology/platform: varies
Speakers/judges: $0–20 (many volunteer, some expect honorariums)
Contingency (10–15% of total): always include this
Online event (per person):
Platform costs: varies
Video conferencing license: $0–5
Prizes: same range as on-site
Marketing: $2–5
Speaker honorariums: $0–20
Cloud credits for participants: $0–10
Hybrid event: Take on-site costs for your in-person group + online costs for your virtual group + an additional 20–30% for the AV bridge (cameras, streaming, extra staff).
Making the numbers work
A few principles:
Know your break-even point. How many participants do you need, at what registration fee plus sponsorship level, to cover costs? Run this calculation early.
Start lean. Your first event doesn't need a DJ, branded hoodies, or a five-course dinner. Focus on the experience: good wifi, decent food, clear challenges, great mentors. Add the fancy stuff once you've proven the model.
Sponsorship is leverage. One good sponsor can cover what would take 100 registration fees to match. Invest time in sponsorship outreach (Chapter 5) — it has the highest ROI of any planning activity.
In-kind sponsorship counts. Venue space, food, cloud credits, software licenses — these aren't cash but they reduce your costs. Track them in your budget as both income and expense.
Be transparent with participants. If you're charging a fee, be clear about what it covers. If sponsors are funding the event, acknowledge them. People appreciate honesty about where the money comes from and where it goes.
Don't forget the legal stuff
It's not exciting, but handling these early prevents headaches later:
IP ownership. Who owns the projects built during the event? In most community hackathons, teams keep their IP. In corporate hackathons, the company may claim ownership. Whatever you decide, document it clearly and communicate it before people start building. This should be in your Terms & Conditions and your registration form.
Terms & conditions. Draft basic event T&Cs covering: eligibility, IP ownership, liability limitations, and dispute resolution. For larger events, have a lawyer review.
Privacy & data. You're collecting personal data during registration. Ensure you're compliant with GDPR (if operating in Europe) or relevant local regulations. Tell participants what you'll do with their data, especially if you're sharing profiles with sponsors.
Prize tax implications. In some jurisdictions, cash prizes above certain amounts are taxable income. Research the rules for your location and inform winners so they're not surprised.
Key takeaways:
Decide early if your event is for-profit, community-driven, or a mix
Most hackathons are funded primarily through sponsorship (50–80% of budget)
Even small registration fees dramatically improve show-up rates
On-site costs roughly $20–60 per person per day; online is much cheaper
Always include a 10–15% contingency in your budget
Start lean, prove the model, then scale up the production value
Sort out legal basics early: IP ownership, T&Cs, privacy/GDPR, prize taxes
BuilderBase's fee model aligns with your success — you pay more when your sponsors pay more