The fractional creative department

Your videographer and our editor spoke. You did not have to.

Three partnerships, and the one boundary that decides which messages reach you. Technical matters go to the specialists. Ownership questions come to you.

This case carries one interactive section: twelve partnership decisions to place, with the consequence of each placement stated.

Sound familiar

Four symptoms of the relay, and what runs instead

Every note goes through you

Technical questions go straight to the person who can answer them. Two direct fixes with a partner's videographer, in September 2025 and January 2026. The September one reached nobody on the partner's side.

You find out a shot is missing when the video is late

The gap is caught in the edit and closed with the person who shot it. A recipe bake in July 2026: reshoot requested and delivered in four days.

Handing over access means losing track of decisions

Anything that is yours to decide still comes to you. A finished video in June 2026 was held until the owner said yes in words, for a request we already agreed with.

The same fault keeps coming back

The fix goes into their process rather than into one file. A colour profile is now baked in at capture, from January 2026, and the problem stopped happening.

The machine that already exists

By the time a brand talks to us it usually has people. A videographer who knows the room. Someone who shoots the food. Somebody handling the posting calendar.

None of them work for us, and we did not choose them. What tends to happen next is that the owner becomes the relay. The editor notices something, tells the owner, the owner tells the videographer, and the answer comes back the same way. Every technical question makes two round trips through the one person whose attention is the scarcest thing in the business.

Nobody designs that. It just arrives.

Three fixes that never reached an owner's desk

A section that was not there. Editing a piano lesson in September 2025, Kubra found a short filming pause around the fifteen-minute mark. She wrote to the school's videographer directly. Six days later he returned a fixed file and an explanation: the camera had corrupted that section. Neither the school's founder nor its operations lead was on any of it.

A fix that outlasted the file. In January 2026, a codec and colour-profile problem on the same channel. Again straight to the videographer, and this time the result was not a repaired file: he changed his own capture workflow and started baking the colour space in at source. The problem stopped happening.

That is the difference between a supplier who is told about a problem and one who is talked to about it. The first gives you a corrected file. The second gives you a corrected process, and nobody spends that hour again.

Footage that stopped too early. In July 2026, cutting a bake for a recipe channel, we noticed the top-angle coverage ended right after the tin came out of the oven: no overhead of the finished loaf. The note went to the photographer the same morning:

"While editing the Chocolate Chip Zucchini Bread, we noticed the Top folder footage ends right after it comes out of the oven. If you have any additional shots from that angle, could you please send them over?"

She agreed a little over four hours later, filmed the extra coverage, and uploaded it four days after that. Four cuts followed: web, web without text, vertical, Reels.

The owner was not on a single message in that exchange, and did not have to chase any of it.

The line we do not cross

In June 2026 the same photographer asked us for an edited video, the Caprese Pasta Salad, to show at a job interview. She was careful about how she asked, and explicit that the editing and the recipe were not hers to take credit for.

We made that edit. We were, for what it is worth, entirely in favour of her showing it.

We did not send it.

She had copied the owner on her request, so nothing here was hidden and nothing needed surfacing. That is exactly why the delay is the point: we could see that the owner could see it, and we still did not act until she said so in words. Kubra wrote to her directly:

"Since the final video is also Foodess's property, we always like to get your quick thumbs-up before sharing any exported files externally. As BUBI, we are completely fine with this and would love to help her out with her interview process."

The answer came the same afternoon. The file went out the next morning with the owner copied in.

We sent the file thirty-one hours after being asked, for something we already agreed with. Agreeing with a request and having the standing to grant it are two different things.

Being handed the line, not taking it

At Urban Farmie the arrangement was not something we proposed. In February 2025 the videographer introduced himself in the partner's Slack, and the founder connected the two of us in the very next message and told us to take any questions straight to him.

We also hold tasks inside that partner's own production calendar, scheduling included. A department inside the building that happens to be on a different payroll.

Does it hold up over time

This is a working pattern rather than three good days. The Foodess partnership has run since September 2024, and every recipe now ships as four separate cuts. The piano channel has been on monthly cycles for more than three years. The two videographer fixes above are four months apart, and the second one is why there has not been a third since.

Ceren handles the edit side of most of this; Kubra runs the coordination. Two people, three partnerships, and the partners' own suppliers treated as colleagues rather than as someone else's problem.

What the line is actually for

Delegation tends to collapse in one of two directions: the owner stays in the middle of everything, or they hand it over and lose sight of decisions that are legitimately theirs. Who gets their footage, whose name goes on what.

The way out is a boundary in one specific place. Technical matters go to the specialists. Ownership questions come to the owner. A shot that stops early is technical. A file leaving the building is not.

The figures

Every figure on this page, sourced

The pattern over timeFoodess partnershiprunning since September 2024, every recipe shipping as four separate cutsown-documentBUBI delivery recordnot-required
The pattern over timePiano channelmonthly cycles for more than three yearsown-documentBUBI delivery recordnot-required
The pattern over timeUrban Farmie direct linehanded to us by the founder in February 2025own-documentBUBI correspondencenot-required
The pattern over timeThe two videographer fixesfour months apart, and the second is why there has not been a thirdown-documentBUBI correspondencenot-required
The three incidents, timedCorrupted section, Sept 2025reported direct, fixed file returned in six daysown-documentBUBI correspondencenot-required
The three incidents, timedMissing overhead coverage, Jul 2026agreed in about four hours, filmed and uploaded four days laterown-documentBUBI correspondencenot-required
The three incidents, timedFile release request, Jun 2026held thirty-one hours until the owner said yes in wordsown-documentBUBI correspondencenot-required
Who runs itPeople on these three partnershipstwo: one on the edit side, one on coordinationown-documentBUBI staffing recordnot-required
Next step

Start with a free audit

We look at what you have, tell you what we would change, and agree the expected result before anything begins.

Start a free audit