Salesforce for event production companies: quotes, shows and crews

Event production companies use Salesforce best as the system that carries a job from first inquiry to final wrap-up. Sales Cloud handles leads, proposals and deal stages. A custom object usually holds the show itself, with its dates, venue, crew and logistics. Gear availability, crew scheduling and accounting tend to stay in specialist tools that connect to it. The build works when every team reads the same job record instead of six separate systems.

This guide covers production work: the jobs you quote, staff and deliver for clients. If you want to run your own marketing events and webinars as campaigns, see our separate guide on Salesforce event and webinar management instead.

Should a show be an opportunity or its own custom object?

Use the opportunity for the sale and a custom Event or Job object for the delivery. The opportunity closes once; the show record lives on through load-in, show days and strike.

Opportunities are built for forecasting. They carry an amount, a close date, a stage and products. A production job needs more than that. It has a show date range, one or more venues, a crew list, hotel blocks and a running list of changes. Cramming all of that onto the opportunity makes page layouts long and reports confusing.

A common pattern looks like this:

• Account: the client company, agency or venue that pays the invoice.
• Opportunity: the proposal, with stages for qualification, quoting, contracting and negotiation.
• Event or Job record: created when the deal closes, holding dates, venue, crew and show status.
• Venue: an account record type or custom object, so venue history builds up over time.
• Junction records: link crew members, gear packages and rooms to the job.

Some companies run several show dates or cities under one contract. In that case one opportunity can spawn several job records. Decide this rule early, because it shapes every report. Our data model design guide walks through the junction and lookup choices.

How do we quote equipment, labor and fees in one proposal?

Put gear packages, labor roles and fees in the product catalog with price books, then quote them as line items. The real question is whether standard quotes are enough or you need a quoting tool.

Equipment usually prices per day or per show, and labor prices per hour or per shift. Fees cover delivery, power, rigging, overtime and production management. Each can be a product with a unit of measure. Price books then separate rate cards, such as standard pricing, agency pricing or a large client’s negotiated rates.

Standard Sales Cloud quotes cover simple proposals. They struggle with bundles, multi-day math, discounts by line and optional add-ons. Revenue Cloud or an AgentExchange (formerly AppExchange) quoting app handles those rules, at extra license cost. Product names and editions change, so check what is included with your Salesforce account team first.

• Bundle common setups, such as a general session package, into one product with child lines.
• Store day counts on the line item so multi-day pricing calculates without spreadsheets.
• Keep labor roles separate from gear so crew costs report on their own.
• Add an optional flag for upsell lines the client may accept later.

Can Salesforce tell us whether gear and crew are available?

Not on its own. Sales Cloud has no native view of whether a projector or a camera operator is free on a given date.

This is the hardest part of any production build, so be honest about it in scoping. There are three broad routes:

• Keep an equipment rental and inventory system as the source of truth, and connect it to Salesforce.
• Evaluate Field Service, which schedules people and resources against time slots. It was built for service visits, so test whether it fits multi-day shows before buying.
• Build a custom availability check that looks for overlapping bookings on the same crew member or asset.

The integration route is the most common for gear. Rental systems track serial numbers, maintenance and warehouse moves, which Salesforce should not copy. A useful link sends confirmed jobs to the rental system and returns pull sheet status. Crew availability is often simpler to keep in Salesforce, as long as booking rules are clear.

How should proposals, contracts and deposits flow?

Generate the proposal and contract from the opportunity, collect a signature, then pass the deal to accounting for the deposit invoice. Each handoff should move a stage, not rely on an email.

A document generation tool merges line items, show dates, venue details and terms into branded PDFs. An e-signature app returns the signed copy to the record and can advance the stage automatically. Both are covered in our document generation and e-signature guide.

Deposits and final invoices belong in the accounting system. Salesforce should send the customer, the job and the billing schedule. Accounting should return invoice numbers, amounts paid and balances due. Our accounting integration guide explains the sync patterns. Avoid rebuilding invoicing in Salesforce unless a specialist tool truly cannot fit.

How do we manage repeat clients and venues?

Treat venues as first-class records and link every job to one. Over time, each client and venue builds a history your team can use when quoting the next show.

Planners often return each year with a similar show. Cloning last year’s opportunity and line items saves hours of setup. Venue records can hold dock details, power notes, house rules and the in-house contacts. If you serve agencies that book on behalf of brands, record both: the agency as the paying account and the brand as a related account. Account hierarchies only matter when a client has divisions that book separately.

What happens after the show closes?

Close the job record with actuals, request feedback, and log anything the next proposal should know. This step is often skipped, which is why repeat quotes keep repeating mistakes.

• Record final labor hours and added charges against the job before invoicing.
• Send a short client survey and link the response to the show record.
• Capture venue notes, such as access problems or power limits, on the venue.
• Create a renewal opportunity for annual shows with the next expected date.

Our surveys and CSAT guide covers the survey options and how responses roll up to accounts.

Wrap-up is also where change orders get reconciled. Clients often add a breakout room or extra camera during the show. If those adds are logged on the job as they happen, the final invoice matches what was delivered. If they live in a producer's notebook, revenue leaks quietly.

Which reports matter most to production leaders?

Pipeline by show date, not just close date, is the first report to build. Production capacity depends on when shows happen, so leaders need both views.

• Pipeline by show month, so you see crowded weeks before they are sold.
• Contracted revenue by show month and job type.
• Crew assignments per person across upcoming shows.
• Venue history: jobs, revenue and notes per venue.
• Win rate and average deal size by client segment.

Utilization is worth tracking, but define it before reporting it. For crew, it might mean assigned days against available days. For gear, the rental system usually holds the better data. Agree the formula first, then decide which system reports it.

Keep dashboards short. A producer needs upcoming shows and open tasks. A sales leader needs pipeline by show month. An owner needs contracted revenue, deposits outstanding and margin trends once accounting data flows back.

What did a real event production build look like?

An audio-visual event company we worked with ran leads, events, contractors and logistics across five or six disconnected platforms. Information was not shared across the team. It had no way to quote, track opportunities or coordinate travel.

We built a Sales Cloud solution around its production workflow. Opportunities moved through custom quoting, contracting and negotiation stages, and Einstein Activity Capture was part of the build. A custom Event Show object managed each show from pre-show planning to real-time execution. A separate booking object coordinated contractor flights, hotels and rental cars. Contractors, venues and hotels each got their own record type. When a deal closed, the event record was created automatically.

The company consolidated six platforms into one Salesforce environment. It automated event and travel coordination and gained reporting across bookings, contractor assignments and venue history. This was a custom Sales Cloud build, not an industry cloud.

What should an event production company build first?

Start with the sale and the show record, then add integrations once the core data is trusted. Most of the value comes from one shared job record.

• Leads, opportunities and stages that match how your team actually sells shows.
• Products and price books for gear packages, labor roles and fees.
• A custom Event or Job object created automatically when a deal closes.
• Venue and contractor records with clean ownership.
• Pipeline by show date and a simple upcoming shows dashboard.