A one-day country festival touring three cities — built on the same engine as Tacos & Tequila. That's the whole point: a second brand shipped fast because the first was built as a system, not a trophy.
The problem
The promoter had a hit on their hands and wanted to run the same play in a new genre — country, not hip-hop. But 'just do it again' almost always means 'build it all again': a second site, a second set of ticket integrations, a second thing to patch and keep in sync forever. Anyone who's tried to clone a winning location knows the trap — the second one costs nearly as much as the first, and now you're maintaining two of everything. That tax is exactly what kills momentum after a first success.
The approach
I didn't start over. Country Rising runs on the same multi-city engine I built for Tacos & Tequila, so the whole skeleton — markets, tour dates, Tixr on-sale, email capture — was live on day one. That freed the real work to be the part that actually differentiates a festival: the brand, the art direction, the country-specific content and the city rollout.
The calls I made
Every real decision costs something. Here's what I traded, and why it was worth it.
Reuse the festival system, reskin the brand.
WhyThe structural problems were already solved and battle-tested on a live festival. Rebuilding them would've been ego, not engineering.
Trade-offLess novel architecture per site — but a second brand shipped in a fraction of the time, and one fix now upgrades both festivals at once.
Keep both festivals on one shared pattern.
WhyTwo events, one maintainable system — security, updates and new-city rollouts happen once, not twice.
Trade-offThe two brands can't diverge structurally without real effort. For events that share a playbook, that's a feature, not a limit.
The result
Country Rising went from idea to a live, touring brand in a fraction of the time the first festival took — because it stood on infrastructure that had already proven itself under fire. Two festivals, one system, one place to fix things. It's the difference between owning a website and owning a playbook you can run again, and again, and again.