Design asset management for small teams — no DAM required

Enterprise DAM platforms earn their price at enterprise scale: tens of thousands of assets, licensed photography with expiry dates, regional teams that must not use last year's packaging, legal sign-off baked into the pipeline. The software is heavy because those problems are heavy — custom metadata models, permission matrices, an administrator who owns the system as a job.

Now the ten-person SaaS team: a few hundred assets, one brand, no licensed-image portfolio, and the entire approval chain is “the design lead said it's final.” Every DAM capability that team pays for and doesn't use has a cost beyond the invoice — heavier onboarding, slower imports, one more system nobody quite owns. Overhead is not neutral; it is why libraries go stale.

The honest question isn't “which DAM?” It's “what is the least system that makes our finished work findable?”

1. Import without friction

The system lives or dies at the import gesture. For a team that designs in Figma, the bar is paste a frame link, get a tagged asset — thumbnail rendered, source reference kept. Thirty seconds, or it stops happening.

2. A type field and a few tags

Asset type as a first-class filter (banner, deck, illustration), plus three to six tags per asset from a capped vocabulary. Skip twelve-field metadata schemas — they are how DAMs die at small scale.

3. Search that actually retrieves

Full-text across titles and tags is the floor; bilingual indexing if your team works in two languages; semantic search for the queries people can't spell precisely. The test: a teammate finds an asset they have never seen in under thirty seconds.

4. Sharing that crosses the team boundary

Sales wants the case-study visuals; an agency needs the campaign kit. Viewer roles and public share links solve this without buying seats for people who will never upload anything.

A shared drive is free and already there — and it fails exactly where you need it to work. Search is filename-only, folders force one classification per asset, and nothing stops the fourth copy of the logo. Fine for archiving; bad at retrieval.

Figma alone keeps everything in one tool, but a design file is a workshop, not a shelf — finished work drowns among explorations, and the people who most need assets don't have seats or the patience to navigate pages of artboards.

An enterprise DAM solves retrieval and ten problems you don't have, at a price and implementation weight sized for the problems you don't have.

A design asset library — the middle shape — does the four capabilities above and stops. No approval workflow engine, no rights module, no admin console that needs a training day. This category exists precisely because the gap between “shared drive” and “DAM” is where most design and marketing teams actually live.

Tools don't keep libraries alive; a tiny operating system does. Ours fits in two lines:

• At import: type the asset, give it three tags, done — the taxonomy rules from our organizing guide apply unchanged at small scale.
• Monthly, one owner: fifteen minutes — merge duplicate tags, archive shipped campaigns, spot-check the ten newest imports.

That's the entire governance model. Write it in the team handbook, put the monthly pass in someone's calendar, and resist every urge to add process until a real failure demands it.

The small-team shape has real limits, and pretending otherwise would be selling. Move to enterprise DAM territory when licensed assets with usage rights and expiry dates become routine; when regulated industries demand auditable approval chains; when asset count crosses into the tens of thousands across many brands; or when a dedicated ops person exists whose job the system should be.

Until one of those is concretely true, every month on the lighter system is money and attention saved. Migration later is a real cost — but paying enterprise overhead for years “just in case” is a larger one.