Post Production Facility Software: Why the Suite Is Full and the Job Still Loses Money

Why a busy facility can be unprofitable and not know it for a quarter

A managing director looks at the schedule board on a Tuesday. Every grading suite is booked, the two online suites are booked, the audio room is booked, three colorists are on jobs and one is on a client attended session that was meant to end at six and is still running at nine. Utilisation looks superb. Then the quarter closes and the margin is worse than last year, and nobody can say precisely why.

The reasons are always the same handful. Attended sessions ran over and the overage was never captured because the client was in the room. Change orders were agreed verbally by a producer who then went on another job. A grade was redone because a note arrived after the deliverable was made, and the redo was absorbed. Storage for a finished job stayed on the fast tier for five months. And the rate card is the 2023 one because updating it means touching four hundred templates.

Post facilities are capital heavy businesses with perishable inventory. An empty suite hour is gone. But full is not the same as profitable, and the gap between the two lives in exactly the transactions that are hardest to capture: the extra hour, the extra version, the extra deliverable, the storage nobody billed. That is the software problem in this category. It is not scheduling. Scheduling is a solved problem. It is connecting the schedule to the money in something closer to real time than the invoice run.

Problem 1: the schedule and the job cost live in different places

Almost every facility books resources in one system and costs jobs in another, usually an accounting package. The link is a person who exports bookings and reconciles them against timesheets and purchase orders at billing time, weeks after the work. By then the details are gone. Whether the session on the 14th overran by ninety minutes because the client changed brief or because a render failed determines whether it is billable, and nobody remembers.

Xytech MediaPulse is a serious system built for exactly this and does connect scheduling to billing properly. Farmerswife schedules cleanly and lightly. Autodesk Flow Production Tracking is strong on creative review and shot level work but was not designed as a facility financial system. The friction with the heavier products is fit: they assume a facility shape, and if your rate structures, session conventions or multi site transfers do not match, you configure around it until the configuration is its own maintenance burden.

What a custom build does: make the booking and the cost the same object. A booking has a resource, a rate, a job, a planned duration and an actual duration, and it accrues cost and revenue as it happens. Then the job cost view is live rather than retrospective. A producer can see on Wednesday that a job is at 78 percent of its quoted value with 40 percent of the work outstanding, which is a conversation you can still have. On the invoice run it is a post mortem.

Problem 2: overage and change orders are captured socially, which means not at all

The single largest recoverable leak in most facilities is work that was done and never billed. A client attended session books four hours and runs six. A colourist does three extra passes because the agency changed its mind. A deliverable list grows by two versions during the job. In a healthy facility every one of those is a change order. In a real facility, they are a conversation, and the person who had the conversation is not the person who raises the invoice.

Booking systems record what was scheduled, not what happened. Some allow an actual duration to be entered. Almost none make raising a change order faster than not raising one, which is the only thing that matters behaviourally.

What a custom build does: capture at the point of work with almost no friction. The suite has a simple check in and check out, so actual time is recorded without anyone filling a form. When actual exceeds booked beyond a tolerance you set, the system drafts a variation with the job, resource, time and a reason prompt, and puts it in the producer's queue that evening rather than at month end. A client portal showing agreed scope, approved variations and current spend removes the awkwardness that stops people raising overage at all. The point is not aggression. A variation raised the same day is a normal conversation, and one raised six weeks later is a dispute.

Problem 3: media logistics is a real cost centre treated as a free resource

Ingest, transcode, transfer, near line storage, archive, restore, delivery. Each is machine time, storage cost and often a person. Almost no facility attributes those costs to jobs. Storage in particular behaves like a utility that nobody switches off: a job wraps, the media stays on fast storage because it might come back, and it sits there for a year.

Facility systems track jobs and bookings. Storage lives in the infrastructure team's world with its own reporting that never joins to the job. High speed transfer services move files without knowing what the job charged for delivery.

What a custom build does: attribute storage and transfer to the job as accruing cost, with a lifecycle policy tied to job state. When a job is signed off the system proposes a tiering action, prompts for contractual retention, then executes on approval. Restores from archive become chargeable events rather than favours. The report you want is which clients cost the most in storage relative to what they bill, and it is rarely the client anyone guesses. In our experience this is one of the faster paybacks in a facility build, because storage cost is continuous and invisible.

Problem 4: multi site facilities run as several businesses pretending to be one

