Engineering for enterprise content platforms.

AI on your content, upgrades, headless delivery and cloud. Optimizely first.

We measure first, then we recommend. We also work on Umbraco, Contentful and Strapi. Our stack is .NET and Azure.

The four planes of a content platformFour stacked slabs. Content is the base, then delivery, then platform, with AI on top.AIPlatformDeliveryContent

AI on your content.

Find out how AI systems read your site today, then decide what they should get.

Our own site, assessedcontentplane.net · measured 7 October 2026

89 out of 100

Overall score

No area below 60

DiscoverableRequest logging is off, so crawler visits are not visible
80 out of 100
RenderableComplete HTML; nothing waits for scripts
100 out of 100
StructuredClean outline and structured data on every page
100 out of 100
AddressableNo www redirect
75 out of 100

Services

Upgrades and modernisation.

Know the cost and the risk before you commit to a date.

Headless delivery.

Content served through an API to a front end your own team can change.

Cloud, edge and pipelines.

Hosting, the edge and the release pipeline, set up so a release is routine.

How we work.

Every engagement we take on follows four steps.

  1. MeasureWe work from your data and your traffic, and state how and where each number was measured.
  2. RecommendYou get a recommendation with costs, risks and written go/no-go criteria. The decision stays yours.
  3. DeliverWork is released in small, tested steps. Where a step cannot be undone, we say so before it starts and agree the way back.
  4. Hand overYou keep runbooks, tests and documentation that your team can use without us.

A content platform has four planes.

A problem that starts on one plane often shows up on another, which is why we work across all four.

  1. AI

    Here you find out what crawlers, assistants and agents see when they read your content.

  2. Platform

    Cloud, edge and release pipelines determine cost, security and downtime.

  3. Delivery

    Slow pages and stale results reach visitors through the APIs, the front end and search.

  4. Content

    Upgrades and wrong access rules start with the models, editors, permissions and the CMS itself.

What we work on.

Optimizely first. Three more platforms, the stack underneath, and services for any CMS.

Home ground

Optimizely

  • Graph
  • CMS
  • Commerce
  • Experimentation
  • DXP

We also work on

Headless delivery and AI on all three, upgrades on Umbraco

  • Umbraco
  • Contentful
  • Strapi

Our stack

What the platforms run on and talk to

  • .NET
  • Azure
  • Next.js
  • React
  • Algolia
  • Cloudflare
  • Azure Front Door
  • Auth0

On any CMS

Work that does not depend on the platform

  • Machine readability
  • .NET modernisation
  • Cloud migration
  • Automated security testing

Companies we have worked with.

Tell us what you need to decide.

Three lines are enough: your platform and version, the decision in front of you, and the date it has to be made.

hello@contentplane.net