What we can evidence today —
and what we cannot.
Product pages tend to claim everything in the present tense. We carry a maturity state per capability instead, with a fixed vocabulary and a rule that holds even when it is inconvenient.
Four states, no more.
Verified in product
The capability exists and was observed in a controlled environment by a party independent of the implementation, with a date.
Pilot / validation
Implemented and scoped. The independent observation is still outstanding.
In active development
Part of current delivery, with open conditions.
Defined capability
A committed target. Defined, described, not deliverable.
What is not marked, we do not claim.
Maturity is an axis of its own. It is never mixed with the business semantics — not by colour and not in the composition. That is why not a single maturity state appears on the homepage: it belongs on the capability, not on the brand.
Seven points, qualitative.
These points were examined in a controlled environment by a party independent of the implementation. The figures that go with them are held back until their publication is decided — which is why no number appears here.
- 01Canonical ERP projection, read-only.
- 02Payment approval server-side, self-approval blocked, approval matrix tenant-configurable, fail-closed.
- 03Tenant separation at row level.
- 04Rates with source, rate date and retrieval time.
- 05Covenants with source, headroom and status — empty rather than green when unknown.
- 06The forecast proposes no pattern from too little history.
- 07Rollback and restore drills with state parity.
Two metrics we do not offer.
This is the most honest point on the page, because it is a negative one.
DPO
There is no authoritative COGS denominator for days payable outstanding. A ratio without a sound denominator is not a ratio, it is a number.
Cash conversion cycle
For the same reason. We could compute and display both. We do not, because the result would imply a precision it does not have.
What that means for other numbers
Where a source is missing, the field stays empty rather than green. An empty covenant status is a statement; an invented one would be a defect.
What is deliberately absent from this website.
Prices and package tiers
A commercial catalogue cannot be presented responsibly on today's basis. We explain modularity, not a package architecture.
Certifications
No certification and no proximity to one. What exists for a review, we state specifically on request.
Figures from operation
Verified runtime figures exist, but their publication is not decided. Until then the substance stays qualitative.
Application screenshots
We show no interfaces that would suggest a state we cannot hold in every environment.
Thirty minutes in which we get specific.
If you want to know which maturity state sits on the capability you need, ask for it. That answer is one we can give more precisely on your case than a website can.