ADSGENCY AI X DATA MANAGEMENT
Enabling teams to reuse the assets they create instead of rebuilding them by turning one flat shared folder into a rule based library that shows each role only what belongs to them
Role
Timeline
Team
Deliverables
AdsGency generated ad creative in minutes and then the flow ended. There was no library to return to, so teams rebuilt work they had already made. Building that library surfaced a second problem underneath it
Four kinds of user groups reach into the same library, all different user flows
Mapping how each user group interacts with an asset, the four collapsed into two. The difference that matters is not job title, it is whether you use the library or govern it.
Design for one library, branch it at permissions and governance
Auditing the two profiles component by component, the parity was near total. Same company profile, same integrations grid, same team list, same asset library, same four tab detail rail. What changes is not what exists but what you can act on.
Both profiles land on the same page, run the same search and filters, and open the same asset drawer. Walking standard first and admin second makes the layering visible, because everything in the second pass is an addition rather than a replacement.
View only, with one honest wall. Integrations and team are read-only, and billing, roles, and security collapse into a single locked card naming the owner.
View only, with one honest wall. Integrations and team are read-only, and billing, roles, and security collapse into a single locked card naming the owner.
View only, with one honest wall. Integrations and team are read-only, and billing, roles, and security collapse into a single locked card naming the owner.
Upload assets
Admins get an upload button in the library toolbar that opens a modal, dropping files into the same auto-tagging pipeline generated assets already flow through
Governance panel
An entire section above the library, admin-only, holding three tabs: users and permissions, rights management, and version oversight.
Segmentation lives in two layers: what a profile can do and what controls an asset carries. A screen is just where the two meet. Claude held the matrix steady and caught combinations I'd have missed.
We traced how assets arrive, by hand or auto-generated, and mapped each entry point to how people expect to find an asset later, not how it technically got in.
PostHog data analytics, google analytics and 1:1 stakeholder conversations from the MVP build showed admins bouncing between the grid, drawer, and profile for one governance task, so the controls were consolidated into a single panel at the top of the admin view.
Claude Code ran the build loop, turning each round of testing into working screens: the asset detail popup, list-view inline edits, user-profile colors matched to the design system, and countless micro-interactions, all iterated live
Working solo as designer, builder, and reviewer, I moved fast through ambiguity with Claude. The risk was bias: mistaking my own intent for clarity. Internal and client testing kept my assumptions honest.
