Most musicians who get told they need a website end up with the wrong thing. They get pointed at WordPress, Wix, Squarespace, or Bandzoogle. Within a week, they're paying a monthly subscription to host a site that's mostly empty, mostly slow, and built to do five things that never required a Content Management System in the first place.
This is a problem worth fixing. As we've noted in Why musicians still need a website in the AI era, a dedicated website is the only way to seed AI search engines with your true identity, and it's the only digital asset immune to algorithmic mood swings. (If you want to see exactly how AIs get it wrong when you don't seed them, read what your business looks like to ChatGPT right now.) You absolutely need a site. You just don't need a massive database to run it.
What a musician's site actually needs to do.
Strip it back. A working musician's site has to do exactly six things:
- Show people who you are and what you sound like.
- List upcoming shows with direct links to tickets.
- Link out to wherever your music lives (Spotify, Apple Music, Bandcamp).
- Capture email addresses for fans who want to hear about new releases.
- Give press, venues, and bookers a single page to grab assets and a bio.
- Sell merch, if you have merch to sell.
That's it. None of that requires a database. None of it requires a login system. None of it requires fragile plugins that update themselves at 3am and occasionally take the site offline.
What it requires is HTML.
The CMS trap.
The sales pitch for a CMS like WordPress is that you can update your own site without knowing how to code. In theory, this is great. In practice, this is what happens:
You build the site. You update it three times in the first month. You update it twice in the second month. By month four, you've forgotten the admin password. By month six, the theme has auto-updated, broken the layout, and you're paying someone fifty quid to fix it. By year two, the site is running an outdated version of PHP, the contact form has silently stopped working, and the calendar plugin has been abandoned by its developer.
Meanwhile, you've paid a hosting subscription every single month for the privilege.
The CMS sold you a problem it then charged you to solve.
What we build instead.
A static site. Hand-built HTML, served from a global CDN, hosted for roughly £0 a month, that loads in under a second on a tour bus 4G connection.
When you have a new show, you tell us — or you edit one line of a JSON file yourself — and the site rebuilds. New release, same thing. New press photo, same thing. The content lives in plain text files in a Git repository. There is nothing to hack, nothing to update, and nothing to break. It just sits there, reliably doing its six jobs, for years.
The press page has your bio in three lengths, your photos in three sizes, your stage plot, your input list, and your tech rider. A booker hits one URL and has everything they need. The shows page pulls from a list you control, with ticket links that go directly to wherever tickets are actually sold (Eventbrite, DICE, the venue). The mailing list signup posts straight to whatever email service you use.
Nothing is locked into a platform. If you ever want to move it, the entire site is just a folder of files. You own all of it.
The sound check version.
There's a useful comparison here. A good live engineer doesn't add gear just because gear is available — they add it when the song demands it, and only then. The signal chain stays as short as possible. Every piece of kit between the source and the speakers is another thing that can fail, another thing that adds noise, and another thing that costs money to maintain.
A website is exactly the same. Every layer between your content and the visitor's screen is another thing that can fail. The absolute shortest signal chain is HTML on a CDN. Everything past that, you add because the project genuinely needs it — not because a YouTube tutorial said you had to.
What this isn't.
This isn't a pitch for a stripped-down site that looks bad. The static sites we build look as good as anything on the web — often better, because there is nothing fighting the design. No cookie banner stacking, no chat widget hovering, no consent modal blocking the hero image. Just the work, presented beautifully, loading instantly.
It also isn't only for musicians who are just starting out. The bigger your audience gets, the more the site needs to handle traffic spikes: a Glastonbury announcement, a BBC Radio play, a viral TikTok clip. A static site on a CDN handles a hundred thousand visits the exact same way it handles ten. There's nothing to scale, and nothing to crash. The same site that costs nothing to host on a quiet Tuesday costs nothing to host on the day everything goes mad.
If you're a musician with a WordPress site that's slow, broken, or just costing you money every month for no reason — we'll rebuild it as static HTML. Same content, same design, none of the maintenance.