The Wedding Photographer's $1,320 Stack: Year 2

The wedding photographer''s $1,320 stack, year 2

One studio. Twelve months. The full ledger — what $1,320 bought in year 1, what the Whimsy-led switch replaced in year 2, the four things that broke, and the four things that held.

Year 1: the 5-tool stack, every line item

A working studio in 2024 ran a familiar stack to deliver a single shoot. The receipt at the end of the year, every line item, is the proofing-zoo total restated as a one-year ledger.

Tool	Job	Year-1 cost
Pixieset	Branded client gallery	$360
ShootProof	Proofing, favourites, contracts	$240
HoneyBook	CRM, contracts, invoicing	$300
Backblaze B2	Off-site backup of source files	$120
Lightroom	Edit + cull	$300
	Annual total	$1,320

Five vendors, five renewal dates, five cancellation policies, and a separate copy of every JPEG in a separate cloud. The credit-card line was the visible cost. The invisible cost was the glue work: 45 minutes per shoot, on average, of uploading the final selects, building the contract, copying the source files into the backup bucket, and chasing the client to mark favourites. Over 30 shoots that is 22.5 hours of billing-zero overhead a year.

Year 2: the 3-tool stack, same workload

The studio replaced the gallery, the backup, and the cloud-to-cloud transfer with one engine — Whimsy — and kept the two products that were already doing real work.

Tool	Job	Year-2 cost	What it replaced
Whimsy	Branded gallery + cross-cloud transfer + object-locked backup	$240	Pixieset, Backblaze B2, the rclone scripts
HoneyBook	CRM, contracts, invoicing	$300	Unchanged — still the right tool
Lightroom	Edit + cull	$240	Unchanged — still the standard
	Annual total	$780

Three vendors, three renewals, one set of credentials for the storage layer, and 14 minutes of glue work per shoot — the upload, the contract hand-off, the backup verification, and the favourites chase all collapsed onto the same delivery record. The studio paid $540 less for the year and reclaimed 15.5 hours of unbilled time.

The gallery, the backup, and the cross-cloud transfer now share one engine, one set of credentials, and one place to check when a client says "I can''t see my photos." The CRM and the editor still own their own jobs and are not going to be replaced by a workflow tool.

The four things that broke

Year 2 was not a clean win. Four things broke, and the post would not be honest if it hid them.

The first 6 TB cross-cloud transfer timed out at 80%. The rclone daemon chunked too aggressively for the studio''s asymmetric home fibre and the resumable job halted mid-flight. Whimsy surfaced the resume token; we restarted with a larger chunk size, and the second pass finished overnight. The original masters were never at risk — the resumable job reads against the source, not against a deleted copy.
A client''s Gmail lost the gallery link to spam on the second pass. A 4,000-photo delivery to a Gmail address was filtered. Whimsy''s expiring-link + reply-to-record pattern caught it: the studio re-sent from the same delivery card, the client opened the link, marked favourites, and signed the contract off the same record. The delivery did not need to be re-issued. The inbox just needed a re-prompt.
The Kopia backup probe flagged our S3 bucket as not having Object Lock enabled. Compliance mode was the policy we asked for; the bucket had been re-issued during a separate migration and the lock was off. Whimsy rejected the backup until the probe said it was on; we re-issued the bucket with the right policy, the next probe passed, and the backup went live. The studio was not "backed up" in the four hours between the migration and the probe — that is the point of a probe.
One Studio Showcase embed dropped its hero image. The source cloud required a fresh OAuth re-consent after a 90-day token expiry, and the showcase did not surface the re-auth fast enough. Whimsy re-prompted the studio account within an hour; the showcase caught up on its next render. The gap was a day, not a week, and the embed recovered without a manual restore.

The four things that held

The four things that broke are a real accounting. The four things that held are a real accounting too.