A group with sites in different cities typically has a schedule per site, a rate card per site, and a client relationship that spans both. Work moves between sites for capacity or for talent. Media has to follow. Cross charging between sites is either ignored, which distorts site profitability, or done through a spreadsheet nobody trusts.

Most facility systems were designed around a single site model and grew multi site support later, which shows in how resource search, availability and cross charging behave. It also shows in the practical detail that time zones and public holidays differ, and a scheduler in one city booking a colourist in another gets it wrong periodically.

What a custom build does: model site as a dimension on everything rather than as separate installations. One client, one job, resources drawn from any site with correct local calendars and rates, media logistics that knows a transfer between sites is a cost, and internal cross charge generated automatically so each site's profit and loss reflects the work it actually did. The consolidated utilisation view is what a group managing director actually needs, and it is precisely what a per site system cannot give without manual assembly.

Problem 5: nobody knows a job's margin until it is too late to change anything

Quotes come from experience. Actual costs land weeks later. The feedback loop is a person's memory and a sense that certain clients are difficult, so the same underpriced work gets quoted again next quarter.

Accounting packages give job profitability after the fact, aggregated enough to hide the cause. Was the loss labour overrun, a rate concession, unbilled overage, or storage carried for months. Without the transaction detail joined to the job you get the number without the diagnosis.

What a custom build does: cost every element at the level it is incurred. Labour at station and grade rates including overtime rules, suite time at actual, freelancers at their agreed rate, media logistics at accrued cost, third party purchases against the job. Then margin reports by client, by job type, by suite and by producer become available while the work is running. The insight most facilities get in the first quarter is not subtle: a category of work they assumed was profitable is being carried by another. Quoting improves within one cycle because estimates are finally informed by comparable actuals rather than instinct.

What this costs and how long it takes

In our delivery experience a first release covering resource and staff scheduling with proper calendars, rate cards, job and quote structure, low friction time capture, change orders and live job costing runs $65,000 to $130,000 and ships in 12 to 16 weeks. A full facility platform adding media logistics with storage lifecycle and cost attribution, client portal with review and approvals, deliverables and quality control tracking, multi site consolidation with cross charging, and finance system integration runs $160,000 to $380,000 phased across 6 to 12 months.

What drives price up in post specifically: the number of sites and whether they cross charge. Storage and transfer integration, which is infrastructure work rather than screen work. Collective agreement rules if your staff are covered, since overtime, turnaround and meal penalty calculations are fiddly and getting them wrong is worse than leaving them manual. Client portals, particularly with media review inside, which pulls in secure playback and watermarking. And creative tooling integration if you want version state automatically rather than by hand.

What keeps it down: one site first, scheduling and costing only, no client portal in phase one, and accepting that storage attribution comes later.

Build versus buy for post production facilities

Buy if you are a single site with a small number of suites and a stable client base. Farmerswife is well suited to that shape, it is affordable, and honestly the discipline of raising change orders matters more than the tool you raise them in. Buy Xytech MediaPulse if you are a large facility whose operating model is conventional and who wants a supported product with a vendor behind it, because it is a capable system and building an equivalent is a serious undertaking you should only start with reason.

Build when two or more of these are true. You operate multiple sites and cross charging is currently a spreadsheet. Your rate structures or session conventions do not fit the products and you are maintaining heavy configuration to compensate. You cannot see live job margin and you know unbilled overage is material. Storage cost is growing and nobody can attribute it to clients. Or you have already bought a facility system and your producers still run the real schedule in a parallel document, which is the clearest signal that the tool does not match how you work.

How to choose a developer for post production facility software

Ask them how they would capture an attended session that overran, from the point of view of the person in the room. If the answer is a form, they have not thought about it, because the person in the room will not fill in a form with a client sitting there. Low friction capture is the whole design problem.

Ask how they model a resource. Suites, people, equipment and storage all behave differently: a person has a calendar and a grade and overtime rules, a suite has a rate and a location, storage has a continuously accruing cost. A single resource table with a type column will fail on the third requirement.

Ask what they have integrated with in this world. Storage platforms, high speed transfer services, editorial and review tooling, and finance systems are four different problems. Ask for the specific product and what went wrong, because something always does.

Ask who owns the code and the infrastructure, and settle it before kickoff. At Digital Heroes the client owns the repository from the first commit. Your rate structures, your job history and your utilisation data are the analytical asset of the business, and you should never need anyone's permission to use them.