One complaint stands out as oddly specific and easy to overlook: 'Lightroom Classic does not access Adobe AI services for tagging photos and lacks a file backup system.' This isn't about editing at all — it's about the organizational half of the workflow, which is supposed to be Lightroom Classic's strength. Adobe has built AI auto-tagging (face recognition, subject detection, semantic search) into Lightroom cloud, but deliberately excluded it from Classic. The backup situation is similarly neglected: Classic stores everything in a local catalog file with no native cloud sync for the catalog or the originals.
Why does this gap persist? Because closing it would make Classic self-sufficient and slow migration to Lightroom cloud, which is where Adobe's subscription growth story lives. Classic users are disproportionately the most invested, highest-volume photographers — the ones with 200,000+ images in catalogs built over a decade — and they're the least likely to migrate willingly. Adobe's incentive is to let Classic stagnate on organization features specifically.
This creates a real recurring cost for Classic users: a working photographer with a 10-year catalog and no tagging AI spends hours doing manual keyword entry, and a photographer whose external drive fails loses an irreplaceable catalog with no automatic recovery path. A standalone service that connects to a Lightroom Classic catalog via file-system access, reads the SQLite schema, runs local AI inference for subject and face tagging, writes those tags back as proper Lightroom keywords, and syncs the catalog file plus sidecar XMPs to cloud storage on a schedule — would give Classic users the two most-requested missing features without requiring them to touch Lightroom cloud or pay Adobe more.
What to build
Build a background service for macOS and Windows that monitors a Lightroom Classic catalog file, runs on-device AI tagging (faces, subjects, scenes) and writes results back as Lightroom-compatible keywords and color labels, while also syncing catalog snapshots and XMP sidecars to the user's chosen cloud storage provider on a configurable schedule.
Where to start
Start with catalog backup only — it's dead simple to ship, has zero accuracy risk, solves a problem that causes real financial loss when it fails, and gets the service installed and trusted on the user's machine before the AI tagging feature is introduced as an upgrade.
The hard part
On-device AI inference good enough to match what photographers expect from cloud-based tagging requires bundling models that are 1-3GB per install — that's a high-friction download for a utility, and first impressions on tagging accuracy need to be nearly perfect or users abandon it immediately and leave negative reviews that kill word-of-mouth.
How it makes money
Subscription at $8/month — cheaper than the incremental cost of upgrading to Creative Cloud just for Lightroom cloud features — with cloud storage either bundled (using commodity object storage at cost) or connected to the user's own Backblaze or S3 bucket.
See the evidence. The complaints behind this idea, the products they came from, and similar ideas in Photo Editing.
More ideas in Photo Editing