Many freelance composers begin by quoting game music at an hourly rate. It seems fair, and it is easy to explain. Yet hourly quotes often make studios nervous, because they cannot predict the final cost, and they can make composers feel that every creative breakthrough is being timed. Quoting by scope, meaning the list of deliverables and their conditions, often gives both sides a clearer picture of what they are buying.
Describe the deliverables first
Start by listing exactly what the studio expects. Include the number of tracks, the approximate length of each, the format, the number of revisions included, and whether implementation support is part of the work. A scope that says eight looping tracks, two stingers, and one main theme, delivered as stereo files with stems, is far easier to price than a request for the soundtrack for a project. Ask questions until the list feels complete, because gaps in the scope are where extra costs hide.
Readers may also want to visit trendfar.com. This table can be attached to the quote and referenced when a change request arrives later. It also helps you spot items that look small but require significant research or testing.
- List the number and type of tracks clearly.
- State the included revision rounds for each deliverable.
- Explain whether implementation or testing support is included.
- Note any items that need the studio to supply assets.
Price each deliverable on its own
Once the scope is clear, price each deliverable separately. A main theme may require more development time than a short menu loop, and an ambient bed may need less effort than a combat track. Pricing separately lets the studio choose which items matter most and removes the sense that one large number hides everything. It also makes future changes easier to discuss, because each line can be adjusted without reopening the whole quote.
Keep your own internal estimate for each item. Note the time you expect to spend on composition, production, revisions, and delivery. Over several projects, these notes show which types of work are more demanding than you thought, and they help you refine future quotes. Be honest in your estimates, including the time spent on communication, because that time is real even if it does not show up in the music.
Set clear terms for changes
Every quote should explain how changes are handled. A simple statement might say that revisions to approved work are included within a set number of rounds, and that new features or significantly altered briefs are quoted separately. Explain what counts as a change in plain words. Studios often assume that a small tweak is free, while composers may see the same tweak as a substantial reworking of finished material.
Set a deadline for feedback as well. If the studio takes weeks to respond, the timeline slips and your availability may be affected. A reasonable window for feedback protects your schedule and helps the studio plan its own milestones.
Explain the value behind the number
When you present a scope-based quote, explain what the price covers in terms the studio can understand. Describe the creative process, the testing, the file preparation, and the support after delivery. Clients who see the work involved are more likely to accept the value of the quote, and they are less likely to compare you only with the cheapest option. Avoid overstating results or promising that the music will improve sales, because outcomes depend on many factors beyond your control.
Be careful with terms that affect rights or payment. If the agreement involves exclusivity, ownership transfer, or unusual payment conditions, speak with a qualified professional before you finalise the figures. General guidance is useful for structuring a quote, but it cannot replace advice on your specific situation.
Review the quote before sending it
Before the quote leaves your desk, read it as the studio would. Is every deliverable listed? Are the revision terms clear? Is the validity period stated? You can also visit pindnews.com for more reading. A short review catches missing details that could cause arguments later.
After each project, compare the final scope with what you quoted. Note any extra work and whether it was billed. This review will sharpen your next proposal, and it will show you where a clearer scope would have prevented unpaid effort. Keep a copy of the final scope with the project files, so the comparison is easy to make. You can find simple project close-out checklists in helpful online resources for independent creative workers. Scope-based quoting takes more care at the start, but it protects your time and gives studios the clarity they need to plan their games.