Introducing WiOS, The Operating System Behind our Studio With Media

A client once messaged me on a Tuesday afternoon: "Hey, small thing — did the note about the intro ever make it into the new cut?"

It hadn't.

The note existed. He'd sent it. Somebody on my team had read it, reacted to it with a thumbs up, and then it drowned — under forty other messages in a chat thread that also contained a meme, three file links, a scheduling discussion, and someone's birthday wishes. The editor never saw it. The cut went out without it. And the client, very politely, was now asking me why.

Here's what made it worse: the edit itself was good. Genuinely good. The pacing was right, the colour was right, the sound design had a moment in the middle I was actually proud of. None of that mattered in that conversation. What the client experienced was not "a beautiful video with one missed note." What he experienced was "they don't listen."

I've thought about that message a lot since. Because nothing about it was a talent failure. My editor was talented. My producer was on top of things, or thought she was. Everyone did their job. The system between them dropped the ball, and the system was invisible, so a person took the blame.

That's the honest starting point for what I want to tell you about today. We built a piece of software. It's called withmediaOS, and it runs the studio. But the story isn't really about software. It's about the slow, slightly embarrassing realisation that the thing limiting the quality of our work was no longer anyone's skill.

Cinematic output is art. Shipping it weekly is logistics.

People see the finished video and assume the hard part is the craft. The camera movement, the grade, the cut that lands exactly where the music turns. And that part is hard — I've spent years of my life on it, and I've hired somewhere near a hundred editors building With Media trying to find people who obsess over it the way I do.

✦In short

• A polite client question about a dropped note revealed the real ceiling was operations, not talent.
• Spreadsheets, chat threads and messy drives work — until they fail quietly, in front of a client.
• withmediaOS runs the studio so the caring lands where it counts and consistency survives busy weeks.

But craft is not what breaks first when a studio grows. Logistics is.

Think about what one video actually involves. A brief, which someone has to write and someone else has to actually read. Raw footage, which arrives in whatever state it arrives in and has to be ingested, organised, backed up. A script, which changes twice. An edit, which goes through drafts. Revisions, which come from the client in voice notes, emails, chat messages, and occasionally a phone call to me personally at 9 p.m. Approvals. Captions. Exports in three aspect ratios. Delivery. And then the quiet aftermath — did it go up, did it perform, what did we learn.

Now multiply that by every video, every client, every week. We've produced well over a thousand videos at this point. Somewhere in the middle of that number, the maths of the studio changed underneath me, and I didn't notice for a while.

The real ceiling on quality stops being talent. It becomes operations.

When you're small, you hold the whole studio in your head. I did. I knew every project's status because I was in every project. If a revision came in, it came to me, and I walked over — or messaged the editor directly — and it got done. The "system" was my memory plus my anxiety, and honestly, that combination is more reliable than people give it credit for.

It just doesn't scale. Not even a little. My memory did not get bigger as the client list did.

The stack every studio runs on, including us, for years

Here is what our operations actually looked like for a long time, and I'd bet money it looks familiar if you run any kind of content operation: a spreadsheet that was supposedly the source of truth, a dozen chat threads that were the actual source of truth, and a shared drive that nobody fully trusted.

The spreadsheet was always slightly out of date, because updating it was nobody's favourite job. The chat threads had everything — every decision, every note, every file — but in the way a landfill has everything. And the drive. The drive had folders named "Final", "Final_v2", "FINAL final", and my personal favourite, "USE THIS ONE". I wish I were exaggerating for the blog. I am not.

And here's the uncomfortable truth about that stack: it works. That's what makes it dangerous. It works on the good weeks. It works when the team is fresh and the client count is manageable and nobody's on leave. Spreadsheets plus chat plus a drive will carry a studio surprisingly far, which is exactly why almost every studio runs on them.

It works until it doesn't. And when it fails, it fails in the worst possible way — quietly, and in front of a client.

A revision gets missed, like my Tuesday message. A deadline slips not because the edit was slow but because the editor didn't know the deadline had moved. A client sends "hey, where are we on this?" — and if you run a studio, you know that message. It looks innocent. It is not innocent. Every "where are we on this?" is a small withdrawal from the trust account. The client is telling you, politely, that they've started tracking your work because they're not sure you are.

I used to get several of those a week. Each one took thirty seconds to answer and left a mark that lasted a lot longer.

The internal version was just as costly, only nobody billed us for it. My producer spent a chunk of every morning reconstructing reality — reading back through threads, cross-checking the spreadsheet, pinging editors to ask what they were actually working on versus what the sheet claimed. Think about that. A smart, capable person, spending her sharpest hours of the day being a human synchronisation service between tools that refused to talk to each other. That time never showed up as a line item anywhere. It just quietly came out of the same budget everything comes out of — attention.

A great edit is the visible ten percent

Somewhere in that period I started thinking about our work differently. The edit — the thing on the client's feed, the thing people compliment, the thing we put on our own portfolio — is the visible ten percent. It's the part everyone evaluates because it's the only part anyone can see.

