My twins were seven years old when they got into my office and started clicking around on my iMac. By the time I found them, they had dragged an entire folder of client proofs into the trash and emptied it. I had delivered the gallery two days earlier, but the client had already requested a re-edit on six images, and those working files were gone.

Gone for about 90 seconds. Then I pulled them off my second local backup drive, which mirrors my working directory every four hours via ChronoSync. I finished the re-edit. The client never knew anything happened.

That story isn’t about my kids. It’s about what happens when a system works the way it’s supposed to, and how most photographers are one bad afternoon away from learning an expensive lesson.

The Backup Stack That Actually Holds Up

I run a 3-2-1 backup system, and I test it the first Saturday of every month. Three copies of every file, two different media types, one offsite. In practice: my primary working drive is a 4TB Samsung T7 Shield. Files copy to a second local 4TB WD My Book every four hours. A third copy goes to Backblaze cloud backup, which runs continuously in the background at about $9 per month.

After a shoot, the first thing I do before I even make coffee is copy the cards to the primary drive using two separate card readers simultaneously. I do not format those cards until both copies are confirmed. Photo Mechanic handles the initial cull and metadata injection, usually in under 20 minutes for a 400-image shoot, because it reads JPG previews embedded in RAW files rather than rendering from scratch the way Lightroom does. That alone saves me 45 minutes per session.

Total hardware cost for this setup: roughly $350 upfront, plus $9 monthly. The cost of losing a client relationship because you can’t deliver a re-edit: incalculable.

Lightroom Catalog Structure That Won’t Collapse Under You

Most photographers I talk to are running one massive Lightroom catalog. That works until it doesn’t, and usually it stops working at the worst possible moment. I use one catalog per year, stored on the primary drive, with a folder structure that goes Client Name / Year / Job Type / Shoot Date. Every catalog has automatic backups set to “once a day, upon starting Lightroom,” written to a separate folder on the local backup drive.

My develop presets are organized into four groups: base exposure corrections, color grading by genre, skin tone adjustments, and delivery sharpening. I have 22 presets total. Photographers with 200 presets have a collection, not a workflow. Export settings are saved as named presets: one for web delivery at 2000px on the long edge, sRGB, 85 quality JPG; one for print delivery at full resolution, Adobe RGB, with output sharpening for matte or glossy depending on the job.

Consistency here means I can process a 600-image corporate headshot day and have galleries delivered within 24 hours. That turnaround is a selling point I put on my website, and I can back it up because the workflow is built, not improvised.

What Your Website Is Actually Communicating

Here is the thing most photographers miss: your website is not a portfolio. It is a business document. Clients are reading it to decide whether you are professional enough to hire and reliable enough to pay. A beautiful homepage with no contact form response time, no FAQ, and no clear pricing information tells them nothing useful. It might even make them nervous.

My website runs on Squarespace (Commerce Basic, $23 per month), and it has six pages: home, portfolio split by genre, about, services with pricing starting points, FAQ, and contact. The FAQ page answers the seven questions I used to get on every discovery call. Including that page alone cut my pre-booking email time by roughly three hours per week.

The portfolio is curated to 45 images total across all genres. Not 200. Not a scrolling feed. Forty-five images I would put on my wall. If a client can’t decide from 45 strong images, more images won’t help them.

My contact form has a two-business-day response guarantee, and I have never missed it. That promise is on the page, which means it functions as a commitment to the client before they’ve spent a dollar.

The Client Communication Loop That Prevents 90% of Disputes

When I worked at the newspaper, you delivered or you got replaced. There was no “I’m still editing” and no “can I have a few more days.” That training made me allergic to vague timelines, and it shows up in how I manage client communication now.

Every booked client gets a two-page PDF I call the Job Briefing. It covers the shoot date and location confirmed, the deliverable count and format, the delivery timeline, the revision policy (two rounds of global edits, individual retouching billed at $15 per image), and my contact availability window. I send it within 24 hours of receiving a deposit, and I ask for a signed acknowledgment via HoneyBook before I schedule anything.

Disputes about what was promised drop to nearly zero when both parties have a document they signed. It also protects the client, which is the point. This is not about covering yourself legally, though it does that. It is about starting the working relationship with transparency.

The Folder on My Desktop Called “Lessons Learned”

I keep a running document from every shoot. Not a journal exactly, more like a technical debrief. Wrong white balance because I forgot to reset after the last job. Client expected more candid coverage but we hadn’t discussed it. Parking lot light at the venue was worse than scouted. Each entry is two to three sentences and a corrective action. I review it before any shoot in a similar context.

That document is 47 pages long. It is the most valuable file I own.

The photographers who stay in business long-term are not necessarily the most talented ones in the room. They are the ones who build systems, protect their work, and show up prepared enough to turn the unexpected into something they can deliver on.