Why I Guarantee Results on Some Projects and Not Others
I don't guarantee results on every project. I know that admission sounds like a hedge, but it's the honest starting point for a conversation almost nobody in this industry has out loud. Some clients ask for a guarantee before they'll sign, expecting a flat no or an uncomfortable dodge. What they usually get from me instead is a real answer about which projects I'll stand behind unconditionally and which ones I won't, and why that line exists in the first place.
That distinction isn't arbitrary, and it isn't about hedging my own risk at the client's expense either. It comes down to how much of the outcome is actually within my control versus how much depends on variables neither of us can manage, like weather, wildlife, or a subject's own performance on the day. I walk through the full framework I use for structuring these agreements, guarantees included, in The Adventure Travel Photographer's Playbook, but the short version starts with being honest about what a guarantee can and can't actually promise.
What a Guarantee Actually Means in Creative Work
In most industries, a guarantee is straightforward: if the product fails, you get your money back. Creative work resists that framing because success isn't binary in the same way. A shoot can technically deliver everything promised in the brief and still not land the way the client hoped, for reasons that have nothing to do with my execution. Light, access, an athlete's mood, a location closing unexpectedly.
So when I talk about guaranteeing a project, I'm careful to define exactly what's being guaranteed. It's rarely "you'll love every image." It's closer to "you'll get a professional process, contracted deliverables, and my full effort to solve problems as they come up." That's a guarantee I can actually stand behind, because it describes things within my control rather than outcomes shaped by forces outside it.
Clients who push back on that distinction are often the same clients who'd be disappointed no matter what got delivered, because their expectations were never really about the process to begin with. Getting clear on what a guarantee covers early tends to filter that mismatch out before it becomes a bigger problem later in the relationship.
The Projects Where I Do Offer a Guarantee
There's a specific category of project where I'm comfortable offering something close to an unconditional guarantee: controlled environments, familiar locations, subjects I've worked with before, and deliverables that don't hinge on unpredictable natural conditions. Studio-adjacent product work in the field, for example, or a shoot at a location I've scouted and shot multiple times already.
In those situations, the variables are known quantities. I can predict, with real confidence, what the shoot day will produce, because I've already seen the location behave in different conditions and I know the client's expectations from prior work together. That predictability is exactly what makes a guarantee meaningful rather than just a marketing line.
Offering a guarantee in these lower-variable situations also tends to close deals faster. Clients who are on the fence about a first project together respond well to reduced risk, and I'm able to offer that reduction honestly because I've done the work to understand where the actual risk in the project lives.
The Projects Where I Won't Offer One
On the other end, remote locations I haven't shot before, weather-dependent conditions, first-time work with an unfamiliar athlete or subject, multi-day expeditions with genuine physical risk involved. These are projects where too many variables sit outside anyone's control, and promising a guaranteed outcome would mean either quietly padding my pricing to cover the risk or setting an expectation I have no real way to back up.
I've found it's far better to be direct about this upfront than to offer a vague guarantee and hope conditions cooperate. A client who understands the real risk profile of a remote or weather-dependent shoot going in is a much easier client to work with when something outside anyone's control actually does happen on location.
This is also where a contract with clear contingency language does more real work than a guarantee ever could. Rather than promising a specific outcome I can't control, the contract spells out what happens if weather or access forces a reschedule, which protects both sides without either of us pretending certainty exists where it doesn't.
How I Explain This to a Client Who Wants Certainty
Most clients asking for a guarantee aren't actually asking for a legal promise. They're asking to feel less anxious about spending a significant budget on someone they haven't worked with yet. Once I understand that's the real question underneath the request, I can usually answer it without offering an outcome guarantee I'm not comfortable making.
I walk them through past examples of similar projects, explain exactly how I handle a shoot day that goes sideways, and show them the contingency planning that's already built into the process. That combination, evidence plus process, tends to address the underlying anxiety more effectively than a blanket guarantee would, because it's specific and grounded rather than a general reassurance.
Clients who've been burned before by vague promises from other vendors often respond especially well to this kind of honesty. It signals that I've thought seriously about risk, rather than papering over it with language designed to close the deal quickly.
Why Overpromising Costs More Than It Saves
Early in my career, I was more willing to say yes to whatever a client wanted to hear, guarantees included, because I was worried about losing the booking otherwise. That instinct cost me more than it ever saved. A guarantee made under pressure, without real confidence behind it, sets up a relationship for disappointment the moment reality doesn't cooperate, which in adventure photography happens more often than in almost any other genre of client work.
The clients who remember a broken promise remember it far longer than they'd have remembered a straightforward, honest conversation about risk from the start. Rebuilding trust after an overpromise is slower and harder than simply not overpromising in the first place, and I learned that the expensive way more than once before it stuck.
Now, when I feel the pull to offer more certainty than I actually have, I treat that pull as a signal to slow the conversation down rather than speed it up. That discipline has protected far more long-term relationships than the guarantees I used to hand out too easily.
Building Trust Without Relying on Guarantees at All
The deeper answer to a client's need for certainty usually isn't a guarantee at all, it's trust built before the guarantee question ever comes up. A strong portfolio of similar work, references from past clients in comparable situations, and a clear, professional process all do more to reduce a client's perceived risk than a guarantee clause buried in a contract.
I try to front-load that trust-building as early in the relationship as possible, so that by the time we're discussing terms, the guarantee question has mostly already answered itself through the evidence I've already provided. That's a slower path than simply promising whatever gets the signature fastest, but it produces relationships that hold up under real pressure later.
This is, honestly, a better long-term strategy than optimizing contract language for maximum reassurance. Contracts matter, but they're not a substitute for a client actually believing in your ability to deliver, built from evidence rather than promises.
How This Shapes the Way I Write Contracts
Once I got clear on which projects deserve a guarantee and which don't, my contract language changed to reflect that distinction explicitly rather than leaving it implied. Projects in the lower-risk category get language that's close to a satisfaction guarantee. Higher-risk, weather-dependent, or first-time projects get detailed contingency language instead, spelling out what happens if conditions prevent the planned shoot from happening as scoped.
That specificity protects both sides. The client knows exactly what they're getting into before they sign, and I'm not left improvising an explanation mid-project about why an outcome couldn't be guaranteed after all. Getting this right in the contract removes a lot of the emotional weight from conversations that would otherwise happen under much more stressful circumstances, mid-shoot or after a disappointing result.
I'd encourage any photographer drafting their own agreements to think through this same distinction before a difficult project forces the question. It's a much easier conversation to have on paper, calmly, than in the field when something has already gone wrong.
What I'd Tell a Photographer Considering Their First Guarantee
If you're a photographer thinking about offering a guarantee for the first time, start by mapping out which parts of your typical project are genuinely within your control and which aren't. That map will tell you almost everything you need to know about where a guarantee makes sense and where it doesn't, far more reliably than trying to guess what will make a client comfortable enough to sign.
Resist the urge to offer a broad guarantee just because a competitor does, or because it feels like the thing that will close a deal faster. A guarantee you can't actually back up under real conditions will cost you more in damaged trust than the deal was worth, and clients tend to remember that kind of disappointment longer than almost anything else about a working relationship.
Treated carefully, a guarantee can be a genuinely useful tool for reducing a new client's risk and closing the right kind of project faster. Treated carelessly, it's a liability waiting for the first unpredictable shoot day to expose it.
How you structure guarantees, contingencies, and the language around risk is exactly the kind of thing I break down in more detail inside The Adventure Photographer's Playbook, built from years of learning where that line actually sits.
How a Guarantee Conversation Changes the Sales Timeline
I've noticed the guarantee question tends to surface at a very specific point in a sales conversation, usually right after a client has decided they like the work but before they've fully committed to the budget. That timing matters. It means the answer I give shapes whether the deal moves forward quickly or stalls out in hesitation, and a vague or overly cautious answer at that moment can cost momentum that's hard to rebuild later in the process.
Being ready with a clear, confident answer, rather than improvising one in the moment, speeds that timeline up considerably. I know exactly which category a given project falls into before the client even asks, because I've already run through the risk profile while scoping the project. That preparation turns what could be an awkward pause into a straightforward, credible answer that actually builds momentum toward signing rather than slowing it down.
Clients notice that kind of preparedness even when they don't consciously register it as a factor. It reads as competence, and competence is one of the fastest ways to move a hesitant client from considering the project to committing to it.
What I Learned From the Times I Got the Balance Wrong
I haven't always gotten this balance right. Early on, I sometimes overcorrected in the other direction, refusing to offer any reassurance at all out of fear of overpromising, which came across as evasive rather than careful. A client asking a reasonable question about risk deserves a real answer, not a wall of caveats that leaves them more uncertain than when they started.
Finding the right middle ground took some trial and error. I learned that being specific about what I can and can't control, rather than either overpromising or refusing to engage with the question, is what actually builds confidence. Clients don't need certainty. They need to feel like they're working with someone who understands the real risks well enough to manage them competently.
That's the version of this conversation I try to have now, every time the guarantee question comes up, whether it's a first-time client or someone I've worked with for years. It's a more honest conversation than the one I used to have, and it's produced far more durable client relationships as a result.
Documenting Guarantees So Everyone Remembers the Same Terms
A verbal understanding about what's guaranteed and what isn't tends to erode over the course of a project, especially a longer one with multiple stakeholders on the client side. Someone who wasn't on the original call sees a deliverable later and assumes a level of certainty that was never actually promised. I learned to put the guarantee terms, and just as importantly the contingency terms, directly into the written agreement rather than leaving them as a spoken understanding from a kickoff call.
That documentation protects the relationship more than it protects me specifically. When everyone on the client side can point to the same written language, there's no ambiguity to argue about later, and no room for a well-meaning stakeholder to remember the conversation more favorably than it actually went. It turns a potentially uncomfortable disagreement into a quick reference back to language everyone already agreed to.
I've found that clients actually appreciate this level of specificity once they see it in practice, even if it feels like a small, procedural addition to a contract at the outset. It signals that I take the agreement seriously enough to write it down precisely, rather than leaving important terms to memory and good faith alone.
The Long-Term Payoff of Being Honest About Risk
None of this makes for the smoothest sales pitch in the short term. It would be easier, in the moment, to just tell every client what they want to hear and sort out the consequences later if something goes wrong. I understand the appeal of that shortcut, especially early in a career when every booking feels urgent and every hesitation from a client feels like a threat to the business.
But the photographers I respect most in this industry, and the ones who've built the longest-lasting client relationships, are almost universally the ones who were honest about risk from the start, even when honesty cost them a booking here and there in the short run. That reputation for straight talk compounds over a career in a way that a string of overpromised, underdelivered projects never does.
I'd rather lose the occasional client who wanted a guarantee I genuinely couldn't offer than win that client under false pretenses and deal with the fallout six months into a project gone sideways. That tradeoff has served the business well, and it's the version of this approach I'd recommend to any photographer weighing the same decision.
Reflection Questions
- Which parts of your typical project are genuinely within your control, and which depend on variables you can't manage?
- Have you ever offered a guarantee under pressure that you weren't fully confident you could back up?
- What would a client need to see from you, beyond a guarantee, to feel confident booking a first project together?
- Does your current contract language distinguish between lower-risk and higher-risk project types?
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.