WRITING · 20 JAN 2026 · 2 MIN READ

I spent 40 hours doing work I don't charge for

A strategy client, a video I could see in my head, and 40 hours in Premiere.

Rishwajeet Singh
Rishwajeet Singh Founder, Machine House Media
Originally on LinkedIn →

I recently spent 40 hours on work that wasn't worth my hourly rate. It made no sense, but it felt incredible.

A client had hired me for content strategy. I ended up directing the shoot and editing the final cut myself. The video got 500K views.

I don't direct. Haven't edited in three years. I charge a premium for thinking, not timeline work — the whole model is scale the thinking, delegate the doing.

The truth is that most video projects die at "close enough." The production pipeline just demands it. Timelines, budgets, feedback rounds, stakeholder alignment — everything pushes toward acceptable. You learn to live with it. Tell yourself "this works" and move on.

But I knew what this video needed to look like. Not the abstract version one might write in a strategy doc — "energetic, modern, premium." The actual version. I could see the specific pacing, where cuts would land, how long a shot should hold before it tips into indulgent — in my head.

The client had a team — great people, but no process to translate what I was seeing into frames. That gap between my head and their execution would have landed us at "close enough" if we were to follow the deadline.

So I directed. Then edited. 40 hours in Premiere for a strategy client.

When I finished I just sat there watching it back. Every frame exactly what I saw in my head. I forgot what that felt like — being actually proud of something I made. If you know me, you've heard me talk about this a million times now haha.

Once it existed, I could teach from it. Point at a specific frame and say "this is what I mean by letting a shot breathe." Build process from something real instead of a brief nobody can interpret.

It is hard and it takes time, but you can't scale taste by explaining it. You have to make the thing first.

The unscalable work is how you eventually scale (thanks PG!)