Most Asked Questions About Client Work

If you have ever walked away from a “quick project” feeling underpaid, overworked, or weirdly responsible for someone else’s chaos, this is for you.

I opened this episode with a gut punch scenario: you are still owed $3,700, and on top of that you lost other opportunities because you were counting on the work. That is the part people forget. It’s not just the invoice. It’s the opportunity cost.

So I pulled together 10 questions I see constantly in the photo and video world and answered them in a way you can actually use on your next gig.

_ _ _

Quick note: the contract and licensing parts are US-based and not legal advice. They are practical guardrails, not courtroom ready.

_ _ _

Why these questions matter

Most client problems are not “creative problems.” They are expectation problems.

The camera work can be solid and you can still get burned if the scope is fuzzy, the feedback is late, six people are “just chiming in,” or someone asks for raw footage without understanding what that even means.

This article is meant to be a checklist you can copy, paste, and build into your process. Without further ado, let’s get into it!

1) How do I stop scope creep without sounding rude?

Scope creep usually starts as “one small ask.” Then it grows teeth.

What I do, especially with a new client, is keep it professional and calm:

• “That’s not really part of our scope.”

• “I’ll do it this time, but going forward that would be an additional charge.”

• “If we need to add that, we’ll do a change order.”

You are not being difficult. You are protecting the agreement you both made.

Pro Insight
If someone balks at basic boundaries, that is useful information about whether you want them as a repeat client.

2) How many revision rounds do you include and what happens after?

I keep this simple: three rounds.

• Draft 1

• Draft 2

• Final

Anything after “final” becomes hourly (or whatever your additional work rate is). If you cannot get aligned by round three, it usually means there was a miss earlier in communication, not a “client being annoying” problem.

A practical way to prevent revision chaos: ask for references up front. A Pinterest board. A video they like. Something that helps you understand taste and intent before you ever edit.

3) What needs to be in a simple contract, even for small gigs?

_ _ _

Quick note: the contract and licensing parts are US-based and not legal advice. They are practical guardrails, not courtroom ready.

_ _ _

I do not care if it’s a small job. A simple contract is still your best friend.

Here’s what I make sure is included, big or small:

Parties and project summary

Who is hiring who, and what the project is. Define “client” and “contractor” clearly.

Scope and deliverables

Be specific:

• Formats (MP4, PNG, etc.)

• Length (3 minutes? 20 minutes?)

• Quantity (one photo? 500 photos?)

• Delivery method (Dropbox, Google Drive, etc.)

Timeline and key dates

Include:

• Shoot date

• Draft delivery date

• Review windows

• Final delivery date

Also spell out call time expectations. If the shoot is at 9:00, and you need to arrive at 6:30 to set up properly, that needs to be clear.

Review windows and what happens if the client is late

This line matters: If review is delayed, the timeline shifts.
Because you are not sitting there frozen in time waiting for an email. You have other work scheduled.

Client responsibilities

Spell out what they must provide:

• Access permissions (site access, locations, etc.)

• One point of contact

• Releases if needed

• Brand assets (logo, fonts, guidelines)

• Approvals on time

Fees and payment terms

Include:

• Total cost

• Deposit amount and due date

• Due dates (Net 15/30/60)

• Late fees if you use them

• Accepted payment methods

My personal line in the sand: I do not step on site without a cleared deposit in my account.

Revision policy

Define:

• Number of revision rounds included

• What counts as a revision vs a new request

• Rate for additional work

Final approval and what “complete” means

How final signoff happens, what “delivered” means, and when the project is officially complete.

4) How do you price quick jobs when the ask is vague?

“Quick” plus “vague” is where people accidentally donate their time.

My move: probe first, then think, then price. I do not give a range on the spot. Not because I want to be dramatic, but because I need time to process what the job actually is.

Questions that change the price fast:

• What are you actually delivering?

• What is the approval process? One decision maker or 15 people?

• How much back and forth is likely?

Then consider opportunity cost. If you race to the bottom to win a “quick job,” you might lose out on better work that week.

5) What do you do when the client is slow to give feedback and the timeline slips?

This is where you protect the project with a paper trail.

Before the deadline slips, send a reminder:

• “Just a reminder, I need feedback by the 14th so we stay on track.”

If they miss it, document it clearly and reset the timeline:

• “No worries. When do you think you can get feedback to me so we can restructure the timeline?”

Key point: do not sign up to “still hit the deadline” because they dropped the ball. If you can pull off a miracle sometimes, cool. But do not make miracles your default business model.

6) What do you do when multiple people are giving notes and nobody can decide?

I have lived this. Six people send feedback individually. Nobody talks to each other. Suddenly you are doing “six revisions” that were never agreed to.

This gets solved with one requirement: a single point of contact who consolidates feedback.

You can call it whatever you want, but the concept is the same:

• Who is collecting notes?

• Who is sending the final, distilled list?

• Who is the head chef?

Put it in the contract. Save yourself.

7) What if the client asks for all the raw footage or project files?

First, clarify what they mean. Most clients do not understand “raw.” They often mean:

