How a Management Layer Keeps Production Margin From Becoming a Conflict of Interest

A platform pays a management layer to tell it the truth about its production network. Which partner is right for this series. Whether this episode meets the bar. Whether a higher tier is worth the money or a lower one will do. The same management layer also earns a margin on the production work itself. Every commissioning team that reads a proposal like that asks the same question, sometimes out loud and sometimes only in the room after the call. Whose interest is the advice serving?

It is the right question. Any structure where an adviser benefits from the outcome it recommends carries a tension, and pretending otherwise is the fastest way to lose a client. The answer is not to remove the margin. It is to design the structure so the margin cannot quietly steer the decisions the platform relies on.

This piece sets out how that design would work inside AXIS Management, the external production management position Axis AI Studios has developed for vertical drama platforms. The model is built on three revenue mechanisms: a set fee, a management percentage and a production margin. Each one pays for something different. Keeping them separate, visible and tied to the right behaviour is what keeps the advice clean.

1. Where the Conflict Actually Comes From

A conflict of interest exists when the person giving advice stands to gain from one answer over another, independent of whether that answer is right for the client. The concept is old and well understood across law, finance and procurement, and the broad shape of the problem is set out clearly in the general literature on conflict of interest. Production management is not special. The same tensions apply.

In a vertical drama context, the tension shows up in four specific places. Tier recommendations, where a higher quality tier carries a larger production value and therefore a larger margin. Partner selection, where some partners may leave more margin than others. Scope advice, where more episodes, more versions or more retakes all increase the production base. And quality acceptance, where rejecting an episode can trigger paid rework.

None of these is a reason to avoid margin altogether. A management layer that earns nothing from production has its own distortions, including weak incentives to keep production running smoothly and little reason to invest in the network. The goal is narrower. Each of the four pressure points needs a rule that holds regardless of how the margin moves.

The rest of this piece walks through those rules.

2. Separating What Each Revenue Mechanism Pays For

The first defence is structural. If a platform cannot see which part of the fee pays for which work, it cannot judge whether the advice is independent. Clarity about the three mechanisms is where trust starts.

The set fee

The set fee pays for the management layer to exist for the platform. Holding the operating record of each series. Maintaining the quality baseline. Running the reporting rhythm. Being available when something goes wrong. It does not move with production volume or tier choice. Because it is fixed, it carries no incentive to push the platform in any direction. The detail of what a fixed fee should and should not include is covered in what a set fee covers in an external production management agreement.

The management percentage

The management percentage pays for active oversight across the slate. It scales with the amount of production being managed, because more series and more episodes mean more reviewing, more coordination and more escalation work. It is the mechanism most closely tied to the effort the management layer actually spends.

The production margin

The production margin sits inside the production network work. It is the commercial reason a management layer can invest in partner development, reference tooling and quality systems that individual partners would not build on their own.

Laid out this way, the platform can see that two of the three mechanisms carry no direct reward for inflating production decisions. Only the margin does. That makes the margin the single place where safeguards need to concentrate.

3. Rule One: Tier Recommendations Are Made Against a Published Framework

The quality and price tier framework is the main tool for keeping tier advice honest. Each tier is defined by what it delivers on screen, what it typically costs, and what kind of series it suits. The definitions are shared with the platform before any recommendation is made.

When the management layer recommends a tier, it would do so in writing, with reasons tied to the framework. A romance series built on dialogue scenes and a small cast has different needs from a fantasy series with heavy environments and many characters. If the recommendation is higher than the platform expected, the reasons should be specific enough that the platform could reach the same conclusion independently.

Equally important is the downward recommendation. A management layer that never suggests a lower tier is a management layer whose advice should be questioned. Part of the job is telling a platform when it is about to overspend on a series that does not need it. A series aimed at a test market, or a concept with an unproven premise, may be better served at a lower tier with a clear path to upgrade if it performs.

The platform retains the decision. The management layer provides the reasoning. Because the framework is shared, the reasoning can be checked. The broader logic of how this pricing structure is built is set out in how AXIS Management prices its work.

4. Rule Two: Partner Selection Is Driven by Fit, Not Margin

The second pressure point is partner choice. In any production network, partners will differ in cost, capability and the margin they leave. The temptation, if left unmanaged, is to steer work toward whichever partner is most profitable for the management layer.

The safeguard is to make the selection criteria explicit and to apply the same margin logic regardless of partner. If the management layer earns a consistent margin structure across the network, there is no partner that is more attractive to the layer for commercial reasons alone. Selection then rests on the things that matter to the platform: genre fit, tooling, continuity discipline, capacity and track record against the quality baseline.

Disclosure of selection reasons

For each series, the management layer would explain to the platform why a given partner was selected and which alternatives were considered. This does not mean disclosing the commercial terms of every partner. It means showing the decision was made on criteria the platform would recognise and agree with.

Platform right to challenge

The platform should be able to question any selection and receive a substantive answer. If a platform has a prior relationship with a partner, or a concern about one, that input should shape the decision rather than be overruled by default.

When selection is transparent, the platform does not have to trust the management layer blindly. It can see the reasoning and judge it.

5. Rule Three: Scope Advice Is Tied to Platform Outcomes

