Platform Foundation Brand Asset Lifecycle

Every brand asset. One trusted source.

Images, video, templates, copy and claims in one governed place, from the first brief to the day the licence runs out. Found in seconds, approved with a trail, and blocked automatically when rights expire.

  • Search by meaning, not filename
  • Rights and expiry enforced
  • Provenance on every AI-made asset
An open vault with neatly arranged frames, swatches, a film reel and folders
Approved for India, UAEModel release valid to 31 Mar

Asset health

  1. Tagged and searchable98%
  2. Rights verified94%
  3. Expiring in 30 days41
Time to find Seconds to the right approved asset
Reuse Existing work used again across markets
Approval time Days from submission to sign-off
Rights incidents Expired or restricted assets going live

Why change

AI can make a thousand assets a day. Who is keeping track?

Creative volume is about to multiply. Without governance, so do the wrong versions, the expired licences and the claims nobody approved.

Assets live everywhere

Shared drives, agency links and inboxes. Teams recreate what already exists.

Versions get confused

The wrong cut reaches the wrong region or channel.

Approvals are slow and opaque

Campaigns lose days to feedback nobody can find.

Rights and expiry are missed

A licence lapses and the asset stays live.

What it does

Ingest, govern, find, activate.

A digital asset system built for a world where much of the content is generated, personalised and published by software.

01 Find and reuse

Describe what you need. Get the approved version.

Every upload is tagged automatically: what is in it, what is said in it, the text on screen, the product, the mood. Search by meaning or by look, and find near-duplicates before someone commissions the same shoot again.

  • Semantic and visual search across images, video, documents and templates.
  • Transcripts and on-screen text extracted and searchable.
  • Performance attached: see how an asset did before you reuse it.
Search4 of 126 results

woman outdoors using the app, festive, approved for paid social in India

Diwali_terrace_hero_v6Image · approved · India, UAE · CTR above medianBest match
Festive_15s_vertical_v3Video · approved · India · subtitles in 4 languagesApproved
Diwali_terrace_alt_v2Image · near-duplicate of v6Superseded
Rangoli_closeup_v1Image · talent release expiredBlocked
Blocked assets are visible but cannot be downloaded or publishedIllustrative

02 Review and approve

From brief to sign-off on one trail.

Briefs, proofs, annotations and decisions live with the asset. Agents run the first pass, checking brand rules, claims and accessibility, so reviewers spend their time on judgement rather than spotting a wrong logo.

  • Automated brand and claim checks before a human sees the proof.
  • Accessibility checks: alt text, contrast and subtitles.
  • Agency collaboration, with roles, deadlines and a full history.
Review · Festive_15s_verticalStep 3 of 4
Brand checkLogo, colour, type and safe zonesPassed
Claims check"Free delivery over ₹499" found in claim registryPassed
AccessibilitySubtitle contrast too low at 0:09Fix suggested
Legal reviewAssigned to A. Kapoor · due tomorrowWaiting
Brand lead sign-offAfter legalWaiting
Version 3 · 2 earlier versions keptIllustrative

03 Rights, provenance and distribution

Know where every asset came from and where it may go.

Licences, talent releases, regions and expiry dates are attached to each asset and to everything derived from it. AI-generated content carries provenance metadata. When rights lapse, links are revoked and live use is flagged.

  • Rights inherited by derivatives, including every personalised render.
  • Content provenance and AI disclosure recorded with each asset.
  • Renditions on demand, delivered by API to campaign and messaging tools.
Rights · Diwali_terrace_heroValid
RightScopeUntilState
Photographer licenceDigital, worldwide31 DecValid
Talent releaseIndia, UAE31 Mar41 days
MusicNot applicable——
AI editsBackground extendedDisclosedProvenance
312derivatives
9live placements
31 Marauto-revoke date
On expiry: share links revoked, 9 placements flaggedIllustrative

Agents at work

A librarian, a proofreader and a rights manager. Always on.

Asset agents tag, check, convert and watch. Anything uncertain is routed to a reviewer with the reason, and nothing new is published without the approval the workflow requires.

  • First-pass compliance, with the rule that failed and where.
  • Stale and orphaned assets surfaced, along with searches that found nothing.
  • Agent-readable, so other agents can request "an approved hero for this audience" and get one.
