Client-Built Assets

Your team can build it. We'll make it deployable.

AI has made it practical for internal teams to produce working interactive tools. The problem isn't building one. It's what happens next. Without a compliance review, access control, and version management, an AI-generated prototype is still just a file on someone's laptop.

Talk through your asset

AI-generated tools without governance are a problem waiting to happen

When technically capable people can produce working tools with AI, they will. And without a governed process, every person who can produce one does.

The result is a fragmented collection of unversioned, untracked, inconsistently branded files scattered across shared drives and email threads. No security review. No access control. No record of what was changed or by whom. Individually, each asset looks harmless. Collectively, they represent a governance problem that grows every time someone opens a new AI session.

Client-Built Assets: governed deployment for internally produced interactive tools

Assets accumulate without oversight

Every person who can produce a tool does, and nobody knows what's deployed or where it's being used.

Security risks go unreviewed

Embedded data, external dependencies, and unknown code patterns create risks that nobody has signed off on.

No version history or rollback

When something changes or breaks, there's no record of what the asset looked like before, or who changed it.

IT can't govern what it can't see

Tools deployed outside formal processes are invisible to the teams responsible for managing them.

A prototype on a shared drive is not a business asset. What makes the difference is the infrastructure behind it.

Client-built asset passing compliance review and deploying to managed PUBLEX infrastructure

The same managed infrastructure, regardless of who built the asset

A client submits an asset; PUBLEX reviews it for compliance and security, provides feedback on any issues, and on approval deploys it to managed infrastructure with authentication, access control, version tracking, analytics, and CDN delivery included. From that point it is treated identically to any other PUBLEX-managed asset. PUBLEX doesn't write the content or validate the data. PUBLEX takes responsibility for the deployment environment.

A natural entry point and a natural path forward

For clients who want to understand whether interactive tools deliver value before committing to a full build, a client-built asset is the lowest-friction entry point. Build something internally, validate the idea, and deploy it properly. The self-build process also surfaces the natural limits of what AI tooling produces reliably: complexity, brand consistency, logic requirements. Those limits are the normal handoff point to a full PUBLEX commission.

Optional add-on

Train your team to build assets that pass review first time

A half-day course for internal teams who want to produce compliant assets from the start, rather than learning what doesn't work during the review process. Delivered via Zoom or on-site, with supporting reference material included. Pricing is standalone and fixed.

Ask about the course

The course covers

What kinds of assets work well in this format and where the limits are

How to brief AI tools to produce compliant output

The technical rules and why they exist

What to do when a project exceeds the self-build boundaries

Practical session: building and reviewing an example asset

Review & deployment fee

From £320

Fixed fee. Scoped before we start.

Review & deployment includes

Compliance and security review
Staging preview before go-live
Feedback loop on any compliance issues
All prices ex-VAT

Ongoing management

Standard Asset
Managed hosting, authentication, and access control
Version tracking and rollback
Basic engagement analytics

From £40/month

Get a scoped price

Send us your asset and we'll scope the review and give you a fixed number before any commitment.

See if your asset is ready to deploy

Tell us what your team has built and we'll talk through what the review and deployment process would look like — including whether it meets the technical requirements or needs adjustments first.