Why a shared folder stops being enough
Picture a client's new office manager who needs the logo for a banner order. She searches her inbox and finds four candidates: logo_final.png, logo_final2.png, logo-FINAL-use-this.jpg, and a zip file from last spring. She picks the one that looks right. The banner arrives in last year's color, and the agency hears about it after it is already hanging at the event.
That scene is an illustration, not a TwoQM client. Nobody did bad work. The approved file existed; it just was not the one anybody could find. For marketing and creative agencies, like other professional services firms, the fix is rarely more storage. It is a client asset library where every file carries a plain name, a status, and a version label, and where the current approved file is obvious to the client, the team, and the vendors they hand it to. TwoQM builds that kind of client portal as custom software connected to the tools an agency already uses.
A shared drive folder per client works well at first. Then versions multiply, people download copies, and the folder holds both the approved logo and the three drafts that came before it. The real question a client asks is not "where are the files?" but "which one is current, and can I use it here?" A folder name cannot answer that. A record can.
What each asset record holds
Here is an original example, not a measured result. Each asset in the library is a record, not just a file:
Plain name and type. "Primary logo, full color" instead of a file name, with a type such as logo, brand guide, photo, video, template, or ad creative.
Version label. A number and a date, such as v3 · 2026-10-12. Never "final," because there is always a next one.
Status. Draft, in review, approved, superseded, or retired.
Approval. The client contact who approved it and the date, taken from wherever approval actually happened.
Variants. Full color, one color, reversed, web, and print files grouped under the same version, so nobody mixes v2 web with v3 print.
Usage notes and rights. Where the asset may be used, and for licensed stock or music, the license terms and any end date your contract or license sets.
Owner. The person on the agency team responsible for keeping that asset current.
Version labels that answer "which one?"
A few rules make labels work:
One current approved version per asset family. When v4 is approved, v3 is marked superseded automatically and links forward to v4.
Superseded is not deleted. Older versions stay visible to the team for history but drop out of the client's default view.
Languages are siblings, not separate files. If a flyer exists in English and Spanish, both carry the same version number and sit on the same record, so the Spanish version does not quietly lag a revision behind. That matters for agencies serving bilingual markets like the Rio Grande Valley.
Search uses words people say. "Logo white background" should find the reversed logo even if the file name says something else.
What clients see and what stays internal
The client view opens on approved, current assets, filtered by type and searchable by plain words. Items in review sit in a separate area where the client can comment or approve, and that approval writes back to the record. Layered source files, working drafts, and internal notes stay internal unless your contract says they are delivered.
When a client needs to send a logo to a printer or a web developer, they share a link to one specific approved version, with an expiration your agency's policy sets. If the asset is updated later, the shared link does not silently change underneath the vendor. One-time delivery of a finished photo set is a different job, covered in gallery delivery permissions and expiration.
Connect what you already have
Files can stay where they live today, in cloud storage or a digital asset management tool. The portal can be an index and a set of rules on top: records, statuses, labels, and client views. Connected systems let an approval logged in your project tool update the asset status, so nobody has to mark it twice. Whether your storage and project tools support those connections is confirmed during scoping.
Sometimes a disciplined naming convention, a shared drive, and one index sheet per client are enough. If that covers your agency, scoping should say so before anything custom is built.
Automation first, then AI suggestions a person confirms
Ordinary automation handles most of it: mark older versions superseded when a new one is approved, notify the client contact that a new version is ready, and remind the asset owner before a stock license end date.
AI can help with suggestions a person confirms: proposing search tags and short descriptions, drafting alt text, or flagging files that look like duplicates. It never approves an asset, never changes a status on its own, and never decides what a license allows.
Where to start this week
Pick one client. Collect every version of their logo you can find in email, the shared drive, and your design tool, and count how many a stranger could mistake for current. Then write the status list and the naming rule your team would actually follow. That is the first draft of the library's specification.
If you want a client asset library where the current approved file is the one everybody finds, TwoQM can scope the portal and its connections to the storage and project tools you already use. Pricing explains how business apps, systems, and custom software are scoped.
Describe Your Client Asset Library · Explore TwoQM custom software