Give clients two or three real options, not a stack of confusing files
Options work when each one is a real production choice. They fall apart when the client has to compare three nearly identical files with different totals.
Who it's for: Production companies that regularly send good, better, best budgets, deal with procurement scrutiny, or lose hours chasing approvals buried in email.
Find the real problem first
What you see
The client writes 'let's go with option two' after getting several attachments, and your team can't say for sure which version, assumptions, or exclusions that means.
Why it happens
The approval lives in email, separate from the estimate itself. Files get passed around while the real numbers keep changing underneath them.
What it costs you
The job starts on a fuzzy promise, every revision turns into an argument, and the number everyone approved may not match the budget your team is actually using.
Three rules that hold in any tool
Every option needs a real reason
Explain the tradeoff behind each price: fewer deliverables, a simpler location plan, a smaller lighting package, or more time in post. A lower number with the same plan is just you cutting your own margin.
The approval should point to one exact version
The client's yes has to land on one option inside one estimate version. If the estimate changes after that, the old approval link shouldn't still look like the current offer.
Asking for changes is a fine outcome
Let the client ask for changes without anyone pretending they already said yes. Tie the request to the exact option they were looking at, so the next version starts from the same page.
Run this on one real job
Don't move the whole company at once. Try it on one job you are bidding now, note what doesn't fit, and roll it out once your producers trust it.
Name options by what they mean, not a letter
Use labels like single location, recommended package, or expanded deliverables instead of A, B, and C. Keep the internal keys if you want, but the client should understand the difference in plain terms right away.
- The recommended option is obvious
- Each option has a one-line tradeoff
- No option secretly depends on free labor
Keep the shared assumptions in view
Show dates, usage rights, number of review rounds, payment terms, and anything the client owes you right next to the options. Those shared assumptions shouldn't disappear just because the line items differ.
- Client-provided items are listed by name
- Overtime and change order triggers are spelled out
- The deadline to decide is visible
Record the decision in one place
Use one approval link that records which option was picked and when. Email is fine for letting people know. It shouldn't be where you go looking for the real answer.
- Only a live, valid link can approve anything
- Clicking twice doesn't cause a problem
- Your producer can see the approved option right away
Let the approval build the first budget
The option the client picks should turn into the job and its starting budget on its own. That closes the gap where sales sold one version and production quietly built another.
- The budget total matches the approved option
- The assumptions the client saw stay attached
- Later changes add history instead of erasing it
How to tell it's working
- Median hours between sending the estimate and getting a client decision
- Revision requests caused by assumptions nobody wrote down
- Approvals tied to the estimate version that's actually current
- Approved jobs that get a matching starting budget without anyone retyping totals
Where Production Engine helps
What the product does for this today, and where it stops.
What it does today
- Send a client several options by one link. They approve one, no account needed, and the pick is recorded with the estimate
- The option they approve becomes the job and its first budget, so nobody retypes line totals
- Each option shows its key assumptions right next to the price
Where it stops: Approving an option doesn't replace your contract, your PO process, or how you collect payment. Keep those running the way they do now, alongside the approval.
Questions producers ask
How many options should we actually send a client?
Usually two or three. One option can feel like a take it or leave it, and four or more just adds decision-making work for them. Only add an option when it's a genuinely different production plan.
Does clicking approve count as signing a contract?
Not on its own. Treat scope approval, the signed contract, and payment as separate steps unless you and your lawyer decide to combine them.
Should the cheapest option go first?
Order matters less than being clear. Lead with the option you'd recommend if you have one, then show the leaner or bigger alternatives with the honest tradeoffs attached.
More field guides
- Let email deliver the estimate, not decide what got approvedHow to get client approval out of long email threads, while keeping the message to the client short and simple.
- The approved estimate should become the job's first budgetHow to hand a won commercial estimate to production as a real budget, keeping the scope, assumptions, options, and sign-off intact.
- An estimate version is a client promise, not a filenameA plain way to version production estimates so revisions, options, assumptions, and approvals all stay tied to the number the client saw.
If this is costing you time or margin, try it on your next job.
Start free with a job you have already bid. If the estimate, the budget, and the wrap don't hold up against how you actually work, you've lost an afternoon.
Plans from $149 a month. If you cancel, your work stays readable.