How Lula Lake Sound Studio got control of its own website

The studio owner needed to update his website. Swap a photo. Add new gear to the gear list. Change a service description. Tasks that should take five minutes.

Instead, every change had to become an email. Explain the edit, wait for a developer, review the update, and hope nothing else moved in the process. For bigger updates, like a new About page or a full section rebuild, the wait and the back-and-forth got longer.

For a studio owner booking sessions, managing engineers, and running the creative side of the business, that loop was dead weight.

Lula Lake Sound came to Inference Partners with exactly that problem. The website was stuck. Good-looking and well-built, but out of their hands. They could not touch it without a developer in the room.

So we built a replacement.

The problem was not the website

The website was fine. The dependency was the problem.

When content lives in a codebase that only a developer can touch, the business has outsourced its own voice. Every update has latency. Every change costs time, even when the change itself is small.

For a studio that needs to reflect what is happening now, the delay matters. New gear, rate updates, engineer bios, seasonal availability, and page copy all need to stay current.

They were not asking for a redesign. They were asking for control.

That changed the shape of the build. The goal was not "make a better website." The goal was to make the website something the studio could run.

What we built

We built a custom CMS: a lightweight admin panel behind the site that lets the studio manage the pieces of content they update most often without touching code.

Homepage copy. Staff bios. Gear lists. Service descriptions. New pages. The team can update them, save them, and publish them without sending the work back through a developer.

The admin interface is narrow on purpose. It is built around what Lula Lake Sound actually needs, not around every feature a generic CMS might offer.

The important choices were simple:

• The interface had to feel obvious. Every field uses plain labels, and every common action has one path.
• The CMS had to protect the site structure. The studio can update content without accidentally breaking the layout.
• The system had to live with the site. No extra third-party publishing tool and no separate subscription to manage.

What changed after launch

The first useful proof was small: the studio updated the site themselves.

A new photo and a gear-list update were done in the same afternoon. No email thread. No waiting. No handoff. They logged in, made the changes, and moved on.

That is what a good CMS does. It disappears. The owner stops thinking about the tool and starts thinking about the content.

For a music studio, that has a real effect. Studio pages stay current. Rates reflect what is actually being charged. New engineers can get their bios published when they start, not weeks later.

Why this model works

Lula Lake Sound is not a tech company. They should not need to think about website infrastructure to keep their own site accurate.

The best version of this client relationship is simple: we build the system, hand it over, and get out of the way. The client can run the day-to-day content without us.

Most small creative businesses do not need a giant content platform. They need the right-sized system for the work they actually do.

For Lula Lake Sound, that meant a custom CMS the creative team could run themselves.

The takeaway

If your own website feels out of reach, the issue may not be design or engineering quality. It may be dependency.

The right system is not always the most powerful one. It is the one your team can actually use.