The Master Workflow: our SOP from inquiry to the wedding — every email included.
This is the operating manual.The pipeline entry was the philosophy; this is the procedure — every step, every email, in order, exactly as my studio runs it in Táve (now part of VSCO). It's also a living document: I'll keep extending it through the wedding day, delivery, and post-production as I write those phases up. Every email below is a copy-paste template — swap the [brackets] and make them yours.
Phase 1 — The inquiry arrives
Inquiries land through the contact form on our website, which is an embedded Táve lead form — so every inquiry is born inside the CRM with a job record from second one. No copying from email to spreadsheet, no leads falling between tools. The moment it's submitted, one automated email fires — the only one in the top of our funnel:
Email · Auto-receipt (automated)
Subject: We have your inquiry — checking our calendar now
Hi [First Name],
Thank you for reaching out about your wedding on [date] — we're excited to learn more about what you're planning.
This note confirms your inquiry arrived safely, and we're checking the calendar now. A real person (usually me) will be back to you within two hours during business hours on weekdays, or within eight hours on weekends.
Talk soon,
[Your Name]
[Your Studio Name]
Notice what that email does and doesn't do: it confirms receipt and puts our response time in writing — and it makes no attempt to answer the availability question, because that answer deserves a human. Then we beat the clock we just promised: under two hours on a weekday, under eight on a weekend.
Phase 2 — The first real reply
A human checks the date. If we're available, the reply does four jobs in one email: congratulates them, answers the date, shows them the right work, and hands them one next step. Two details carry this email. First, the investment guide we link is date-based — a peak Saturday gets a different guide than an off-season Friday (why). Second, the galleries are matched: their venue in their season if we have it, or the closest similar venue in the same season if we don't. A couple looking at their own ballroom in their own month stops comparison-shopping.
Email · Availability + galleries + investment
Subject: Good news about [date] — galleries and investment inside
Hi [First Name],
Congratulations on your engagement — and wonderful news: [date] is open on our calendar.
Since you're celebrating at [venue], here are two full galleries we photographed there in [season]:
[Gallery link 1]
[Gallery link 2]
And here's our investment guide for your date:
[Investment guide link]
The best next step is a short call — we'll walk through your day, your venue, and what you care about most, and see if we're the right fit. Pick a time that works for you here:
[Booking link]
Looking forward to it,
[Your Name]
[Your Studio Name]
That booking link goes to our own scheduler — the one we built ourselves. They pick a time, choose Google Meet or a phone call, and it lands on the calendar with reminders set.
Phase 3 — The call
The call runs our discovery system: six stages, from rapport to venue talk to the package conversation, ending with a clear next step. I've documented the whole framework — the say-this-not-that, the recap email — in Discovery Call Mastery, free. By the end of a good call, we know which package fits their day — which means the quote writes itself.
Phase 4 — The quote, and the two-week hold
The quote goes out within a day, and it's built on one piece of pricing psychology: the first number they see is the lowest honest configuration of what they want, with everything else as optional add-ons. No sticker shock — they build up from a comfortable anchor instead of negotiating down from an intimidating one. The contract is attached to the quote, so approval flows straight into signing.
Then — and this surprises people — we don't follow up. The quote holds their date for two weeks, and the quote itself expires on the same day. The deadline does the following up. One exception, and it's a genuine courtesy, not a tactic: if another couple inquires about their date inside the window, we tell them. After the two weeks, the date is simply open again — no notification.
Email · Quote sent
Subject: Your proposal — and [date] is held for you
Hi [First Name],
It was a pleasure talking through your day. Your proposal is ready:
[Quote link]
It starts with the essentials we discussed, and the add-ons are listed so you can shape it however feels right. The contract is attached to the same link, so when you're ready, approving and signing happen in one place.
We're holding [date] exclusively for you for the next two weeks — the proposal expires on [expiry date]. If another couple inquires about your date before then, you'll hear from us first.
Any questions at all, just reply.
[Your Name]
[Your Studio Name]
Email · Courtesy date notice (only if it happens)
Subject: A quick heads-up about [date]
Hi [First Name],
No pressure — just keeping my word. Another couple has inquired about [date]. Your proposal still holds the date exclusively until [expiry date], so nothing changes unless that day passes.
If you've already decided, approving the proposal locks everything in. If you're still thinking, that's completely fine too — I just didn't want you to hear it any way other than from me first.
[Your Name]
Phase 5 — Booking: retainer, contract, and the confirming questionnaire
When they approve the quote, Táve runs the sequence: a short questionnaire fires first — names, locations, date. It looks administrative; it's actually a quiet SOP masterstroke: the client enters their own details, which confirms everything in their handwriting before a contract exists. Then the contract (annotated teardown here — with the merge tokens that weld this exact order into the signed document), and the 20% reservation retainer — retainer, never deposit. Signature and payment, all inside Táve, no email tennis.
Phase 6 — "Officially yours"
The moment the retainer clears, this goes out — part celebration, part onboarding:
Email · Booking confirmed
Subject: It's official — [date] is yours
Hi [First Name] and [Partner Name],
Your retainer is confirmed and your contract is signed — [date] is officially yours. We could not be happier to be part of it.
One small piece of housekeeping: your client portal is ready. Use the invitation in this email to create your login — inside you'll find your quote, your contract, and your questionnaires, all in one place, any time you need them:
[Portal link]
Here's what happens between now and the wedding:
- Around a year out, we'll reach out to schedule your engagement session [if included].
- Six months out, a short check-in questionnaire — and we'll open your collaborative Event Guide.
- Three months out, we'll finalize the guide together: timeline, family shot list, and every detail of the day.
Until then — enjoy being engaged. We've got the rest.
[Your Name]
[Your Studio Name]
The client isn't the only one who hears the news. The same booking trigger does two more things. First, the team gets notified — everyone assigned to the job: assistant, associate photographers, video, and the photo editor. They know the date is real before the couple has closed the confirmation email, which means calendars get blocked months out, not weeks:
Email · Internal — to the team (on booking)
Subject: BOOKED — [Couple], [date], [venue]
Team,
New wedding on the books: [Couple] at [venue] on [date].
Assigned: [Lead] (lead photo), [Associate] (associate photo), [Video Lead] (video), [Assistant] (assist), [Editor] (post).
Block the date now. The full production brief comes a week before the wedding — you don't need to do anything else yet.
[Your Name]
Second, booking arms the whole automated sequence in Táve: every milestone email below is now scheduled off the wedding date, and so is the album-completion reminder that fires after the wedding. One approval click, and the next eighteen months of touchpoints exist. That's the point of a workflow — the decisions get made once.
Phase 7 — The long runway
Between booking and the wedding, three scheduled emails keep the file warm without anyone remembering anything:
Email · ~1 year out (if engagement session included)
Subject: Let's plan your engagement session
Hi [First Name],
The wedding is about a year out — which makes this the perfect season for your engagement session. The best light and locations book early, so let's get yours on the calendar:
[Booking link]
If you have a location in mind, bring it — and if not, we have favorites for every season.
[Your Name]
Email · 6 months out
Subject: Six months! A short check-in — and your Event Guide
Hi [First Name],
Six months to go. Two small things to keep everything effortless:
1. A short check-in questionnaire — five minutes, confirms the details we have and catches anything that's changed:
[Questionnaire link]
2. Your Event Guide is open. This is a collaborative document we build together — the timeline, your family shot list, locations, and every name and detail we need to photograph your day like we've known your family for years. We've started it for you; add, edit, and comment freely:
[Event Guide link]
No deadline yet — we'll finalize it together at the three-month mark.
[Your Name]
Email · 3 months out
Subject: Three months — let's finish your Event Guide
Hi [First Name],
Three months out — time to put the finishing touches on your Event Guide:
[Event Guide link]
The parts that matter most: the timeline, the family shot list (every name spelled the way you want it called out), and any family dynamics or must-have moments we should know about. Once it's complete, our whole team works from this one document on the day.
If it's easier to talk it through, grab fifteen minutes here: [Booking link]
[Your Name]
The Event Guide itself
The guide is a collaborative Google Doc — we build the first draft from their questionnaire, send it for approval, and the couple edits it directly: shot list changes, notes, timeline moves. By the wedding it's a document they shaped, and the whole crew works from it. Nine sections: locations · the team · the schedule · the family (every name) · the shot list in priority order · photo notes · video notes · details (guests, attire, colors) · vendor tags. I've published a sanitized example with fictional names so you can copy the structure: the example Event Guide. (Family formals go faster if the names come from a real tool — the Shot List Builder exports straight into this.)
Phase 8 — The week before
Seven days out, two things happen on the same day. First, a final call with the couple — we walk the Event Guide top to bottom one last time: timeline, names, the shot list, anything that changed since the three-month pass. After this call, the document is frozen and it becomes the single source of truth for the day.
Email · Final call (1 week out)
Subject: One week! Let's do the final walkthrough
Hi [First Name],
One week out — it's really happening. Let's grab twenty minutes this week to walk through your Event Guide together one last time: the timeline, the family list, and anything that's changed.
Pick a time here: [Booking link]
After this call we lock the document, and our whole team runs your day from it.
[Your Name]
Second, the team gets the production brief — the finished Event Guide plus the logistics that should never be solved on a wedding morning. Call times per role, where to park, who's driving with whom: transportation gets coordinated this week, in writing, so the day itself starts with coffee instead of texts.
Email · Internal — team brief (1 week out)
Subject: [Couple] — [date] — your production brief
Team,
Here's everything for Saturday: [Event Guide link]
Read it before the day — timeline, family names, shot list, and notes are all in there.
Logistics:
- Crew start: [time] at [location]. Be shooting-ready, not arriving-ready.
- Transportation: [who's driving / meeting point / parking notes]. Sort any changes in this thread THIS WEEK — not Saturday morning.
- Everyone shoots dual card slots, including video. Slot 2 is your backup and it goes home with you.
- Time sync at crew start — all cameras and audio.
Questions in the thread. See you Saturday.
[Your Name]
Phase 9 — After the wedding: cards, ingest, and the archive
The wedding-day run sheet gets its own write-up later — but here's what happens the moment the last dance ends. Before anyone leaves, I collect the memory cards — every primary card from every shooter, photo and video, into one case that rides home with me. Nobody's night ends with client files scattered across five camera bags.
The safety net behind that: everyone on my team shoots dual card slots — including video. The second slot writes a duplicate that stays with the shooter, and the policy is that they keep that backup for at least six months. For my long-term shooters — which is all of them — I make it easy: I buy them the hard drives. They back up to a studio-issued drive; when it fills, they hand it back, I put it into storage, and they get a fresh one. The backup outlives the delivery, and it never depended on anyone's personal diligence budget.
Home from the wedding, the ingest is deliberately boring: everything drags onto a Mac mini wired to two drive hubs, eight bays each, filled with 22 TB drives running in mirrored pairs — RAID 1, so every file lands on two physical disks at the moment of ingest. (The full storage and archive setup deserves its own entry — it's coming.)
One honest note: there's an app called Photo Mechanic that verifies files during ingest and renames everything on the way in — a lot of photographers I respect build their whole intake on it. I don't use it yet, purely because I haven't gotten around to trying it, and I probably should. Take that as a real recommendation from someone who hasn't earned it firsthand.
Next comes building the Lightroom catalog — and that's where this document currently ends.
This SOP now runs from first inquiry to the ingest drives spinning down — for now. The wedding-day run sheet, the Lightroom catalog build, editing, and delivery get added as I write them. It's a living document, like every good SOP.
A Living Document
The newsletter hears first when the next phases land.
Your market sets your ceiling: why pricing advice doesn't travel.
Most pricing advice in this industry has an invisible asterisk:*in my market. The educator telling you to "just charge $8,000" shoots in Manhattan. You shoot in a county where the entire wedding — venue, catering, dress, everything — costs $18,000. Their advice isn't wrong; it just doesn't travel. NYC isn't rural Ohio. (No offense, Ohio — your barns photograph beautifully.) Copying big-market prices into a small market doesn't make you premium. It makes you unbooked.
So here's the frame I use on every coaching call, and it has three parts: your costs set your floor — that's math. Your market sets your ceiling — that's geography. Your positioning decides where between them you live. The floor I've already written about: run the 50% Rule — the free profit calculator does that math for you — and you know the number below which every booking loses you money. This post is about the ceiling.
What weddings actually cost, by market
Ranges from my own market, my coaching calls, and twenty years of watching this industry — experience, not a survey. Full-day coverage for a wedding around 150 guests:
$8–12k+Major-metro top end (NYC, LA, Miami). My studio's range for a 150-guest wedding is $8–10k, and the most popular add-on — a second photographer — is another $2k. Above this tier the ceiling basically disappears: $100k+ weddings exist, and they hire photographers accordingly.
$5–8kEstablished major-metro. Strong portfolio, real referral network, city venues. Most "successful big-city photographer" advice is written from here.
$3.5–6kMid-size city. A healthy market with a real top end — thinner than a metro's, but present at the country clubs and the two best venues in town.
$2–4kSmall town / rural. A full calendar is absolutely buildable here — at numbers that match what the area's weddings cost. The 50% Rule matters most in this tier, because thin margins hide easiest in low prices.
One giant caveat, and it's the most interesting thing on this list: geography lies. The Hamptons is a collection of small towns — and one of the most expensive wedding markets in America. Aspen, Napa, coastal Connecticut, half the lake towns in Michigan: tiny populations, enormous money. Your market isn't defined by your population density. It's defined by money density — and specifically by the venues you shoot, not the city on your driver's license.
How to read your own market
Nobody publishes your market's real number, but it's sitting in plain sight if you know where to look. This is the homework I assign on coaching calls:
Price your true peers.
Not the market average — the photographers at your level. Find five whose work honestly sits where yours does (couples compare you to them, not to the median), and find their numbers: pricing pages, "starting at" lines, or the ask-a-planner route. Where they cluster is your market's read on your tier.
Read the venues, not the census.
What do your five most common venues charge for a Saturday? What's catering per head? Couples anchor every vendor budget to the venue bill. If the venues you shoot run $15k+ before food, your ceiling is higher than your zip code suggests.
Ask a planner what budgets run.
Planners see every line of every budget. One coffee with a planner who works your venues tells you more than a year of guessing — and builds exactly the referral relationship the top of this industry runs on.
Sanity-check with public data.
County household income and the published "average wedding cost" surveys are blunt instruments — but if the survey says weddings in your metro average $35k and you're charging $1,800, the blunt instrument is still telling you something.
The booking-rate signal
Once you're priced, your inquiry close rate becomes the live gauge. The heuristic I use: if you're booking most of the qualified couples who inquire, you're underpriced. Healthy in a good market looks like booking roughly one in three or four. Booking eight out of ten doesn't mean you're beloved — it means you're the bargain, and your calendar fills with weddings that each subsidize the couple's decision not to think twice. When you're consistently above that band, raise 10–15% and hold. Repeat until the close rate settles into the healthy range. That's your ceiling, found empirically — no survey required.
A composite from my coaching calls — call her Dana: mid-size Midwest market, gorgeous work, priced at $7,500 because a California educator said that's what "premium" charges. She booked three weddings in a year. Her market's best venues ran $12k total. We repriced at $4,200 — top of her actual market — and she booked out the next season, then raised twice. The advice wasn't bad. It was just written for a different city.
The hot take: move where the money is
The polite version of this advice says "market to destination couples" or "import city clients." I'll give you the impolite version I actually believe: if your ceiling is too low for your ambition, go where the money is. Physically. The photographers I know who broke into real numbers didn't trick wealthy couples into flying them out of a low-cost market — they moved to the metro, or planted themselves in the wealth pocket within driving distance and shot there until that market knew their name. Money density is a place. You can visit it occasionally, or you can work in it.
A word about the word "luxury"
Luxury is a made-up word. Real luxury is quiet, and it lives in the details — nobody at a $100k wedding is using the word. And the photographers working at that level aren't there because they "went luxury": they're the 1% who pair impeccable work with a serious network — planners, venues, and a client list that keeps referring the next client. That isn't a pricing tier you declare on your website. It's an ecosystem you earn your way into, one relationship and one flawless wedding at a time. Price to your market's ceiling; build the network that raises the ceiling.
Common questions
How much should a wedding photographer charge?
There's no universal number — it depends on your market and your level within it. Find your cost floor with the 50% Rule, read your ceiling from peer pricing and venue costs, then use your booking rate to find your spot between them. In major metros, established photographers charge $5–8k+; in small markets, a strong full-day package runs $2–4k.
What do wedding photographers charge in NYC?
At the established end, roughly $8,000–$10,000 for a 150-guest wedding, with a second photographer around $2,000 more — and an effectively unlimited top end above that.
How do I know if I'm underpriced?
Your close rate. Booking most qualified inquiries means the market considers you a bargain. Raise 10–15% until you're booking roughly one in three or four, and check your true margin with the profit calculator.
Can I charge premium prices in a small market?
You can charge the top of your market — every market has a best-paid photographer. But the ceiling is real. If it's too low for your ambition, look for the wealth pocket within reach, or move where the money is.
Read Your Market With Me
Finding your ceiling is literally what the first coaching call does.
SEO isn't one thing. It's three engines — and each one can run itself.
When photographers say "I need to work on my SEO," they almost always mean one thing: ranking on Google for "[city] wedding photographer." Which is a shame, because that's the single most contested phrase in the industry — and it's only one of three places couples actually find you. My studio treats SEO as three separate engines, each with its own fuel, and — this is the part that matters — each with an automation so it keeps running during wedding season, when every marketing habit you have will otherwise die.
Engine one: the blog. Claude does the heavy lifting.
The strategy is simple and criminally underused: go after venue keywords, not photography keywords. "[Specific venue] wedding" is searched almost exclusively by couples who have booked that venue, have a date, and are actively hiring vendors. There are hundreds of venues and almost nobody competing for them. One post per real wedding, structured around the venue, and after a year you own fifty of those searches while everyone else fights over the big phrase.
The catch was never strategy — it's that blogging a wedding used to eat a full day, so nobody sustains it. That's the part I automated. My workflow runs on Claude: it catalogs the selects, renames every file into an SEO slug, optimizes them for web, drafts the post in my voice with the venue keyword placed where it matters, sets the alt text, and preps one outreach email per vendor — as drafts, for my review.
The automation: a weekly scheduled task. I drop a curated folder of selects into staging; Monday at 9 AM, Claude turns it into a ready-to-review draft. My only recurring job is to read it and hit publish.
Consistency beats brilliance here — Google rewards the site that publishes every week for a year, not the one that publishes five perfect posts and goes quiet. The full system, prompts included, is in my Blog Publishing Workflow guide, with paths for WordPress and for custom-built sites.
Engine two: Google Business Profile. The free real estate almost everyone ignores.
For "[city] wedding photographer," most couples never scroll past the map pack — the three businesses Google shows above every organic result. Getting into that box has almost nothing to do with your website. It's your Business Profile: complete categories, accurate service area, and above all reviews — their count, their recency, and whether you reply. A profile with fresh reviews landing every month outranks a prettier competitor whose last review is from two years ago. Google also quietly rewards profiles that act alive: new photos, regular posts, answered questions.
Nobody remembers to do any of that manually in October. So:
Review requests ride the delivery automation.
In Táve, the review ask is part of the post-gallery email sequence — every delivered wedding produces a request automatically, which is what keeps recency alive. (This is the same automation stack from the pipeline entry.)
Replies get drafted, not composed.
When a review lands, have Claude draft the reply — warm, specific, venue named (that text is indexable) — and approve it in ten seconds instead of staring at a blank box for a week.
Posts and photos get batched monthly.
Once a month, have Claude pull from the weddings you just blogged and prep a batch of Business Profile posts and a set of fresh photos. Fifteen minutes of uploading covers four weeks of "this profile is alive" signal.
Engine three: Pinterest & the wedding platforms. The slowest burn, the longest life.
Here's the thing photographers miss about Pinterest: it isn't social media, it's a search engine where weddings get planned — usually months before a single vendor is hired. An Instagram post is dead in a day. A pin surfaces in searches for months, sometimes years, and every one of them links back to your blog post, which links to your contact page. It's the top of the funnel with the longest half-life of anything you can publish.
The motion is mechanical, which is exactly why it's automatable: every blog post yields three or four pins — different images, keyword-rich titles and descriptions ("[venue] wedding ceremony," "spring wedding at [venue]"), pinned to boards organized the way couples search: by venue, by season, by style.
The automation: pin creation happens in the same session as the blog post — Claude picks the images and writes every title and description while the post is still open — and Pinterest's own free scheduler spaces them out over the following weeks. Publish once, drip for a month.
And if your blog has an RSS feed, Pinterest can auto-publish new pins from it entirely hands-free — that's the fully automated tier, worth setting up the day your posting rhythm is stable.
The same engine has a second cylinder most photographers never fire: the wedding platforms. The Knot, WeddingWire, Zola, PartySlate, Carats & Cake — these are high-authority wedding domains where couples already are, and every one of them will link back to you. Two motions matter. First, claim and complete your vendor profiles on The Knot, WeddingWire, and Zola — a finished profile with fresh galleries is both a directory listing couples actually browse and a permanent backlink from a domain Google deeply trusts. Second — and this is the underused one — submit your real weddings for features on PartySlate and Carats & Cake. A published real wedding means your name credited on a luxury-wedding domain, a do-follow link, and planners browsing exactly those galleries when they build their vendor short lists.
The automation: the submission package is 90% identical to the blog post you just made — selects, venue, vendor list, a short story of the day. So it gets prepped in the same Claude session: while the post drafts, Claude also assembles the feature submission (the platform-sized image set, the full vendor credits with links, the description) and the profile-gallery update. One wedding in, four surfaces out: your blog, Pinterest, the directories, and a feature submission.
Why three engines beat one
Because they feed each other. The blog post gives Pinterest its pins, the Business Profile its photos, and the wedding platforms their feature submissions. The review mentions the venue, which reinforces the exact keyword the blog post targets. A couple finds a pin in January, reads the venue post in February, sees forty reviews in March, and inquires in April — and every step of that chain ran on a schedule while you were shooting.
None of this is glamorous. That's the point. The photographers who win search aren't the ones with the best eye for SEO — they're the ones whose system kept publishing in the months everyone else got busy.
The scheduler was next: we replaced a $12-a-month booking app with an afternoon and Claude.
After the website rebuild, I started auditing every subscription the studio pays for with one question: is this software doing something hard, or is it just doing something first? The scheduler was next on the list — $12 a month so couples and photographers could pick a time on my calendar. Good software, genuinely. But the job it does is small, and I now own a website that can do small jobs.
So I gave Claude the same brief I'd give a developer. It was four sentences long:
"I need something that syncs with my calendar and blocks out times I'm not available. The client selects a date and time, enters their info, and gets a generated Google Meet link. I get a notification and it shows up in my calendar. And a reminder is set an hour before the call."
That paragraph was the entire spec. An afternoon later, learn.alexknightstudio.com/book was live on my own site, in my own design, running on the same free hosting as everything else.
Everything it does
Reads my real calendar. Anything on it — weddings, edits, personal — blocks those slots automatically. No separate availability to maintain.
Follows my rules. 30-minute calls inside working hours, a 12-hour minimum notice so nobody books tomorrow morning at midnight, a 15-minute buffer around existing events, and a 21-day booking window.
Speaks the client's timezone. Slots display in whatever timezone the visitor is sitting in.
Can't double-book. The calendar is re-checked at the moment of confirmation — if two people race for a slot, the second one is asked to pick again.
Generates the Google Meet link instantly. It's on the confirmation screen and in a proper calendar invite in the client's inbox before they close the tab.
Lands on my calendar with a notification. The event appears with the client's name, email, phone, and notes — and I get an email the moment it's booked.
Reminds everyone an hour before. Email and popup, built into the event itself.
Fails politely. If anything's ever down, the page falls back to "email me" instead of a broken widget.
What a booking looks like
Maya, a planner in Chicago, opens /book.
She sees next Thursday has openings and picks 2:00 PM — her time. The system knows that's 3:00 PM mine, and that my 3:30 is already blocked by an edit session it quietly buffered around.
She enters her name, email, and what the call is about.
Twenty seconds of typing. No account, no app, no "this app would like access to…" screen.
The Meet link appears on her confirmation screen.
The same second, a Google Calendar invite lands in her inbox with the link inside.
On my side, everything just happens.
The call is on my calendar with her details in the event, a booking email is in my inbox, and an hour before the call we both get reminded. I did nothing.
The math, again
$12 a month is $144 a year. The replacement runs on a single serverless function and Google Calendar's own machinery — both free at any volume a photography studio will ever see. Add the $636 the website rebuild saved and the subscription audit is now worth about $780 a year — for software that fits my business better than what it replaced, because it was built to my spec instead of everyone's.
That's the real pattern worth stealing: the subscriptions most worth replacing aren't the expensive ones. They're the ones whose whole job you can describe in four sentences.
Inside the machine: how an inquiry becomes a booked wedding.
A studio that photographs 45 to 50 weddings a year doesn't run on memory. It runs on a pipeline — the same sequence, every inquiry, no exceptions. Ours lives in Táve (now part of VSCO): every inquiry, quote, contract, invoice, questionnaire, and team assignment in one place. This is the whole thing, start to finish, including the parts most photographers get backwards.
Step zero: an auto-reply that promises a human.
Every CRM fires an instant "we got your inquiry!" email — ours does too, but it's built to do exactly two jobs: confirm receipt, and put our reply time in writing while we check the calendar. What it deliberately does not do is pretend to answer the only question the couple actually asked — are you free on our date? That answer always comes from a human, fast: within two hours during weekday business hours, within eight on weekends — the same numbers the auto-reply promised. Speed is the real automation. It's also the first proof of how we'll treat them as clients.
The first reply does four jobs
Congratulate them.
They got engaged. The first sentence of the first email is about them, not about us. You'd be amazed how many photographers skip straight to the price list.
Answer the date.
Available or not, say so plainly. If we're not, we say who we'd recommend — planners remember that.
Share pricing.
The full guide, not a teaser — more on how that's built below.
Show their venue.
Galleries from their actual venue — same time of year and the same kind of celebration when we have it. A couple looking at their own ballroom, in their own season, stops comparison-shopping.
The email ends with one link: our booking page. No "let me know if you have questions." A specific next step — pick a time — converts; an open loop doesn't. (For years that link went to a paid scheduling app. We've since replaced it with a scheduler we built ourselves — that build got its own entry.)
Pricing that filters before it sells
Our starting price is printed on the website's contact page. That's deliberate: it costs us some inquiries, and every one it costs us is an inquiry that was never going to book. The couples who do reach out already know the neighborhood they're shopping in.
Behind that starting number, the pricing guide isn't one document — it's several:
By dateLead vs. associatePhoto / video / albums split
We don't treat every weekend the same. A peak-season Saturday carries a premium and a higher minimum; an off-season Friday gets friendlier numbers. Both directions, on purpose — the premium protects the dates everyone wants, the discount fills the dates nobody asks about. And because photo, video, and albums are priced as separate lines, there's always room to reward a couple for bundling without discounting the core.
Different guides for different dates also means we're never "negotiating." The price for their Saturday simply is the price for their Saturday.
The call
What we tell them it's for: a relaxed walk through their day — timeline, venue, what they care about — to see if we're the right fit. All true. What it's also for: qualifying seriousness, building the trust a five-figure booking requires, and steering toward the package that actually fits their day. Nobody books a luxury photographer from a PDF; they book from a conversation.
One tool worth naming: we run Granola on every call. It takes the notes while we stay in the conversation, and the recap writes the follow-up email practically by itself. (That deserves its own entry — coming soon.)
I've written a full guide on exactly how we run these calls — the six-stage framework, the say-this-not-that, the recap email. It's free: Discovery Call Mastery.
The quote: nobody should have to guess
Within a day of the call, the quote goes out from Tave — and it spells out everything we discussed, in writing:
Coverage, exactly.
Hours, locations, and who's on the team that day — lead, second, assistant. Names where we can.
Deliverables with timelines.
What they receive and when — sneak peeks and the full gallery each get a written delivery window. "You'll get them when they're ready" is not a timeline.
Album specs, if included.
Size, pages, design rounds — the things that otherwise become a surprise conversation a year later.
The money, all of it.
Package total, the retainer to book, the payment schedule for the rest, and an expiration date on the quote itself. An open-ended quote invites an open-ended decision.
The contract is attached to the quote — one link takes them from reviewing the offer to signing to the first invoice without another email from us. Friction kills bookings in the gap between "yes" and "signed," so we removed the gap.
And it's a 20% retainer — retainer, not deposit. The word matters legally and it matters in tone. (The full contract now has its own annotated teardown — steal it.)
After the booking, the robots take over
Everything up to the signature is deliberately human. Everything after it is deliberately automated. The Tave automations that earn their keep:
Payment reminders alone justify the software — chasing money is the worst conversation in this business, and now a polite machine has it for us. The anniversary email is the sleeper: it costs nothing, lands on the happiest date on their calendar, and quietly asks nothing — which is exactly why it produces referrals.
Staffing runs through Tave as well: every job carries its roles — lead, second, assistant — and the team sees their assignments in one place instead of in a group text. How we decide who shoots what is its own topic for another day.
The pattern under all of it: human where it builds trust, automated where it doesn't. Fast replies, real conversations, and paperwork that runs itself.
I replaced my $53-a-month website builder with two days and Claude.
First, this is not a takedown of the builder. My studio site lived on a popular drag-and-drop website builder for years and it earned its place — the drag-and-drop editor is genuinely good, it's built for photographers, and when I was redesigning constantly, it was worth every dollar. If you're in that season, stay in it.
But I wasn't in that season anymore. The site was finished. I'd touch it a few times a year — swap a gallery, update a price. And I was still paying $53 a month, every month, for the privilege of hosting a design that was done. Somewhere along the way the subscription had stopped buying me design tools and started being rent on my own website.
A subscription you use is a tool. A subscription you've outgrown is rent.
What I actually did
I don't write code. That's not modesty — I can't write a line of it. What I can do is describe what I want, and it turns out that's now the whole job. I gave Claude an export of my old builder site and screenshots of every page, and asked it to rebuild the whole thing as plain HTML and CSS: same fonts, same layout, and — this part matters — the same URL for every single page, so years of Google rankings didn't reset to zero.
Total time: about two days, spread across a migration I ran alongside normal studio work. Here's roughly what the conversation looked like:
claude code · alexknightstudio.com
The actual shape of the process — describe, review, deploy.
That's it. No template, no page builder, no plugins. The site is now a folder of files that I own outright, hosted for free, and when I want something changed I open Claude and say what I want changed.
The honest math
Builder subscription, $53/month × 12$636 / year
Hosting the rebuilt site (Netlify free tier)$0
Domain — which I was already paying either way~$15 / year
Back in my pocket, every year, forever~$636
The other big reason: SEO
The money made the decision easy. The SEO made it obvious. Builder sites are heavy by nature — all that drag-and-drop flexibility ships to your visitors as layers of scripts and rendering code the browser has to chew through before a single image appears. Google has been explicit for years that page speed is a ranking signal, and a wedding blog full of galleries feels that weight most of all. The rebuilt site is plain HTML with optimized images: same design, a fraction of the load time, nothing between the couple and the photos.
And there's a newer game that builders haven't caught up to: AI search. Couples increasingly ask ChatGPT, Claude, and Perplexity for vendor recommendations — and AI crawlers don't fight through a builder's rendering layer, they read clean HTML. When you own the code, optimizing for that is a sentence, not a project: I asked Claude to add structured data telling search engines exactly who I am and what I charge, an llms.txt file — a plain-text overview written specifically for AI models — and descriptive markup on every page. Inside a builder, you get whatever SEO boxes it decided to expose. On my own site, if a new standard shows up next year, I ask Claude to add it that afternoon.
Cheaper, faster, easier to find — by Google and by AI. There's no catch in that sentence.
Who should not do this
Fair is fair. If you redesign your site every month, love tweaking layouts visually, or panic at the idea of not having a drag-and-drop editor — keep your builder. It's good software, and $53 a month is cheap for something you actively use. This move is for photographers whose site is essentially done: if your last real design change was over a year ago, you're not a software customer anymore. You're a tenant.
The part that surprised me
The rebuild was supposed to be about the $636. The website was just the first domino: the next subscription to fall was the $12-a-month scheduler — we replaced our scheduling app with one serverless function. And the blog now publishes through the same conversation. Claude writes the post page in my site's exact design, renames and optimizes the images for SEO, updates the blog index, and deploys — the workflow I used to dread became the one I run weekly. I documented that entire system, prompts included, in a private guide.
The Follow-On System
The same approach, applied to publishing every week.
Ask a photographer what they charge and you'll get an instant answer. Ask what they keep, and the room goes quiet. That gap — between the price on the proposal and the number that actually lands in your pocket — is where most photography businesses quietly fail while looking successful from the outside.
Here's the honest math. Take one wedding. Start with the package price. Subtract everything that wedding actually costs you: the second photographer, the editor or your own editing hours at a real rate, albums at wholesale, travel, and — the one everyone skips — a slice of your annual overhead. Insurance, gear, software, website, education: it all exists so you can shoot weddings, so every wedding carries its share. What's left, divided by the package price, is your true margin.
If you keep less than half of what a couple pays you, you don't have a pricing strategy. You have a job with unpredictable hours.
Where the line sits
After running this math on my own studio for years — and on dozens of photographers' numbers in coaching calls — the zones are remarkably consistent:
Under 40%You're subsidizing your clients' weddings. Every booking makes the problem bigger, not smaller. Stop marketing and fix the price first.
40–50%Survivable, fragile. One slow season or one gear failure eats the year's profit. Most "busy but broke" photographers live here.
50–65%A real business. You can pay yourself properly, reinvest, and say no to bad-fit inquiries. This is the minimum target.
65%+Luxury-market territory. Margin like this is what funds great client experience — which is what justifies the price. It compounds.
Why 50% and not "whatever's normal"
Because you are not a product business — you are selling a fixed, perishable inventory of Saturdays. You can't manufacture more of them. When each one nets you 35%, the only lever left is volume, and volume is exactly the thing that destroys the quality that lets you raise prices. It's a trap that gets tighter the harder you work.
At 50%+, the math flips. Every wedding funds the business and your life, so you need fewer of them, so each one gets more of your attention, so the work gets better, so the price can rise again. That loop — not talent — is what separates the photographers who are booked from the ones who are booked and paid.
Do the math today
Not estimates — your real numbers, from your last full year. Most photographers who do this honestly for the first time land in the amber zone and are surprised. That surprise is the most valuable thing on this page: you can't fix a number you've never calculated.
