Case Study 2: One Job, Start to Finish — Quoting, Contracting, and Delivering a Testimonial Without Scope Creep

This is a constructed shoot-along, run in the product-and-talking-head setups (§3 of the style guide): a small-business testimonial with product B-roll — the kind of job a phone-first reader can shoot and a pro-track reader will quote every week. Where Case Study 1 was an autopsy of a job that failed on all four business axes, this is the same class of job run correctly, so you can watch every document do its work in real time. The business is invented; the artifacts are models to adapt, not legal templates to copy blindly. Nothing here is legal advice, and the law varies by jurisdiction.

The brief and the constraints

A small coffee roastery — call it Riverside Roastery — wants a short video. This is the product-on-a-table plus talking-head job in its most common commercial form: a testimonial. We will follow it from the first email to the final paid invoice, treating the business as the production it is.

Before any camera, the goal is understood in the Chapter 22 sense — a real client brief (§22.1), not just "make us a video." A short discovery call surfaces it:

• Business goal: bring new customers through the door and sell more bags of beans online.
• Audience: local coffee lovers, and out-of-towners who discovered the roastery once and want to reorder.
• Key message: "Small-batch coffee, roasted by hand by people who care — worth the trip and worth the reorder."
• Call to action: Visit the shop (local) / Order online (everyone).
• Constraints: modest budget; the owner can give one morning before opening; wants it for the website homepage and Instagram; needs it in three weeks for a seasonal push.

That discovery call is itself a business skill. It costs nothing, it makes the client feel heard, and — crucially — it is what lets the job be priced against value rather than guessed at. A video that "brings new customers and drives online orders for a seasonal push" is worth more to this business than "a morning of filming," and understanding the goal is what earns the right to price it accordingly.

⚙️ Deal Terms Box: the shape of this job. The business equivalent of a Settings Box — the starting terms, to adjust per client and market. (Figures are illustrative for this constructed job, not universal rates.)

Term	This job	Why
Pricing model	project rate, built from a day-rate estimate	client wants one predictable number
Deliverables	1× 80–100s hero (16:9) + 1× <60s vertical (9:16) + captions	website + Instagram, from the brief
Shoot	one half-day (pre-open morning), one location, owner + product	the owner's real constraint
Music	one licensed royalty-free track (line item)	legal, cheap, clears instantly (§38.5)
Revisions	two rounds included; extra = change order	the scope fence (§38.3)
Ownership	client gets deliverables + license; freelancer keeps raw + project	standard; enables reel (Ch.39)
Payment	50% deposit to book · balance on delivery · net-15	protects both ends (§38.2)
Releases	owner + any featured staff/customers; location covered	it's a commercial ad (§38.4)

Phase 1 — The quote

The freelancer does not name a number on the call. They say, "Let me put together a quick quote and send it over today" — which buys the time to price properly and delivers a professional artifact instead of a nervous guess.

The internal math (never shown to the client, but the backbone of the number) is a day-rate estimate across all three stages: roughly half a day of pre-production (planning, a shot list, coordinating the morning), a half-day shoot, and — the part beginners forget — about a day and a half of post (edit, color, sound, captions, two deliverables). Add the hard cost of the music license. Add margin. That internal figure becomes a single confident project rate on the quote.

FIGURE CS2.1 — The quote sent to the client (day 1)

  ─────────────────────────────────────────────────────────────────────
  [FREELANCER / STUDIO]                                  QUOTE #2026-021
  [email · phone]                                        Date: [day 1]
                                                          Valid: 30 days
  Prepared for: Riverside Roastery
  Project: Customer/owner testimonial video for website + Instagram
  ─────────────────────────────────────────────────────────────────────
  ITEM                                            QTY      RATE     AMOUNT
  Pre-production (plan, shot list, coordinate)    0.5 day  [rate]   [   ]
  Production (half-day shoot: owner + product)    0.5 day  [rate]   [   ]
  Post (edit, color, sound, captions, 2 cuts)     1.5 day  [rate]   [   ]
  Licensed music track (royalty-free)             1        [cost]   [   ]
  ─────────────────────────────────────────────────────────────────────
                                                        SUBTOTAL     [   ]
                                                        TOTAL        [   ]

  INCLUDED:  1× 80–100s hero video (16:9, 1080p) · 1× vertical cut-down
             (<60s, 9:16) · captions (.srt) for each · TWO revision rounds.
  NOT INCLUDED (separate quote): extra shoot time/locations/subjects,
             additional deliverables or platform versions, paid actors,
             licensed stock footage, motion-graphics beyond simple lower-thirds.
  PAYMENT:   50% deposit to book the shoot date · balance on delivery · net-15.
             Final master files released on final payment.
  ─────────────────────────────────────────────────────────────────────

