Product & platform lifecycle

Know what you own,
who owns it, and what breaks if it goes away.

Most organisations cannot answer those three questions. ProductPro is a catalogue with real stage gates: customer-facing products and internal platforms in one place, bridged to the ServiceNow CMDB, with the gates computed from actual data rather than ticked by hand.

Try it with GoogleYou get your own sandbox, pre-loaded with a working portfolio. Nothing you do touches anyone else.

Catalogue: Products & platforms, one record type
Governance: 10 stages, 8 gates, full audit trail
Sources: CMDB, incidents, changes, Jira
Answers: Blast radius in one click

The portfolio overview: attention cards, a pipeline strip across all ten lifecycle stages, and a board of products beneath. — **It opens on what needs doing.** Not a wall of statistics — every card is a link. “4 missing an owner” takes you to exactly those four.

Products and platforms are the same thing wearing different hats

A product serves customers. A platform serves the teams inside your organisation — your hosting, your database service, your CI pipeline, your Azure or AWS footprint. Both need an owner, a lifecycle, and someone accountable when they go away.

Keeping them in one catalogue is not tidiness. A dependency is a link from one entry to another, so splitting them into two systems makes the most valuable question unanswerable.

Would anyone be annoyed if this disappeared without notice, and is there a named person you’d complain to? Two yeses means it belongs in the catalogue.

The dependency graph with Shared PostgreSQL selected, highlighting the four products that would be affected. — **The question everyone asks too late.** Pick a platform and see exactly what breaks — *four would be affected if Shared PostgreSQL were withdrawn; one of them is tier 1*. Links nobody has confirmed in six months are drawn dashed, because an unverified diagram is a confident lie.

Gates that check, instead of gates that ask

Every governance tool has checklists, and everybody ticks them. The criteria here marked EVALUATED are queries against real data: is a production configuration item linked? Is there an approved change record? Is the security review still in date? Does anything still depend on this? Nobody can tick those.

Conditional go

The verdict every real process needs and most tools omit. It moves work forward but records each outstanding item as a dated debt with an owner.

Waivers expire

A gate you cannot waive is one people route around. A waiver with no expiry date is a permanent hole. Both are handled.

Rules stay put

A product pins its lifecycle template the day it enters. Change the process later and work already in flight keeps the gates it started with.

A product's gates, showing criteria marked EVALUATED with computed detail beneath each. — **Each gate shows its evidence.** Computed checks explain themselves — “product manager and engineering owner assigned” is the result of a query, not somebody’s assurance.

Wired to the systems that already know

Configuration items from the CMDB. Major incidents and change records from ServiceNow. Epics and blocking defects from Jira. App ID and SAID from your application inventory, if you have one — and it works fine if you don’t.

The rule each of them has to meet: it must make a gate computable, or it is decoration. Go-live cannot pass without an approved change record. Release readiness fails while a blocker defect is open.

Configuration items are owned by the CMDB. This never writes over one, and never shows you a cached value pretending to be live.

A product's operations tab: a blocker-defect banner, counters, and tables of major incidents, changes and Jira work. — **Read the banner.** “1 open blocker defect. G5 Release Readiness cannot pass while that holds.” That is an integration doing work rather than filling a tab.

Try it on a portfolio that already has something to look at

Signing in gives you your own organisation, seeded with seven products, five internal platforms, their dependency graph, configuration items, incidents, changes and work in flight. Create things, run a gate, archive something, break it however you like — it is yours alone and nobody else can see it.

Continue with GoogleTakes about five seconds. Start with “How this works” in the sidebar.