Case study · Client project
Operations platform for an asset rental business
A platform covering quote to invoice for a production equipment rental company: tariff pricing, multi version negotiation, management approval, equipment movement, vendor sub-rental, billing reconciliation and a full audit trail.
New quotation · Site #4, North Depot
At a glance
The project in brief
- Business: rents cameras, lenses, heads, filters, batteries and accessories to film, web series and advertising production houses in India, and sub-rents equipment to and from other vendors
- What we built: two connected web apps on one database, an admin portal for the company and an operations portal for field managers
- Scope: quotation, negotiation, contract, mid-shoot additions, vendor flow, billing reconciliation, invoicing and payments
- Team: MetaNova AI delivery and engineering from Hyderabad
The challenge
A rental business that ran on trust and spreadsheets
Aurelian Frames rents production equipment by the day. The commercial side of that business is negotiated, not list priced. A producer asks for a camera package, the price moves up and down over a few conversations, equipment is added halfway through a shoot, and the final bill depends on how many days the gear was really out. Some of the equipment does not even belong to the company. When its own stock runs short it rents from other vendors, and sometimes rents its own gear out to them.
All of that was being held together by spreadsheets, messages and memory. There was no single record of what had been quoted, who had agreed to what, which version of a price was the last one, or which items were added to a live job and who approved them. Managers in the field could promise things the office had not seen. The office could not see a shoot's real position until the invoice was already late.
The owners wanted three things. Managers should be free to move fast in front of a client. The money side should stay in the hands of a small number of people who approve it. And every number on every invoice should be traceable back to the decision that produced it.
What we set out to do
Four goals we agreed before writing code
- Separate duties: field managers propose, administrators approve and own the money
- Make negotiation a controlled process with a clear last version, not a trail of edited files
- Let live jobs grow without losing control: extra equipment mid-shoot must be visible, approved and billed from the right date
- Treat sub-renting to and from other vendors as part of the same system, tied to the job it serves
How we approached it
Workflow first, then software
Map the real steps
We sat with the managers and the administrators and wrote down what actually happens between a first enquiry and a paid invoice, including the shortcuts. The statuses in the system are the words the team already used, not words we invented.
Draw the line between propose and approve
Every screen was classified by who may start the action and who must confirm it. That single decision shaped the two apps, the roles, the database policies and the notification model.
Build the spine first
We shipped quotation to contract end to end before anything else, so the team could run real quotes through it. Vendor flow, mid-shoot additions and finance were added on top of that spine, each one tested on live work.
Keep the money rules in code that can be tested
Billable days, additional equipment totals, price rebalancing and vendor status rules are small, pure functions with their own tests. A finance rule is never hidden inside a screen.
What we built
From first quote to final payment
Quotations with controlled negotiation
A manager builds a quotation in a four step wizard: choose the client or vendor flow, pick or propose the customer, select equipment, then settle the price. A quote can be revised up to three times. Each revision becomes a new version linked to the previous one, with the earlier version kept and a history entry written. Only the latest version can move forward.
Settlement that hits a target total
In the last step the manager types the total the client has agreed to. The system redistributes unit prices across the lines so the total matches exactly, never pricing a line above its tariff and leaving discount-locked lines untouched. Rounding drift is absorbed by the last adjustable line so the total is exact to the paisa.
Admin review and equipment assignment
Administrators see every submitted quotation, assign specific equipment to each line, send a quote back to the manager with a reason, accept it with notes, or reject and archive it. A version comparison view shows exactly what changed between V1, V2 and V3.
Contracts that stay live
An accepted quotation converts to a contract in one controlled step that copies the commercial terms, links the quote history and stops a second contract from being created. Activation is blocked while any linked vendor deal still waits for approval. Start and end dates, project phase and mandatory remarks for stalled or cancelled jobs are recorded against the contract.
Additional equipment mid-shoot
Managers add extra gear to an active contract from the field, with remarks. Each addition waits for approval, and on approval the administrator sets the exact billing window for that set. Contract totals include an addition only when it is approved and has both dates, so a pending request can never leak into an invoice.
Custom equipment requests
When a client asks for something that is not in the catalogue, the manager raises it from inside the quote. Administrators approve it, which creates a proper equipment record with pricing, or reject it with a reason.
Vendor flow, inward and outward
Renting from a vendor or sub-renting to one runs through the same engine, linked to the contract it supports. Status changes follow explicit rules, and moving a deal back to draft or into dispute requires a reason. Vendor margin is visible per line.
Finance: reconcile, invoice, collect
For each contract, the system compares planned days and amounts with what actually happened, including extra days, adjustments, damage and missing items. Invoices are generated with a due date, payments are recorded against them by method, and a finance dashboard shows what is outstanding and overdue.
Design decisions
The choices that made it work
Two apps, one database
Administrators and field managers have different jobs, different devices and different risks. Separate apps with isolated sessions mean a manager's screen simply does not contain the controls an administrator needs, and the two can be signed in side by side in one browser.
Versions are rows, not edits
A revised quotation is a new record that points to its parent. Nothing is overwritten, so any figure in a contract can be traced back through every version that led to it.
Approval is a state, not an email
Pending additions, new customers, new vendors and custom equipment each have an explicit pending state, and a notification bell collects everything waiting for an administrator. Nothing depends on someone remembering to forward a message.
Billable days that survive time zones
Rental days are counted on calendar dates, inclusive of start and end, with holidays and chosen dates excluded. Counting is done in UTC so a date picked in one place never drifts by a day in another.
Indian billing as a first class concern
GST is built in at the line and header level, with CGST and SGST or IGST, and amounts are shown in Indian number format with two decimals. Totals are never rounded to whole rupees.
Under the hood
How it is built
- Next.js and React with TypeScript, as two separate web apps in one monorepo with shared types
- PostgreSQL with row level security, database functions for numbering and totals, and triggers that keep roll-ups consistent
- Role based access for administrators and operations managers, with a managed pause and reset flow for staff accounts
- Audit tables for negotiation history, quotation changes, vendor transactions and staff account actions
- Unit tests on the pricing, billing, vendor status and rename-propagation rules
- CSV importers to load the client's existing customer and vendor master data
The result
What changed for the business
- One record per deal, from first quote to final payment, instead of files and chat threads
- Managers negotiate in front of the client and see the agreed total land correctly on every line
- Administrators approve from one queue and always know what is waiting on them
- Extra equipment added mid-shoot is approved, dated and billed from the right day
- Sub-renting sits beside the contract it serves, with margin visible
- Finance sees planned against actual before an invoice goes out, and outstanding payments in one place
What comes next
Built to keep growing
The platform was built to grow. Because the commercial rules live in tested functions rather than in screens, new capabilities such as utilisation and vendor margin reporting, scheduling of equipment across overlapping jobs, or a client-facing view of quotes and invoices extend the system instead of reworking it.
