Nabil Khaled · September 18, 2025

Why I Put Every Team Under One Roof.

Why I Put Every Team Under One Roof.

For a while, the companies and specialists around me worked like neighbours who get on well. Friendly and talented, and forever passing work over the fence. Every handoff was a small border crossing. The brief picked up a new accent on the way through, and the person paying for it had to keep track of all the accents.

This year we launched iklipse, the new name for Digiredo, and put those companies and specialists under one roof. One business development engine. One quality control bar for everything that ships. That sounds administrative, and it shapes almost everything a client experiences.

Handoffs are where good work goes missing

When separate teams pass work to each other, each one optimises for its own part. Production wants a tight brief. Post-production wants clean files and a locked edit. Everyone is right, and the project still drifts, because nobody owns the whole thing from the first call to the final export.

Separate teams also quote separately. Each one prices its own slice, and the gaps between the slices turn into extra rounds and repeated briefings that somebody ends up paying for. Nobody plans that. The structure produces it on its own.

The client feels that drift first. They repeat context they have already given. They approve something, then discover the next team never saw the approval. Each of those moments is small. Together they make a capable group of people look disorganised, which is a bloody waste of capable people.

One engine brings the work in

A single business development engine means one front door. One person owns the relationship and the brief, and pulls in the specialists behind it. The client talks to someone who can see the whole engagement, including the parts they have not asked about yet. The specialists get a brief that has already been questioned once, which saves everyone a round of polite confusion.

It also stops us selling the org chart. Clients come for an outcome: an ad, a film, a set of product visuals, a campaign that runs. Which internal unit made which frame is of no interest to them. At iklipse we sell the outcome, and the structure underneath is our problem to manage.

One quality bar for everything that ships

The second decision matters more. Every team now works to the same quality control bar. Product accuracy, language, casting, composition and delivery formats are written down as checks, and they apply to a commercial, a social cut and a set of product visuals alike. A frame that would fail review in one team fails it everywhere.

That shared standard is what lets people direct every film while AI builds the shots, without the result feeling like a gamble. I trained my teams in AI, quality control and business systems because those skills only work together when everyone answers to the same standard. I wrote about how that checking works in why every AI team needs a quality department.

What clients notice

Most clients will never see the restructure, and that is the point. What they notice is one person answering for the whole job, and work that looks like it came from one place. Inside the team, the change shows up as fewer debates about whose problem something is. When a problem appears, it already has an owner. Arabic and English versions come out of the same process and get checked against the same bar.

If you run a group of small teams yourself, try this. Pick your last project and count how many times the brief changed hands. Then ask who could have answered for all of it. If the answer is nobody, you have neighbours, and you may need a roof. Ours is at iklipseworld.com if you want to see where we ended up.

Nabil Khaled is the founder of iklipse, an AI production agency for advertising, based in Cyprus. Read his story.