Chapter 38: The Business of Video

Overview

Here is a video you will never see, and the reason you will never see it. A freelancer shot a beautiful two-minute testimonial for a local business — well framed, well lit, clean audio, a warm grade, a perfect music track under it. The client loved the cut. Then three things happened in the same week. The person featured in the testimonial saw it online, said "I never agreed to be in an ad," and asked to be removed. The catchy song under it triggered an automated copyright claim and the platform muted the audio. And the "quick two-day job" had, over five weeks of unpaid revisions, quietly become the least profitable thing the freelancer did all year. Every frame of that video was competent. The business around it was a disaster, and the business is what sank it.

This chapter is about the half of the craft that never appears on the timeline. You have spent thirty-seven chapters learning to make video and, in Chapter 37, to never lose it. None of that skill protects you from an unsigned release, an unlicensed track, a handshake that turned into a dispute, or a job you priced so low you resented finishing it. Getting paid — and staying protected while you do it — is a craft with its own techniques, and they are as learnable as a lighting setup. A contract is a tool. A release is a tool. A quote is a tool. Used well, they do something better than winning the argument later: they prevent the argument entirely, and they make the client trust you more, not less.

We will move through the whole business in the order a real job unfolds. You will learn to price your work three different ways and put the number in writing. You will learn what a contract and a statement of work actually do, and how they protect the relationship, not just your bank account. You will learn to see scope creep coming and defuse it with a sentence. You will learn to get the releases that make footage of a person publishable, and to license the music, footage, fonts, and graphics that make a video legal instead of a liability. And you will learn where the next job really comes from — which, it turns out, is almost never advertising.

One promise before we start, and it will recur: nothing in this chapter is legal advice. It is a working practitioner's map of how the business runs, at a general level. Laws about contracts, likeness, and copyright vary enormously by country, state, and situation, and they change. For anything that matters — a big contract, a tricky rights question, a dispute — the professional move is to consult a qualified lawyer in your own jurisdiction. This chapter will make you fluent enough to know what to protect and when to get help. It will not make you your own attorney.

In this chapter you will learn to:

• Price a job three ways — by the day, by the project, and by the value it creates — and write a quote that covers your true costs.
• Use a contract and a statement of work to define the job before it starts, and get paid on a schedule that protects you.
• Recognize scope creep and handle new requests with a revision policy and a change order instead of resentment.
• Get model and property releases so the people and places in your footage are yours to publish.
• License music, footage, and assets legally, and understand copyright well enough to stay out of trouble.
• Win and keep clients the way professionals actually do — through trust, referrals, and repeat work.

Learning Paths

This chapter is where a hobby becomes a business, and it serves the 💼 Pro-track reader hardest of anyone in the book — but there is not a creator alive who has not been burned by one of these six things. Weight your attention like this:

• 📱 Phone-first: even if no money has changed hands yet, §38.4 (releases) and §38.5 (licensing) apply to anything you publish — the moment a real person is on camera or a real song is under your edit, these are your rules. Read those two cold; skim the pricing sections until money is involved.
• 🎥 Creator: §38.5 (music, footage, and copyright) is the one that gets channels muted, claimed, and struck — learn it before it costs you. §38.4 matters the instant you film anyone who isn't you, and §38.6 is how a "channel" becomes brand and client work.
• 💼 Pro-track: all of it, and it is arguably the most valuable chapter in the book for your income. §38.1–38.3 (pricing, contracts, scope) decide whether you make a living or just make videos; §38.4–38.5 decide whether you get sued. This is the invisible professionalism a client is really paying for.
• 🎓 Student: the examinable spine here is the distinctions — day rate vs project rate vs value; a revision vs a new request; consent to film vs consent to publish; owning vs licensing; copyright vs a license. The Production Checkpoint applies all six sections to the three projects you have built across the whole book.

38.1 Pricing: day rates, project rates, and value

Let us start with the question that makes new video makers most uncomfortable, because discomfort is exactly where the money leaks out: what do you charge? The wrong answer is not a bad shot; it is a good shot given away. Beginners rarely fail because their work is unsellable. They fail because they charge too little, forget half their costs, say yes to "exposure," and burn out doing excellent work for free. So before the cameras, the contracts, or the releases, we fix the number.

Pricing is the deliberate craft of deciding what your work is worth and how you charge for it — not a figure you pluck from the air or copy from a stranger online, but a decision built from your real costs, the time the job takes, the market you work in, and the value the finished video creates for the client. Pricing is a skill you get better at, and like every other skill in this book, the first rule is motivate the choice: you should be able to say out loud why the number is the number.

There are three ways to arrive at that number. Most professionals use all three, switching between them depending on the job and the client.

The day rate. A day rate is a fixed price for a day (or a half-day) of your time and labor — the unit that shooters, editors, and crew most commonly quote by. It prices you: your hands, your eye, your presence for the day, usually including your basic kit. Anything beyond the basics — extra gear, a second shooter, a drone operator, travel, unusual insurance — is added on top. Day rates vary enormously by market, by role, by experience, and by region, and anyone who quotes you a single universal number is selling something. The right way to find yours is to research your market (what people at your level in your city charge for your role), not to copy a figure from a video by a creator in a different country with a different cost of living. What matters is the concept: the day rate is how you price time, and it is the building block crews and rentals are quoted against.

The project rate. A project rate (also called a flat or fixed bid) is one price for the whole deliverable, no matter how many hours it takes. Clients often prefer it, because it gives them a number they can budget against with no surprises. It carries one sharp danger: if you underestimate the work, you eat the overage — the extra days, the extra revisions, the problems — for free. That is precisely why the next two sections (contracts and scope) exist. You build a sound project rate by estimating the days the job will really take across all three stages — remember pre-production, production, and post-production are all work — then adding your hard costs (music and stock licenses, insurance, travel, rented gear, a second shooter) and a margin. The classic beginner error is to price only the shoot day and forget that the edit is usually the longest stage.

Value-based pricing. The most advanced move is to price by the value the video creates for the client, not by your hours at all. A thirty-second ad that drives a product launch is worth more to a company than "two days of my time," and pricing it as two days leaves money — sometimes a great deal of money — on the table. This is where the client brief from Chapter 22 pays off directly: when you understand the business goal behind the video (§22.1), you can price against the outcome, not the clock. Value pricing is not a trick to overcharge; it is the recognition that a great video is an asset that earns for years, and that your fee should bear some relationship to what it earns.

FIGURE 38.1 — Three ways to price the same job (and when each fits)

  MODEL           YOU CHARGE FOR…      BEST WHEN…                    THE RISK
  ─────────────   ──────────────────   ───────────────────────────  ───────────────────────
  DAY RATE        your time (per day)  crewing for someone else;    open-ended jobs drag on
                  + basic kit          shoots of unknown length;    and you're still only
                                        you're one of several        paid per day
  PROJECT RATE    the finished         a defined deliverable a      you under-estimate and
                  deliverable          client can budget for;       eat the overage —
                  (one flat price)     most freelance client work   SCOPE must be nailed down
  VALUE-BASED     the outcome/value    you understand the           harder to justify;
                  the video creates    business goal (Ch.22); the   needs trust and a track
                                        video is a real asset        record to command
  ─────────────────────────────────────────────────────────────────────────────────────────
  Most pros: quote client jobs as a PROJECT RATE built up from an internal DAY-RATE estimate,
  nudged by the VALUE when the goal is big. All three answer the same question — what is it worth? —
  from three directions: your time, the deliverable, and the result.

