To build an event estimate from an RFP, pull out every date, venue, scope item and crew need, keep the RFP wording each line came from, and price each line from your own rate cards. Then a person reads every line against the RFP before the estimate goes to the client, because a missed day or a misread headcount multiplies through the whole number.
The RFP is the client's description of the show. The estimate is your translation of it into days, people and things. Most estimating mistakes are translation mistakes, not arithmetic.
The steps
- Read for dates and venues first. Load-in, rehearsal, show days, strike. Every other line runs for some number of these days.
- List scope items. Stage, LED, audio, lighting, cameras, graphics, streaming, staging labor. One line each, with quantity and unit.
- List crew by role. Headcount and days for each role, and whether they travel.
- Keep the source. Next to each line, the RFP phrase that asked for it. A line with no source is either your judgement (say so) or a mistake.
- Price from rate cards. Your own current rates, not last year's quote and not a number from memory.
- Flag what the RFP leaves out. Power, rigging points, permits, overtime assumptions. Write them as assumptions in the estimate.
- Review against the RFP. One person who did not build it checks every line before it goes out.
What a good estimate line carries
| Field | Example (illustrative) |
|---|---|
| Category | Video |
| Description | LED wall for main stage |
| Quantity and unit | 3 days |
| Source in the RFP | "a large LED backdrop for the general session, all three days" |
| Price basis | Your rate card, or "needs a vendor quote" |
| Confidence | Clear in the RFP, or inferred and worth confirming with the client |
How ShowOps.AI handles it
- Upload the RFP or brief to an estimate. You can add more than one document, for example the RFP and a venue rate card. The extractor reads Word documents and PDFs that have a text layer; Excel and plain-text files are accepted too. A short RFP comes back as a draft in a few minutes.
- It drafts a draft estimate: scope lines, crew headcounts by role, quantities and dates. Lines drafted by AI are labelled as AI, and the estimate shows which document it was drafted from and how confident the extraction was.
- The AI sets no prices. Run pricing prices lines against your own rate cards. Crew roles usually match a day rate; most gear lines do not, and need a price entered by hand. The estimate stays a draft until a person approves it.
- The schedule it reads from the RFP is a suggestion. A person approves it before it is applied to the project.
- Winning a deal that has a client on it creates the project and a draft budget, and one approval turns the approved estimate into budget lines on that project.
What it does not do: it cannot read scanned PDFs that have no text layer, and it does not decide what to charge. Every AI run is logged, and AI calls to Anthropic run under Zero Data Retention.
For deals and estimates, see Sales. For how ShowOps.AI compares with a crew-first platform that also quotes, read ShowOps.AI vs LASSO.