From Enquiry to Invoice: The AV Company Workflow

The end-to-end workflow of an AV company is the same shape whether you are a freelancer or a team of 20. What changes is where the time leaks and which step is the bottleneck. Here is the full lifecycle, the tools that fit each stage, and the moves that consistently save time without losing quality.

The eight stages

1. Enquiry comes in
2. Brief is clarified
3. Kit list and crew are built
4. Proposal is written
5. Proposal is sent
6. Client questions and revisions
7. Proposal is accepted
8. Job is delivered and invoiced

Each stage has a different rhythm. Each one breaks for different reasons.

Stage 1: Enquiry

Where it happens: inbox, phone, website form, referral. What goes wrong: the enquiry sits in someone's inbox for three days.

What helps: a single shared point of capture, even if just a CRM or shared inbox, so enquiries do not disappear into individual mailboxes. A two-hour acknowledgement rule beats most things you can spend money on.

Stage 2: Brief clarification

Where it happens: phone call or email exchange. What goes wrong: the proposal gets built against assumptions, then re-built when the client clarifies later.

What helps: a short list of questions you always ask. Venue, dates, audience size, run of show, deliverables, accessibility, budget range, decision timeline. If the client cannot answer most of them, the proposal is premature.

Stage 3: Kit list and crew

Where it happens: in the rental management system (Current RMS, HireHop, or similar), plus a crew scheduling tool or whiteboard. What goes wrong: kit gets quoted that is not actually available; sub-hires come in over budget after the proposal has gone out.

What helps: build the kit list in the rental system against real availability. Lock sub-hire pricing before the proposal goes out. Do not promise availability you have not checked.

Stage 4: Proposal writing

Where it happens: Word, PowerPoint, or a proposal tool. What goes wrong: rebuilding the structure from scratch every time. Inconsistent branding. Wrong client name copied from a previous proposal. Out-of-date case studies.

What helps: a template structure you trust and a library of reusable blocks (team profiles, case studies, terms, testimonials). The writing is the part that needs your time. The scaffolding should not.

Stage 5: Sending

Where it happens: email attachment, or proposal tool with branded link. What goes wrong: PDF gets stuck in spam, file size too big, link expires, recipient has no way to forward to colleagues.

What helps: send the proposal as a link, not an attachment. Track when it is opened. Get a notification when the client first reads it so your follow-up timing is right.

Stage 6: Questions and revisions

Where it happens: email thread, calls. What goes wrong: revisions get lost, the wrong version becomes "the current version", different team members are working from different versions.

What helps: the proposal lives at one URL. Every meaningful update creates a new revision. Old versions are preserved but the link always shows the latest. Conversations with the client happen on the proposal itself, not in a separate email chain that the rest of your team cannot see.

Stage 7: Acceptance

Where it happens: client signs by some method. What goes wrong: print-sign-scan delays of days; ambiguity about which version was accepted; nobody on your team notices the proposal was accepted because the notification went to one person's inbox.

What helps: online acceptance with a typed name and timestamp. The accepted version is locked. Everyone on your team gets notified. A PDF of the accepted proposal is generated automatically for both sides.

Stage 8: Delivery and invoice

Where it happens: rental system, accounting tool, on the day. What goes wrong: the accepted proposal does not translate cleanly into a job in the rental system; invoicing is manually constructed from the proposal again; payment terms slip because nobody is watching them.

What helps: the accepted proposal flows into a confirmed booking in the rental system. The invoice is generated from the accepted scope, not rebuilt from scratch. Payment terms are tracked, with automated reminders before they slip.

Where the time really leaks

For most AV companies, the biggest leaks are:

• Stage 4 (writing the proposal from scratch every time)
• Stage 6 (managing revisions across email)
• Stage 8 (rebuilding invoices from the proposal manually)

Fixing any one of these gives back hours per week. Fixing all three transforms the rhythm of the business.

Tools per stage

A simple working stack:

• Stages 1-2: shared inbox or CRM (HubSpot Free, Pipedrive, Capsule)
• Stage 3: rental management (Current RMS or similar)
• Stages 4-7: proposal tool (pro-posal.io)
• Stage 8: accounting tool (Xero, QuickBooks, FreeAgent)

These talk to each other where it matters: pro-posal.io pulls from Current RMS, the accepted proposal informs the booking, the accounting tool handles invoicing.

The end-to-end principle

The single biggest workflow improvement is not any individual tool. It is the principle that each piece of information should live in one place and flow to where it is needed. Build the kit list once, in the rental system. Build the proposal once, in the proposal tool. Approve the booking once, in the rental system. Invoice once, in the accounting tool. No re-keying. No spreadsheets in the middle.

Most AV companies get this wrong by accident, growing into a workflow rather than choosing it. The companies that grow profitably tend to be the ones that choose the workflow deliberately.

pro-posal.io is the proposal layer in that workflow. It connects to Current RMS, captures acceptance cleanly, and gives you the structure to stop rebuilding documents from scratch. Try it free for 60 days, no card required: pro-posal.io.