Whichever model you use, the number has to clear a bar most beginners never even calculate: your true costs. The fee for a shoot day is not spending money; it is the visible tip of an iceberg. Under it sit the unbilled hours — the emails, the quoting, the scouting, the revisions, the admin — plus gear that wears out and must be replaced, software subscriptions, insurance, taxes, and, crucially, the days you don't book. A freelancer is not paid for a five-day week; they are paid for the days a client hires them, and the rate on those days has to cover the days in between. This is why "I earn twenty dollars an hour at my job, so I'll charge twenty an hour" is a road to bankruptcy: an employee's wage is subsidized by an employer covering all of that overhead, and a freelancer covers it themselves, out of the rate.

⚙️ Settings Box: what a sustainable rate has to cover. Before you quote, make sure the number clears all of this — not just the shoot. A starting checklist, not a formula.

Cost bucket	Examples	Why it's easy to forget
Your time, all stages	pre-pro, shoot, edit (usually longest), revisions, admin	beginners price only the shoot day
Hard costs of the job	music/stock licenses, rented gear, travel, second shooter, meals	these are pass-through plus handling
Business overhead	gear depreciation, software, insurance, phone, website	invisible until the gear breaks
The unbilled days	quoting, scouting, marketing, the gaps between jobs	you're paid per booked day, not per week
Taxes & a margin	set-aside for tax; profit to reinvest and survive slow months	the fee is not take-home pay

A day rate that only covers the day is a slow way to go broke. Price the iceberg, not the tip.

Once you have a number, put it in writing as a quote — never a number muttered on a phone call that you and the client will later remember differently. A written quote (or estimate) is itself a professional signal, and it becomes the seed of the contract in §38.2.

FIGURE 38.2 — A written quote / estimate (the artifact the client receives)

  ─────────────────────────────────────────────────────────────────────
  [YOUR NAME / STUDIO]                                   QUOTE #2026-014
  [contact · email · phone]                              Date: 2026-07-06
                                                          Valid for: 30 days
  Prepared for: [Client name / business]
  Project: 90-second customer testimonial video for website + social
  ─────────────────────────────────────────────────────────────────────
  ITEM                                            QTY      RATE      AMOUNT
  Pre-production (planning, scripting, scout)     0.5 day  [rate]    [   ]
  Production (half-day shoot, 1 camera + audio)   0.5 day  [rate]    [   ]
  Post-production (edit, color, sound, captions)  1.5 day  [rate]    [   ]
  Licensed music track (royalty-free)             1        [cost]    [   ]
  ─────────────────────────────────────────────────────────────────────
                                                        SUBTOTAL      [   ]
                                                        Tax (if appl.) [   ]
                                                        TOTAL          [   ]

  INCLUDED:   1 finished 90-sec video (16:9) + 1 vertical (9:16) cut-down;
              captions (.srt); up to TWO rounds of revisions.
  NOT INCLUDED (quoted separately if needed): additional shoot days,
              extra deliverables/versions, paid actors, travel beyond 30 mi,
              licensed footage, on-screen talent releases you don't supply.
  PAYMENT:    50% deposit to book the date · balance due on delivery.
              Net-15. Final files released on final payment.
  ─────────────────────────────────────────────────────────────────────

Read FIGURE 38.2 as a teaching document, not a template to copy blindly (a fuller version lives in Appendix I). Three things in it are doing quiet, heavy work. The line items across all three stages make visible that the edit is real labor, not a free bonus after the "real" work of shooting. The INCLUDED / NOT INCLUDED block is your first and best defense against scope creep (§38.3) — it draws the fence before anyone leans on it. And the payment terms — a deposit to book, the balance on delivery, files released only on final payment — are how you get paid at all, which we build out in §38.2 and §38.6.

⚠️ Common Mistake: working for "exposure," and the race to the bottom. The single most expensive sentence in a young video maker's inbox is "we can't really pay, but it'll be great exposure." Exposure does not pay rent, and the clients who lead with it are rarely the ones who later pay well. This is not to say never work free — a cause you genuinely believe in, or a portfolio piece you fully control and can show off, can be worth your time as an investment you chose. The mistake is letting yourself be talked into it, repeatedly, by people treating your skill as worthless because you offered it cheaply once. Undercharging does not just hurt you; it trains a client to expect professional work for amateur money, and it drags down the whole market you are trying to join. Price like you intend to still be doing this in ten years.

💡 Why It Works: the number is an anchor and a signal. Pricing feels like pure math, but it is also communication. The figure you quote anchors the client's sense of what the work is worth — quote confidently in the professional range for your market and clients calibrate to it; quote apologetically low and they conclude the work must be low-value, and treat it that way. Your price is the first thing that tells a client whether they are hiring a professional or a favor. A fair, confident, itemized number does not scare good clients away; it reassures them. The ones it scares away were going to be the difficult ones anyway.

🔄 Check Your Eye. 1. What are the three pricing models, and what does each one actually charge the client for? 2. Name three real costs a beginner is likely to leave out when setting a day rate. 3. Why is "I make $X/hour at my job, so I'll charge $X/hour freelance" a route to going broke?

Check yourself

1. Day rate charges for your time (per day, plus basic kit); project rate charges for the finished deliverable (one flat price); value-based charges for the outcome/value the video creates for the client.
2. Any three: the edit (usually the longest stage), pre-production time, revisions and admin, gear depreciation, software/insurance, taxes, and the unbilled days between bookings.
3. An employer covers your overhead — equipment, insurance, benefits, downtime, taxes — so your wage is take-home. A freelancer pays all of that out of the rate, and is only paid on booked days, so the rate must cover the empty days too. Matching an hourly wage ignores the entire iceberg of cost.

38.2 The contract and the statement of work

You have a price. Before any work begins, that price and everything around it goes into a document both of you sign. This is the habit that most separates a professional from an enthusiastic amateur, and — like a shot list — it feels like bureaucracy until the day it saves you.

A contract is a written agreement, signed by both parties, that sets out what will be delivered, for how much, by when, and on what terms. It converts a friendly conversation into a shared, enforceable understanding. Notice the word shared: a contract is not a weapon you keep in a drawer to use against a client. Its real job is to make sure you and the client have the same picture of the job — the same deliverables, the same deadline, the same price, the same idea of who owns what — so that the dispute a contract would be used to win never happens in the first place. The best contract is the one you never have to enforce, because writing it forced both of you to agree on everything while you were still friendly.

Before we go further, the promise from the Overview, restated because it matters most right here: this is not legal advice. Contract law varies by jurisdiction and situation. What follows is a practitioner's account of what a video contract does and the parts it usually contains, so you know what to protect. For a significant agreement, start from a reputable template made for your region and have a qualified lawyer review anything important. Being able to read and reason about a contract is a professional skill; drafting an airtight one for a high-stakes job is a lawyer's.

Here is what a video agreement generally needs to pin down. You do not need legal language for most of it — plain, specific sentences that both parties actually understand are worth more than borrowed jargon nobody reads.

FIGURE 38.3 — What every video agreement should nail down (the clause checklist)

  CLAUSE                     THE QUESTION IT ANSWERS
  ─────────────────────────  ──────────────────────────────────────────────────────
  Parties                    Who is agreeing? (legal names, business, contact)
  Scope / deliverables       EXACTLY what you'll deliver — this is the SOW (below)
  Price & payment schedule   How much, and WHEN — deposit, milestones, final
  Timeline & dates           Shoot date(s), delivery date, what the client owes when
  Revisions                  How many rounds are included; extra rounds are billed (§38.3)
  Ownership & rights         Who owns the footage, the PROJECT FILES, the final video
  Usage / license grant      Where & how long the client may use it; which platforms
  Releases & permissions     Who is responsible for getting them (§38.4)
  Music & asset licensing    Who licenses/warrants the music, stock, fonts (§38.5)
  Cancellation / kill fee    What's owed if the client pulls out after booking
  Liability & indemnity      Who's responsible if something goes wrong / a claim arises
  Force majeure              What happens if a shoot is stopped by events beyond control
  Late payment               Interest or fees on overdue invoices; when files release
  ─────────────────────────────────────────────────────────────────────────────────
  Plain, specific sentences beat borrowed legalese. For anything high-stakes: a lawyer.

