Getting a digital asset management (DAM) project approved rarely comes down to one yes. It comes down to several, from several different people, each asking a different question. If you’ve heard “we already have a DAM platform,” “we just bought one,” or “can’t we just use a shared drive,” the problem usually isn’t that leadership doubts the value. It’s too often that no one has answered the specific question each stakeholder is actually asking.
This is a practical guide to those questions, organized by who’s asking them, so you can walk into any conversation, with any role, already knowing what they need to hear.
Why does DAM buy-in stall even when everyone agrees it’s needed?
Buy-in stalls because the people who feel the daily pain, missing files, unclear rights, duplicate assets, are rarely the people who approve the budget to fix it. That gap between who feels the problem and who signs off on the solution is where most DAM projects get stuck.
It’s made worse by a common misunderstanding: a lot of teams assume DAM software is a marketing tool, full stop. Ad versions, campaign folders, brand assets. If that’s the only framing anyone’s heard, teams solving a different problem, like managing 3D files, engineering assets, or research archives, will conclude a DAM isn’t for them. One organization spent over a year running focus groups and evaluating alternatives, project management tools, engineering version-control software, before landing back on the obvious answer: “I guess we do need a DAM.” The delay wasn’t a lack of pain. It was a messaging problem.
For a structured way to identify who should be in the room before that happens, see AVP’s guide to assessing your organization’s DAM needs, which includes an eight-role stakeholder-identification framework.
Who’s actually in the room?
A DAM decision usually touches four groups, and each one is protecting something different.
- Risk reduction and ROI, not features
- A named executive sponsor
- Integration, security, and audit trails
- A seat at the table early
- A shared foundation, not a rigid one
- A phased, team-by-team rollout
- Proof a common task gets faster
- Real training, not a help doc link
Leadership: is this worth the money, right now?
Leadership isn’t asking whether a DAM is a good idea. They’re asking whether this DAM, this year, beats every other line item competing for the same budget. They need to see the cost of the current workflows, time lost searching, assets recreated because no one could find the original, risk from expired or unclear usage rights and the damage that can cause a brand, set against a clear, specific outcome.
What helps here:
A short, plain-language business case that ties the investment to risk reduction and time saved, not features
A named executive sponsor who can speak for the project when you’re not in the room
A connection, even a rough one, between the DAM and revenue or speed to market. In growth-focused organizations, “this helps us work better” rarely moves a budget on its own. “This gets us to market faster” often does.
Real numbers from your own team wherever you have them, and a clearly marked placeholder where you don’t yet
Examples of numbers to gather
- Average hours per week, per person or team, spent searching for assets
- Time lost when no one can find the “source of truth” version
- Time spent recreating or reshooting content that already exists somewhere
- Stock or licensing spend that could’ve been avoided by reusing owned assets
- Cost of a single reshoot, framed as “reshooting next year costs $X unless…”
- Vendor or freelance spend tied to recreating assets
- Dollar amount tied to past license violations or expired-rights incidents
- Number of assets without clear rights metadata, as a proxy for exposure
- Number of duplicate or near-duplicate assets in current storage
- Percentage of produced content that goes unused and unfindable a year later
Budget conversations also tend to climb a chain: you make the case to a director, who carries it to a senior director, who carries it to a VP, sometimes higher, depending on the price tag. The bigger the ask, the more it needs to serve more than one team. A tool pitched as solving one group’s problem gets a harder no than one framed as helping the entire company work toward its goals. Anticipate the pushback, what’s the ROI, why do we need this at all, before you’re standing in the room answering it live.
AVP’s guide on building a DAM business case for the full walkthrough on baselines, ROI, and pitching leadership, and AVP’s DAM strategy guide for framing the problem before the ask.
“A real result can do more than a projection. One AVP client, the New York Public Library, used a stakeholder-backed case like this to secure an immediate funding increase of over $1M, along with a much larger multi-year commitment. Numbers like that came from a clear case, not a bigger deck.”
Read the NYPL case studyIT: will this create more work than it saves?
IT isn’t pushing back to be difficult. They own uptime, security, and everything that breaks at 2am. Their real question: does this fit cleanly into what we already run, or does it become one more system to patch, secure, and explain during an audit?
What helps here:
Early answers on integrations, API access, and how the platform handles access controls and audit trails
A straight answer on data migration, including what happens to existing folders, permissions, and file history
If you’re looking to migrate, clear answers on why the existing solution isn’t working for the business, not just your team
A seat at the table before the decision, not after it
Bringing IT in early, even informally, tends to shorten this conversation more than any amount of documentation later on.
AVP’s DAM RFP checklist guide for the security, integration, and vendor-evaluation questions IT will ask, and AVP’s DAM Implementation Success Predictor, which includes an IT and security readiness section.
Internal teams across multiple brands or departments: whose way of working wins?
If your organization spans multiple brands or business units, this question gets sharper. Each team has its own workflows, naming conventions, integration requirements, and sense of what “done” looks like. The real question isn’t “do we need a DAM.” It’s “will this force my team to work someone else’s way?”
The most useful answer tends to be: not all at once. A shared foundation, one taxonomy, one set of governance rules, one rights framework, with room for each team to configure its own views, folders, and approval steps tends to land better than a rigid structure applied everywhere on day one. A phased rollout, team by team, gives each group a chance to see the shared system work before they’re asked to fully adopt it.
This also heads off a specific objection: “we already have something.” Sometimes that something was built for one team’s needs and doesn’t hold up for anyone else, rigid metadata fields that only make sense for one kind of asset, or a structure nobody outside the original team had input on. The fix isn’t arguing the existing tool is bad. It’s showing, concretely, where it doesn’t fit the work other teams actually do.
See AVP’s case study on a multi-brand organization’s phased, two-brand pilot rollout.
End users: is my day about to get harder?
This group is most likely to feel unheard, and most likely to quietly work around a new system if their concerns go unaddressed. Their question is simple: will this slow me down while I’m already busy? They’re not asking about ROI. They’re asking whether they’ll still be able to find the file they need by Friday to meet their deadline.
What helps here:
Involving a few actual end users in requirements gathering, not just their managers
Showing, concretely, how a common task, finding the current logo, confirming an asset is cleared for use, uploading a new file, gets faster, not slower
Being honest about the learning curve, and pairing the rollout with real training, not just a link to a help doc
The moment that actually changes minds
Slides make the case. A live demo tends to close it. Load in a real batch of assets, tag a handful, and search for something the room already knows is hard to find today, or build out one process or workflow that shows how the platform will increase your team’s speed. Watching a result appear in seconds does more than any projection slide. It’s not magic, it just makes the “so what” visible instead of theoretical. Pair that moment with an honest note: the system doesn’t organize itself. Someone, increasingly an AI-assisted tool working alongside a person, still has to do the tagging work up front.
That last point matters more than ever. AI search and recommendation tools are only as good as the metadata behind them. A DAM full of inconsistent, incomplete metadata will hand back inconsistent, incomplete answers, from your team and from any AI layered on top. It’s the same story as always, told with new urgency: assets that are easy to find and ready to use only get that way because someone made the rights, structure, and metadata clear first.
AVP goes deeper on this in The DAM AI Gap: Why AI Fails Without DAM Fundamentals.
When leadership says “we already have a DAM” or “we have shared storage”
This objection almost always means one of two things: the current tool was never fully adopted, or it’s solving a different problem than the one you’re describing. Shared drives and general storage are, at their core, storage. A DAM manages rights, versioning, metadata, and controlled access at scale, in a way storage tools weren’t built to do.
The most direct response is usually a short, live comparison: pick one real task, finding the latest approved product image with rights confirmed, and show how long it takes today versus how it could work. That’s often more convincing than any slide.
See AVP’s article on why the case for DAM investment holds up even in a tight budget environment.
What buy-in is actually protecting
Every one of these conversations, leadership’s budget question, IT’s integration question, the multi-team alignment question, the end user’s workflow question, comes back to the same three things:
When you frame each stakeholder’s question back to one of these three, the project starts to read less like a system purchase and more like what it actually is: a way for your assets to finally earn their keep.
Getting the right people to the table
None of this requires convincing everyone alone, or getting every answer perfect on the first try. It usually just takes making sure the right people are in the room, with a chance to ask their real questions and get real answers, and someone willing to keep having the conversation until it lands.
If you’d like a second set of eyes on your business case, or help facilitating that conversation across leadership, IT, and your internal teams, AVP can help.
