How I Decide Which Projects Are Worth a Money-Back Guarantee
A money-back guarantee sounds like a bold, confidence-inspiring thing to offer a client, and on certain projects, it genuinely is. On others, it's a promise I have no business making, no matter how good the work turns out. The difference isn't about how talented I feel that week. It's about whether the outcome is actually something I control from start to finish, or whether weather, access, a client's internal approval process, or a subject's mood is going to have more say in the result than my camera does.
Over a decade of client work, I have landed on a rough internal test for this, and it has saved me from a few guarantees I would have deeply regretted. If you are weighing whether to offer one yourself, or wondering why a photographer you hired won't, the framework in The Adventure Travel Photographer's Playbook covers the pricing and scoping side of this decision in more depth than I can in one post, but the short version starts with understanding what a guarantee is actually protecting the client from.
Why I Don't Guarantee Everything
The instinct to guarantee results comes from a good place. It signals confidence, and it removes a layer of risk for a client who has never worked with you before. But a guarantee is only honest if you actually control the variables that determine success. On an adventure shoot, weather, animal behavior, a client-side approval chain, and a subject's energy on the day are all variables I influence but do not control. Promising a specific outcome when half the inputs are outside my hands isn't confidence, it's a bet I'm making with someone else's money.
So the real question I ask before offering a guarantee isn't "am I good enough to deliver this," it's "do I actually own enough of this outcome to promise it." Those are different questions, and conflating them is how photographers end up over-promising early in their career, usually out of a desire to close the deal rather than a clear-eyed read of the project.
I've learned to separate the two instincts deliberately. Confidence in my own work stays constant. What changes project to project is how much of the final result actually sits in my hands versus everyone else's.
What "Results" Even Means on an Adventure Shoot
Before I can guarantee anything, I have to define what "results" means for that specific client, and it's rarely as simple as "good photos." A gear brand wants images that show a product being used correctly in a real environment. A tourism board wants images that make a place feel inviting to someone who has never been there. A hospitality client wants a specific mood. None of those are purely aesthetic judgments, they're strategic ones, and strategic judgments are harder to guarantee than technical competence.
This is where a lot of guarantee conversations go sideways. A photographer guarantees "great photos," the client receives technically excellent images that simply don't match what they had in mind, and now there's a dispute about a subjective standard nobody actually defined in writing. If I'm going to guarantee anything, it has to be tied to something specific and checkable, not a feeling.
That's why the projects I'm willing to guarantee almost always start with an unusually detailed brief. If a client can tell me exactly what they need, I can tell them exactly what I'm capable of delivering against that brief. Vague briefs and guarantees don't mix.
The Type of Project I Will Guarantee
The clearest candidates for a guarantee are projects with a tight, well-defined shot list, controlled conditions, and a client who has done this kind of shoot before and knows what "done" looks like. Product-in-use photography for an established gear brand, where the shot list is specific and the location is known, is a good example. I know what the deliverable looks like before I show up, which means I can commit to it.
Repeat clients are also easier to guarantee for, simply because we've already been through a full project cycle together. I know how they give feedback, what their internal approval process actually rewards, and what "good" means to their team specifically, not in the abstract. That shared history removes a lot of the ambiguity that makes guarantees risky with a brand-new client.
Shorter, single-day, single-location projects are also safer ground than multi-day expeditions, simply because there are fewer places for the plan to fall apart. Fewer moving parts means fewer excuses either of us needs, which is exactly the condition a guarantee should require.
The Type of Project I Won't Touch With a Guarantee
Anything dependent on weather, wildlife, or a subject's real-time performance is off the table for a guarantee, full stop. A summit shoot that depends on a clear window at altitude, a wildlife encounter that may or may not happen, or an athlete's actual send on a route are all outcomes I can prepare for extensively but cannot promise. I can guarantee my preparation and my presence. I cannot guarantee the mountain.
Documentary and editorial work is the other category I avoid guaranteeing, because the entire value of that kind of work is that the story reveals itself in the field and in the edit, rather than being fully scripted in advance. If I could guarantee the exact outcome of a documentary shoot before I left, it probably wouldn't be documentary work anymore, it would be a commercial with extra steps.
Multi-day trips with a lot of client-side decision points also make me cautious. The more people who touch the approval process, the more subjective judgments get layered on top of the actual photography, and subjective judgments are exactly what a guarantee shouldn't be riding on.
How Weather and Access Change the Calculation
Weather is the single biggest reason I decline to guarantee outdoor work, and it isn't close. A forecast can be wrong, a window can close early, and an entire shoot day can get scrapped through no fault of anyone's planning. I build contingency days into contracts specifically because of this, but a contingency day is a mitigation, not a guarantee, and clients need to understand the difference before they sign anything.
Permit and access issues carry a similar risk. A location that requires a permit can have that permit denied or delayed, a trail can close for conditions I don't control, and access that was confirmed weeks out can change on short notice. None of that reflects on the quality of the work, but all of it can derail a guaranteed outcome, which is exactly why I scope guarantees narrowly around what's actually within reach.
When access and weather risk are genuinely low, I'm far more comfortable extending a guarantee. A studio-adjacent shoot, an indoor gear detail session, or a location I've shot dozens of times before all carry less of this risk, and the guarantee conversation gets a lot simpler as a result.
The Contract Language That Makes a Guarantee Safe
If I do offer a guarantee, it's written narrowly and specifically, tied to deliverables I actually control rather than a subjective read of quality. I'll guarantee a minimum number of usable images meeting the agreed shot list, delivered by a specific date, in the agreed format. I won't guarantee that the client's internal team will love every single frame, because that's a taste judgment, not a production outcome.
The contract also spells out what happens if the guarantee isn't met, and it's rarely a full refund. More often it's a reshoot, an extended revision window, or a partial credit toward a future project. A blanket "money back if unsatisfied" clause invites disputes about subjective satisfaction that neither side can resolve cleanly, so I avoid that phrasing entirely.
Weather and force majeure carve-outs are non-negotiable in any guarantee language I write. If a shoot day gets rained out or a permit falls through, that's explicitly outside the guarantee, and it's written that way before anyone signs, not negotiated after the fact when everyone's frustrated.
What a Guarantee Actually Costs Me
A guarantee isn't just a marketing line, it's a real financial exposure, and I price accordingly. Any project with a guarantee attached gets a slightly higher rate, because I'm effectively pricing in the risk of a reshoot, an extended revision cycle, or a partial refund. Clients who want the guarantee generally understand this trade-off once it's explained, and the ones who balk at it usually weren't a great fit for a guaranteed structure in the first place.
There's also a time cost that's easy to underestimate. A guaranteed project gets more of my planning attention up front, because the margin for error is lower. I'll spend more time on the shot list, more time scouting, and more time building contingency plans, all of which is time I'm not spending on other work. That opportunity cost is real, even when the guarantee itself never gets invoked.
The emotional cost is worth naming too. A guaranteed project carries a different kind of pressure on shoot day, and I've learned to only take that pressure on for clients and conditions where I genuinely believe the odds are in my favor. Taking it on for the wrong project just adds stress without adding much protection for the client.
How Clients React When I Offer One
Most clients react well to a guarantee, but the reaction I actually pay attention to is what happens after I explain the narrow scope of what's covered. Clients who nod along and understand why weather and subjective taste aren't part of the guarantee tend to be the clients I want to work with regardless of whether a guarantee is on the table. Clients who push back and want the guarantee broadened to cover everything are usually telling me something important about how the rest of the relationship will go.
Some clients specifically ask for a guarantee as a way of vetting a new photographer, and I understand that instinct completely. Hiring someone for a remote, expensive shoot with no track record together is a real risk on their end too. In those cases, I'd rather offer a smaller, well-defined guarantee on a narrower slice of the project than a broad one on the whole thing, because it lets both sides build trust without either of us overcommitting.
On repeat projects with existing clients, I've noticed the guarantee conversation almost never comes up anymore, because the track record has already done that work. That's the real end state I'm building toward: a relationship secure enough that a formal guarantee becomes unnecessary.
The Line Between a Guarantee and a Discount
Early in my career, I sometimes blurred a guarantee with a discount without meaning to, offering a reduced rate as a hedge against a project I wasn't fully confident about instead of being upfront about the risk. That's a mistake. A discount is a pricing decision. A guarantee is a promise about outcome. Mixing the two just confuses what the client is actually paying for and what they're actually owed if something goes wrong.
Now, if I'm uncertain about a project's outcome, I say so directly and either decline the guarantee or price the uncertainty into the rate rather than discounting around it. Clients respect a direct "I can't promise that specific outcome, here's what I can promise" far more than a vague hedge dressed up as a good deal.
This distinction matters most when a client asks for both a lower rate and a guarantee on the same project, which is a combination I turn down almost every time. A guarantee is a form of insurance, and insurance costs something. Asking for it at a discount is asking me to absorb more risk for less compensation, which is a bad trade for me and, honestly, a bad precedent for them too.
What I'd Tell a Photographer Considering This
Start narrow. Guarantee something specific and small before you ever guarantee a whole project, and make sure the guarantee is tied to a deliverable you actually control rather than a subjective outcome. A guarantee on "you'll receive at least twelve usable images meeting the agreed shot list" is defensible. A guarantee on "you'll love the photos" is not, no matter how good you are.
Price the risk in, every time. If you're not adjusting your rate to reflect the exposure a guarantee creates, you're essentially offering free insurance, and that adds up fast across a full year of projects. It's not cynical to price this in, it's just accurate accounting for a real cost.
Most of all, use the guarantee conversation as information, not just a sales tool. How a client reacts to the boundaries of what you're willing to guarantee will tell you a lot about how the rest of the relationship is going to go, often before a single frame gets shot.
How This Fits Alongside Everything Else in the Contract
A guarantee clause never sits alone in a contract, and I've learned to make sure it doesn't contradict or duplicate other language elsewhere in the same document. The payment schedule, the revision limit, and the kill fee clause all interact with a guarantee in ways that matter, since a guarantee promising a reshoot has to line up with whatever the revision limit already says, or the two clauses end up in quiet conflict the moment a dispute actually happens.
This is part of why I review the entire contract as a system whenever a guarantee is added, rather than treating the guarantee as a bolt-on paragraph inserted at the end. A deposit structure that assumes full payment up front doesn't mesh cleanly with a guarantee that includes a partial refund, for instance, so the payment terms sometimes need light adjustment specifically to accommodate the guarantee language cleanly.
Clients rarely read a contract this carefully themselves, which means the responsibility for catching these interactions falls on me. It's a small amount of extra diligence per contract, but it's exactly the kind of diligence that keeps a guarantee from becoming a genuine liability if a project ever does go sideways.
If you want a fuller framework for pricing risk into a project before you ever put a guarantee in writing, it's covered in The Adventure Travel Photographer's Playbook.
Reflection Questions
- Which parts of my own outcomes do I actually control on a typical project, and which parts depend on the client, the weather, or the location?
- Have I ever guaranteed something vague, like "great photos," instead of something specific and checkable?
- Do my rates already reflect the real risk of the guarantees I offer, or am I giving that protection away for free?
- How does a client's reaction to guarantee boundaries change how I feel about taking on the project at all?
Dalton Johnson is a professional adventure and editorial photographer with over a decade of experience creating images on all seven continents. His client work includes Patagonia, GoPro, Arc’teryx, Four Seasons, Nike, Rivian, Big Agnes, Ford Bronco, and 160+ other brands. He runs Dalton Johnson Media as a full-service studio, from pre-production through post and distribution.