AV and Live Production Rental Software: Why Availability Looks Fine Until the Kit Is Already on the Road

Why availability lies, and why you find out on site

Friday 6am, prep bay two. The pull sheet for a corporate general session says four moving lights, one console, a comms package and 12 lengths of a specific cable. Three of the fixtures are on the shelf. The fourth is on a truck that left Wednesday for a show that was meant to return Thursday night and now returns Saturday, because load out slipped. The system said available, because the system was told the return date and nobody told the system the return date changed.

So the crew chief does what crew chiefs do. He calls a friend at another rental house, gets a sub rental at whatever the phone price is, sends a driver across town, and it makes the truck. Nobody records the sub rental cost against the job. The client never knows. The job looks profitable in the accounting system because the sub rental invoice arrives three weeks later coded to general cost of sales.

That is the real economics of an AV rental house. Across projects in this sector we have delivered, the pattern is consistent: sub rentals that never get costed to the job that caused them, a prep floor that runs on the memory of two senior techs, and jobs each year that were quietly loss making because the losses were spread across cost categories. Then there is the other cost, which is the account you lose because a case missed the truck and the client's CEO was standing in front of a dark screen.

Problem 1: your inventory is not a list of items, it is a nested set of cases

Generic rental systems model a line item with a quantity. A production house models a comms package that contains four belt packs, two antennas, a rack, and the specific cables that live in that case, all of which can also be pulled individually for a different job. A console has a hot spare relationship. A moving light has a serial number, a lamp hour count and a repair history, while gaff tape and batteries are consumables that leave and never come back. A truss span is measured in metres.

Flex Rental Solutions handles complex kit lists better than most, and if what you need is deep containerised inventory it is a genuinely capable product. The complaints we hear are about cost, the pace of change when your process differs, and how much of the prep floor reality still lives outside it. Current RMS is clean and cloud native and works well for straightforward hire, but nested packages, partial sub hire of a container and sub rental margin tracking tend to become manual. Rentman is strongest on crew and scheduling, and its equipment side is generic by comparison.

What a custom build does: model containers, serialised assets, bulk stock and consumables as different things, because they behave differently. A pull that breaks a package apart shows what is left in the case and what the case is missing. Availability is computed across overlapping jobs with real out and in dates including prep and turnaround time, not just the show dates, because a fixture that returns Saturday at 2am is not available for a Saturday 7am load.

Problem 2: the prep floor is where the money is made and nothing records it

Prep is the whole quality process. Kit gets pulled against the sheet, tested, packed, and scanned. When it comes back it gets checked, faults get flagged, and something either goes to the shelf or to the bench. In most houses this is a paper sheet with ticks, plus two senior techs who know which console has the flaky fader and which cable box is short.

The consequence is not just the missing item. It is that a fault found on return is often not recorded, so the same faulty unit gets pulled for the next show and fails on site. And it is that you cannot answer a client asking why they were charged for a damaged fixture, because the evidence is a memory.

What a custom build does: barcode or RFID scanning at pull, at truck load, at return, and at check in, with a fault state that takes an asset out of availability the moment it is flagged rather than when someone gets round to it. Photographs attach at check in, so a damage charge has evidence behind it rather than an argument. The prep sheet becomes a live checklist per case with a signature, which means a new tech can prep a package correctly on their second week, and the knowledge stops living in two people who both want to take August off.

Problem 3: sub rental is invisible margin and it is usually negative

Every busy house sub rents. In peak season it can be a serious share of what goes out of the door. The problem is that it is arranged by phone under pressure, agreed at whatever price gets it there, and recorded as an invoice that arrives weeks later with a reference nobody can match to a job.

Then there is the reverse: you sub rent to other houses, and your gear goes out on someone else's paperwork with your serial numbers on it. If it comes back damaged, the claim depends on what you can prove about its condition when it left.

What a custom build does: sub rental in and out are first class transactions attached to a job, with the vendor, the agreed rate, the expected return and the margin on the line visible while the deal is being made rather than after. Then the job costing shows the true cost, and after a season you can finally see which recurring shortage is costing you more in sub rental than the equipment would cost to buy. That answer surprises operators almost every time, and it is usually the business case for the whole build.

Problem 4: the truck, the freight and the packing list nobody can find