• “All the clips, unedited”

• Or “All the Photos that were tak”

Raw files also come with reality:

• They take time to organize and transfer

• They can include rejects you would normally filter out

• Many clients cannot even open RAW photos without the right software

If I provide raw footage, I treat it as a separate deliverable and I set a clear boundary:

• I’m happy to help you get what you need, but edits made by others should not be presented as my work

That last part is critical. If someone slaps a terrible grade on it, that is their choice. Don’t let it reflect poorly on your name.

8) Who owns the work and what do rights or licensing mean?

In most cases (again, US-based context), the person hired to capture photo or video owns the work, and the client is granted licensing rights.

Licensing can vary a lot:

• Unlimited use

• Limited use

• Time-limited use (example: 30 days)

The important part is not the perfect legal language. It’s that both sides understand what the client can do with the work after delivery.

9) How do you keep versions organized so you do not lose your mind?

Part of my naming convention helps keep this clear:

• Use Drafts for iterations within the same direction

• Use Versions only when the direction changes significantly

Example structure: “Dave’s Awesome Video File D1.mp4”

• D1, D2, D3 for drafts

• If it becomes a new direction: Version 2, Draft 1 (V2 D1)

10) How do you handle deliverables and exports so clients do not get confused?

When the final file has been approved make sure to rename it “Dave’s Awesome Video File D3-FINAL.mp4”

This lets you and the client easily know which version got the nod for publication.

If You Remember One Thing

A contract is not about being cold. It’s about being clear.

Clear scope, clear revision rules, clear timelines, clear decision makers, and clear deliverables. That is how you protect the relationship and protect your time.

Until next time, Be Good to Each Other.

-Dave

Client Relations Is the Unsexy Advantage (And It’s Why You Get Rebooked)

Client relations is not the fun part of this work. It’s not the flashy transition. It’s not the color grade. It’s not the new lens.

It’s the part that keeps your business alive.

If you’ve ever felt like a project got “weird” halfway through, it usually wasn’t because your work suddenly got worse. It was because expectations were never nailed down. That gap is where stress breeds, revisions multiply, and trust takes a hit.

So let’s talk about the real side of client relations, the part that actually makes clients come back.

Flashy Isn’t the Job

I’m all for good editing. I love a strong sequence. But clients don’t hire us for a flex. They hire us to solve a problem.

That problem might be visibility. It might be fundraising. It might be recruitment. It might be community trust. It might be internal communication. Whatever it is, your job is to make the client feel supported while you build something that serves their goal.

When you anchor to that, the “should we do a cooler transition?” question becomes a lot easier to answer. Cool is optional. Clear is not.

Pre-Production Is Where You Win

Pre-production is the most important phase, and it’s also the phase people rush through because they want to “just shoot.”

This is where you prevent most of the pain.

A few things I try to lock in early:

• What does success look like for this project?

• Where is this being used (website, social, internal, grant report)?

• What are the deliverables (exactly)?

• What’s the timeline, including review windows?

• Who is the decision-maker?

Most frustration is not about quality. It’s about surprise. Pre-production is how you remove surprises.

Clients Can’t Always Explain It, But They Can Spot It

A lot of clients don’t have the vocabulary to describe what they want. That’s normal. They’ll say things like “make it feel more professional” or “I don’t know, it’s just not it.”

They can’t always name the destination, but they can tell you when you took a wrong turn.

Your job is to guide them with good questions, show examples, and translate fuzzy feelings into clear decisions. That is part of the craft.

Put It In Writing (It Protects Everyone)

I’m not saying you need to turn into a contract robot. I’m saying the basics need to be written down so nobody is relying on memory.

At minimum, I want:

• Scope and deliverables

• Timeline

• Payment schedule

• Revision expectations

• Usage, licensing, and any brand requirements

Writing is not a trust issue. It’s a clarity tool. Clarity lowers stress for both sides.

Learn Your Client’s World

If you want to be great at client relations, learn enough about their world that you can speak their language.

Sometimes that’s municipal work. Sometimes that’s conservation. Sometimes that’s a small business where the owner is doing six jobs at once. The more you understand their constraints, the better your recommendations become.

And sometimes, brand guidelines are real constraints. You might hear a rule that sounds silly, but it exists for a reason. Your job is to work within reality, not fight it.

Reliability Beats Impressiveness

Word of mouth doesn’t come from your fanciest project. It comes from the experience people had working with you.

Show up. Communicate. Set expectations. Deliver what you said you’d deliver.

The unsexy stuff is the thing that builds a sustainable career.

If You Remember One Thing

Client relations gets easier when you stop trying to impress and start trying to understand, then you plan like it matters.

Until next time, Be Good to Each Other.

- Dave

Gear That Actually Matters

I love talking about gear, but gear talk gets weird fast. It turns into wish lists, brand wars, and people buying things to feel “official.” This episode was my attempt to drag it back to reality.

Here’s the core idea: gear only matters if it solves a problem in your workflow. Not a hypothetical problem. Not a YouTube problem. A problem you actually hit in the field.

