Why I built Studio
A personal note from our founder: software is data, shaped and governed differently — and most of software development should be configuration, not coding.
The blog is written in the studio's voice. This post is different: a personal note from our founder, Rich Hill, on why Studio exists. The words are his.
Someone once said to me that “we’re in the business of selling electrons”. It was a throwaway line, but it stuck, because I instantly recognised what it meant. I see software as data. Email, video games, CRMs, project management and, of course, digital media: all of it is data. The difference is that each is shaped, governed and presented differently. Email is data, but I don’t want anyone else reading mine unless I forward it on. I do want my team reading tasks, especially the ones assigned to them. And if I’m playing a game, the other player needs to know exactly what I’m doing so they can respond.
The same shapes, over and over
Take a step back, though, and the similarities start to matter more than the differences. In software we call these recurring shapes design patterns, and they are the reason Studio exists. Why re-invent the wheel? Do we really need to build a new login system, or another file export, for the hundredth time? Wouldn’t our clients be better off with a platform that already knows these patterns?
Most of software development should be configuration, not coding. The valuable hours are the ones spent with a client, analysing their needs in detail — not repeating work we have done hundreds of times before.
What that buys you
The economic case makes itself: work that used to take months of hand-building becomes weeks of describing. But the benefit I care about most is quality. Studio was built with software development principles from the outset, and every application it produces is generated from one checked description of the business. Nothing reaches a client without passing the same proofs: that one customer’s records cannot be reached from another’s account, and that the code carries no known security flaws. What was built matches a specification we can print and hand over.
It sounds like a soundbite, but it is true: we genuinely can’t ship bad code. Not because we’re superhuman — because the platform refuses.
That, in the end, is the business we’re in. Not selling electrons. Selling the shapes they make.