Platform Forward Group· 2 min
The reporting stack nobody owns
Every estate has a reporting layer that grew instead of being built. How to inventory it, what it costs, and the rebuild pattern that actually holds.
Inventory first. Then the plan. Then the work.
Platform Forward Group modernizes legacy systems: monolith decomposition, cloud moves, and roadmaps that name owners and dates. The first engagement is always the same two-week inventory. Nobody has ever regretted knowing what actually runs in production.
The Modernization Inventory
Two weeks, fixed fee, same product for everyone. It exists to replace opinions about the legacy estate with a list of what runs, who owns it, and what it costs to keep.
Walk the floor
We catalog what actually runs: applications, jobs, databases, the server under the desk. Every entry gets an owner, a business function, and a last-touched date. Half of every estate is a surprise to somebody.
Price the standing stock
What each system costs to keep: licenses, infrastructure, and the people-hours that keep it breathing. The retirement-risk list gets names on it. This is the part nobody has written down.
Hand over the roadmap
A sequenced plan with dates: what to decompose, what to move, what to leave alone on purpose. Priced in effort, ordered by risk, written so your team can run it without us.
The work after the inventory
Every follow-on job is scoped from the inventory. Fixed scope, every time.
Monolith decomposition
Carving services out of the monolith in the order the seams allow, not the order the org chart wants. Strangler-fig routing, parallel running, and the cutover checklist taped to the wall.
Cloud migration
Moving workloads that earn the move and saying so about the ones that don't. Landing zones, data migration rehearsals, and a rollback plan written before anyone touches DNS.
Legacy .NET modernization
Framework 4.x to modern .NET, the WCF and WebForms problems included. We have met your app before. It can be moved, and there is a wrong order to do it in.
From the casebook
How the work actually goes: inventories, cutovers, and the mistakes we only make once. Serial numbers filed off.
· 2 min
The Java 8 deadline nobody circled
Temurin now lists Java 8 as available until at least December 2030. The cliff is not coming, and the bundled JREs in your appliances were never going to take the updates anyway.
· 1 min
Debian 11 runs out on Monday
Bullseye's Long Term Support ends August 31st, five years after release, per Debian's own lifecycle page. The OS inventory has it in two places nobody lists: the base images and the appliances.
Asked on every first call
Can you just tell us to move everything to the cloud?
No. Some of your estate should move, some should be retired, and some should stay put because moving it buys nothing. The inventory says which is which, with numbers.
Our documentation is years out of date.
Expected. The inventory does not start from your documentation; it starts from what is actually running. Stale docs are a finding, not a blocker.
How much does the inventory cost?
A fixed fee, quoted after a thirty-minute walkthrough call, sized by system count. The walkthrough is free. If your estate is small enough to not need us, we say so on the call.
Do you stay for the modernization itself?
If you want us. Each follow-on engagement is scoped from the roadmap, fixed in writing. Some clients run the whole roadmap themselves. The roadmap is written assuming they will.
Book the walkthrough.
Thirty minutes. Describe the estate, get a straight answer on whether the inventory fits, and a fixed quote if it does.