The gallery never held a copy of the files. Twelve months and 211 deliveries, and the original masters are still in the same Google Drive folder they started in. No second store. No sync drift. The "we never see your files" promise from the proofing-zoo post was load-bearing all year and it held.
The test-restore ran every Sunday at 03:00. The studio inbox received a pass/fail receipt, every week, all 52 of them. The backup was not "on" as a belief; it was a green email on Monday morning. The receipt was the answer to the question "is the backup working?" that no other tool in the studio''s stack had ever answered.
The cross-cloud transfer of the 4.2 TB archive finished in a weekend. Dropbox to OneDrive Business, in the browser, with checksum verification on completion. The studio''s archive had been on the move for the better part of a year under the rclone script and had not moved; under Whimsy''s browser-direct fast path, it moved in a single weekend. The migration cost was a Saturday and a Sunday.
The renewal churn dropped from five dates a year to three. A small thing that compounds. Every removed renewal is a removed hour of "did I remember to cancel that?" The CRM still renews in March, the editor in October, and the storage engine in July. The studio''s calendar has one renewal a quarter, and that is the cadence a working studio can keep straight.

The ledger, year 2

The full 12-month numbers, line by line, no rounding:

Cost: $780/yr across 3 vendors (down from $1,320 across 5).
Glue work per shoot: 14 minutes (down from 45).
Total annual time saved: ≈ 15.5 hours, billable to clients.
Deliveries sent: 211.
Galleries the client lost to spam: 1 (caught on the re-prompt; counted as a "break" above).
Test-restore receipts: 52 (one a week, all green).
Cross-cloud archive transfers completed: 3 (the 4.2 TB, a 1.8 TB incremental, and a one-off 280 GB client archive).
Backups the studio had to re-issue manually: 0 (the Object Lock probe caught the one miss before any data was at risk).

What we still don''t love

The honest accounting is more than the wins. Four things the studio does not love in year 2.

The Whimsy desktop app is still in early access. On Linux the studio runs the CLI, and the CLI is a real CLI — not a wrapper, not a no-op, but a CLI that wants to be configured. The team wrote a one-page runbook for the studio''s junior editor and it is fine, but it is not "install and forget" yet.
The cross-cloud transfer''s browser-direct fast path requires both endpoints to be logged in on the same machine. If they aren''t, the transfer falls back to the server-routed path, which is slower and metered. The studio learned to schedule its large transfers from the studio desktop on Sunday morning, which is honest, but a constraint all the same.
HoneyBook is still the CRM. Whimsy has not built a contract tool, and it is not going to. The CRM swap is a year-3 problem, possibly a year-4 problem, and the studio is fine with that because the contract-to-invoice loop is not the storage layer''s job.
The Lightroom → Whimsy folder handoff is manual. The studio''s editor exports the final selects to a Google Drive folder, then opens Whimsy and selects the folder for the delivery. A Lightroom plugin is on the roadmap; the manual step is honest but it is still a step.

What this proves (and what it doesn''t)

The proofing-zoo post said five tools were doing three jobs. The after-gallery-closes post said the review and the public-review redirect were jobs the gallery did not solve. This post is the receipts — one studio, one year, one ledger. The numbers are real, the failures are real, and the parts that broke were not hidden.

What it does not prove: that the 3-tool stack is right for every studio. A solo photographer doing 5 deliveries a year does not need this consolidation; a studio doing 200+ does. The threshold is somewhere around the 20-deliveries-a-year line, and it is not the same threshold for every working photographer. Studios with predictable clients and short delivery windows can ride the 5-tool stack comfortably; studios with year-long delivery cadences and multiple destinations cannot.

The proofing-zoo was a real solution to a real problem in 2018. The 3-tool stack is a real solution to a real problem in 2026. Neither is the final answer; both are honest pictures of what is possible at the time they were written. Year 3 of this studio''s ledger will be the next honest picture, and the parts that broke then will not be hidden either.

Whimsy is in free early access at whimsy.numeracode.com. The first year of a working studio on a 3-tool stack is the cleanest argument for collapsing the proofing-zoo — and the first year is exactly the year the receipts show up.