Demo project — fictitious code, with the engine’s reading on every stage and no model drafts or test runs. Nothing you do here is saved. A demo run is never signed. No signed run, no audit pack and no export comes out of this screen — a signature says a named account analysed a named source, and none of that happened here.Nothing here counts against your five free analyses: the demo is the same for every account, and what you change lives in this browser only.Try an example or your own code
DemoAssumptions needed
Demo · Z_MM_PO_APPROVAL — Economics
The forecast starts empty: no day rate, no investment, so no amount — you enter the assumptions.
Step 1: Your codebase
Measured by the engine run over the example file — nothing to do here.
- Lines of custom code
- 552
- Clean Core Score
- 40
Step 2: Your rates
What a developer day and a cost. The model refuses to produce a figure until the numbers behind it are yours.
per day
per day — the people who test by hand
Step 3: Budget and cadence
The one-time budget the payback is measured against, and how often upgrades arrive — the two frequencies start at an assumed value of the model.
your budget, once
assumed 1 until you change it
assumed 2 until you change it
Step 4: Result
Maintenance effort before and after modernising, and the . Days and ratios only — the amounts belong to your own project.
No forecast yet: still missing the developer day rate, the key-user day rate, the modernisation investment. An output built on a number nobody entered is not a scenario, it is an invention.
A simulation, not a quote: computed only from figures you state.