The First Thing That Changed When I Started Treating the Platform as a Product

Working on an enterprise portal platform, I hit a realization: the platform team was really an internal vendor — and its customers were the other teams trying to integrate with it. Once I saw it that way, I made one decision: run the platform like a product. I split that decision into three rules.

Rule 1: Teams don't come to us — they self-register

Early on, every new integration meant a request, a meeting, a wait. The platform team had become the bottleneck — every team was waiting on us.

The fix: a manifest-driven registration system. When a team wants to plug a new application into the platform, they don't come to us — they define their application's manifest, register it with version information, and the platform discovers it automatically. Tenant-scoped rollout runs through the same mechanism.

Rule 2: No integration without a contract

A manifest alone isn't enough. How each application talks to the platform — authentication, the shared data model, the event schema — has to be defined as an API contract up front. Teams showed up with React, Vue, Angular, Flutter, and even legacy iframe-based apps — four different frontend technologies living side by side on one platform, under one set of contracts. The only reason that worked is that no integration ever started without one.

Rule 3: Every rollout has to be reversible

This was the most concrete result of running it like a product: nothing ships to production without version pinning and a rollback path. When a team releases a new version, it rolls out scoped to their own tenant; if something breaks, one command reverts to the previous version without touching the rest of the platform.

What actually changed

Treating the platform as a product was really a transfer of authority: the platform team stopped standing in the middle of every change, and started building the rules that let change happen safely without us. Teams moved faster — and we got fewer 3 a.m. wake-up calls.

These rules turned into a durable way of working — and that way of working is now at the core of what I teach at NEBULACT AI Academy.