The Production Company Software Stack

Operations Published Sep 6, 2026 6 min read

production company software stack event production software AV company software production management tools

Start free

In this article

Most stacks grow by accident

Nobody designs a production company software stack. It accumulates. A quote template because a quote was due, a scheduling tool because two shows collided, a chat workspace because email was too slow, a folder structure because someone needed a file at three in the morning.

Each addition was correct at the time. The problem is that the seams between them are invisible on any given day and expensive across a year.

What the stack has to cover

Job to be done	Typical tool	Can it be consolidated
Quoting and client approval	A document template plus email.	Yes, and it should be, because approval is where pricing gets locked.
Equipment catalog and availability	A spreadsheet or a rental system.	Yes. This is the record everything downstream prices from.
Show planning and run of show	A document, a shared drive, a whiteboard.	Yes, once it can hang off the approved job.
Crew availability and calls	Messaging apps and a spreadsheet.	Yes, and this is usually the biggest single time recovery.
Warehouse prep and movement	Printed lists.	Yes, provided the pull sheet comes from approved scope.
Invoicing and payment	Accounting software.	Partly. Raise and collect where the job lives; keep the ledger in accounting.
Bookkeeping and payroll	Accounting and payroll systems.	No. Keep these specialised.
Design and drawings	CAD and visualisation tools.	No. Attach the output to the show record instead.

The rule for what to consolidate

Consolidate anything where the same fact has to exist in two places. A gear item, a price, a call time, a client decision. Every duplicate of a fact is a future disagreement between two documents.

Keep separate anything that is genuinely a different discipline with its own professionals and its own compliance surface. Payroll is a different discipline. Bookkeeping is a different discipline. A rendering tool is a different discipline. Nobody wins by folding those into a production platform, and a vendor claiming to replace them is selling you a worse version of each.

What Flightcase is trying to be in that map

Flightcase covers the middle band: quoting and client approval, the equipment catalog and availability, the show record, crew availability and calls, warehouse prep and movement, and raising and collecting the invoice.

It does not try to be your accounting system, your payroll, or your drawing tool. It is explicit about that on the FAQ, and it is a deliberate boundary rather than a roadmap gap.

The argument for consolidating that middle band specifically is that every fact in it is shared. The gear on the quote is the gear on the pull sheet. The date on the show is the date the crew were called for. The price the client approved is the price on the invoice. Those are not integrations waiting to be built; they are the same fact, and keeping them in one record is the only way they cannot disagree.

A stack audit you can do in an hour

List every tool a job touches from first call to final payment.
For each one, write down what fact it is the source of truth for.
Circle every fact that appears twice.
For each circled fact, note who is responsible for keeping the copies in agreement.
That list of people is the cost of your current stack, and it is usually the same one or two names.

FAQ

Should we keep our accounting software?

Yes. Raise and collect where the job lives so the invoice inherits the approved pricing, and keep the ledger, reconciliation and reporting in your accounting system. Flightcase is built to sit alongside accounting rather than replace it.

Do we still need a group chat?

For company wide conversation, probably. For show specific coordination, moving it into the show record is what stops information about a job living somewhere the next person cannot find it. Most teams end up with far less traffic in the general chat rather than none.

How many tools is too many?

The count is the wrong measure. Count the facts that exist in more than one place instead. A stack of six tools that never duplicate a fact is healthier than a stack of three that each hold their own version of the gear list.

Try it against a job you already ran

The fastest way to judge this is to rebuild one recent show and count what you had to retype. Start free, or bring the job to a walkthrough and we will trace it with you.

Book a walkthrough

The software stack a production company actually needs