StudioOps

From the founder

Introducing the Atlas

The document that defines what StudioOps believes about creativity, artists, AI, and craftsmanship.

Hey everyone,

I wanted to share something a little different this week.

For the past few months I've been spending a surprising amount of time writing… not code, but principles.

Internally we call it the Atlas.

It's basically the document that defines what StudioOps believes about creativity, artists, AI, craftsmanship, and the kind of company we want to build. Every major feature eventually has to answer to it.

That might sound like overkill, but honestly I think it's more important now than ever.

AI is making it easier for everyone to build software. It can generate features, write code, design interfaces, and move incredibly fast.

The hard part isn't building something.

The hard part is building something that knows what it should not become.

I've used enough creative software over the years to know what I don't want StudioOps to feel like. I don't want it to encourage artists to create more noise. I don't want it replacing judgment with automation. And I definitely don't want it nudging people toward whatever keeps them engaged instead of whatever helps them grow.

So before we build features, we spend a lot of time asking questions like:

  • Does this actually help the artist?
  • Does this strengthen their judgment or replace it?
  • Will this still feel right five years from now?

Sometimes those conversations end with us deleting weeks of work because we realize we were solving the wrong problem.

It hurts a little.

But I think that's what craftsmanship looks like.

The funny thing is, it's exactly what we ask artists to do. Cut the verse that isn't working. Rewrite the lyric. Throw away the idea that isn't honest enough. Keep chasing the version that feels true.

Why shouldn't we build software the same way?

Over the next few weeks I'd love to pull back the curtain a little and share some of the principles from the Atlas. They're internal documents, but I think they're worth talking about because they explain why StudioOps feels the way it does.

If you're trusting us with years of your creative work, you deserve to know what guides the people building the tools.

Talk soon,

Todd

Artist Beta

We're preparing to welcome our first group of StudioOps beta artists. We're looking for thoughtful musicians who want to help shape the product while it's still being forged. If that sounds like you, simply reply to this email or reach out to todd@studioops.ai.

Stay in the loop

Get occasional updates from StudioOps — no noise, unsubscribe anytime.

No noise. Unsubscribe anytime.

Introducing the Atlas — what guides StudioOps | StudioOps