Industry guides
DAM for agencies and in-house studios
Quick answer
Agencies and in-house studios need a DAM that separates work in progress from approved finals, isolates each client or brand, runs review and approval inside the creative tools, and records licence and AI-use data on every asset. Prioritise client workspaces, proofing, Adobe and Figma plug-ins, guest access pricing and clean handover of finals to client DAMs.
Key takeaways
- Agency DAM needs differ from brand DAM needs: the core unit is the client or job, and finals usually end up in the client's own DAM.
- Review cycles drive studio throughput; cutting average rounds from four to three saves roughly a quarter of review time per job (illustrative calculation).
- EU AI Act Article 50 transparency obligations have applied since 2 August 2026, so studios using generative AI need to record AI involvement and keep machine-readable markings intact.
- Guest and reviewer licensing can double the effective cost of an agency DAM, so pricing models with unlimited external users deserve close comparison.
- Stock, talent and music licences must travel with the asset to the client, or liability for misuse becomes disputed.
Agencies and in-house studios should select a DAM around the job and the client: it must separate work in progress from approved finals, keep each client's assets isolated, run reviews inside the creative tools and hand finals over cleanly. Studios that pick a brand-library DAM built for distribution usually end up running production on shared drives beside it.
Agency and studio asset problems: jobs, clients and handover
Agency asset problems fall into three groups: production volume, client separation and handover. Production volume is high and messy, since one campaign job can generate hundreds of layered source files, exports and review versions within weeks. Client separation is a contractual requirement: staff working across competing brands must see only the assets of their own clients. Handover closes the loop, because approved finals, source files and licence terms must reach the client's DAM complete and traceable.
In-house studios share the first and third problems and add intake pressure: briefs arrive from many internal teams, so request management and capacity visibility matter as much as storage. Regulation now adds an AI layer. Article 50 of the EU AI Act, Regulation (EU) 2024/1689, has applied since 2 August 2026, requiring disclosure of deepfakes and machine-readable marking of AI output by providers; our guide to the EU AI Act and marketing content covers the details.
Must-have DAM capabilities for agencies and studios
Proofing inside the workflow and strict client isolation are the two capabilities that matter most.
| Capability | Why it matters for agencies and studios | Priority |
|---|---|---|
| Client or brand workspaces with isolated permissions | Prevents cross-client exposure | Must have |
| Online proofing with versioned annotations | Fewer review rounds, clear approval trail | Must have |
| Adobe Creative Cloud and Figma plug-ins | Designers save and retrieve without leaving tools | Must have |
| Licence, talent and stock usage fields | Terms travel with the asset to the client | Must have |
| Unlimited or low-cost guest reviewers | Clients review without seat costs | Should have |
| Video proxies and frame-accurate review | Motion work dominates many studios | Should have |
| Provenance metadata and C2PA support | Records AI involvement and edit history | Should have |
| Request intake and capacity reporting | In-house studio planning | Could have |
Our guides to creative workflow and proofing and Content Credentials and C2PA explain how to test the proofing and provenance rows.
Integration needs: creative tools, work management and client DAMs
Agency integration needs follow the job lifecycle. Creation depends on Adobe Creative Cloud and Figma connectors; planning depends on a work management tool such as Adobe Workfront, Asana or monday.com, which should create the DAM job folder automatically. Delivery depends on connectors or portals into the client's DAM, typically an enterprise platform with its own metadata schema, so map that schema before the first handover. Our DAM integrations guide lists common connector types and their limits.
Typical shortlist profile for agencies and in-house studios
Studio shortlists usually split by size and the share of work that is production versus distribution.
- Creative operations platforms for in-house teams: Lytho combines creative workflow, online proofing and DAM, with a base in regulated sectors.
- Creative team workspaces: Air, based in New York, combines asset storage, review and AI editing, with unlimited users on every plan.
- Lightweight client portals: Filecamp, operated from Switzerland, offers a branded library with unlimited users at low entry pricing.
- Production and proofing systems: DALIM SOFTWARE, a German vendor, focuses on production workflow and proofing for print and packaging studios.
These are neutral examples of each profile, to be scored against your own requirements.
Pitfalls in agency and studio DAM projects
Four pitfalls recur in agency and studio deployments (practitioner observation).
- One shared library for all clients. Permission errors become likely, and client audits fail.
- Licence terms in emails. Stock and talent restrictions must sit on the asset; see rights and licence management.
- Seat-based reviewer pricing. External reviewers inflate cost quickly, so model guest volumes before signing.
- AI provenance stripped on export. Some export paths drop embedded metadata, breaking disclosure records.
What to do next
- Separate your requirements into production, review and handover, and weight each by share of studio hours.
- Count external reviewers per month and request pricing at that volume.
- Test whether provenance and IPTC metadata survive your full export path.
- Agree source-file ownership, retention and AI disclosure clauses in client contracts.
- Pilot one live client job end to end, including delivery into the client's DAM.
Frequently asked questions
Should an agency use its own DAM or the client's DAM?
Most agencies use both. The agency DAM or production system holds work in progress, source files and reusable internal assets, while approved finals are delivered into the client's DAM through a connector or upload portal. Contracts should state which party owns source files and how long the agency retains them.
What is the difference between a DAM and a proofing tool for studios?
A proofing tool manages review rounds, annotations and approvals on individual files or jobs. A DAM manages the long-term library: metadata, rights, versions and distribution of approved assets. Many studio-focused platforms combine both, which removes manual transfers between review and storage.
Do agencies have to label AI-generated content under the EU AI Act?
Article 50 of Regulation (EU) 2024/1689 requires deployers to disclose deepfakes, meaning AI-generated or manipulated image, audio or video content resembling real people, places or events, with limited adjustments for evidently artistic or creative work. Providers of generative tools must also mark outputs in a machine-readable format. Agencies should agree disclosure responsibilities with clients in writing and preserve provenance metadata through export.