Your Workflow Decides Your Kit

I’ve worked run-and-gun where you are outside, moving fast, and you cannot control lighting, audio, or the environment. I’ve also done the opposite, full studio setups where you can dial everything in.

Those are two different planets. So any recommendation I give comes with an asterisk: it might not work for you, and that’s fine. Your job is to figure out where your pain points are, then buy to fix those.

What I Actually Carry in the Field

When I’m shooting construction or environmental work, I need to move. A tripod often stays behind because it slows me down. My main setup is simple: camera, one primary lens, and a utility belt with extra lenses, SD cards, batteries, and the little stuff that saves a shoot.

Most of the time, my main lens is a 24–70 f/2.8 because it gives me versatility in one shot. I keep a couple primes as backup, not because primes are magic, but because if something breaks, I still need to deliver. I also keep redundancy nearby, a second camera in the car, extra batteries, and a plan for when things go sideways.

Budget Gear That Still Gets Work Done

When you’re starting out, you might have tastes bigger than your budget. I get it. I’ve felt the “just let me buy the shiny thing” urge too.

But there is a lot of good entry-level gear that can carry you a long way. Brands like Neewer and SmallRig have options that are genuinely usable, especially while you’re still discovering your workflow.

I also talked about buying cheaper lenses as a starting point. A cheap lens can be “good enough” while you learn, as long as you understand the tradeoffs and you’re not pretending it’s the same thing as higher-end glass.

Lighting: From Umbrellas to a Real System

My lighting journey started with a cheap photo kit: stands, bulb holders, umbrellas, and a bag that basically fell apart immediately. The stands still have value, but that kit was a “get started” moment.

Later, I moved into the Aputure ecosystem and it taught me what a real lighting system feels like. I’m lighting my set in this video with the Aputure 600x, plus an Amaran light bar for the colored background. The ability to control intensity and color quickly, without running across the room, is the kind of upgrade that actually changes your workflow.

Client Perception Is Real, But Don’t Go Into Debt

I shared a story where a client reacted to a shooter using the company’s lower-end gear. The photos were fine, but the client had already gotten used to seeing my big lens, my gear, my “pro look.” Their perception got wrapped up in the equipment.

That said, do not use that story to justify debt. At the end of the day, what matters most is how good the results are, how smoothly you deliver, and how easy you are to work with.

If You Remember One Thing

Buy gear when it solves a real problem in your workflow, and never confuse “looking professional” with doing professional work.

Until next time, Be Good to Each Other.

- Dave

Stop Buying Gear. Start Solving Problems.

If you and I were grabbing coffee and you told me you’re thinking about buying new gear, I’d ask one thing: what problem is it solving? Not “what would be nice,” but what’s actually getting in your way right now.

Because here’s the trap. New gear is a mood booster. It feels like momentum. It feels like progress. Sometimes it even looks like progress, sitting on your desk like a tiny metal promise.

But if it does not solve a real problem, it is usually just an expensive way to feel better for a day.

“Does This Fix Something” vs “Does This Just Feel Good”

I’m not anti gear. I love good tools. I just don’t love buying tools to avoid the uncomfortable part of getting better.

A lot of creators get stuck in a loop where the solution is always “upgrade.” New camera. New lens. New mic. New light. New gimbal. Then you’re back to the same problem, except now you have less money and more stuff to manage.

So I try to slow down and separate two thoughts:

• This would be fun to own

• This would fix something that is currently costing me time, quality, or reliability

Only one of those earns a purchase.

When an Upgrade Actually Makes Sense

Here’s a real example from my world.

Upgrading from the Canon EOS R to the Canon EOS R6 Mark II was worth it for client work, because it solved real problems. Stuff like reliability and limits that actively got in the way. Dual card slots are not exciting, but they are professional insurance. Longer recording options matter when you need the camera to simply keep rolling. These are boring problems, which is exactly why they are the right ones to solve.

When you’re working with clients, “almost” is not a plan. The gear does not need to be sexy. It needs to be dependable.

The Purchase I Regret

On the flip side, I bought a Ronin-S gimbal thinking it would level me up. In reality, it did not solve the problem I actually had.

The real problem was not stabilization. The real problem was reps. Practice. Getting faster at shooting clean handheld. Learning when movement adds something, and when it just adds motion.

The gimbal was a detour. It felt like I was doing something smart, but it mostly created friction. Setup time, balancing, hauling it around, deciding whether it’s worth it for a quick shot. It became a tool I owned more than a tool I used.

What I’d Spend Money On First

If you’re early in the game and trying to go pro, I’d think about three things before big upgrades:

• Training and practice that makes your current setup work harder

• Software you actually use consistently

• Redundancy, so one failure does not take you out

The goal is not to own the “best” gear. The goal is to build a reliable system you can repeat under pressure.

If You Remember One Thing

Before you buy anything, ask: does this solve a real problem, or does it just make me feel better? If you cannot name the problem clearly, keep the money. Put it into skills, repetition, and reliability. That is the stuff that turns beginner energy into professional results.

Until next time, Be Good to Each Other.

- Dave