Table of Contents
The studio owner needed to update his website. A simple thing. Swap out a photo, add new gear to the gear list, update a service description. One of those tasks that should take five minutes.
Instead, he had to send an email, explain what he wanted, wait for a developer to get back to him, review the change, and hope nothing else broke in the process. Every single time. For bigger changes – a new About Us page, a full section rebuild – the wait and the back-and-forth got longer. For a studio owner who books sessions, manages engineers, and runs the creative side of his business, that loop was dead weight.
I run Inference Partners, a small technical agency. The team at Lula Lake Sound came to us with exactly that problem. The website was stuck. Good-looking, well-built, but completely out of their hands. They couldn't touch it without a developer in the room.
So I built him a replacement.
The Actual Problem Wasn't the Website
Most agencies miss this: the website was fine. The dependency was the problem.
When your content lives in a codebase that only a developer can touch, you've essentially outsourced your own voice. Every update has latency. Every change has a cost – sometimes money, always time. For a studio that needs to reflect what's happening right now – new gear, rate updates, engineer bios, seasonal availability – that's a slow bleed.
They weren't looking for a redesign. They were looking for control.
That framing changed how I approached the build. The goal wasn't "build a better website." The goal was: make the website something they could own.
What I Built
The solution was a custom CMS – a lightweight admin panel sitting behind the site that lets the studio manage every piece of content without touching a line of code.
Homepage copy? They update it. Staff bios? They manage them. New gear added to the gear list? Done in seconds. New pages – like a full About Us section – built and published without a developer in the room. The developer is out of the loop entirely, which is exactly how it should be.
I used Cursor to move fast on this. The build went from scope to deployed in a tight window – the kind of turnaround that only happens when your tooling isn't fighting you. The admin interface is clean, opinionated, and built specifically for what Lula Lake Sound actually needs. Not a generic CMS retrofitted to their content. A system built around their workflow.
A few things I was deliberate about:
The interface had to feel obvious. Sound engineers aren't product managers. If the CMS required training, it was already failing. Every field is labeled plainly. Every action has one path. You open it, you see your content, you change what you want, you save. Done.
Nothing breaks. One reason studio owners avoid touching their own sites is fear. They've been burned before – edited something, the layout fell apart, now it's a bigger mess than before. The CMS constrains what can be changed and how, so the site stays structurally intact no matter what's updated.
It lives at his domain. No third-party login. No subscription to another tool. It's part of the site, owned by the client, which is where it belongs.
What Changed After Launch
The first time the studio updated the site themselves – without emailing anyone, without waiting, without a back-and-forth – that was the moment the project made sense.
A new photo and a gear list update, done in the same afternoon. Two things that previously would have involved me or someone on my team. Instead: they logged in, made the changes, closed the tab.
That's what a good CMS does. It disappears. You stop thinking about the tool and start thinking about your content.
For a music studio, the ripple effect of that is real. Studio pages stay current. Rates reflect what's actually being charged. New engineers get their bio published the week they start, not six weeks later when someone gets around to it.
Why This Model Works for Creative Businesses
Lula Lake Sound isn't a tech company. They shouldn't need to think about their website infrastructure at all. The best client relationship I can have is one where I build the system, hand it over, and get out of the way – and the client is fully capable of running it without me.
Most agencies build dependency. I think that's the wrong model, especially for small creative businesses. A studio owner's time is spent on music, not on managing a developer relationship. The right build gets them back to what they're good at.
Inference Partners is built around this idea: that AI-assisted development can close the gap between what a small business needs and what they can actually afford to maintain. A custom CMS used to be a big agency project with a big agency price tag. It isn't anymore.
The Takeaway
If you're running a creative business and your own website feels out of reach – if updating it requires a conversation, a ticket, a wait – that's not a technical problem. It's a dependency problem. And it's solvable.
The right system isn't the most powerful one. It's the one you can actually use. Build for that, and everything else follows.
If you want to see what this looks like in practice, Lula Lake Sound's site is live at lulalakesound.com. And if you're thinking about a similar build for your own business, Inference Partners is where to start.