Notice the three quiet defenses already in the first document the client sees. The line items across all three stages teach the client, gently, that the edit is real work — so the price is legible, not arbitrary. The INCLUDED / NOT INCLUDED block draws the scope fence before anyone leans on it, which is what will make Phase 5 painless. And the payment terms put a deposit up front and the master behind final payment, so the freelancer is protected at both ends. The client reads a professional. Good clients relax when they see this; the number is fair, itemized, and confident.

Phase 2 — The contract and the SOW

The owner replies: "Looks great, let's do it." The freelancer does not start planning the shoot. First, the agreement — because the deposit and the scope live here, and work begins only when both are in place.

The contract is short and plain (a fuller version would be a lawyer-reviewed template for the freelancer's region — this is a model). Its heart is the statement of work, lifted almost verbatim from the quote's INCLUDED / NOT INCLUDED so the two documents cannot contradict each other.

FIGURE CS2.2 — The Statement of Work inside the signed agreement

  STATEMENT OF WORK — governed by the Agreement dated [day 3]
  Project: "Riverside Roastery" testimonial + social cut
  ─────────────────────────────────────────────────────────────────────
  DELIVERABLES
    1. One (1) hero testimonial — 80–100 sec, 16:9, 1080p, H.264
    2. One (1) vertical cut-down — under 60 sec, 9:16
    3. Caption file (.srt) for each deliverable
  SCOPE OF PRODUCTION
    • One half-day shoot (up to 4 hrs), pre-opening, one location
    • On camera: the owner; product/roastery B-roll
    • Freelancer supplies ONE licensed royalty-free music track
  REVISIONS
    • TWO (2) rounds; each = one consolidated set of notes
    • Further rounds / new requests: written change order
  NOT INCLUDED (separate quote): extra days/locations/subjects, extra
    deliverables or versions, paid actors, licensed stock, larger graphics
  OWNERSHIP / USE
    • Client: the finished deliverables + perpetual license to use them
      on its website and social channels
    • Freelancer: RETAINS raw footage + project files; may show finished
      work in portfolio/reel unless otherwise agreed
  RESPONSIBILITY: Freelancer licenses the music and warrants it. Client
    warrants it owns/licenses any logo or assets it supplies.
  TIMELINE: shoot [day 8] · first cut [day 13] · final on approval + payment
  ─────────────────────────────────────────────────────────────────────

The owner signs and pays the deposit. Only now — with a signed scope and money in the account — does the freelancer touch a camera-adjacent task. Two things in FIGURE CS2.2 will matter enormously later and cost nothing now: the revision clause (two rounds, a round defined as a consolidated set of notes) and the responsibility line (the freelancer clears the music; the client warrants its own logo). Each is one sentence. Each prevents a specific future fight.

The pattern to absorb: the quote and the SOW say the same thing twice, on purpose. The quote sells the job and the contract governs it, but their scope language is identical, so there is never a gap between "what we discussed" and "what we signed." Copy your INCLUDED / NOT INCLUDED straight across.

Phase 3 — The shoot, and the releases

The morning of the shoot, the freelancer arrives with a shot list (the value of pre-production, Chapter 16) and something most beginners forget until it is too late: a small stack of release forms and a pen. Getting the releases is treated as part of the setup, as routine as checking audio levels.

The shoot itself is the product-and-talking-head craft from across the book: the owner seated near the window (natural key, Chapter 13), a lavalier and a shotgun for two-mic safety (Chapter 19), clean room tone recorded (Chapter 15), and a set of product B-roll — beans pouring, the roaster turning, hands scooping, steam off a fresh cup — shot as sequences the edit can actually use (Chapter 20). But this is a business case study, so we hold on the business move: the paperwork.

FIGURE CS2.3 — Releases collected on the shoot day (filed to 08_DOCS same day)

  WHO / WHAT                    RELEASE                 SIGNED BY
  ────────────────────────────  ──────────────────────  ─────────────────────
  The owner (on camera)         model / appearance      the owner
  A staff member in B-roll      model / appearance      that staff member
   (recognizable, foreground)
  A customer glimpsed in deep   — (not identifiable /    notice sign posted at
   background, out of focus      not featured; venue      the door: "filming in
                                 is private + controlled) progress today")
  The roastery interior         property / location     the owner (also the
   (private property)                                     property authority)
  The roastery's logo (on bags) client-supplied asset    covered by SOW
                                                          responsibility line
  ─────────────────────────────────────────────────────────────────────────
  Rule applied: every IDENTIFIABLE, FEATURED person signs, ON THE DAY.
  Consent to film ≠ consent to publish — the signatures make it publishable.

Two judgment calls in FIGURE CS2.3 are worth naming. The staff member who appears recognizably in the B-roll signs a release, because "featured and identifiable" is the test, not "is the main subject." The customer who drifts through the soft-focus deep background is a different case — not featured, not identifiable, on private property the owner controls, with a notice posted — so an individual signature is impractical and the notice covers the situation; but the moment the edit had featured that customer, a signature would have been mandatory. This is exactly the release triage the chapter teaches, made real. Every signed form is photographed and filed to the project's 08_DOCS folder that same afternoon, while the freelancer still remembers who is who.

The habit that separates this job from Case Study 1's disaster: the release is coverage. It is gathered on the day, in the room, with the people present — not chased weeks later when the edit is already built around someone who has since gone quiet. Ten seconds a signature, and the footage is yours to publish forever.

Phase 4 — Licensing the music

Back at the desk, the edit comes together. When it is time for the music bed (Chapter 33, §33.4), the freelancer does the thing that Case Study 1's freelancer did not: they license it properly, and it is easier, not harder.

They pull a warm, unobtrusive track from the royalty-free library they subscribe to — a track cleared for commercial client use — and, before dropping it on the timeline, they check the license tier and save the license file to 03_MUSIC-SFX.

FIGURE CS2.4 — The music, licensed and logged

  TRACK:     "[library track name/ID]"
  SOURCE:    [Royalty-free subscription library]
  LICENSE:   Commercial / client use · single project · perpetual · worldwide
  ATTRIBUTION REQUIRED?  [per library terms — recorded either way]
  LICENSE FILE:  saved to  03_MUSIC-SFX/LICENSE_[track-id].pdf
  ─────────────────────────────────────────────────────────────────────
  Why this matters later:
   • It clears the platform's automated check (Content ID) — no mute, no block.
   • If a FALSE claim ever appears, the saved license is the proof to dispute it.
   • It archives with the project (Ch.37) so the piece can be re-cut / reused.

The check the freelancer runs before committing to the track is the one from §38.5: what use (commercial/client — yes), where (website + Instagram — yes), how long (perpetual — yes), how many projects (this one — yes), attribution (noted either way). The whole thing takes two minutes and costs a fraction of the fee already budgeted as a line item. When the client later uploads the video, the audio plays, because the music was legal from the first drop. The contrast with Case Study 1 is the entire point: the legal path was the cheap, fast, frictionless one all along.

Phase 5 — The revision request that could have been scope creep

The first cut goes out on schedule. The owner loves it, and sends back one consolidated list of notes — one round, one email, exactly as the SOW defined it:

1. "Fix the spelling of our roaster's name in the lower third."
2. "The middle drags a little — can you tighten it?"
3. "The color feels slightly too warm on the beans."

The freelancer handles all three without a second thought, because every one is a revision — a fix to the thing they were hired to make (§38.3). The name spelling, the pacing, the grade: these refine the agreed deliverable, and they are squarely inside the two included rounds. This is the job.

Then, in the same email, comes a fourth request — and this is the hinge the whole case study is built to show:

4. "This is great! Could we also get a square version for our feed, and a longer three-minute cut for the website's About page that goes into our history? Oh, and my business partner wants a version set to a different song."

Here is where Case Study 1's freelancer said "sure" three times and lost a week. Here is where this freelancer reaches for the sentence that saves freelance careers. Requests 4a (a new square deliverable), 4b (a whole new three-minute video — a different piece entirely), and 4c (a re-edit to a new track) are new requests, not revisions. None is in the SOW. So the reply is warm, fast, and unmistakably a yes-and-here's-the-cost:

FIGURE CS2.5 — The reply that defuses scope creep (and the change order it triggers)

  "Love that you're thinking about the feed and the About page — great ideas,
   and easy to do. Those are a little beyond what we scoped (the hero + the
   vertical cut), so I've put together a quick change order below so you can
   decide what's worth it. No pressure to take all of it — just pick what helps.

   Meanwhile I'm applying your first three notes now and you'll have the
   updated hero + vertical tomorrow as planned."

  ── CHANGE ORDER #1 — governed by the Agreement dated [day 3] ──────────
   NEW WORK                                        ADDED COST   NEW TIMELINE
   4a. Square (1:1) cut of the hero, <60s          [rate]       +1 day
   4b. NEW 3-min "our history" video (About page)  [quote]      +[days]; new shoot?
   4c. Alt version cut to a client-supplied track  [rate]       +0.5 day; client
                                                                 must supply a
                                                                 LICENSED track
   Proceed on written approval of the items you choose.
  ─────────────────────────────────────────────────────────────────────

Look at everything FIGURE CS2.5 accomplishes at once. It says yes to the client's creativity (no bruised relationship). It prices the new work so the client — not the resentful freelancer — decides what is worth doing. It quietly flags that 4b is not a tweak at all but a whole new production that may need its own shoot (managing the expectation before it becomes a fight). And on 4c it hands the licensing responsibility back where the contract put it: if the partner wants a specific song, the client must supply a licensed track, because an unlicensed favorite would get the video muted — the freelancer will not repeat Case Study 1's mistake on the client's behalf.

The owner reads the change order, decides the square cut (4a) is worth it, drops the three-minute history piece for now ("let's do that next quarter"), and abandons the alternate-song idea once they learn their partner's favorite pop track can't be legally used. The freelancer picks up a paid extra deliverable, the client gets exactly what serves them, and nobody is annoyed with anybody. That is what a defended scope buys: not fewer client ideas, but client ideas that pay.

The move to internalize: you almost never say "no." You say "yes, and here's the change order." The client's enthusiasm is good for business; you simply route it through a document that turns each new idea into a priced choice they get to make. Scope creep dies not by refusing clients but by pricing them, kindly.

Phase 6 — Delivery, invoice, and the follow-up

The second round (the square cut plus any final polish) comes back approved. The job locks. Now the last business moves, which are where the money actually lands and the next job is seeded.

The freelancer sends the final invoice — and only then, on final payment, releases the high-quality master files (per the SOW). The deposit covered the front; this collects the back.

FIGURE CS2.6 — The final invoice (sent on delivery)

  ─────────────────────────────────────────────────────────────────────
  [FREELANCER / STUDIO]                                INVOICE #2026-021
  Bill to: Riverside Roastery                          Date: [day ~15]
                                                        Due: net-15
  ─────────────────────────────────────────────────────────────────────
  DESCRIPTION                                                     AMOUNT
  Testimonial video package (hero 16:9 + vertical 9:16 + captions) [   ]
  Change Order #1 — square (1:1) cut                               [   ]
  ─────────────────────────────────────────────────────────────────────
                                                        SUBTOTAL   [   ]
                                        Less deposit paid [day 3]  [ - ]
                                                    BALANCE DUE    [   ]
  PAY BY: [bank transfer / link] · Ref: INV-2026-021
  Thank you! Final master files delivered on receipt of payment.
  ─────────────────────────────────────────────────────────────────────

Payment clears; the master, its captions, and the deliverables go to the client (Chapter 36's platform-correct exports). The project — footage, project file, releases, music license, master, invoice — is archived with 3-2-1 backup (Chapter 37), which means it can be reopened, re-cut, and legally reused a year later, and pulled for the freelancer's reel (Chapter 39) because the SOW reserved that right.

One week later, the freelancer sends a short, warm follow-up — the cheapest, highest-return marketing there is:

"Thanks again — the piece looks great on the homepage. Hope it's helping with the seasonal push! If it's useful to anyone you know, I'd be grateful for the referral, and I'd love to help with that About-page history video next quarter whenever you're ready."

That message does three things: it checks that the client is happy (catching any problem early), it opens the door to a referral (the top source of new work, §38.6), and it plants the seed of repeat business (the three-minute video, deferred, not lost). A single well-run job has now become a relationship — which is the whole game.

Discussion questions

1. The freelancer refused to name a price on the discovery call, promising a written quote instead. What does that one choice protect, and what would have been risked by blurting a number to be agreeable?
2. The quote and the SOW carry identical INCLUDED / NOT INCLUDED language on purpose. Why is that redundancy a feature and not sloppiness? What goes wrong when the sales pitch and the signed scope drift apart?
3. In FIGURE CS2.3, the recognizable staff member signs a release but the soft-focus background customer does not. Defend that line. Where exactly does "not featured" become "featured," and what would have flipped the customer into needing a signature?
4. Request 4 mixed a real revision (implicitly) with three new requests. How do you train yourself to feel the difference in the moment, warmly, without sounding defensive or nickel-and-diming a client you like?
5. The change order let the client choose which extras to buy — and they dropped two of the three. Is that a loss (less revenue) or a win (a happy client and a clear scope)? Argue both sides.
6. On request 4c, the freelancer pushed the music-licensing responsibility back to the client. Was that fair, or should a good freelancer just handle it? What does the contract's responsibility line have to say about it?

Your turn: run a real job on paper

Take one of your three portfolio projects and run the entire business of it, start to finish, producing every artifact — even if the "client" is imaginary and no money changes hands. The craft you already did; now do the business around it.

Produce, in order:

1. A discovery summary — the brief (goal, audience, key message, CTA, constraints) in the Chapter 22 sense.
2. A written quote — itemized across all three stages, with a music line item, an INCLUDED / NOT INCLUDED block, and payment terms (FIGURE CS2.1).
3. A statement of work — deliverables, scope, a two-round revision policy, ownership, and a responsibility line (FIGURE CS2.2).
4. The releases — a filled model release for every identifiable person and a property release for any private location (FIGURE CS2.3).
5. A music license record — the track, its source, its license terms for your use, and where the proof is filed (FIGURE CS2.4).
6. A change order — invent one plausible out-of-scope request and write the warm reply plus the priced change order that handles it (FIGURE CS2.5).
7. An invoice — itemized, with the deposit deducted and net terms (FIGURE CS2.6).

When you have the stack, you have something more valuable than the video: a reusable business template for every job that comes after. Keep it in a folder. The second job will take a tenth of the time, because you will be filling in blanks instead of inventing structure — which is exactly how professionals make the business feel effortless. It was never effortless. It was templated.

Key takeaways

• The business is a production you run in phases, just like the shoot: discovery → quote → contract + SOW + deposit → shoot (with releases) → licensed music → revisions via change order → delivery → invoice → follow-up.
• Understand the goal before you price. A discovery call that surfaces the business outcome (Chapter 22 brief) is what lets you price against value, and it makes the client feel heard.
• The quote and the SOW say the same scope twice, on purpose. Copy the INCLUDED / NOT INCLUDED across so the sale and the signed job can never contradict each other.
• Releases are collected on the day, as coverage — every identifiable, featured person signs, filed to 08_DOCS the same afternoon. "Featured and identifiable" is the test; a notice covers an uninvolved crowd on controlled private property.
• Licensing music properly is the easy path, not the hard one: a royalty-free track cleared for client use, logged in 03_MUSIC-SFX, plays through automated checks and proves itself if falsely claimed.
• A defended scope doesn't reject client ideas — it prices them. Meet every new request with "yes, and here's the change order," and the client's enthusiasm becomes paid work instead of unpaid resentment.
• Get paid on a schedule that protects you (deposit up front, master on final payment, net terms) and seed the next job with a warm follow-up that invites a referral and repeat business. One well-run job becomes a relationship — which is the entire point.