.png)
One photographer pulled their lead data from last year. Out of 350 inquiries, nearly a hundred were for events with 50 guests or fewer. Not full elopements — most had family there. Not big weddings either. Twenty people at a state park. Fifteen on a beach with a food truck. Forty in a parent's backyard with a string quartet and no DJ.
Five years ago, you could get away with two pricing tiers: wedding package and elopement package. The wedding package assumed 150 guests, an 8-hour day, a venue with walls, and a reception. The elopement package assumed two people, a mountaintop, and four hours. Everything in between got awkwardly jammed into one or the other.
That doesn't work anymore. A 2024 industry roundup confirmed what photographers have been seeing in their inboxes: couples are designing weddings that don't fit traditional categories. The micro wedding has outlasted "trend" status. Couples have permanently redefined what the word "wedding" covers.
Most photographers who struggle with micro wedding pricing try to solve it with more packages. A small wedding package. A micro wedding package. An intimate elopement package. An adventure elopement package. Pretty soon you have six tiers on your website and couples are still emailing to ask which one fits their 30-person backyard ceremony with a two-hour portrait hike afterward.
The better approach is modular. Stop thinking in packages and start thinking in components. Base coverage is one line item with a per-hour rate or a block minimum. Location scouting is another. Second shooter, albums, travel, adventure add-ons — each priced independently, combined depending on the event.
This only works if your invoicing system supports it. A PDF invoice you built in Canva with two line items isn't going to cut it when you're quoting a 35-person micro wedding with a morning hike, a midday ceremony, and an evening dinner. Itemized invoicing with individual line items for each deliverable makes the quote clear and the boundary explicit. When the invoice spells out that the hike is a separate add-on, nobody shows up expecting it was bundled in.
Maroo's invoice templates let you save your component line items once and reuse them across events. Same base coverage line item whether it's two people in the mountains or forty in a garden. Add or remove components depending on the event. Consistent pricing, less manual work, fewer mistakes.
When a couple inquires, they know what they want their day to feel like, and none of it maps to your package names. They want something personal with their favorite 25 people, outdoors but not a backcountry expedition, and completely free of the reception they dread planning.
When your response is a clean, itemized quote that reflects exactly what they described — not a package they have to squint at and imagine — you've already separated yourself from the photographer who sent a PDF with three tiers and a "contact me for custom pricing" note at the bottom.
Payment milestones help too. A retainer to hold the date, a second installment at 90 days, final balance two weeks before the event. That structure works whether the event is two people or forty. Automated reminders keep things moving without you sending follow-up emails you feel weird about.
The photographers booking these 20-to-50-person events aren't the ones with the most creative package names. They quote any configuration a lead describes — a Tuesday morning hike-and-vows, a Saturday garden lunch for 40 — quickly and clearly, without rebuilding their pricing from scratch every time.
.png)
.png)
