Layer audit and naming enforcer for design teams

The moment it becomes a problem: a project file comes back from a contractor with layers named 'Layer 47', 'copy of copy of Background', and a dozen unlabeled groups — and the in-house editor now has to reverse-engineer the entire structure before touching anything. This happens constantly in teams where multiple people touch the same file, and there is no enforced convention or audit step before a file enters the production pipeline.

This gap persists because it's a process problem that individual software vendors have no incentive to solve — Adobe sells to the individual designer, not to the team's quality control workflow. Layer naming discipline is a human coordination problem that sits in the gap between the editing software and whatever project management or file storage system the team uses. Nobody has built enforcement into the file-acceptance step.

Users describe the specific downstream cost: 'it is easy to lose track of which layer holds which object when working on complex projects' and layers without names or tooltips force people to 'Google solutions' when something is locked or broken. The compounding version of this: when groups are nested inside groups with generic names, resizing or masking one layer 'affects the entire image, often forcing me to delete all actions in history and start over.'

This is a business because the audit need recurs every time a file moves between hands — which in any agency or in-house creative team happens on a fixed cycle tied to project delivery. The buyer is a creative director or production manager, not the individual designer, which means purchasing decisions are made on team efficiency grounds rather than personal preference. That's a stickier, higher-value sale.

What to build

Build a CLI and web dashboard that accepts a PSD or Affinity Photo file upload, runs a configurable audit against team-defined naming rules (e.g., all text layers must be named, no 'copy of' names, groups must have descriptive names), and returns a pass/fail report with a layer-by-layer checklist — integrable into a Dropbox or Google Drive folder watch so files are checked on arrival.

Where to start

Start with agencies that use Dropbox Business or Google Shared Drives for file handoff — the folder-watch integration gives you a natural trigger point that doesn't require anyone to change their existing workflow, which removes the adoption barrier and lets the audit run passively before teams even fully commit to using it.

The hard part

Getting teams to actually enforce the audit at handoff — rather than bypass it under deadline pressure — requires buy-in from the art director AND the individual designers, so you're selling a behavior change to two different stakeholders simultaneously, which makes the initial sale longer and harder than a pure tooling purchase.

How it makes money

Monthly team subscription based on number of seats or number of files audited per month, starting around $30–60/month for a small team, with a free tier for solo designers that caps at five file audits per month.