The tour list is the product, not a feature
For an actively touring act, the gig calendar is the single most important piece of content on the site — it's what fans check before buying tickets, what bookers scan before extending an offer, and what a mailing-list subscriber wants updated the moment a new date drops. We build it as a dense, date-led list (date, city, venue, ticket link) that scales past sixty rows without a redesign, with sold-out shows marked rather than hidden — proof of demand, not a dead end.
This format holds across every genre we build for; only the visual skin (jazz's liner-note asymmetry, rock's poster-grade contrast, folk's intimate warmth) changes underneath it.
Maintenance sized to how often you actually tour
A weekend-warrior act playing a handful of regional shows a year has a very different update cadence than a band on a six-month tour cycle — and our maintenance tiers reflect that directly. The entry tier (12 changes/year) fits an occasional touring schedule; the Touring tier (120 changes/year, roughly 10/month) is built for an act adding and dropping dates weekly, updating a mailing-list hook, and swapping a hero image around each release. Both are opt-in — a $249/$499 build works standalone with zero ongoing cost if you don't need it.
A mailing list that converts, not a generic subscribe box
Every touring build ships with an email-capture field tuned to the genre convention that actually converts — a concrete hook ("tour presale 24 hours before public sale") rather than generic "join our newsletter" copy, placed once above the footer with no interrupting popups. This is the single highest-leverage piece of owned-audience infrastructure a touring act can have, and it's standard, not an upsell.
One site, deployed to your own hosting
The site deploys to your own free Cloudflare account — you own the code, the domain, and the hosting outright, with no monthly platform fee from us. That matters specifically for touring acts: your site's uptime and load speed during a ticket on-sale isn't dependent on a third-party platform's pricing tier or bandwidth caps.