Working example · Production Desk
Say what you will own, before you say what it costs.
Production Desk is a supplier-side record of a show: its parts, who owns each one, what each depends on, and what is still unresolved. A quote comes out of that record rather than being assembled from memory the night before it is due, and what you learned scoping the job is still there when the next one looks like it.
On a live stream to cinemas we ran two hundred metres of tactical fibre outside for a clean signal. Nobody owned the route it took through the building, and someone not in the loop closed a door on it. The crew knew not to close that door. The people sharing the space did not.
What a quote actually costs
Four things are true of every complex quote, and only the first one is ever discussed.
01
A number is a promise about signal path, crew, setup time, power, access and a dozen other things. Getting it wrong costs twice: a budget you are now held to, and a failure on the day if the thing you did not model turns out to matter.
02
The work of getting to that number is the same work a technical director would be paid for, done by the person also running operations and marketing, usually after hours, usually against a deadline set by somebody else.
03
The plan goes upward. The producer looks capable in front of their executive producer, and owes nothing to whoever assembled it. This is not sharp practice, it is how the market works, and closing jobs sometimes requires it.
04
When the job goes elsewhere, the work goes with it. The next show that looks like it starts from nothing, nobody else can pick it up, and there is no record of which criteria produced which conclusion.
A lost pitch should still leave an asset.
Where the gaps actually are
Two kinds of gap, and neither of them belongs to a department.
01
Two hundred metres of tactical fibre on a route through a building the venue controlled, and a door closed by somebody who was never told. A caravan that was the set, with the contestants, every camera and all the audio built into it and tied back to a separate video village, moved by the people entitled to move it, and the build came out each time.
The crew knew. The building did not. The build assumed. Nobody specified.
02
Setup time, a test window, an unhurried load: all visible in the quote, and all looking like padding next to concrete deliverables. A build that is only technically possible in the window means a show that must run perfectly first time with no private test stream. A load compressed by another job returning late, with the crew gone home, means finding what matters among dozens of boxes at the worst moment.
Professional productions pay for setup margin and control of the space things depend on. That is a fair part of the price, and if it is cut, it should be cut knowingly.
The other direction is worth stating. An orchestral session is booked long in advance and cannot move. On a session in Budapest, flights were grounded on the morning I was due to travel. The schedule had me arriving several days early, so an overland journey was still possible: the session ran, and the premiere dates held. The margin was the only reason there was a decision to make rather than a cancellation.
A quote priced department by department can be complete and still miss both, because a department is a list of what somebody supplies, and a show fails on the conditions nobody guaranteed and the time nobody was willing to buy.
Both of these shows went out fine. That is the point rather than a qualification. The gap was absorbed by people who noticed in time, and the cost of absorbing it appeared nowhere: not in the budget, not in the debrief, not in the quote for the next one. What was at stake was never really the equipment. It was who carried the risk, and who would have had to explain it.
A quote allocates that risk whether anyone means it to or not. Silence allocates it to you.
This is not an argument that production software is bad. It is an argument about which part of the work has no home, so the choice to leave it there is at least deliberate.
Where the scoping actually happens, and where it stays. The questions asked, the assumptions made and the reasons behind them are in a thread nobody will find again, including you.
Fast, reusable and genuinely good at arithmetic. They price things somebody supplies, so a condition nobody has guaranteed has no line to sit on, and neither does the margin that protects it.
Strong on inventory, availability, crew and subhires, and they begin at the confirmed order. The expensive thinking happened weeks earlier, when there was no order to attach it to.
Tasks with names against them, which is exactly right once the work is known. They model the work, not the conditions the work quietly assumes, and they also start after the job is won.
None of these needs replacing, and the gap is not in any of them. It is in the weeks before there is an order, where the show gets understood, the price gets committed and nothing gets written down. The test is simple enough. When that producer calls back next spring with a show that looks a lot like this one, what do you have?
What changes
01
Every part of a show depends on something staying as it is: a route, a position, a window, a room. That condition usually belongs to someone other than the person whose work rests on it. Recording them as two separate things is the whole fix, and it is already how the data model works rather than a claim invented for a web page.
02
Setup time stops being padding when it is recorded as the thing standing between a first-time-perfect show and a tested one. It can still be cut. It just cannot be cut silently by someone who never saw what it was for.
03
Once the questions and the criteria behind them are written down, the scoping can be delegated and still reach the same conclusions. That is the difference between knowledge in one person’s head and capacity a business actually has.
04
The next show that looks like this one starts from the last one. Someone picking it up later sees the summary and can dig into what produced it. The unpaid work stops being unpaid and starts being inventory.
There is a producer-facing front door to this as well, Sunset Scout, which asks a producer the questions a supplier would ask and produces a structured brief before anyone’s time is spent on a call. It is a separate thing with a separate boundary: it defines the ask, it never quotes, and the supplier owns delivery. Its live scoping tools are open to try.
The demo here is the supplier-side workspace on fictional data, and it is still a work in progress. It shows the shape of the record rather than a finished product.
Experience behind it
Production work from 2009 onward: videography across four Academy Awards ceremonies, then a break, then back from 2015 into technical direction and live streaming, through to a 2025 cinema live stream across the United States. Sometimes the scoping was mine. Often it was somebody else’s, and the job was to make it work in the time and the circumstances presented, with no standing to manage the client’s expectations beforehand or to protect the work and the time that deserved it. Either way, the explaining was mine when a condition nobody had written down turned out to matter.
Both stories on this page come from that work, and neither is unusual. What is unusual is the number of chairs: above-the-line composer credits on multiple projects across the same period, where the discipline was delivering a score and parts to an orchestra on a date fixed months earlier; the supplier delivering inside somebody else’s creative vision; and the person turning that vision into a number before anyone knew enough to give one.
A brief looks different from each of those seats, and the gaps this page is about live in the spaces between them.
Nobody in these stories did anything wrong. The venue controlled its own building. Production moved its own set. The budget holder cut the line that looked most like padding. Every one of those was a reasonable act, and the risk still landed on the people at the end of the chain, because nothing had been written down that said otherwise.
2009–2025
Both ends
Above the line
Small team
The demo
A supplier-side production workspace on fictional data. It is a work in progress and says so: it shows the shape of the record rather than a finished product.
Open the demo ↗What you can see in it
I would like to hear which part of your last quote you were least sure about, and what you would have had to explain if it had gone the other way. One conversation about one job, not a pitch, and no follow-up sequence.
If a better spreadsheet would fix it, I will say so. The point is knowing what you are taking responsibility for, not software for its own sake.