DrupalCon DC By the Numbers: Community, Profit, and Sustainability
The number crunching from DrupalCon DC is done, and we wanted to share the results.
- 1,422 people came to DrupalCon DC.
- 130 people presented 109 sessions.
- That doesn’t include the people who led the 100 birds of a feather sessions that we know about (and we know we don’t know about all of the ones that took place).
- 9 people helped record the 109 sessions, and they’re all online now.
- 75+ people volunteered their early mornings, weekends, and conference time to register people at DrupalCon, stuff those green bags we all got, monitor IRC and twitter to make sure questions were answered and issues were dealt with, point people to where they wanted to go, and generally make sure DrupalCon DC rocked. Thank you : )
- 55 shops, companies, and organizations sponsored DrupalCon.
- 91 individuals sponsored DrupalCon as well.
- 100s of blog posts were written and 10,000s (and maybe more) of messages were tweeted that helped us all learn from each other and let people follow along from home.
Revenue was more than a half million dollars at $542,350.
Our expenses came in at $356,569.31.
The Drupal community made a profit of $185,780.69 from DrupalCon DC.
A Closer Look at Where the Money Came From
Ticket sales for DrupalCon DC brought in $230,750.
Sponsorships of DrupalCon DC brought in $311,700.
- 91 Individual sponsors raised $9,100.
- 23 Bronze sponsors raised $57,500.
- 17 Silver sponsors raised $85,000.
- 10 Gold sponsors raised $100,000.
- 4 Platinum sponsors raised $60,000.
How We Spent It
DrupalCon DC cost $356,569.31 at the end of the day. This means that it cost just over $250 for each person to attend. (Thank you sponsors!)
- It cost $44,210 to rent the space at the Convention Center. The venue also required us to have a nurse ( $990 ), security ( $2,022.41 ), and insurance ( $556 ).
- Projectors, screens, mics, and other AV equipment cost $39,176.01. Bringing in extra electricity by wiring some rooms with extra outlets and buying 70 power strips cost $2,469.40.
- Wireless internet cost $24,225.23. That’s with a hefty discount for not so great service.
- We ate $111,061.50 in lunches (4,475 total), and drank $29,504.64 in coffee (509 gallons).
- Pre-event planning by professionals cost $15,430, and their help at the conference itself cost $15,350.
- We paid our keynote speakers $3,000 each (well, the two other than Dries) to deliver targeted-to-us talks.
- Travel and hotel for our 25 scholarship winners cost $14,990.65 (plus 25 free tickets, which we’re not counting here), and $9,378.32 for our keynote speakers and event planning team.
- We spent $11,152.37 on DrupalCon swag: $7,510.99 on t-shirts, $3,397.23 on bags, and $244.15 on posters for sponsors.
- Printing program handbooks cost $3,919.55, and the banners and signs cost $3,134.80. We also paid a moving company $660.52 to bring this stuff from Development Seed’s headquarters to the venue.
- Paypal charged us $7,513.57 for processing DrupalCon tickets.
- Video recording almost every session at DrupalCon cost $6,006.20. Another big thank you to the video team : )
- Our two interpreters earned $3,305 combined for their assistance.
- We spent $1,035 on advertising, which includes printing buttons for Drupal user groups, stickers, and signs for DrupalCon Paris. Volunteers picked up the tab for all the designs.
- Lastly, we spent $4,478.14 on many small and random things.
This was all made possible because so many people volunteered their time to make DrupalCon DC a success, and this energy from the roots of the community is what made the conference so amazing. This is a feeling that sets us apart and that can’t be outsourced.
We are now in a unique situation in that we have the financial resources on hand to take DrupalCon to the next level. We’re sure that there will be some exciting conversations in the coming weeks as the Drupal Association looks at what DrupalCon should be in the future and how we as a community can make them sustainable. Do we want to keep doubling in size each year? How big should DrupalCons be? Should they stay heavily focused on development, or should designers, business folks, and other be seriously targeted too? Is it DrupalCon’s job to service n00bs, or should for-profit training events fill that void? When do we need to hire someone full-time to support DrupalCons and work alongside the host communities to help them put on a large community conference? What would a full-time support person mean for Camps, and how could that person help facilitate Camps and reduce the liability risk of a Camp or other event going poorly? Or would paying three times more for a DrupalCon ticket from an O’Reilly run conference make all these issues go away?
All of these are very real questions that are a result of our growth, and they don’t have any easy answers. At least now we have serious reserves so we can implement the hard decisions we need to make to ensure that the next DrupalCon will always be better than the one before it.
Et maintenant nous rendre à Paris!