Don’t Let your Photos Become Depreciating Assets

Every firm budgets for photography like it's a capital investment, because it is one. Professional photography of the finished building. Renderings before it existed. A photographer flown in for the ribbon-cutting. The works.

But here's what nobody tracks: the depreciation curve on all of it.

The depreciation curve everyone knows about but can’t avoid (yet)

This situation will sound familiar to anyone who's built a proposal under deadline. Nobody goes looking for the best photo. They go looking for whatever they can find in five minutes, and that means the same six "safe" images show up in submission after submission, sometimes for the same client. At the same time, the shot that would've actually differentiated the firm sits in a folder with a name nobody remembers, as the person who knew about this file moves teams or leaves the firm. That’s depreciation right there.

An image loses value every time it isn’t used right. In my experience, this is the part marketing leaders don't talk about in budget meetings, because it doesn't show up as a line item. It shows up as a photo nobody can find, six years later, for the exact market sector where it would've mattered most.

This is the same story as every other piece of institutional knowledge a firm accumulates and then can't access. Old pursuits, project sheets, the stuff that lives in someone's head instead of a system. Try to solve it with a typical Digital Asset Manager (DAM), and you hit the same wall.

The case of the missing brain

Most traditional DAMs are flat content libraries. They index whatever text and tags a human typed in by hand. Reverse image search doesn't exist for them, neither does context, because it requires understanding the pixels, not just the label next to them. So no matter how much AI gets layered on top afterward, they still remain fundamentally metadata-dependent.

With Kantiv, images live inside the same pursuit workflow you're already building the proposal in, connected to the same knowledge graph that knows your firm's people, projects, and clients. This means Kantiv auto-tags, and then later finds and recommends images. You simply select and place it without leaving the tool.

The fried chicken test (that we didn’t set intentionally)

Here's a story that says more than any explanation could. One of our clients had shot a sports bar inside an airport and had the professional photos sitting in their library (we didn’t know about this). During a demo of this capability, someone on their team typed "fried chicken" into search, mostly as a joke to see what would happen.

The platform pulled up the photo of the sports bar with chicken wings in it. And then it went ahead and also pulled up the menu board! Nobody had tagged that photo. In fact, nobody had tagged any of the photos. The system read the prices and the words printed on the board and decided, on its own, that the page belonged in the results.

That's the difference between an asset that depreciates and one that appreciates. The photo didn't need someone to maintain its value with tagging. The system understood it the moment it landed, and it'll still understand it the same way five years from now, long after whoever filed it has moved on.

Built around your workflows

The fried chicken test was not a party trick limited to one weird search term. It's how the system was built to work across every way marketing teams actually look for images. In fact, in the process of building this capability, we asked Architecture Engineering and Construction (AEC) marketing teams how they'd ideally look up an image if their tool actually cooperated. Then we built all of it.

• Name search: The most used way of typing in a name you remember, finding the photo.
• Semantic search: Describe what's in the photo, get the photo.
• Reverse image search: Drop in a screenshot or a low-res copy, get back the original or the closest visual match. Nobody else in AEC offers this.
• Usage-based lookup: Find images used most for a client or sector. This way "which photo have we already shown this client" stops being a guess or and so does “which images are right for this sector”.
• Metadata search: For anyone who's already put years into IPTC/EXIF tagging in Adobe Bridge, that work carries over instead of getting thrown out.

No "final_v3_USE_THIS" ever again: The duplicate-file problem nobody budgets for

Finding the right image is half the problem. Knowing which version of it is the real one is the other half. Another team told us the thing that actually got their attention was the absence of a problem they'd stopped noticing they had. The system clearly demarcates the one ‘marketing approved’ copy of an image, instead confusing them with four nearly-identical files named "final," "final_v2," and "final_v2_USE_THIS" and making them guess. Burn 20 minutes on that guessing game, or submit the wrong revision because of it, and you've just watched part of that asset's value disappear in real time.

With Kantiv’s image intelligence platform, format or size variants generated from a source image stay linked back to the original. Resize it, crop it, export it for a different template – it's still one image with a family tree, not five orphaned files competing for "real." No "final_v3_USE_THIS" ever again.

None of that helps if finding the photo still means downloading it, then uploading it into InDesign, then placing it. That download-upload-place cycle was one of the most common complaints we heard from AEC marketing teams, because it means bouncing between tools on every single image, on every deadline. Kantiv's InDesign plugin skips the cycle: drag an image straight out of search and drop it into your layout. No competitor offers this level of InDesign integration for AEC.

The other side of the ledger: what you haven't invested in yet

Depreciation is the value you're already losing. There's a second problem sitting right next to it: value you haven't created at all. The system flags those gaps before a pursuit ever lands, for example, a market sector with thin visual proof, a service line that's never had a strong hero shot. That's the difference between reacting to depreciation after the fact and directing next year's photography budget before an RFP forces the question.

Every image also carries a usage history, which proposals it's appeared in, how many times, for which client types, so reuse decisions become data-backed instead of a gut call. That's the shift from noticing depreciation to preventing it.

The real return on 20 years of photography

A firm can spend 20 years and a real budget on photography and still watch that investment depreciate to zero on a shared drive nobody can search. But it doesn’t have to be that way. The photos just have to be findable, with the gaps visible before the next RFP lands, that's the difference between a library that depreciates and one that compounds.

Want to see where your own library sits on that curve? Book a demo and bring it with you. Type in a project type, a material, a client's name, whatever comes to mind, and see what comes back. Got questions first? Ask them. We'd rather answer than pitch.