Agent activity  Live
240 agency uploads ingested and taggedTranscripts, OCR and product detectionAutomated
18 near-duplicates linked to existing mastersUploader notifiedAutomated
Subtitle contrast failure at 0:09Fix rendered as v4, sent to reviewerNeeds approval
Talent release expires in 41 daysOwner alerted, renewal task createdAutomated
Publish request for asset with expired licenceDistribution refused, requester told whyBlocked
Every step logged with inputs, reason and outcomeIllustrative

You decide what the agents may do here.

AutomatedKeeping the library in order

Tagging, de-duplication, renditions, expiry alerts and revoking links when rights lapse.

Human-approvedReleasing work

Final approval of new masters, new claims, rights exceptions and anything going to a new market.

RestrictedHard stops

Distributing expired or restricted assets, unapproved claims and undisclosed AI-generated content.

What's inside

Creative scale without creative chaos.

Use it as your asset system of record, or as the governance layer over the storage you already have.

Central library

Images, video, documents, templates and ads.

AI tagging and metadata

Auto-tagging, OCR, transcripts and a managed taxonomy.

Semantic and visual search

By meaning, by look, by product or by performance.

Duplicate detection

Near-duplicates and visual similarity.

Versions and lineage

History, relationships and immutable released masters.

Review workflows

Briefs, annotations, statuses and multi-step approval.

Rights management

Licences, releases, regions, expiry and retention.

Provenance and disclosure

Origin, edit history and AI-generation metadata.

Claim registry

Approved claims with proof, owner and expiry.

Renditions

Transformations and channel-ready formats on demand.

Distribution

APIs and webhooks to campaign, web and messaging tools.

Usage analytics

Reuse, zero-result searches, orphaned and top-performing assets.

How it runs

From upload to expiry, every step on record.

Each step is a named, logged stage. Nothing autonomous is switched on until its data, permissions, monitoring and rollback have been checked.

  1. Upload or import the asset
  2. Extract metadata with AI
  3. Check duplicates and rights
  4. Review and approve the version
  5. Publish controlled renditions
  6. Distribute to campaign channels
  7. Monitor use, performance and expiry

How you'll measure it

Faster to find, safer to use.

We agree the numerator, denominator, cohort and success gate with you before anything goes live, and compare against a baseline or a holdout, never against a hunch.

  • Median find timeTime for a user to locate the approved asset they need.
  • Asset reuse rateDistinct approved assets reused, divided by assets deployed.
  • Approval cycle timeMedian time from submission to final approval.
  • Metadata completenessRequired fields populated, divided by required fields.
  • Expired-asset incidentsUses after licence or asset expiry. The target is none.
  • On-time deliveryApproved assets available by the campaign due date.

Questions

Things people ask before they start.

We already have a DAM. Why would we need this?

You may only need part of it. Many teams keep their storage and add the AI tagging, rights enforcement, claim registry and distribution APIs that older systems lack.

How are AI-generated assets handled?

They are stored with provenance metadata recording that they were generated or edited by AI, from which template and by which model, and they pass the same brand, claim and rights checks as any other asset.

What happens when a licence expires?

The asset is blocked from download and distribution, share links are revoked, and anywhere it is still live is flagged to the owner. Derivatives inherit the same expiry.

Can agencies work in it?

Yes. External teams get scoped roles to upload, respond to annotations and track approvals, without seeing the rest of the library.

Composable by design

Useful alone. Sharper when connected.

Every capability that makes or sends content draws from here, and reports back how the content performed.

Keeps your existing stack

Sits alongside your existing storage, creative tools and CMS. Imports from shared drives and agency systems.

Runs where your data lives

Small language models trained on marketing data are deployed inside your cloud or data centre, so customer data and the models reasoning over it stay under your control.

Getting started

Start with one campaign's assets.

Import one campaign, tag it, attach the rights and run one approval cycle. Measure find time and approval time against how you work today.

  1. Agree taxonomy, roles and rights model
  2. Import and auto-tag one campaign
  3. Run reviews and distribution through it
  4. Extend to markets, agencies and channels