The invisible ninety percent is everything that has to go right around it. A brief that's actually clear. Footage that's organised so the editor spends the first hour editing, not excavating. Revisions captured against the exact cut they refer to, so "tighten the intro" doesn't get applied to the wrong version. A client who knows where their video is without having to ask. The final file landing on time, in the right specs, in the right place.

Get the ninety percent wrong and the ten percent never gets its moment. I've watched it happen. A genuinely beautiful edit, delivered two days late after a confused back-and-forth, does not feel beautiful to the client. It feels like a headache with good colour grading.

A revision note is a small promise. Lose it, and you haven't lost a comment — you've broken a promise.

This reframing bothered me more than I expected, because it meant that most of what determined our clients' experience was stuff I had never designed. The edit, we designed obsessively. We'd recut a hook nine different ways. The ninety percent around it had just... accumulated. Nobody chose the spreadsheet. It was simply there one day, the way weeds are.

The client who left, and what he was actually paying for

I've told this story before, but it belongs here, because it's the emotional centre of why withmediaOS exists.

A client left us. His numbers were good — the videos were performing, the work was strong by any external measure. And he left anyway. It took me about a week of turning it over to understand why: somewhere along the way, his channel had become a row on a board for us. A thing to deliver. He wasn't paying us for edits. He was paying for someone to care about his channel more than he did, and he could feel that we'd stopped. Not dramatically. Just gradually, the way teams drift when the process is about moving cards from left to right.

The fix we made first was human, not technical: every client gets a call with me on Monday. Not a strategy call. Just — how was your week, what's going on with the channel, what's bugging you, are we good. It sounds small. It changed the studio.

But those Monday calls taught me a second thing, and this one took longer to admit. A lot of what surfaced on those calls shouldn't have needed a call to surface. "I sent a note last week and I'm not sure anyone saw it." "What's the status on the second video?" "Did you get the footage I uploaded?" I was spending relationship time — the most valuable half hour I have with a client — answering questions a decent system would have answered before they were asked.

The call should be for the real stuff. The channel, the ideas, the doubts, the thing they saw a competitor do that's bugging them. If the call is spent on logistics, the logistics have failed twice: once operationally, and once by eating the conversation that actually matters.

So the human fix demanded a systems fix. One doesn't replace the other. They need each other.

Why a video studio ended up building software

Fair question, and I asked it myself, repeatedly, usually late at night: why on earth is a cinematic content studio building software? We make films. We're the people who argue about whether a cut should be a few frames tighter. Building an operating system for the studio is about the least cinematic thing imaginable.

We tried the existing routes first, to be clear. Project management tools, agency templates, elaborate board setups. Some of them helped. But every general-purpose tool we tried had the same quiet problem: it wasn't shaped like our work. Video production has a specific anatomy — footage in, drafts out, revisions against specific cuts, approvals, delivery — and generic tools make you contort that anatomy into someone else's idea of a task. The team maintains the tool instead of the tool carrying the team. Within weeks, the real information migrates back into chat, and you're paying for a prettier spreadsheet.

At some point I stopped asking "which tool should we use?" and started asking a different question: if the invisible ninety percent determines the client's experience, why are we treating it as an afterthought while obsessing over the ten percent?

We would never ship an edit built on someone else's leftover timeline. But we were running the studio on the operational equivalent of one.

So we built our own. withmediaOS — the operating system that runs With Media. It lives at withmediaos.com, and I'll let that page show it off in full. But here's the shape of it, because it has grown a great deal since I first published this essay.

Three private rooms sit behind one login — one for clients, one for the team, one for me. Clients get a portal where they can see the live status of every deliverable, pull up their documents and invoices, and scroll the full archive of everything we've ever made them. When a cut is ready they open a link — no login, no app — and leave feedback pinned to the exact second: typed, spoken as a voice note, or recorded straight off their screen with their face in the corner while they draw on the frame. The transcript is there on demand too, auto-generated even in Hinglish or Tanglish, searchable, click any line to jump to it. The moment they approve, the footage unlocks and the editor gets pinged on Discord. A note literally cannot drown under a birthday wish anymore.

Behind that glass is the part clients never see. The team runs on boards, tables and calendars that sync both ways with Notion and ClickUp, with a trash that actually restores and a script editor built in. Invoices, payments and e-signatures live in the same place as the work instead of three apps away. And a row of creator tools rides alongside the pipeline — subtitles and transcripts across dozens of languages, script feedback, music search, a virality score, analytics, and WiWi, the little assistant that keeps the studio honest and now spins on the homepage as a 3D mascot you can drop on your desk in AR. None of it is glamorous. That is still, entirely, the point.

None of that sounds glamorous, I know. That's rather the point. The glamour is supposed to be in the videos.

Repeatability is a systems problem, not a talent problem

Here's the belief underneath all of this, and it took me years and a lot of hiring to arrive at it.

Almost anyone with taste and time can make one great video. I mean that. Give a talented editor a month, a good brief, and no other obligations, and you'll get something special. The industry is full of one great video.

