Flash price on The Ultimate Motion Bundle
Flash price on The Ultimate Motion Bundle
A proposal is not just a price quote. For a freelance video editor or motion designer, it is often the first piece of professional work the client sees. Before they see an edit, a motion test, or a polished export, they see how you define the project, organize decisions, and reduce uncertainty.
That matters more than most freelancers realize.
If your proposal is too thin, the client fills in the blanks themselves. They assume extra cutdowns are included. They assume revisions are unlimited. They assume “social versions” means every platform, every aspect ratio, and every caption style they might need later.
If your proposal is too detailed, you create a different problem. The client gets buried in process notes, technical language, and unnecessary creative explanation. The offer becomes harder to understand, not clearer.
A strong freelance video production proposal sits in the middle. It gives the client enough structure to feel confident and gives you enough definition to protect the project once work begins.
The goal is not to sound corporate. The goal is to make the working relationship easier before anyone opens Premiere Pro or After Effects.
In 13 years of creating video templates and working around production workflows, one pattern keeps showing up: the most common source of project friction is not creative disagreement. It is a mismatch between what the client thought they were buying and what the freelancer thought they were selling.
The client thought they bought a complete campaign package. The freelancer thought they sold one edited video.
The client thought revision rounds meant trying different structures. The freelancer thought revisions meant tightening the approved direction.
The client thought vertical exports were included. The freelancer thought they were quoting only the 16:9 hero video.
None of these problems are really about taste. They are about undefined expectations.
A good proposal closes that gap before work starts. It turns a loose conversation into a shared project definition. It also gives the client a preview of how you manage the work: calmly, clearly, and professionally.
A proposal does not need to be long. For most freelance editing and motion design projects, 2 to 5 pages is enough. The structure matters more than the page count.
Here is the high-level structure:
| Proposal section | What it should answer | Why it matters |
|---|---|---|
| Project summary | What are we making and why? | Proves you understood the brief |
| Goals | What should the video accomplish? | Aligns creative decisions with business needs |
| Scope | What is included and excluded? | Prevents assumptions and scope creep |
| Deliverables | What files will the client receive? | Defines the actual output |
| Revision terms | How feedback will be handled | Keeps revisions manageable |
| Timeline | When key milestones happen | Gives the client confidence and accountability |
| Pricing | What each deliverable costs | Makes value clearer than hourly math |
| Payment terms | When and how payment happens | Protects cash flow |
| Scope change process | What happens when the brief changes? | Keeps extra work from becoming unpaid work |
You can adapt this structure to small editing jobs, larger brand videos, YouTube packages, social ad campaigns, event recaps, explainers, product demos, or ongoing content retainers.
Start by summarizing the project as you understand it. Do not copy the client brief back to them. Translate it into your own words.
This section does two things at once. It reassures the client that you listened, and it gives them a chance to correct misunderstandings before they become expensive.
A weak proposal starts like this:
Video editing project for your new product launch.
A stronger version sounds more specific:
Based on our call, the goal is to create a polished product launch video that introduces the new feature, explains the main customer benefit, and gives the sales team a short asset they can use across the website, email, and LinkedIn.
That sentence is not just nicer writing. It defines the job. It connects the creative work to the reason the client is hiring you.
For freelance editors, this is especially useful because many clients describe videos by format instead of purpose. They ask for “a 60-second edit” when what they really need is investor confidence, product clarity, lead generation, recruitment interest, or social proof.
Your proposal should name the purpose.
You can keep this section short. One or two paragraphs is enough. The important part is that the client can read it and think, “Yes, that is exactly what we need.”
Scope is where most proposal problems happen. Too many freelancers write a price and a general description, then hope the client will be reasonable later.
Hope is not a scope strategy.
Your scope section should define what work is included, what deliverables are included, and what assumptions the quote depends on. This does not have to be cold or defensive. It simply needs to be clear.
For video editing and motion design projects, scope usually includes:
The key is to avoid vague phrases like “social versions,” “some graphics,” or “final files.” Those phrases sound fine during a sales call, but they create problems later.
Instead of writing “social cutdowns included,” write something like this:
Includes two social cutdowns: one 15-second vertical version in 1080×1920 and one 30-second square version in 1080×1080. Additional durations or aspect ratios can be quoted separately.
That single sentence prevents a surprising amount of confusion.
Here is a simple deliverables table you can adapt:
| Deliverable | Duration | Format | Aspect ratio | Notes |
|---|---|---|---|---|
| Hero video | 60 to 90 seconds | MP4 | 16:9 | Website and presentation use |
| Social cutdown 1 | 15 seconds | MP4 | 9:16 | TikTok, Reels, Shorts |
| Social cutdown 2 | 30 seconds | MP4 | 1:1 | LinkedIn and paid social |
| Thumbnail still | 1 image | JPG or PNG | 16:9 | Based on final video frame |
This kind of table is boring in the best possible way. It removes guesswork.
If something is not included, say so. For example:
This scope does not include original filming, scriptwriting, voiceover recording, paid stock footage, advanced 3D animation, or additional language versions unless added in writing.
You are not being difficult. You are being specific.
Clients buy outcomes, not your timeline panel.
That is why your proposal should focus on deliverables first. Still, it is useful to briefly explain what production tasks are included inside those deliverables.
For example:
Production includes footage review, edit assembly, pacing refinement, basic color correction, music placement, light sound design, title graphics, export, and delivery of the approved final files.
This helps the client understand what they are paying for without turning the proposal into a tutorial.
The distinction matters because tasks can expand endlessly. “Motion graphics” could mean a lower third, a logo animation, a full animated infographic system, or a complete visual language for the campaign. If you do not define the level of work, the client may assume the highest version while your quote reflects the smallest one.
A practical way to keep this under control is to use plain categories:
| Category | Clear proposal wording | Risky proposal wording |
|---|---|---|
| Motion graphics | Includes simple titles, lower thirds, and branded transitions | Includes graphics |
| Sound | Includes music placement and basic mix using provided or licensed tracks | Includes audio |
| Color | Includes basic color correction for consistency | Includes color work |
| Versions | Includes one 16:9 final export and two listed cutdowns | Includes social versions |
The clearer your language, the fewer awkward conversations you need later.
Revision terms are not just there to protect you from difficult clients. They also help good clients give better feedback.
A revision round should be a defined event, not an endless email thread.
For example:
This proposal includes two rounds of revisions. A revision round means one consolidated set of client feedback provided after a review link is shared. Revisions apply to the approved scope and creative direction. New deliverables, major restructuring after approval, or requests based on new source material may require a separate estimate.
That language does a lot of work.
It tells the client how many rounds are included. It asks them to consolidate feedback. It separates normal revisions from new work. It also avoids the vague “unlimited changes” trap that destroys margins.
You should also define what happens after the included revision rounds are used:
Additional revision rounds are billed at a fixed rate of $X per round or at an agreed project rate before the work begins.
If you prefer not to list an exact additional revision price in the proposal, you can write:
Additional revision requests will be reviewed and quoted before work continues.
That is still better than silence.
If revisions have caused problems for you before, you may also want to clarify the difference between revisions and direction changes.
| Request type | Usually a revision | Usually a scope change |
|---|---|---|
| Replace a typo | Yes | No |
| Adjust timing in an approved section | Yes | No |
| Swap approved music for a similar track | Usually | Sometimes |
| Rebuild the video around a new message | No | Yes |
| Add new footage after the first cut | Sometimes | Often |
| Create extra cutdowns not listed in scope | No | Yes |
| Change the format from 16:9 to full vertical design | No | Yes |
This is not about being rigid. It is about having a shared definition before the pressure starts.
For more on making revisions manageable, read this guide on handling client revision requests without rebuilding from scratch.
A proposal that says “delivery in two weeks” is incomplete. Two weeks from when? From approval? From receiving footage? From receiving brand assets? From the client paying the deposit?
Your timeline should show the main milestones and the client responsibilities attached to them.
A simple timeline might look like this:
| Milestone | Timing | Responsibility |
|---|---|---|
| Proposal approval and deposit | Day 0 | Client approves scope and pays deposit |
| Asset handoff | Day 1 | Client provides footage, brand assets, copy, and references |
| First cut | Day 5 | Freelancer shares review link |
| Revision round 1 | Day 7 | Client provides consolidated feedback |
| Revised cut | Day 9 | Freelancer applies approved revisions |
| Revision round 2 | Day 11 | Client provides final feedback |
| Final delivery | Day 13 | Freelancer exports final approved files |
The exact timing will vary, but the structure is what matters.
Make client dependencies explicit. If the client takes five days to send feedback, your delivery date should move. If they send footage late, the schedule should move. If they add stakeholders after the first cut, the schedule may move.
A useful sentence:
Timeline assumes all required assets are provided before production begins and feedback is delivered within two business days of each review. Delays in asset delivery or feedback may shift the final delivery date.
This one line can save you from being blamed for delays you did not create.
Hourly pricing can be useful internally. It helps you estimate labor, protect your margin, and understand whether a project is worth taking.
But in most freelance video proposals, pricing should be structured around deliverables.
Clients do not really know what 18 editing hours should produce. They do understand “one hero video, two cutdowns, and two revision rounds.” Deliverable-based pricing makes the offer easier to approve because the client can connect cost to output.
For example:
| Item | Price |
|---|---|
| Hero video, 60 to 90 seconds, 16:9 | $X |
| Two social cutdowns, 9:16 and 1:1 | $X |
| Two included revision rounds | Included |
| Final exports and delivery | Included |
| Total project fee | $X |
If there are optional items, separate them clearly:
| Optional add-on | Price |
|---|---|
| Additional 15-second cutdown | $X |
| Additional aspect ratio adaptation | $X |
| Extra revision round | $X |
| Subtitle file and burned-in caption version | $X |
This gives the client choices without weakening the core proposal.
It also protects you from quietly absorbing extras. If the client later asks for three more cutdowns, you already have a pricing structure in place.
This connects directly to how you position your value. You are not selling hours in a chair. You are selling judgment, process, delivery, reliability, and a finished video the client can use. If you want to go deeper on that, this piece on pricing client work when templates are part of the process is useful even if you are not using templates on the job.
Payment terms should never be hidden at the bottom as an afterthought. They are part of the project structure.
At minimum, include the deposit, payment schedule, invoice due dates, and what happens before final delivery.
Common structures include 50% upfront and 50% before final file delivery, or milestone payments for larger projects. The right structure depends on project size, client relationship, and risk.
A simple version:
A 50% deposit is required to reserve the project and begin work. The remaining 50% is due upon approval and before delivery of final high-resolution files.
For larger projects, you might use milestones:
Payment is split into three stages: 40% deposit to begin, 30% after first cut delivery, and 30% before final export delivery.
Also clarify expenses. Music, stock footage, voiceover, fonts, translations, and paid plugins can all become points of confusion.
You might write:
Third-party costs such as licensed music, stock footage, voiceover, translation, or paid font licensing are not included unless listed in the scope. Any required third-party costs will be approved by the client before purchase.
If your proposal doubles as a statement of work, it is worth having a lawyer review your terms for larger engagements. This article is about proposal structure, not legal advice.
Every freelancer knows the moment: the client likes the first cut, then casually asks for “just a few extra versions.” Or a stakeholder appears late and wants the video to take a different angle. Or new footage arrives after the structure has already been built.
These things happen. Your proposal should not pretend they will not.
A good scope change clause does not make you sound difficult. It makes the process predictable.
Use language like this:
Requests outside the approved scope will be reviewed before work continues. If the request affects deliverables, timeline, creative direction, or production complexity, a separate estimate and adjusted schedule will be provided for approval.
That gives you room to be flexible without giving away work by default.
It also helps the client understand that changes are allowed, but they have consequences. More work costs more. Faster timelines may require a rush fee. New formats require new layout decisions. Major messaging changes affect the edit structure.
This is especially important for motion design, where small-sounding requests can have hidden complexity. “Can we make it vertical too?” might mean redesigning compositions, rethinking type scale, rebuilding transitions, and checking every shot for safe framing.
Your proposal should make that reality visible before the project starts.
This section depends on how you work and what the client needs, but do not ignore it.
Some clients only need final exported videos. Others expect project files. Some assume they can hand your After Effects project to another editor later. Some need broadcast usage, paid ads, or internal-only usage. Some need editable text versions for localization.
If you do not define this, assumptions take over.
At minimum, state what is delivered:
Final delivery includes approved MP4 exports listed in the deliverables section. Editable project files are not included unless agreed in writing.
If project files are included, define what that means. Are you delivering Premiere Pro files? After Effects files? Linked media? Fonts? Plugins? Template assets? Licensed music? Some of those may have separate licensing limits.
You do not need to turn the proposal into a legal contract, but you should not leave ownership and source delivery completely vague. For client work that involves templates, stock, or third-party assets, review licensing carefully. This guide on what a commercial license actually covers for client work covers the main issues to watch.
Freelancers sometimes overcorrect. After a few bad scope experiences, they start sending proposals packed with process, references, software notes, moodboards, animation theory, and every possible decision they might make.
That can overwhelm the client.
Your proposal is not the full creative treatment unless the project requires one. It is not a production diary. It is not a place to prove every technical skill you have.
The creative section should answer three simple questions:
For example:
The edit will use a clear product-led structure: problem, feature introduction, benefit proof, and call to action. Motion graphics will support clarity rather than decoration, using branded title cards, simple callouts, and clean transitions to keep the message easy to follow.
That is enough for many projects. It shows intention without drowning the client in execution details.
Here is a clean structure you can adapt for your own proposals:
You can keep this simple. A clear one-page proposal is better than a vague six-page one.
The biggest mistake is assuming that a friendly client conversation is enough. It is not. Clients forget details. Stakeholders join late. Priorities shift. A written proposal gives everyone something stable to return to.
Another mistake is quoting only the final price. A number without scope is not a proposal. It is an invitation for assumptions.
Freelancers also get into trouble when they describe effort instead of value. “Editing, motion graphics, color, sound” is useful, but it does not tell the client what they actually receive. Lead with deliverables, then support them with production details.
Finally, do not leave revision language soft because you are afraid of sounding strict. Clear revision terms are not hostile. They are professional. Good clients appreciate knowing how feedback will work.
A strong proposal does not remove every possible problem, but it gives you a much better starting point.
How long should a freelance video production proposal be? Most proposals for freelance editing or motion design work can be 2 to 5 pages. Smaller projects may only need one page if the scope, deliverables, revisions, timeline, pricing, and payment terms are clear.
Should I include hourly rates in my video proposal? Usually, quote by deliverable rather than by hour. You can use hourly estimates privately to calculate your price, but clients understand finished outputs more easily than editing hours. If the project is highly open-ended, an hourly or day-rate structure may make sense with clear caps and approval points.
How many revision rounds should I include? Two rounds is common for many freelance video projects, but the right number depends on complexity and client approval structure. The important part is to define what a revision round means and what happens when the included rounds are used.
Should source files be included in the proposal? Only if you want to include them or the client has paid for them. Final exports and editable project files are different deliverables. If source files are included, define exactly what is being handed over and check any third-party licensing restrictions.
What should I do if the client asks for extra versions after approving the proposal? Treat extra versions as a scope change unless they were listed in the deliverables. Review the request, estimate the added work, adjust the timeline if needed, and get written approval before producing the new versions.
Is a proposal the same as a contract? Not always. Some freelancers use proposals as statements of work that become binding once approved, while others pair them with a separate contract. For larger projects or higher-risk clients, use a proper contract and get legal guidance.
A well-written proposal is not just legal protection. It is a signal.
It tells the client they are working with someone who can manage a project, not just execute an edit. It shows that you understand goals, define deliverables, respect timelines, and handle changes professionally.
That confidence matters. Clients do not only hire freelancers for creative taste. They hire them because they want the project to feel under control.
When your proposal is clear, the client knows what they are buying. You know what you are selling. And the project starts with alignment instead of assumptions.
