Why I Price in Packages Instead of a La Carte
Early in my career I priced everything a la carte — a day rate here, an editing fee there, licensing quoted separately depending on what the client needed. It felt fair and precise. It was also slow, confusing for clients, and it made every single proposal a fresh negotiation from zero instead of a decision between clear, pre-built options.
These days I lead with packages, and the shift changed both how fast I close projects and how consistently I protect my margin across them. I'll walk through how I actually build a package and why I still keep itemized detail behind it, not instead of it. The fuller pricing framework this fits inside is in The Adventure Travel Photographer's Playbook, but this piece is specifically about packages versus building every quote from scratch.
The Case Against Pure A La Carte Pricing
Pure a la carte pricing sounds more precise, but in practice it puts an unreasonable amount of decision-making burden on a client who usually doesn't know enough about photography production to confidently assemble their own scope. Handed a menu of individually priced line items with no guidance, most clients either freeze or under-scope the project entirely.
It also slows down my own sales process considerably. Every a la carte quote required a fresh conversation about what the client actually needed, which meant more back-and-forth before I ever got to a signed agreement, and more opportunities for a client to lose momentum or get a competing quote in the meantime.
The final problem was consistency. Pricing everything separately every time made it easy to accidentally underprice a project by forgetting to account for something I'd normally include, since there was no standard bundle acting as a check against my own memory under pressure.
What a Package Actually Solves for the Client
A well-built package solves the client's actual problem, which usually isn't "I want the cheapest possible price for each component," it's "I want to understand quickly whether this photographer can meet my need and roughly what that's going to cost." Packages answer that question in seconds instead of requiring a client to interpret a detailed line-item menu on their own.
Packages also reduce decision fatigue. A client choosing between three clearly defined options makes a faster, more confident decision than one facing a dozen individually priced components they have to mentally assemble into something coherent themselves.
There's a trust dimension too. A thoughtfully structured package signals that I've done this enough times to know what a project like theirs typically requires, which is reassuring in a way that a blank a la carte menu simply isn't, especially for a client who isn't deeply familiar with photography production themselves.
How I Structure My Own Packages
I build my packages around real project types I see repeatedly, rather than arbitrary price tiers. A package built around an actual common scope — a single-location brand campaign, a multi-day trip gallery, a hospitality property refresh — maps much more naturally to what a client is actually trying to buy than a generic "good, better, best" structure with no real basis.
Each package includes a defined scope: number of shoot days, deliverable count, usage rights, and turnaround time, all bundled at a price that reflects the full value of that combination rather than the sum of individually discounted parts. That bundling is part of what protects margin — clients aren't comparing my price against a competitor's individual line items, they're evaluating the whole package.
I also build in enough flexibility within each package to adjust for reasonable variation without having to rebuild the whole structure from scratch for every single client. A package is a starting template, not a rigid, unchangeable product, and treating it that way keeps it useful across a wide range of actual projects.
Where Itemized Detail Still Lives Behind the Package
Moving to package pricing didn't mean abandoning itemized detail entirely — it just moved that detail behind the package rather than in front of it. Every package I quote is still built from a full internal breakdown of day rate, assistant costs, location fees, post-production hours, and licensing, so I always know exactly what's contributing to the final number.
That internal breakdown becomes essential the moment a client wants to adjust scope, which happens often. Instead of renegotiating a bundled number from scratch, I can show the client which specific line items change if they add or remove something, which keeps the conversation grounded and fair for both sides.
This is the piece that makes package pricing work rather than just feeling like an opaque number pulled from nowhere. Clients get the simplicity of a clear package upfront, and the transparency of a full breakdown the moment they ask for it or want to adjust the scope.
The Psychology of Choosing Between Three Options
Presenting three package tiers rather than one flat price changes how a client engages with the decision entirely. A single price invites a binary yes-or-no response, which often defaults to "let me think about it" or a request for a discount. Three options invite a comparative decision, which tends to move faster and produces a stronger sense of client ownership over the choice.
The middle tier usually gets chosen most often, which isn't an accident — it's positioned to feel like the obviously reasonable choice between a stripped-down option and a premium one. I build my middle package to be the one I'd genuinely recommend for most projects, not just a psychological anchor with no real substance behind it.
The top tier matters even when it's rarely chosen, because it reframes the middle option as moderate rather than expensive by comparison. And the bottom tier matters because it gives budget-conscious clients a legitimate way to say yes rather than walking away entirely.
What I Learned From Clients Who Wanted to Build Their Own
Some clients, particularly ones with more production experience, want to build a custom scope rather than choosing from a package. I've learned to welcome that conversation rather than resist it, since it usually means they have a clear enough sense of their own need that a custom quote actually serves them better.
What I don't do is let a custom build become an unstructured negotiation from zero. I still start from the closest package as a baseline and adjust from there, which keeps the conversation anchored to a known, well-tested structure rather than reinventing the pricing logic for every custom request.
This hybrid approach — packages as the default, itemized customization available on request — has given me the speed benefit of packages without losing the flexibility that some clients genuinely need. It's not either-or in practice, even though I lead with packages for the vast majority of proposals.
Avoiding the Trap of Too Many Add-Ons
It's tempting to build an ever-growing list of optional add-ons on top of each package — extra locations, expedited turnaround, additional deliverable formats — and I've had to be disciplined about not letting that list grow so long it recreates the exact decision fatigue packages were meant to solve.
My rule is to keep the add-on list short and genuinely useful, covering the handful of adjustments clients actually ask for repeatedly, rather than trying to anticipate every conceivable variation in advance. A shorter, well-curated add-on list keeps the whole pricing structure fast to navigate.
When a request falls outside both the packages and the standard add-ons, that's the signal for a genuinely custom quote rather than trying to force it into an ill-fitting existing structure. Recognizing that distinction quickly keeps both the package system and the custom process clean and functional.
How Packages Speed Up the Sales Conversation
The single biggest operational benefit of packages has been speed. A prospective client can look at three clearly defined options and self-select the right starting point far faster than they could work through an open-ended conversation about scope from a blank page.
That speed compounds across a business. Faster proposals mean more proposals sent in the same amount of time, and a client who can quickly understand what they're buying is more likely to move forward before momentum fades or a competing photographer's proposal lands in their inbox first.
Packages also make my own proposal-writing process faster, since I'm adapting a known template rather than building pricing logic fresh for every single inquiry. That efficiency gain shows up directly in how much of my week goes into pricing conversations versus actual shooting and editing.
When A La Carte Still Makes Sense
I still use fully a la carte pricing in a handful of situations — an ongoing retainer client adding a specific, well-defined piece of work outside their existing agreement, or a highly specialized project that doesn't resemble any of my standard package scopes closely enough to adapt one.
In those cases, the itemized approach I described earlier in the discount conversation still applies directly, since the client isn't choosing between packages, they're evaluating a single custom breakdown. The two systems aren't in conflict — packages handle the majority of standard inquiries, and itemized a la carte pricing handles the genuine exceptions.
Recognizing which situation I'm in early in a conversation, rather than defaulting to one pricing approach for every inquiry regardless of fit, has kept both systems useful instead of forcing every project through a structure that doesn't actually match its shape.
Pricing Packages So They Actually Protect My Margin
A package only protects margin if it's priced against the real cost and effort of the scope it represents, not against a competitor's lowest advertised number. I build each package price from the same itemized internal math I'd use for a fully custom quote, then round and bundle it into a clean, presentable number.
I also revisit package pricing periodically rather than treating it as fixed once it's built. Costs change, my own rate has changed as my experience and demand have grown, and a package that made sense two years ago can quietly underprice the exact same scope of work today if it's never revisited.
The discipline of tying packages back to real underlying costs, rather than letting them drift based on what feels reasonable to charge, is what keeps package pricing from becoming a slow, invisible discount on my own work over time.
What I'd Tell a Photographer Still Pricing Everything Separately
If you're still building every quote from a blank page, the first thing I'd say is that packages aren't about being less precise — they're about moving the precision behind the scenes where it belongs, rather than putting it in front of a client who doesn't need to see every individual line item to make a confident decision.
Start by looking at the last dozen projects you've quoted and finding the patterns — the scopes, deliverables, and prices that repeat most often. That's your first package, built from real data rather than guesswork, and it'll almost certainly cover more of your actual business than you'd expect before you tried it.
The transition takes a little upfront work to build clean, well-tested package structures, but the payoff in speed, client clarity, and consistent margin protection has been one of the more durable improvements I've made to how I run this business.
How Packages Changed My Contracts, Not Just My Quotes
Moving to packages had a knock-on effect I didn't fully anticipate when I first restructured my pricing: it simplified my contracts as well. A contract built around a clearly defined package scope is easier to write, easier for a client to review quickly, and easier to enforce if something about the project drifts from what was originally agreed.
Before packages, my contracts had to accommodate an almost unlimited range of possible scopes, since every project was priced individually from scratch. That flexibility came at the cost of clarity, and it made scope creep harder to identify clearly, since there was no clean baseline definition of what the original agreement actually included.
With packages, the contract language can reference the specific package tier directly, with a clear, pre-written definition of what's included and what falls outside it. When a client requests something beyond the package, that request is immediately visible as an addition rather than a vague gray area that has to be argued from first principles every time.
This has made conversations about scope creep considerably easier, since I'm no longer relitigating what a normal, expected scope looks like from zero on every single project. The package itself does a lot of that defining work upfront, well before any disagreement about scope has a chance to develop mid-project.
Packages have also made it easier to train an assistant or a second shooter on how I quote and scope projects, since there's a clear, repeatable structure to hand off rather than an intuition built entirely from years of individual, one-off pricing decisions that lives only in my own head. That documentation has become genuinely useful as the business has grown beyond just me handling every client conversation directly.
There's a longer-term benefit too, in how packages make my own pricing history easier to track and evaluate. I can look back at how a specific package's uptake and margin have performed over a full year and make a deliberate decision about adjusting it, rather than trying to reconstruct pricing patterns from a scattered history of individually negotiated quotes that never shared a common structure to compare against each other.
That comparability is worth more than it might sound. Knowing precisely how a package's margin has shifted over a year, rather than guessing based on scattered memory of individual projects, is what lets me make a confident, timely decision to raise a package's price rather than realizing months too late that it's quietly been underpriced the whole time.
For the full pricing structure, including how I build and revise package tiers over time, I go deeper into it inside the Adventure Travel Photographer's Playbook, including the exact worksheet I use to build a brand new package from scratch and stress-test it thoroughly against several realistic project scenarios before ever offering it to a real client for the first time.
Reflection Questions
- Do your current quotes get built fresh every time, or from a repeatable structure based on your most common project types?
- How much of your sales process slows down because a client has to interpret an open-ended menu of individually priced options?
- If you built three package tiers today from your last dozen projects, what would the most common scope actually look like?
- How often do you revisit your own pricing structure to make sure it still reflects your real costs and current experience level?
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.