What's rare — genuinely rare — is the hundredth great video. The one made in a normal week, alongside every other client's normal week, by a team having an ordinary Tuesday. Holding the bar there has almost nothing to do with talent and almost everything to do with whether the machinery around the talent protects it or erodes it.

Repeatability is a systems problem, not a talent problem.

I watched this play out across our longest client relationship. Dr. Shilpa Arora's channels went from around three thousand Instagram followers — most of them bots, if we're being honest — to a million, with over seven hundred thousand YouTube subscribers alongside. That growth didn't come from one viral miracle. It came from series, shipped consistently: the Morning Routine videos, What I Eat In A Day, the Ghee Series. Formats, repeated and refined, week after week, for years. Every one of those videos needed the ninety percent to work — footage in, notes captured, cuts approved, files delivered — hundreds of times in a row, without the wheels coming off.

Early on, I thought the way to protect quality at that volume was to simply care harder. Hire more obsessive people, push more intensity into the room. And obsessive people matter — finding them is basically the whole job, I've said that before and I stand by it. But I've also watched brilliant, obsessive editors produce mediocre work inside a broken system, because their energy went into chasing files and clarifying notes instead of into the cut. Talent doesn't fail loudly in a bad system. It just quietly delivers less than it could, and everyone wonders why.

The system doesn't make the work great. People make the work great. The system decides how much of their greatness survives contact with a busy week.

The objections I'd raise if I were reading this

Let me argue against myself for a minute, because a smart reader is already doing it.

First: "You run a studio and you're telling me systems matter — of course you are, you built one." Fair. I'm biased, openly. All I can offer is the order of events: the pain came first, for years, and the software came out of the pain. We didn't build withmediaOS to have something to write a blog post about. We built it because I was tired of apologising for things nobody did wrong.

Second, the one I feel most strongly about: "Doesn't systematising the work make it colder? Isn't this exactly the 'client becomes a kanban card' problem you said drove a client away?" This objection kept me up, honestly, because it's half right. A system used as a substitute for caring is exactly how you lose clients. If I ever start pointing at a dashboard instead of getting on the Monday call, we've lost the plot. But that's not what the system is for. The system exists so that the caring lands where it counts. It clears the logistics off the table so the human attention — the calls, the creative arguments, the "I watched your competitor's reel at 2 a.m. and here's what's bugging me" — has room to happen. Cold studios aren't cold because they have systems. They're cold because they have nothing else.

Third: "Couldn't you have just used an off-the-shelf tool properly, with more discipline?" Maybe. Some teams do, and if your setup genuinely isn't leaking — if nobody's sending you "where are we on this?" — then you don't have the problem this post is about, and you shouldn't fix what isn't broken. We tried that route with real effort and kept hitting the same wall: the tools weren't shaped like video production, so the truth kept escaping back into chat. At our volume, the contortion cost more than the build did. At a smaller volume, it might not. I'm not going to pretend our answer is everyone's answer.

And fourth, the quiet one: "Is this just a studio congratulating itself?" I hope not. The missed revision that opens this essay is real, and it was ours. The client who left was ours. withmediaOS is not a trophy. It's scar tissue, organised.

Practising what we preach

There's one more reason this matters to me, beyond the operations.

We tell every founder and coach we work with the same thing: consistency beats intensity. A few exceptional pieces a month, shipped reliably, compound in a way that a burst of thirty random uploads never will. Show up every week, at a standard, for years — that's the whole game. I've said versions of that sentence in more calls than I can count.

But you can't run that discipline on vibes. Consistency is easy to preach and brutal to practise, because practising it means being consistent on the boring weeks. The week two editors are sick. The week three clients all move their deadlines. The week I'm travelling and my memory — the original operating system — is on a plane. Intensity survives on adrenaline; consistency survives on infrastructure.

So withmediaOS is, in a very real sense, us eating our own cooking. It's the machinery that lets a studio built on "consistency beats intensity" actually be consistent, rather than just intense in a sustained panic. If we're going to stand across the table from a creator and tell them to build systems around their content, we'd better be running on one ourselves.

The quiet engine

I'll end where I started, with that Tuesday message. "Did the note about the intro ever make it into the new cut?"

What still gets me about that moment is how small it was. One note, one thread, one distracted afternoon. No villain anywhere. And yet that's exactly how trust erodes in this business — not through disasters, but through small promises quietly dropped by systems nobody designed.

The videos will always be the part people see, and I'm glad. I got into this because of the ten percent — the cut, the light, the moment the music turns. That love hasn't gone anywhere. But I've stopped being romantic about the other ninety percent. The invisible part isn't beneath the craft. It's what the craft stands on.

withmediaOS is the part of With Media nobody was ever supposed to see. We're showing it to you anyway, partly because I'm proud of it, and partly because I think every creator and studio owner eventually meets their own Tuesday message — the moment the work was fine and the system wasn't. If you've had yours, withmediaos.com is where the rest of this story lives.

The feed shows the art. This is the engine underneath it, finally with a name.