Two rows in that checklist deserve their own spotlight, because they are where video jobs most often go wrong.

The first is ownership and rights, and it is subtler than beginners expect. There are actually three different things a client might think they are buying: the final video, the right to use it in certain ways, and the raw footage and project files. These are not the same, and your contract should say which the client gets. Most commonly, a client pays for the finished video and a broad license to use it, while the videographer retains the raw footage and project files (and can license the footage separately, or use it on their reel). Some clients — often larger ones — pay more to own everything outright, a "buyout." There is no universal right answer, but there is a universal rule: decide it in the contract, before the shoot, not in an awkward phone call when they suddenly ask for "all the raw files." This is exactly the ownership question Chapter 37 flagged when you archived and packaged your projects for handoff (§37.6): whether you hand over the project files at all is a business decision the contract should already have made.

The second is the statement of work — the heart of the whole agreement, and the reason scope creep has somewhere to break. The statement of work (SOW) is the part of the contract that spells out exactly what you will deliver: the specific videos, their lengths, their formats and aspect ratios, the number of revision rounds, and — most importantly — what is included and what is explicitly not. If the contract is the agreement, the SOW is the fence around the job. Everything inside the fence is what you were hired to do. Everything outside it is new work, quoted separately. A vague SOW ("some social videos") is an invitation to scope creep; a specific one ("one 90-second hero video in 16:9, plus one 9:16 cut-down under 60 seconds, with captions, two revision rounds") is a boundary you can point to, kindly, when the requests start to grow.

FIGURE 38.4 — A simple Statement of Work (the fence around the job)

  ─────────────────────────────────────────────────────────────────────
  STATEMENT OF WORK — attached to & governed by the Agreement dated ____
  Project:  "Riverside Roastery" — customer testimonial + social cut
  ─────────────────────────────────────────────────────────────────────
  DELIVERABLES
    1. One (1) finished testimonial video — 80–100 sec, 16:9, 1080p, H.264
    2. One (1) vertical cut-down — under 60 sec, 9:16, for Reels/Shorts
    3. Caption file (.srt) for each deliverable
    4. One (1) high-quality master file retained by [videographer]

  SCOPE OF PRODUCTION
    • One half-day shoot (up to 4 hours), one location, one on-camera subject
    • 1 camera, 1 lavalier + shotgun, available/window light + one LED
    • Videographer supplies ONE licensed royalty-free music track

  REVISIONS
    • TWO (2) rounds of revisions included, each = one consolidated set of notes
    • Additional rounds or new requests: billed via written change order (§38.3)

  NOT INCLUDED (available by separate quote)
    • Additional shoot days, locations, or on-camera subjects
    • Extra deliverables, languages, or platform versions beyond those listed
    • Paid actors; talent the client does not supply releases for
    • Licensed stock footage; motion-graphics packages beyond simple lower-thirds

  OWNERSHIP / USE
    • Client receives the finished deliverables + perpetual license to use them
      on its website and social channels.
    • Videographer RETAINS raw footage and project files; may show the finished
      work in portfolio/reel (§38.6, Ch.39) unless otherwise agreed.

  TIMELINE: shoot [date] · first cut [date] · final on approval + payment
  ─────────────────────────────────────────────────────────────────────

FIGURE 38.4 is the document that makes §38.3 possible. Look at how much it protects both sides at once: the client knows exactly what they will get and when, and you know exactly where the job ends. The "NOT INCLUDED" block is not hostility — it is honesty, and clients respect it. It tells them the truth that everything is possible but nothing is free, and it turns every future "can you also…" from a tense favor into a simple, unemotional "sure, here's the quick add-on."

Finally, the money has a shape, and the shape protects you. Do not start work on a promise. The near-universal professional structure is a deposit to book the date (commonly a portion of the total, paid before you lift a camera), then the balance on delivery — sometimes with a milestone payment in between on larger jobs. Two rules ride along with it. First, the deposit is often non-refundable (or partly so) precisely because booking a date means turning down other work for it. Second — and this is leverage you should never casually give away — the final high-quality files are released only when the final payment clears. The client can review a watermarked or lower-resolution draft; they receive the master when they have paid for it. This is not distrust; it is the same logic as any trade, where you get the keys when the house is paid for.

🚪 Threshold Concept: the contract protects the relationship, not just you. Beginners avoid contracts because presenting one feels like accusing the client of being a future cheat — as if trust and paperwork were opposites. They are the reverse. A clear agreement is a gift to the client: it means no unpleasant surprises, no "I thought that was included," no ambiguity about what they are paying for. It lets a friendly working relationship stay friendly, because the money and the deliverables are settled and off the table. The professionals who never use contracts are not more trusting; they are the ones with the horror stories. Offer a contract not to protect yourself from the client, but to protect the good relationship with them. Once you see it that way, presenting one stops feeling awkward and starts feeling like exactly what it is: competence.

⚠️ Common Mistake: the handshake deal and the missing deposit. Two failures, one root cause — starting work on nothing but goodwill. The handshake deal ("we agreed on the phone, it's fine, they seem nice") has no shared record, so when memories drift — and they always drift, honestly and in the payer's favor — there is nothing to point to, and you eat the difference. The missing deposit is worse: you shoot the whole job, deliver it, and then try to collect from someone who now has what they wanted and no reason to hurry. Never begin production without a signed agreement and a deposit in your account. If a client won't sign a reasonable agreement or pay a reasonable deposit, that is not a paperwork problem — it is the client telling you, early and for free, exactly how the payment at the end is going to go.

🔗 Connection. The contract is where several threads you already know get decided in advance. The deliverables and their specs come straight from the client brief (Chapter 22, §22.1) and are exported to the platform specs of Chapter 36 (§36.3). Who owns the project files is the handoff-and-ownership question from Chapter 37 (§37.6) — answered here, before the shoot, not after. And the releases and music licensing clauses are the subjects of the next three sections. A contract is, in a sense, this entire book's worth of decisions written down before anyone rolls a camera.

🔄 Check Your Eye. 1. In one sentence, what is the real purpose of a contract — beyond "so I can sue if it goes wrong"? 2. What is a statement of work, and how does the "NOT INCLUDED" section protect both parties? 3. Why release the final master files only after final payment — and why is a deposit non-negotiable?

Check yourself

1. To make sure both parties share the same picture of the job — deliverables, price, timeline, ownership — so the dispute a contract would settle never arises. It protects the relationship by removing ambiguity.
2. The SOW spells out exactly what you'll deliver (which videos, lengths, formats, revision rounds) and what's excluded. "NOT INCLUDED" is honest, not hostile: the client knows precisely what they're getting, and you have a clear fence to point to when new requests arrive — turning favors into simple add-on quotes.
3. Releasing the master only on final payment keeps your leverage until you're paid; once the client has the deliverable, they have no incentive to pay quickly. A deposit protects you against a no-show or cancellation (you turned down other work for the date) and filters out clients who were never going to pay.

38.3 Scope creep and revisions

