Running a festival is like conducting an orchestra where every instrument is a different stakeholder, and the score is written in real time. In our case, the conductor is also the composer, the sound engineer, and the stagehand—all rolled into one remote‑first studio. The day‑to‑day rhythm of a festival—ticket sales, line‑up curation, stage scheduling, audience engagement—flows alongside the sprint cycles of building the very software that powers it.
The Overlap of Schedules
The first lesson we learned was that the festival calendar and the development roadmap can bleed into one another. When we built FestOps, the platform that runs a festival from a single dashboard, we had to align the release of new features with the festival’s own milestones. For Blossom, the desert gathering that relies on crowd‑booked acts, the launch of the voting module had to coincide with the first round of ranked‑choice voting. We found that the best practice is to treat each festival milestone as a sprint goal. That way, the code that powers the ticket purchase, the leaderboard, and the ledger anchor is delivered just in time for the public event.
The Human Side of Code
In a small studio, the code is written, reviewed, and deployed by the same person. That creates a unique intimacy between the product and its users. When a festival organizer calls at 2 a.m. to fix a glitch in the lineup display, the fix is a single pull request that I review myself. The immediacy of that feedback loop keeps the software responsive to the festival’s needs. It also means that the responsibility for uptime falls squarely on the shoulders of one person. We learned to build in redundancy—multiple server instances, automated backups, and a clear rollback plan—because we cannot afford a single point of failure when the festival is live.
Balancing Creativity and Reliability
FestOps and Blossom both rely on a mix of Node/Express back‑ends, Vite/React front‑ends, and a Postgres or SQLite database. The code is AI‑assisted, but every line is still reviewed by a senior engineer. That balance between speed and quality is crucial when the stakes are high: a broken ticket sale during a live event can mean lost revenue and a damaged reputation. To keep creative freedom alive, we separate the “show” code (the fan app, the lineup display) from the “operations” code (staff apps, run‑of‑show, bulletins). This separation allows us to iterate quickly on the user experience while keeping the core operational logic stable and well‑tested.
The Power of Thematic Cohesion
One of the most rewarding aspects of building software for a festival is seeing the brand’s identity come to life across multiple touchpoints. Blossom’s lineup is reflected in the fan app every fifteen minutes, the quest badges appear in a lively marigold theme, and the ticket sales page echoes the desert aesthetic. When the software and the festival share the same visual language, the audience feels a seamless connection between the physical event and the digital experience. It also simplifies the development process: a single theme studio import can regenerate the entire front door, the public blog, and the licence plans on the marketing site.
Lessons for Other Small Businesses
1. Treat the festival as a living product—every change to the schedule should trigger a corresponding code change. Keep the codebase lean and modular—the smaller the scope, the easier it is to test and deploy during a live event. Invest in automated testing—unit tests, integration tests, and end‑to‑end tests give you confidence when you’re live on stage. Document everything—from API contracts to UI component libraries, so that a single person can pick up the project at any time.
The experience of running a festival while building its software has taught us that the rhythm of code and the rhythm of the event can harmonize. It demands discipline, but it also rewards with a product that feels alive, responsive, and deeply connected to the people who use it.
How would you balance the demands of a live event with the iterative nature of software development in your own business?