The third pressure point is scope. More episodes, more alternative cuts, more localised versions, more retakes. Every one of these grows the production base and therefore the margin. Every one of them may or may not be right for the platform.

The safeguard is to tie scope advice to the outcomes the platform has stated, not to production volume. If the platform goal is to test a premise, the management layer should argue for the smallest scope that produces a meaningful test, even when a larger order would be more profitable. If the goal is to build a franchise, a larger initial scope may make sense, and the reasoning should say why.

The pilot to portfolio go to market is the clearest expression of this principle. A platform starts with a pilot: a limited commission that proves the production approach and the management relationship. Only when the pilot delivers does the conversation move to a portfolio. A management layer that recommended skipping the pilot to reach volume sooner would be putting its own margin ahead of the interests of the platform. The structure exists precisely so that scope grows only when evidence supports it.

Retakes deserve specific mention. Paid rework should be distinguished from correction of errors the partner made. If an episode fails the agreed quality baseline because of a production fault, the correction should not generate new margin. If the platform changes its creative direction after approval, rework is a legitimate new cost. The line between the two needs to be written down before production begins.

6. Rule Four: Quality Acceptance Runs Against a Fixed Baseline

The fourth pressure point is the one platforms often worry about most. A management layer that rejects episodes can generate rework. A management layer that accepts weak episodes can protect partner relationships or avoid delay. Either way, the acceptance decision could drift away from what the platform actually wants.

The safeguard is the quality baseline. Before production starts, the platform and the management layer agree reference episodes and acceptance criteria for the series, set against its tier. Every acceptance decision is then made against that baseline, and the reasoning is recorded. Rejections cite the specific criterion missed. Acceptances confirm the criteria met.

This record does two jobs. It makes the acceptance decision checkable, so the platform can see whether rejections are justified. And it makes patterns visible over time. If one partner accumulates rejections against the same criterion, that is a production issue to address. If rejections cluster in ways that only ever generate paid rework, that is a signal the platform is entitled to question.

A fixed baseline also protects the partner. Production teams are entitled to know the bar in advance and to be judged against it consistently. Fair treatment of the network is not only ethical. It is what keeps good partners willing to work through the layer.

7. Making the Whole Structure Visible

The four rules only work if the platform can see them operating. That means reporting that goes beyond production status.

A management layer operating within this design would report, at a regular rhythm, on tier decisions made and their reasoning, partner selections and alternatives considered, scope changes and what triggered them, and acceptance outcomes against the baseline. Where any of these decisions increased production value, the report would say so plainly.

The property management analogy is useful here. A good property manager earns from the maintenance work it coordinates, and owners accept that because the manager shows its decisions: why this contractor, why this repair now, why this cost. Owners leave managers who hide those decisions, not managers who earn from the work. The same principle applies to production management. The margin is not the problem. Opacity is.

How the management percentage behaves as a slate grows, and what the platform receives for it, is covered in more detail in what a management percentage buys across a commissioning slate.

Axis AI Studios Perspective

Axis AI Studios presents AXIS Management as a working strategy position, not as a finished operating service with a track record to point to. That makes the design questions more important, not less. A platform weighing an external management layer has to evaluate the structure itself, because there is no long history to evaluate instead.

The structure is deliberate. Three revenue mechanisms, each paying for something distinct. A set fee for holding the record and running the relationship. A management percentage for active oversight that scales with the slate. A production margin that funds the network and its tooling. Around the margin, four rules: tier advice tied to a shared framework, partner selection on fit, scope tied to platform outcomes through a pilot to portfolio path, and quality acceptance against a fixed baseline.

The intent is simple. A platform should be able to read every recommendation and see that it would make sense even if the management layer earned nothing from it. Where that is not the case, the platform should be able to see that too.

Axis AI Studios also produces vertical drama directly, which is where most of these rules come from. The pressure points described here are the ones that show up in real commissioning conversations.

For platforms that want to test this structure against their own slate, the conversation starts at business@axisaistudios.com.

FAQ

Why should a management layer earn a production margin at all?

Because the margin funds things the platform benefits from but would not pay for separately: partner development, shared reference tooling, quality systems and the capacity to move work across the network when something goes wrong. A layer with no stake in production also has weak reasons to keep production healthy. The goal is not to remove the margin but to stop it steering advice.

How can a platform tell whether a tier recommendation is honest?

By checking it against the published quality and price tier framework. A sound recommendation names the specific series characteristics that call for the tier, and the platform should be able to reach the same view independently. A management layer that only ever recommends upward, never downward, is a signal worth questioning.

Does correcting a rejected episode create extra cost for the platform?

Not when the episode failed the agreed baseline because of a production fault. Correction of a partner error should sit within the existing commercial terms. New cost only arises when the platform changes direction after an episode has been approved, and that distinction should be written down before production starts.

Further Reading

For commissioning teams who want to understand the full commercial structure before evaluating any single part of it, the overview of how AXIS Management prices its work covers how the three revenue mechanisms fit together.

For finance and procurement leads checking exactly what a fixed fee should include, the breakdown of what a set fee covers in an external production management agreement covers the boundaries of that fee.

For platforms planning several series and wondering how oversight cost behaves at volume, the explainer on what a management percentage buys across a commissioning slate covers what the percentage pays for as a slate grows.