4 / 35
profiled systems document an AI module
Four of the systems Stackmark profiles document an AI module. In demonstrations the layer looks finished. In contracts it is often a roadmap. Here is how to tell the two apart before the shortlist is set.
Every finance-system demonstration this year has had an AI segment. Invoice capture that codes the line, a journal anomaly flag, a cash forecast that narrates itself, a chat box over the reports. The segment is polished, and it is usually the part the room remembers.
Stackmark records an AI module for a vendor only when the vendor documents it as offered. Four of the systems profiled meet that bar today. That is not a small number for a module that did not exist in most product catalogues three years ago, but it is a long way from the impression a season of demonstrations leaves.
A useful habit is to ask, for each AI capability shown, which of three states it is in. The vendor knows; the demonstration rarely says.
The module page for AI features carries four demonstration questions written to force that answer. The first is the blunt one: which of these are generally available to all customers today? Ask it before the segment starts, not after.
The second question buyers under-ask is about data residency for the model. A capture feature that sends an invoice image to a third-party model is a data-processing arrangement, whether or not the vendor calls it one. It belongs in the security review, not in the demonstration debrief.
If the vendor cannot say where the model runs, the feature is not ready to be scored.
Do not remove a system from a shortlist because its AI layer is thin. The transactional core is what runs the close; the AI layer is what will change fastest over the contract term. Do remove a system that cannot answer the three-state question, because a vendor that will not say which state a feature is in is asking to be scored on a roadmap.
11
systems sold only as multi-tenant cloud
Eleven profiled systems are sold only as multi-tenant cloud. That changes which questions matter: upgrade cadence and tenant isolation move to the top, and infrastructure sizing drops off the list entirely.
16
modules, each a category rather than a capability
A module list is a table of contents, not a scope. Two systems that both say ‘procurement’ can differ by an order of magnitude in what the word covers. A short guide to reading the list the way an implementer does.
0
vendors publishing a list price for a real configuration
No vendor profiled publishes a list price for the configuration a buyer will actually run. A directory that prints one anyway is guessing. Here is what Stackmark records instead, and how the cost model turns it into a range.