One person — which is why it looks like this.

I started in design — brand identity, layout, motion, 3D — before I wrote software. That’s still how I start a build: what someone needs to see when they open it, then the code that makes it true.

Now I build full-stack software end to end: the interface, the backend, the data and the automation behind it. The first studio build was for a video editing studio running its whole pipeline on spreadsheets, chat and memory. The same mess turned out to exist in almost every small studio, so Studio OS is that build, made repeatable.

You deal with me from the first call to handover. I show work early — something clickable by week one — and every week after that.

Feedback goes in one place and gets a reply within a working day. If a request would make the tool worse, I’ll say so and explain why.

I don’t take on more than two builds at once. I don’t bill by the hour.

I don’t build on anything exotic that ties you to me — it’s a standard stack you own outright. And if a spreadsheet and a bit of discipline would fix your problem, I’ll tell you that instead of selling you software.