Build a Transparent Quote for a Small Creative Project

Start with a shared scope

Before calculating anything, restate the deliverable in a short paragraph. For a workshop presentation, specify the number of slides, whether the client supplies approved copy, whether charts need rebuilding and which file formats are included. A quote based on a vague brief is fragile: ten simple slides and ten research-heavy slides are different assignments. Add the scope version and date so later conversations refer to the same package. If the input is not yet clear enough, propose a separate discovery stage instead of disguising uncertainty.

Break the work into genuine stages

Estimate your own effort for reviewing inputs, setting a visual direction, production, quality checks, the agreed revision round and handoff. Include communication and file preparation. You can show a concise stage summary to the client without exposing every private calculation. The purpose is to notice missing work before committing. Track a practice project if you lack a baseline, then compare planned and actual effort afterward. Do not copy a stranger's hourly assumptions or describe an invented figure as a standard market rate.

Make assumptions and dependencies visible

List the conditions behind the quote: final copy provided before layout, one consolidated reviewer, existing brand assets and no translation. Give missing information a decision date. Describe how a changed assumption will be discussed before extra work proceeds. If the client supplies a new script halfway through editing, the relevant issue is the effect on assembly and captions, not whether the change looks small in an email. A useful assumption is specific enough that either person can recognise when it no longer applies.

Separate core work from optional items

A plain structure might be core package, optional second format and optional additional illustration. State what each option adds and whether choosing it changes the schedule. Avoid bundling unwanted services simply to make the package seem large. Also identify third-party costs such as a specially commissioned asset or a required licensed font, and who approves them. Do not buy resources on the client's behalf without an agreed process. The client should be able to understand the total package without hunting through several unrelated messages.

Explain what the document represents

Say whether you are giving a preliminary estimate based on limited information or a quote for a defined package. Include a preparation date, an availability note and a clear way to ask questions. Commercial payment arrangements, cancellation terms and rights should be agreed appropriately for the engagement; do not pretend a generic paragraph resolves every jurisdiction's rules. Keep personal banking information out of a public example. Where a project comes through a platform, check its official rules rather than assuming an external arrangement is permitted.

Discuss trade-offs instead of invisible discounts

If the package exceeds the client's resources, offer a smaller scope: fewer slides, supplied rather than newly drawn diagrams, or one output size. Explain what the smaller version can still accomplish. A deadline change may improve scheduling, but it does not automatically remove production work. Record the chosen package and get confirmation before starting. After delivery, compare estimated stages with actual effort and update your future planning. That learning is more useful than chasing an arbitrary price point detached from the work you provide.

Your working checklist

Checkmarks stay in this browser when storage is available. They do not submit a form or complete a booking.

• Dated scope and brief
• Private effort estimate
• List of third-party resources needing approval
• Quote document with core and optional items

Put it into practice

1. Confirm quantities, formats and supplied inputs. Label unresolved information and decide whether you can quote responsibly or need a preliminary discovery stage first.
2. Estimate effort across the complete workflow, including communication, quality review, revisions and handoff. Use your own practice records rather than unsupported industry averages.
3. Present the core package, options, assumptions and availability in one readable document. Explain which decisions would require a revised quote before work proceeds.
4. Discuss scope adjustments if needed, confirm the chosen version and save it with the project. Compare your effort estimate with actual delivery afterward.

Common questions