Now the payoff for that fence. Chapter 22 named this danger and deliberately left it for here (§22.6); this is where it gets its full treatment, because it is the single thing most likely to turn a profitable job into an unprofitable one.

Scope creep is the gradual, unbudgeted expansion of a project beyond what was agreed — extra deliverables, extra revisions, extra versions, "small" additions — each request individually reasonable-sounding, all of them together fatal to your time and your profit. It rarely arrives as one big unreasonable demand you could easily refuse. It arrives as a trickle of tiny ones: "could we also get a square version for Instagram?"; "can you try it with different music?"; "my boss wants to see one with the logo bigger"; "just one more small tweak." Each is easy to grant. Granted without limit, they are how a two-day job becomes a two-week one, entirely for free.

Understand why it happens and you will stop taking it personally. Clients are usually not trying to exploit you. They genuinely do not know the cost of what they ask, because the cost is invisible to them. "Just swap the music" sounds like a two-minute change; to you it can mean re-editing to a new track's rhythm, re-timing cuts, re-licensing, and re-exporting every deliverable. The gap between how small a change feels to the client and how much work it is for you is the exact space scope creep grows in. Add a natural desire to please and keep the client happy, and — if there is no written scope to point to — the trickle never stops.

The defense has three parts, and you already built the first one: a specific statement of work (§38.2). The second is a revision policy, and the key is to define what a "round" actually is.

FIGURE 38.5 — Is this request inside the fence? (the scope decision)

                    ┌─────────────────────────────────────┐
   Client asks  ──► │  Is it in the signed SOW's scope?    │
   for a change     └───────────────┬──────────────┬──────┘
                                    │ YES          │ NO
                                    ▼              ▼
                     ┌──────────────────────┐  ┌──────────────────────────┐
                     │ Is it a REVISION      │  │ It's a NEW REQUEST.       │
                     │ (refining what was    │  │ "Great idea — that's      │
                     │ agreed) within the    │  │ outside our current scope,│
                     │ included rounds?      │  │ so I'll send a quick      │
                     └──────┬─────────┬──────┘  │ CHANGE ORDER for it."     │
                            │ YES     │ NO(used  └──────────────────────────┘
                            ▼         │  up rounds)      │
                   ┌─────────────┐    └────────►─────────┘
                   │ Do it — it's │            ▼
                   │ the job.     │   ┌──────────────────────────┐
                   └─────────────┘    │ Bill it (change order):   │
                                      │ scope + price + new date. │
                                      │ Proceed ONLY once agreed. │
                                      └──────────────────────────┘

The decision in FIGURE 38.5 turns on a distinction worth memorizing: the difference between a revision and a new request. A revision refines the thing you were hired to make — "the client's name is spelled wrong," "this cut feels a beat too slow," "the color's a touch green." Those are fixes; they are the job, and your included rounds cover them. A new request is a different or additional thing — a new deliverable, a new version, a re-shoot, a change to the agreed concept. That is not a fix; it is new work, and new work has a price. Beginners blur the two and give away the new work as if it were revision. Professionals keep the line bright.

A "round" of revisions, defined properly, is one consolidated set of feedback — a single list of notes the client has gathered and sent together — not each individual comment as it occurs to them. This distinction alone saves you enormous grief. Insist, gently, on consolidated feedback ("send me all your notes in one list, ideally with timecodes"), because ten notes in one email is one round, while ten notes dribbled across ten texts over three days is you re-opening and re-exporting the project ten times. Chapter 30's locked cut exists partly for this reason: locking picture is a business boundary as much as a creative one.

The third defense is the change order — and it comes with the most useful sentence in the freelance business. When a client asks for something outside the scope, you never simply say "no," and you never silently swallow it. You say some version of: "That's a great idea. It's outside what we scoped, so let me send you a quick change order with the cost and the new timeline, and we'll get it going." A change order is a small written add-on to the SOW describing the new work, its price, and its effect on the deadline. It does something almost magical: it reframes every new ask from an emotional favor-conflict ("are they taking advantage of me? do I dare say no?") into a calm business transaction ("here is the thing, here is what it costs"). You are not the bad guy who refuses; you are the professional who says yes, and here's how. The client gets to decide whether the new thing is worth the price — which is exactly the decision that should be theirs to make.

✂️ In the Edit. Feel where scope creep actually lands, because it lands on you, at the timeline, at night. Every "small" out-of-scope ask is a real sequence of labor: re-opening the locked project (Chapter 30), re-cutting to accommodate the change, re-doing the color match (Chapter 31) if a shot changed, re-balancing the mix (Chapter 33) if the music moved, re-rendering the master, and re-cutting and re-captioning every platform deliverable (Chapter 36). The client sees "make the logo bigger"; the editor lives "re-export six versions and re-upload the captions." This is why the fence matters more to the person cutting than to anyone else: an unbounded scope does not fill the client's evenings. It fills yours. Protect the edit by protecting the scope.

⚠️ Common Mistake: unlimited revisions and the "final final v7." Two symptoms of the same missing boundary. Unlimited revisions — a contract that promises "revisions until you're happy" — sounds generous and is a trap, because a small number of clients are never quite happy, and "until satisfied" has no floor; you can lose weeks chasing a moving target for free. Always cap the included rounds and price the rest. The "final final v7" death spiral — a filename graveyard of final, final2, FINAL-use-this, final-v7-actually — is the scope problem wearing Chapter 37's naming problem as a costume: the versions pile up because the approval never got pinned down. Fix it with a defined lock: "two rounds, then the cut is approved; further changes are change orders." A job that cannot end is a job that cannot be profitable.

💡 Why It Works: the change order removes the emotion. The reason scope creep is so corrosive is that it feels personal — every unbudgeted ask forces a tiny, stressful choice between resentment (do the free work and stew) and confrontation (risk the relationship by refusing). The change order dissolves that choice by moving the decision to the client and grounding it in money instead of feelings. "Here's the cost of that change" is not a rejection and not a favor; it is information. It lets you keep saying yes to your client's ideas and stay in business, and it lets the client weigh each idea on its merits. Everyone stays friendly, because the awkwardness was never really about the request — it was about the unpriced favor, and you just gave it a price.

🎬 On Set (at the desk): write your revision policy and a change-order template. Before your next real job — or for one of your three portfolio projects, imagining a client — draft two short documents you can reuse forever. First, a revision policy in three sentences: how many rounds are included, what counts as one round (a consolidated set of notes), and what happens after they're used up. Second, a one-paragraph change-order template with blanks for the new work, the added cost, and the new delivery date. Constraint: keep each under 120 words and write it in plain language a non-expert client would find friendly, not lawyerly. Self-review: read them aloud as if you were the client — do they feel fair and clear, or defensive? Rewrite until a reasonable client would happily sign.

🔄 Check Your Eye. 1. What is the difference between a revision and a new request, and why does it matter to your income? 2. What is a "round" of revisions, properly defined — and why insist on consolidated feedback? 3. Give the one-sentence response to an out-of-scope request that keeps both the relationship and your time intact.

Check yourself

1. A revision refines the thing you were hired to make (a fix — covered by included rounds); a new request is a different or additional thing (new work — priced separately). Giving away new requests as if they were revisions is how a profitable job becomes unprofitable.
2. One consolidated set of feedback — a single list of notes sent together — not each comment as it arrives. Consolidated feedback means one re-edit and one re-export per round; dribbled notes mean re-opening and re-rendering the project over and over for the same "one round."
3. Some version of: "Great idea — that's outside our current scope, so let me send a quick change order with the cost and new timeline." You say yes, and here's what it costs, never a flat no and never a silent free favor.

