One Point of Contact, No Chain

In post-production, one point of contact means the same person you talk to is also the one editing the material — no project manager, coordinator and artist as separate stops in between. What sounds like an organizational detail at first turns out, in practice, to decide a project's speed and precision.


The Real Problem Is Rarely Quality

When a post-production project stalls, it's surprisingly rarely down to a lack of skill. It's the chain. The client talks to a project manager. The project manager passes the request to a coordinator. The coordinator briefs an artist the client never meets. Every piece of feedback travels the same path back. Something as simple as "the color's too cold" can easily take two or three days before the change even reaches the person doing the work.

That's not a failing specific to larger providers — it's the structural consequence of project management and execution being separate people. No one is doing anything wrong. But it costs time, and it costs precision, because every handoff introduces a small shift in understanding.


What Changes When One Person Is Both

With me, that chain doesn't exist. From the first inquiry through final sign-off, you talk to the same person — and that person edits the material too. If a color is off, I see it directly in the footage, not in a colleague's description. If a cut isn't working, I know immediately what fixes it, because I'm sitting in the timeline, not reading a status report.

For a single, clearly defined task, I bring in a senior when needed, if the scope and margin work for that specific case — transparently billed, never as a standing crew. That's the exception, not the model. Responsibility and the point of contact stay with me throughout. No second, invisible layer of coordination appears.


A Fixed Structure vs. Continuous Ownership

The difference comes down to one point. An agency or studio provides a fixed structure — multiple roles, multiple contacts, a project-management layer that exists whether or not the project actually needs it. That's sensible and necessary for very large, parallel productions. With me, the default runs the other way: one person handles the material and holds ownership from inquiry to sign-off without handing it off. Bringing someone else in is the exception for a single task, not a second pillar of the model.

The client isn't paying for structure they don't use, and doesn't lose time to communication paths that aren't necessary. For most mid-sized and smaller projects, that's the more efficient setup; for very large, many-stranded productions, an agency's fixed structure may be the better fit.


What This Means for a Smaller Project

For a city, a municipality or a small agency, this isn't a nice-to-have — it's often the deciding difference. A recap video for a town festival or a corporate film for a mid-sized company rarely has the budget for a multi-person project team — and doesn't need one. What it needs is someone who understands what the video is supposed to do, handles the material personally, and gives direct feedback on whether a change makes sense or not.



Where This Approach Reaches Its Limits

On very large projects with many parallel workstreams, some coordination structure becomes unavoidable — even for me, once several artists work simultaneously on different parts. The difference is that this structure forms when needed and dissolves afterward, rather than being permanently installed from day one. For most projects that come my way, it simply isn't necessary.