A show does not ship as a list of items, it ships as cases on a vehicle with a load order, sometimes across multiple trucks, sometimes with a freight forwarder and a carnet if it crosses a border. The load list and the pull sheet are different documents with different logic, and in most houses one is derived from the other by hand at 5am.

What a custom build does: cases carry dimensions and weight, so the load plan knows what fits and the freight quote is based on real numbers instead of an estimate. The load order reflects the unload sequence on site, which the crew chief cares about more than anything else in the system. Scanning at truck load produces a manifest that is the same document the site crew checks against, so a missing case is found in the yard and not in the venue. For international work the same data feeds the carnet list, which otherwise consumes a day of somebody's week.

Problem 5: you do not know which jobs made money until the season is over

Rental houses run on gross margin per job, and most cannot compute it until well after the fact. The rate on the quote is known. The labour is in a timesheet system or a WhatsApp thread. The sub rental invoice arrives late. The freight is a separate bill. Damage and loss recharges may or may not have been raised. The consumables that went out and did not come back are absorbed.

What a custom build does: every cost attaches to the job as it is committed, including crew hours from the schedule, sub rental at the agreed rate, freight, consumables issued and any damage recharge. Then the job closes with a real margin, and the client view shows margin per account across a year. Operators who get this running usually find two things: a long standing account that has been repricing them downward for three years is now below cost, and the small jobs they treat as filler carry more overhead per pound of revenue than anyone assumed.

What this costs and how long it takes

Across the 2,000-plus projects Digital Heroes has delivered, here is the honest shape for AV and live production rental. A first release covering nested inventory, quoting from kit lists and templates, true availability across overlapping jobs with prep and turnaround windows, and scan based prep and check in runs $65,000 to $130,000 and ships in 12 to 16 weeks. A full platform adding sub rental in and out, truck and freight packing with dimensions and weights, crew scheduling and call sheets, maintenance and service history, and per job costing runs $160,000 to $400,000 phased over 6 to 11 months.

What drives cost up in this sector specifically: the number of warehouse locations and whether gear transfers between them, because inter depot transfers double the availability model. RFID, if you want gate reads rather than handheld barcode scanning, which is a hardware project as much as a software one. Crew scheduling, if your crew are a mix of staff, freelancers and agency with different rates and availability rules. International freight and carnets. And integration with your accounting system, because Xero, QuickBooks and Sage are three different jobs.

What keeps it down: starting with one warehouse and your top revenue kit categories, and leaving the long tail of clamps and adapters as bulk stock until the model is proven.

Build versus buy, and when buying is the right call

Buy if you are a smaller house doing straightforward dry hire with limited kit list complexity. Current RMS is well built, quick to get running and will cost you a fraction of a custom project. Rentman is a sensible buy if crew scheduling is your main pain and equipment is simpler. Flex is the right buy if your inventory complexity is the whole problem, you can live with its shape, and your process is willing to bend to it.

Build when two or more of these are true. You are past roughly $4M in rental revenue with more than one show going out per day. Sub rental is a material line and you cannot see its margin per job. Your prep floor depends on two people who hold the knowledge of what belongs in each case. You transfer gear between depots and availability is a phone call. Or you have lost an account to a missing item and cannot explain in the debrief how the system said it was available.

How to choose a developer for rental and live production software

Ask them to whiteboard availability before anything else. The right model is a timeline per asset with out, prep, show, return and service windows, not a stock count per day. A developer who draws quantity on hand has built an ecommerce warehouse and will produce a system that says available for gear that is on a truck in another city.

Ask how they will model a container that can be sub hired in part. If they treat a package as a bundle that always moves together, your prep floor will route around the system in the first month and you will be back on paper.

Ask what they have integrated on the hardware side. Handheld barcode scanning on a warehouse floor, label printing that survives a road case, and RFID portals are three different pieces of work, and only the first is straightforward. Ask for the specific device and the specific site, not a claim about hardware in general.

Ask who owns the code and get it in writing before kickoff. You should own the repository, the infrastructure accounts and the right to hire anyone else to continue the work. At Digital Heroes the code is yours from the first commit. Your asset register, service history and client pricing are the business, and none of it should sit in a system you cannot take with you.