38.4 Releases: model and property

We now arrive at the responsibility this whole book has been pointing toward — the one the license note at the very front of this book flagged and deferred to this chapter. It is the difference between a beautiful piece of footage and a beautiful piece of footage you are actually allowed to publish.

Return to the freelancer from this chapter's opening, the one whose testimonial was pulled because the person in it "never agreed to be in an ad." That is not a rare disaster. It is the single most common way a finished, paid-for, technically excellent video becomes unusable — and it is entirely preventable with one signed page.

A model release is a signed document in which a person who appears identifiably in your video grants you permission to use their image, likeness, and voice for the stated purposes. It is the piece of paper that converts footage of a person into footage you can legally and safely publish, sell, and put in an ad. A property release is its equivalent for places and things: permission from an owner to depict recognizable private property, a distinctive private location, or protected artwork or logos, in your published work. Together they are what people mean when they say "get your releases."

The idea that unlocks all of this — and that beginners consistently get wrong — is a single distinction:

🚪 Threshold Concept: consent to film is not consent to publish. Someone standing still and letting you point a camera at them has agreed to be filmed in that moment. They have not, by that act alone, agreed to appear in a commercial, be posted to a company's social media forever, or be edited into a story they never saw. Those are different permissions, and in most commercial contexts you need them in writing. The reflex to build is exactly like the reflex you built for room tone in Chapter 15: you get the release every single time, as a matter of routine, on the day, while the person is right in front of you — not because you distrust them, but because "I meant to get it later" is how footage becomes unpublishable. No release, no publish. Make the signature as automatic as pressing record.

Here is the model release you should adapt, keep, and carry (a fuller version is in Appendix I). It is deliberately plain; a release the signer cannot understand is doing half its job.

FIGURE 38.6 — A basic model release (adapt for your jurisdiction; not legal advice)

  ─────────────────────────────────────────────────────────────────────
  MODEL / APPEARANCE RELEASE
  ─────────────────────────────────────────────────────────────────────
  Project / production:  ______________________________________________
  Producer / company:    ______________________________________________

  I, ________________________ ("I" / "me"), grant [Producer] and its
  assigns the irrevocable right to record my name, image, likeness,
  and voice, and to use, edit, reproduce, and distribute that material —
  in whole or in part — in the above production and in related promotion,
  in any media now known or later devised, worldwide.

  I understand this material may be used for [ ] commercial  [ ] editorial
  [ ] internal  [ ] other: __________ purposes, and I waive any right to
  inspect or approve the finished use. I confirm I am doing this
  [ ] for good and valuable consideration  [ ] as a volunteer.

  I am 18 or older:  [ ] Yes   [ ] No — if No, a parent/guardian signs below.

  Signature: __________________________   Date: ______________
  Printed name: _______________________   Contact: ___________

  IF THE PERSON IS A MINOR — parent/legal guardian:
  I am the parent/legal guardian of the above minor and grant the rights
  above on their behalf.
  Signature: __________________________   Date: ______________
  Printed name (guardian): ____________   Relationship: _______
  ─────────────────────────────────────────────────────────────────────

Walk through why each part is there. The broad grant of use ("any media now known or later devised, worldwide") exists because you cannot always predict where a video will travel, and a release that only covered "the website" leaves you exposed when the client wants to run it as an ad. The purpose checkboxes matter because — as we will see — commercial and editorial uses are treated very differently, and a person is entitled to know which they are consenting to. The consideration line records that the signer got something in exchange (payment, or the experience, or simply "good and valuable consideration"), which in many jurisdictions helps make the agreement stick. And the minor's section is not optional: for anyone under the age of majority, a parent or legal guardian must sign, and you should treat filming minors with extra care and extra documentation, always.

Now, the honest complications — stated carefully, because this is exactly the territory where the law varies most and where "not legal advice" carries the most weight.

Commercial versus editorial use is the great divide. Using a person's identifiable image to sell or promote something — an ad, a testimonial, a branded video, anything commercial — almost always requires a signed release, and the consequences of not having one are serious. Using footage for genuine news, journalism, or documentary is treated differently in many jurisdictions, under doctrines of newsworthiness and public interest, and often does not require a signed release in the same way (Chapter 21's ethics of nonfiction, §21.5, live here too — a legal right to use footage is not the same as an ethical one). But the boundary between "editorial" and "commercial" is genuinely tricky, it varies by country, and the safe habit for anyone not doing hard journalism is simple: when in doubt, get the release. A signature costs you nothing and protects everything.

Public places, private property, and crowds each have their own texture. Filming in a truly public place is often permissible, but using an identifiable person's image from it commercially usually still needs their release. Private property — a shop interior, someone's home, a distinctive private building — is controlled by its owner, who can set conditions or refuse; that is what the property release covers, and what a location agreement formalizes for a shoot. Some public-seeming spaces (museums, many landmarks, transit systems, private "public" plazas) restrict commercial filming and require a permit. For crowds and events, you generally cannot get a signature from every face in a wide shot; the professional approach is notice — clear signage and announcements that filming is happening and footage may be used — plus individual releases for anyone featured, foregrounded, or identifiable as a "character" in the piece. And recognizable logos, artwork, and branded products in frame can raise trademark and copyright questions for commercial use, which is why controlled commercial shoots dress their sets carefully.

Property and location deserve a short template of their own, because the person who signs it is different from the model release's signer.

FIGURE 38.7 — A short property / location release (adapt; not legal advice)

  I, ____________________, am the owner or authorized manager of the
  property at ______________________________________. I grant [Producer]
  permission to film on/at this property on [date(s)] and to use the
  resulting footage — including recognizable features of the property —
  in the production named above and its promotion, in any media, worldwide.
  Any conditions (areas off-limits, hours, restoration, credit): __________
  Signature: __________________  Printed: __________  Date: __________

⚠️ Common Mistake: the verbal "sure, that's fine," and the release you meant to get later. Two versions of the same fatal shortcut. The verbal yes — "I asked and they said it was fine" — evaporates the moment the person changes their mind, moves away, or simply denies it later, and you have nothing to show for it; a friendly nod is not a grant of rights you can rely on. The release you meant to get later is worse, because "later" means chasing a signature from someone who has since left, gone quiet, or realized they can now say no while you have already built a whole video around them. Both mistakes share a cure: get it signed, on the day, before anyone leaves. Build releases into your shoot the way you build in room tone and a memory-card backup — as a step that simply always happens, so that "we forgot the release" becomes as unthinkable as "we forgot to press record."

