Skip to main content
Forge

Platform · 6 min read

Developer platform strategy in the AI era

Internal platforms fail for social reasons more often than technical ones. Adoption is the metric that matters, and it has to be earned.

Sam OrtegaDirector of Developer Experience

A platform nobody adopts is a liability

An unadopted internal platform still needs maintenance, on-call and security patching — it simply produces no leverage in return. Measure adoption honestly and early, because the cost of the platform does not wait for the benefit.

The most reliable adoption signal is whether teams choose the platform when they are not required to.

Compete with the alternative, which is doing nothing

Your competition is not another vendor. It is a team writing a small script that solves their problem this afternoon. The platform has to be faster than that for the first useful result, or it loses regardless of how much better it is at month six.

  • A meaningful result inside the first hour
  • Documentation that starts with a working example
  • An escape hatch so the platform is never a dead end
  • Visible ownership — a name, not a shared mailbox

Add AI where the contract is clear

Intelligence belongs in the parts of a platform where the input and output can be described precisely: classification, extraction, routing, summarisation. Where the contract is vague, an AI feature mostly produces confident output that someone has to check — which is work you have moved, not removed.

Keep reading

Related guides

  • Workflow design

    Designing AI workflows that survive production

    Read guide
  • Strategy

    An automation strategy that scales past the pilot

    Read guide
  • Engineering

    API architecture for platform teams

    Read guide

Apply it

See these ideas running in the platform

The product and platform pages show how these principles are implemented in Forge itself.