The asset creation process

From idea to scale — and where the Authority fits.

Becoming a product-centric business means every AI asset follows one process, from demand to lifecycle management. The AI Design Authority owns a specific, decisive role in it: the technology approval. This page sets out the end-to-end process, the naming conventions, and the roles around it.

One process, seven steps

How an AI asset moves from 0 to scale.

One framework covers every variant — however the idea is triggered, whoever builds it, wherever it is published. The steps are constant; the handling differs by trigger and asset type.

1 Step 1DemandIdeas & backlog
Gate 2 Step 2PrioritizationFund & assign build
3 Step 3BuildBuild & test with users
DA gate 4 Step 4ApprovalsTech · Content · Value
5 Step 5MarketplacesPublish & list
6 Step 6Realizing ValueAdopt & scale
Gate 7 Step 7Lifecycle MgtReview, update, retire

Gates sit at Prioritization, Approvals, and Lifecycle review. The Authority owns the technology decision at Approvals.

Our role in the process

The Authority owns the technology approval.

At Step 4, an asset is approved across four lenses before it can be published. The AI Design Authority is the technology lens — the others sit with content, commercial, and marketplace owners.

Ours

Technology

The AI Design Authority. Technical soundness, security, and standards compliance — evidenced through our five review gates.

Content

User acceptance

The asset does what it must, with correct application of our methods and frameworks. Owned by the Product Owner.

Value

Commercial / delivery

Commercial value or delivery productivity gain. Owned by the commercial or delivery sponsor.

Readiness

Marketplace readiness

Licence and terms & conditions cleared for the intended marketplace. Owned by legal / portfolio.

Build feeds the gate. The Authority's five review gates run through Steps 3–4: they produce the technology evidence the Approvals gate needs, so a team that has passed our gates arrives at Approvals already cleared on the technology lens.

The seven steps in detail

What happens, and who owns it.

StepWhat happensOwner / criteria
1 · DemandGenerate ideas and build a backlog of methods to "assetize". One central backlog in the AI Library, open to all.Anyone — consultants, leadership, client settings
2 · PrioritizationDecide which methods to fund and who builds. A committee validates and prioritizes ideas.Criteria: funding, reusability, unique Invent IP, clear demand, business/ROI case, build-vs-buy
3 · BuildBuild the AI tool with iterative testing in a team of users.Builder — AI Factory / Knowledge Factory, central AI team, or assigned resources
4 · ApprovalsTest, review and approve for broader use across four lenses before publication.Technology (Design Authority), Content, Value, Marketplace readiness
5 · MarketplacesPublish and list the asset in the right place for its audience.Central AI team — AI Library, Asset Exchange, hyperscaler, or client environment
6 · Realizing ValueAdopt and scale: internal communication and embedding; external marketing and client adoption.Product Owner, with comms & marketing
7 · Lifecycle MgtReview value, currency and technical health. Decommission, send back to Step 2 to update, or to Step 6 for more adoption.Product Owner, with the Authority on technical currency
Naming · AI Asset taxonomy

Four tiers, from AI for Us to AI from Us.

Every AI asset sits in one of four tiers. The lower tiers are how we work; the upper tiers are what we sell. Note: asset tiers describe the asset type — distinct from the risk class that sets review depth.

AI for Us

Tier 1 · Invent-Wide Foundations

Baseline productivity and consistency, Invent-wide. Codified methods, skills, prompts on our own instances.

Owner: Delivery / L&D · Bucket: Industrialisation

AI for Us

Tier 2 · Domain-Specific Capability

Encodes one practice's or industry's recurring know-how — domain workflows and agent personas.

Owner: CU / Industry L0/L1 · Bucket: Industrialisation

AI from Us

Tier 3 · Client-Facing IP Augmented Offering

Sold within an engagement; the IP differentiates and people deliver it. Client-facing UI, marketplace-listed.

Owner: Portfolio + Offer Lead · Bucket: Portfolio

AI from Us

Tier 4 · Productized Advisory

Sold standalone — the product is the offer. Dedicated platform or product, licence or subscription model.

Owner: Incubation / AI Factory · Bucket: Portfolio

Naming · the words we use

IP, asset, product — and where they live.

Consistent language keeps the process legible. These are the terms the Authority uses across gates and standards.

IP

The raw ingredient — a proprietary method, model, dataset, or content. Ownable and protectable, but inert on its own.

Asset

IP packaged for reuse inside delivery — an accelerator, tool, or diagnostic. Makes delivery faster or better; rarely a line item.

Product

An asset commercialized as a standalone thing the client buys — with a roadmap, versioning, and a price independent of any deal.

Asset types

  • Demonstrator — brings a use case to life in client conversations; one-shot, not built for reuse.
  • Internal Claude Skill — a reusable skill for our own consultants, published to the AI Library after the Authority's review.
  • Accelerator — a client-ready, IP-rich component that speeds selling and delivery; listed on the Asset Exchange.
  • Product — fully-fledged, maintained, evolutive solution sold standalone across the client base.

See what the Authority expects of each →

Where assets live · Beacon

  • AI Library — internal Claude skills for consultants to use during delivery; published after the Authority's review.
  • Asset Exchange — client-ready accelerators and products we sell to clients or were paid to build.
  • Hyperscaler marketplaces — external listing on partner platforms.
  • Client environment — deployed directly in the client's setting.

The Library and the Exchange both live inside Beacon, our single AI portal.

Where assets live · Beacon

One portal. Two homes.

Every codified asset lives in Beacon — Capgemini Invent's single AI portal, where our people go to discover what we have to bring. Beacon has two homes, and the Authority is responsible for the quality of what enters each.

AI for Us · internal

The AI Library

Home to the internal Claude skills our consultants use in delivery. The Authority runs the review: every submitted skill is QA'd and approved against the skill checklist before it is published to the Library for others to use.

AI from Us · client-ready

The Asset Exchange

The marketplace where our people discover client-ready accelerators and products — the IP-augmented offerings and products we sell to clients or were paid to build. The Authority clears the technology lens before an asset is listed here.

From the Exchange, client-facing assets can also be published outward — onto a hyperscaler marketplace, or straight into a client environment. The AI Library stays internal.

The Authority's two-sided remit. We govern both sides of Beacon: the development and review of internal Claude skills before they enter the AI Library, and the technology approval of client-ready accelerators and products before they list on the Asset Exchange. Same bar for good; different route to it.

Roles around the Authority

The AI Asset Product Owner organization.

Content ownership is decoupled from technical build so assets stay accurate, current, and adopted. Three roles orchestrate content, expertise, and build — and interlock with the Authority.

AI Asset Product Owner

The content/methodology expert who owns quality and adoption of one asset — not a builder. Reporting line to the Design Authority for gate approvals.

Chief AI Asset Product Owner

The product-minded leader who prioritizes and coaches across a capability or industry's whole asset portfolio.

Chief AI Asset Product Owner Lead

The single global orchestrator of the transformation agenda across the community — and a member of the Design Authority.

How this connects to us. Product Owners bring content and requirements; the Authority provides the technology standard and gate approval. The Chief Product Owner Lead sits within the Authority, keeping the process and the standards in step. See Governance for decision rights.

Building an asset? Know where the gate is.

Our review gates deliver the technology approval your asset needs at Step 4. Start early so you arrive cleared.