♿ Accessibility & Inclusion: consent is part of respect, not just paperwork. A release is the legal floor; genuine, informed consent is the ethical standard, and it is inseparable from inclusive practice. Make sure the people you film actually understand how they will be shown — not just that they signed, but that they know what the video is, where it will run, and that they can be edited. Take extra care with anyone in a vulnerable position: minors (always a guardian's signature), patients, employees who may feel pressured to agree by a boss, or people sharing something painful on camera. Consent is also ongoing — if someone becomes uncomfortable, the professional and humane response is to listen, not to wave the signed form at them. Inclusive work means representing people with dignity and accuracy, casting and crewing without exclusion, and remembering that the person in your frame is trusting you with their face and their story. Treat that trust as seriously as you treat the exposure.

✂️ In the Edit. This is the cruelest place for a missing release to surface, and it happens constantly: you are deep in the edit, you build an entire sequence around one person's perfect soundbite or one striking face in the crowd, the piece finally works — and then you discover there is no signed release for them. Now the edit is a hostage. You either tear out your best material and rebuild around its absence, or you gamble on publishing footage you have no right to use. Neither is a good night. Everything you learned about shooting for the edit (Theme 3) includes this: the release is part of the coverage. Footage you cannot legally cut is not footage — it is a liability with a timecode. Get the paperwork on set, and the edit stays free.

🔗 Connection. Releases connect back and forward across the book. Consent begins on set, in how you direct and treat real people (Chapter 10, §10.3) — the release is the formal end of a relationship that starts with respect. The synthetic-media problem of Chapter 35 (§35.6) is this same principle at its sharpest edge: you must never use AI or VFX to put words in a real person's mouth or their likeness in a scene without their explicit consent — a deepfake of a real person without consent is the ultimate release violation. Specialty capture like drones (Chapter 25, §25.1) adds permits and airspace rules on top of releases. And every signed release belongs in your archive's 08_DOCS folder (Chapter 37, §37.5), because a video you cannot prove you have the rights to is a video you cannot safely reuse — or put on the reel you build in Chapter 39.

🎬 On Set: get (or draft) the releases for your three projects. Go through Project 1 (the talking-head), Project 2 (the documentary short), and Project 3 (the branded piece) and, for every identifiable person on camera and every private location, either get a signed release now or draft the one you would have gotten. Constraint: use the FIGURE 38.6 / 38.7 templates, and for any minor, note explicitly that a guardian must sign. Self-review: for each project, could you honestly publish it, sell it, and put it on your reel today with the rights you can prove? Every "no" is a signature to go collect — and a lesson in getting it on the day next time. File every signed release in that project's 08_DOCS folder.

🔄 Check Your Eye. 1. State the threshold idea in one line, and explain why letting you film someone doesn't settle it. 2. What is the difference between a model release and a property release, and who signs each? 3. Who must sign for a person under the age of majority, and why is "I'll get the release later" a trap?

Check yourself

1. Consent to film is not consent to publish. Standing still for a camera agrees only to being recorded in the moment; using that footage commercially — in an ad, a testimonial, a company's forever-posts — is a separate permission you generally need in writing.
2. A model release grants the right to use an identifiable person's image, likeness, and voice, signed by that person (or their guardian). A property release grants the right to depict recognizable private property or location, signed by the owner or authorized manager.
3. A parent or legal guardian must sign for a minor. "Later" is a trap because the person may leave, go silent, or simply change their mind once they can — and by then you've built a whole video around footage you may no longer have the right to use. Get it signed on the day.

38.5 Music and footage licensing (and copyright)

The other half of the freelancer's opening disaster — the muted audio — is a rights problem too, but pointed the other way. Releases are about the people and places you put into your video. Licensing is about the work of other creators you build into it: the music, the footage, the images, the fonts, the graphics, the sound effects. Almost none of that is yours by default, and understanding why is the difference between a video that is safe and a video that is a lawsuit or a takedown waiting to happen.

Start with the concept underneath everything. Copyright is the automatic legal right of a creator to control the copying, distribution, and use of their original work — a song, a film clip, a photograph, a font, a graphic, a piece of writing. Four facts about copyright do most of the work here, and each corrects a common and dangerous belief:

• Copyright is automatic. The moment someone creates an original work, it is generally protected — no © symbol, no registration, no publishing required. The song, the stock clip, the photo you found: assume it is copyrighted unless you have specific reason to believe otherwise.
• "Publicly available" is not "free to use." A track on a streaming service, a clip on a video platform, an image in search results — being able to access something is nothing at all like being allowed to reuse it. The entire internet is visible; almost none of it is yours.
• Using it without permission is infringement, and it carries real consequences — takedowns, muted or blocked videos, demonetization, channel strikes, and, in the worst cases, legal liability. When you do it in a client's video, you have handed them a liability, which is a fast way to never work for them again.
• Credit is not permission. "I'll just credit the artist" does not make unlicensed use legal. Attribution may be required by some licenses, but it never substitutes for one.

The way you use someone else's work legally is to get a license. Licensing is obtaining permission — a license — to use someone else's copyrighted work under stated terms, usually in exchange for money or in return for meeting conditions. The critical mental shift: a license is permission to use, not ownership. When you "buy" a music track for a video, you are almost never buying the song; you are buying a license to use it in certain ways. Read what those ways are.

FIGURE 38.8 — Where legal music, footage, and assets come from

  SOURCE                WHAT IT IS                        WATCH OUT FOR
  ────────────────────  ────────────────────────────────  ──────────────────────────
  Royalty-free library  subscription/per-track music &    "royalty-free" ≠ free; you
  (music, SFX, stock)   footage licensed for broad reuse   still license it; read the
                                                            tier (personal vs client)
  Licensed stock        per-asset or subscription footage, still has terms: territory,
  (footage/photo/SFX)   photos, sound effects              editorial-only vs commercial
  Creative Commons      free to use UNDER CONDITIONS       check the flavor: BY (credit),
  (CC)                  (attribution/non-commercial/etc.)  NC = NO client work, SA, ND
  Public domain         copyright expired or waived —      verify it truly is; a NEW
                        genuinely free                     recording of old music can be
                                                            copyrighted even if the tune isn't
  Commissioned /        you pay a composer/creator to      agree the RIGHTS in writing:
  original              make it for you                    do you own it or license it?
  Direct license        permission straight from the       popular music = expensive &
  from rights holder    rights holder(s)                   slow; needs TWO rights (below)
  ────────────────────────────────────────────────────────────────────────────────────
  You OWN what you shoot and make yourself. Everything else, you LICENSE — and keep the proof.

Two practical points about FIGURE 38.8 will save you the most trouble. First, "royalty-free" does not mean free. It is a licensing model — you pay once (or subscribe) and then owe no further per-use royalties — but you still have to obtain the license, and you still have to use the asset within its terms. This is the category most working video people rely on: subscription libraries of music, sound effects, and stock footage cleared for broad commercial reuse. It is Chapter 33's advice (§33.4) made concrete: the music bed under your edit comes from here, licensed and logged, not from a song you like.

Second, the license terms are the whole game, and they vary: what you may use it for (personal vs commercial vs broadcast), where (which platforms, which countries), how long (a perpetual license vs a term that expires), how many projects (one project vs unlimited), and whether attribution is required. A track licensed for your personal vlog may not be licensed for a paying client's ad; the same file, different use, different rules. So the discipline is simple and non-negotiable: read the license for the actual use, and keep the proof. The license file or receipt goes into the project's 03_MUSIC-SFX folder and travels into the archive (Chapter 37, §37.5), because the day a platform's system flags your video, your license is the thing that clears it.

That platform system deserves naming, because it surprises people. Major platforms automatically scan uploads against databases of copyrighted music and footage (the best-known such system is YouTube's Content ID). If it matches your audio to a copyrighted track, it can mute, block, demonetize, or place a claim on your video automatically — sometimes even when your use is legitimately licensed, which is exactly why you keep your license records to dispute a false claim. Use unlicensed popular music and the outcome is worse and deserved: the video is muted or taken down, the account collects strikes, and enough strikes end a channel. "It's just for a client, it won't be that public" is no defense — client videos get flagged too, and now the embarrassment and liability are the client's.

One trap people forget entirely: fonts and graphics are licensed too. The typeface in your lower-third (Chapter 34) has a license that may or may not permit commercial use; a stock graphic, template, or motion-graphics preset has terms. Treat every element you did not create yourself as something to clear, not just the obvious music and footage.

And finally, the question the contract must answer: who is responsible for clearing what? The standard, sane arrangement — which your agreement (§38.2) should state plainly — is that you clear and warrant the assets you bring (your music, your stock, your fonts), and the client warrants that they own or have licensed anything they supply (their logo, their product shots, footage from their previous vendor). Put it in writing, so that when the client hands you a "song our founder loves" or "footage from our last agency," the contract already says whose problem its clearance is.

🔬 The Tech: how copyright actually works (skippable, but it demystifies the scary parts). Skip this and you lose nothing operational — the rule "license everything you didn't make, and keep the proof" is enough to keep you safe. But the mechanics explain why. Two rights live in every piece of music: the composition (the song itself — melody and lyrics, owned by songwriters/publishers) and the sound recording or master (a specific recorded performance, owned typically by a label). To use a famous recording in your video you need both a sync license (to synchronize the composition to picture) and a master-use license (for that recording) — which is why licensing a hit song is so expensive and slow, and why royalty-free libraries, which bundle both rights into one simple license, exist. Work-for-hire vs licensing: when you create something, who owns it depends on your contract and jurisdiction — an employee's work often belongs to the employer, while a freelancer usually owns what they create and licenses it to the client unless the contract transfers ownership (a "buyout"); this is the §38.2 ownership clause seen from the copyright side. Fair use / fair dealing is not the shield people think it is: many jurisdictions have a narrow, fact-specific exception allowing limited use for things like criticism, commentary, news, or parody — but it is a defense, decided case by case, not a blanket permission, and it varies wildly by country (some use "fair dealing" with a fixed list of purposes; some have neither). Relying on "it's fair use" for commercial work without advice is how people end up in the disputes they were sure they'd win. Creative Commons is a family of standardized licenses creators apply voluntarily to let others use their work under set conditions — BY (credit required), NC (non-commercial only — unusable in client work), SA (share-alike, like this very book's CC BY-SA), ND (no derivatives). Public domain is work whose copyright has expired or been waived — genuinely free — but terms vary by country (often the creator's life plus a number of years), and beware that a new recording or edition of a public-domain work can carry its own fresh copyright. None of this is legal advice; it is the map that tells you when to stop guessing and ask a professional.

⚠️ Common Mistake: "I found it online, so it's basically free." This one belief causes more takedowns than any other, and it comes in a dozen costumes: "it was on a free download site," "it's only for a client so it's not really public," "I bought the song on a store so I can use it in a video," "there was no copyright symbol," "I'll credit them." Every one is wrong. Finding something does not license it; buying a song for personal listening does not license it for use in a video; the absence of a © changes nothing (copyright is automatic); and credit is not a license. Purchasing access and purchasing usage rights are different transactions. The only safe path is a real license for the actual use, from a legitimate source — and the proof kept on file. When you are tempted to skip it "just this once, it's a small project," remember that automated systems do not care how small your project is.

🔗 Connection. This section is the full payoff of a promise made twice already. Chapter 33 (§33.4) told you the music bed must be "properly licensed" and pointed here for what that means; now you know. Chapter 37 (§37.5) had you archive the license files alongside the music in 03_MUSIC-SFX; now you know they are the evidence that clears a claim and permits a re-use. And this is the "music and footage" half of the responsible-use note at the front of this book: do not use copyrighted music, stock footage, fonts, or graphics without a license — "found it online" is not a license. The specific sources — reputable royalty-free libraries, Creative Commons repositories, public-domain collections — are catalogued in Appendix J.

🔄 Check Your Eye. 1. Why is a song you can stream or a clip you can find online almost never "free to use," and what does "copyright is automatic" mean? 2. What does "royalty-free" actually mean — and why is it not the same as "free"? 3. You licensed a track for your personal channel; now a client wants it in their paid ad. Are you covered? Why or why not?

Check yourself

1. Access is not permission: being able to see, stream, or download something says nothing about your right to reuse it, and copyright is automatic — an original work is protected the moment it's made, with no symbol, registration, or notice required. Assume everything is copyrighted unless you have specific reason to know otherwise.
2. "Royalty-free" is a licensing model: you pay once or subscribe and then owe no further per-use royalties. You still must obtain the license and use the asset within its terms. It means "no ongoing royalties," not "no cost and no rules."
3. Not necessarily — probably not. A license is tied to a specific use; a personal-use tier usually excludes commercial/client work. The same file in a paid ad likely needs a higher (commercial) license. Read the license for the actual use and upgrade it before using it in the client's video.

38.6 Getting and keeping clients

Everything so far protects a job you already have. This last section is about where the next job comes from — and the answer surprises people, because it is almost never advertising. (The reserved terms for building your public presence — your reel, your niche, your personal brand — belong to Chapter 39, and the career shapes of freelance, in-house, and agency to Chapter 40; here we cover the relationship craft that feeds them all.)

Ask working freelancers where their work actually comes from and you hear the same ranking, over and over. At the top, by a wide margin: referrals and repeat business. A happy client who hires you again, or who tells a peer "you should call the person who made our video," is worth more than any ad you could buy — because they arrive pre-trusted, having been sold by someone with no reason to lie. Below that: your existing network, a body of visible work that lets people find you (the reel and portfolio of Chapter 39), and being genuinely findable when someone goes looking. Near the bottom, least effective of all: cold outreach to strangers. The practical consequence is profound and freeing: the best marketing you can do is to make a current client so happy they become your next three clients. Which means the business skills in this chapter — pricing fairly, contracting clearly, defending scope without friction, delivering what you promised on time — are not separate from "getting clients." They are how you get clients, because they are what makes a client refer you.

It helps to see a whole job as a repeatable lifecycle, because every stage is a chance to earn the referral or lose it.

FIGURE 38.9 — The client lifecycle (every stage earns the next job, or loses it)

  INQUIRY  ─►  DISCOVERY  ─►  PROPOSAL  ─►  CONTRACT  ─►  PRODUCTION
  (they      (understand    (quote +      + DEPOSIT     (deliver what
   reach      the real       SOW; §38.1    (§38.2)       you promised,
   out)       goal; Ch.22)   –38.2)                       on time)
                                                              │
      ┌───────────────────────────────────────────────────────┘
      ▼
  DELIVERY  ─►  INVOICE  ─►  FOLLOW-UP  ─►  ┌─ REPEAT WORK ──┐
  (files on     (get paid;   (check in,     │  or RETAINER   │ ─► REFERRALS
   final        net-15/30)   thank, ask)    └─ (ongoing) ────┘
   payment)                                  the goal: turn ONE job into a RELATIONSHIP

Two moments in that lifecycle are where money is most often won or lost, so they get special attention.

The first is getting paid, which does not happen by hoping. Send a real invoice — a clear document with your details, the client's, an invoice number, the itemized work, the total, the payment terms (commonly net-15 or net-30, meaning payment is due within 15 or 30 days), and how to pay. Set the terms in the contract so the invoice holds no surprises. Your deposit (§38.2) has already de-risked the front of the job; for the back, the discipline is to follow up on late payment without embarrassment — a polite, firm reminder on the due date, then again after, is normal professional practice, not rudeness. Late-payment fees, stated in the contract, give a slow payer a reason to prioritize you. And the master-on-final-payment rule from §38.2 is your quiet backstop: the client's motivation to pay is strongest right before they receive the files they are waiting for.

The second is keeping the client, which is where the real money lives, because it is far cheaper to keep a client than to find a new one. Keeping them is mostly about being easy to work with — responsive, reliable, calm when a problem arises, honest about what you can and cannot do, and consistent about hitting the dates you promised. It is Chapter 22's "managing expectations" (§22.6) extended across the whole relationship: under-promise and over-deliver, never the reverse. The highest form of a kept client is the retainer — an ongoing arrangement where a client pays a set amount monthly for a set amount of work (a video a month, a package of social clips). A retainer is close to the freelancer's dream, because it converts the feast-and-famine of project work into predictable, recurring income and a relationship deep enough that scope and trust are rarely in question. You do not start there; you earn your way to it by being the person a client stops wanting to replace.

💡 Why It Works: trust compounds, and it is the only asset that does. Gear depreciates. Software changes. A specific technique goes out of style. The one thing in a video career that appreciates is a reputation for being reliable and good to work with, because every satisfied client is a node in a network that refers more clients, who refer more still. A single well-handled job — fair price, clear contract, scope defended without friction, delivered on time, invoice paid without drama — does not end when you deliver; it seeds the next several jobs. This is why the "boring" business discipline in this chapter is not a tax on the creative work but an investment in the career: professionalism is literally how the work compounds into a living.

🔗 Connection. This section hands directly to the next two chapters. The visible body of work that lets referrals and searches find you — the demo reel, the portfolio, the niche, the personal brand — is all of Chapter 39, and it is why you cleared the rights in §38.4–38.5: you can only show client work on a reel if your contract and releases let you. And the larger shape of the working life these clients add up to — freelance versus in-house versus agency, how rates and roles grow — is Chapter 40. The relationship craft here is the engine; those chapters are the vehicle it drives.

🎬 On Set (at the desk): build your business toolkit. Draft the three reusable documents that will run your client work for years: a one-page proposal/quote (start from FIGURE 38.2), a simple invoice (your details, client details, invoice number, itemized work, total, terms, how to pay), and a short, warm follow-up message to send a week after delivery ("Thanks again — hope it's performing well. If it's useful, I'd be grateful for a referral, and I'd love to help with your next one."). Constraint: make all three so clear and professional that you would feel confident sending them to the most impressive client you can imagine. Self-review: does the whole set make you look like a business, or like someone doing a favor? Polish until it is unmistakably the former.

🔄 Check Your Eye. 1. Rank the real sources of freelance work, and name the single most effective one. 2. What is "net-30," and what two mechanisms in this chapter protect you against not being paid? 3. What is a retainer, and why is it close to the freelancer's ideal?

Check yourself

1. Referrals and repeat business first (by far), then your network and a visible body of work that makes you findable, with cold outreach to strangers least effective. The most powerful source is a happy existing client who refers you or hires you again.
2. "Net-30" means payment is due within 30 days of the invoice. You're protected front and back by the deposit (§38.2, taken before work starts) and by releasing the final master only on final payment (§38.2), plus contractual late fees and disciplined follow-up.
3. A retainer is an ongoing arrangement where a client pays a set amount each month for a set amount of work. It's ideal because it converts unpredictable project income into recurring, predictable income and a deep, trusting relationship — the opposite of feast-and-famine.

Production Checkpoint

All three projects — sort out the business behind them. This is not a shooting assignment; it is the professional work that makes everything you have built across this book publishable, sellable, and safe. You have three finished (or nearly finished) videos — the talking-head, the documentary short, and the branded piece. It is time to make each one legally and financially real.

For each of your three projects, do all three of the following:

1. Releases. For every identifiable person on camera and every private location, get a signed model or property release — or, if that is genuinely impossible now, draft the exact release you would have gotten, using the FIGURE 38.6 / 38.7 templates. For anyone under the age of majority, note that a guardian must sign. File each release in that project's 08_DOCS folder (Chapter 37).
2. Licensing. Confirm that every piece of music, stock footage, font, and graphic in each project is properly licensed for the way you are using it — and that you have the license file or receipt saved in 03_MUSIC-SFX. Anywhere you cannot prove a license, replace the asset with a properly licensed or public-domain one (Appendix J) before you would publish.
3. Price. For each project, write the price you would charge a real client to make it — built up honestly from your day-rate estimate across all three stages plus hard costs (the FIGURE 38.1 / 38.2 method). Then write one sentence on why that number: which pricing model you used and what it covers.

Why this matters: a video you cannot prove you have the rights to is a video you cannot publish, sell, or even safely put on the reel you will cut in Chapter 39 — no matter how good it looks. And a maker who cannot name a fair price for their own work is not yet in business, however skilled they are. This checkpoint turns "three videos I made" into "three assets I own the rights to and know the value of." Do it now, while all three are fresh — it is the last thing standing between the craft you have learned and the career it can become.

Summary

• Pricing is a deliberate craft, not a guess. Three models answer "what is it worth?" from three directions:

• A sustainable rate covers the iceberg, not the shoot day: all-stage time (the edit is longest), hard costs, overhead, the unbilled days between jobs, taxes, and margin. Put the number in a written quote.
• A contract makes both parties share one picture of the job; it protects the relationship, not just you. Nail down parties, deliverables, price & schedule, timeline, revisions, ownership/rights, usage, releases, licensing, cancellation, and late payment. Not legal advice — jurisdiction varies; use a lawyer for anything significant.
• The statement of work (SOW) is the fence: exactly what you deliver (videos, lengths, formats, revision rounds) and what's not included. Take a deposit to book; release the master only on final payment.
• Scope creep is unbudgeted expansion, one "small" ask at a time. Defend with the SOW, a capped revision policy (a "round" = one consolidated set of notes), and the change order: "Great idea — that's outside scope, so here's a quick quote for it." Distinguish a revision (a fix, included) from a new request (new work, billed).
• Consent to film is not consent to publish. Get a model release for every identifiable person (guardian signs for minors) and a property release for private locations — on the day, in writing. Commercial use essentially always needs one; when in doubt, get it.
• Copyright is automatic; "publicly available" and "I'll credit them" are not licenses. License everything you didn't make — music, footage, fonts, graphics — for the actual use, and keep the proof (it clears platform claims like Content ID). "Royalty-free" means no ongoing royalties, not free.
• Clients come from referrals and repeat business far more than advertising — so clean pricing, contracts, scope, and delivery are your marketing. Get paid with real invoices, deposits, and follow-up; grow toward the retainer.

Spaced Review

Retrieval from two earlier chapters that set this one up — the planning of Chapter 16 and the commercial work of Chapter 22. Answer before you check.

1. (Chapter 16) What is a budget (§16.5), and how does the budgeting you learned in pre-production relate to the pricing and quote you build in this chapter?
2. (Chapter 16) How is a treatment (§16.1) different from this chapter's statement of work — one describes the film you want to make, the other describes… what?
3. (Chapter 22) How does the client brief (§22.1) — the business goal, audience, and key message — make value-based pricing possible in a way that a vague "make us a video" request never could?
4. (Chapter 22) Chapter 22 named managing the client's expectations (§22.6) but deferred scope creep to here. Connect them: how is a defended scope the ultimate form of managing expectations?

What's Next

Your three projects are now delivered (Chapter 36), archived beyond loss (Chapter 37), and — as of this chapter — priced, contracted, released, and licensed: they are genuinely yours, and you could hand any of them to a client, publish them, or sell them without a rights problem hanging over you. You have crossed the line from someone who makes videos to someone who runs a video business. What remains is to make that business findable — to turn three finished, rights-clear videos into the single thing that brings the next client through the door. In Chapter 39 you build your demo reel and your brand: you will curate your best sixty to ninety seconds from these three projects (which you can now legally show, precisely because you did the work of this chapter), cut it with the pacing and music skills you have earned, and put it somewhere the referrals of §38.6 can send people. The craft made the videos; the business protected them; now the reel goes and gets the work.