Operator field note refined 2026-10-07. This is a decision method, not a product-wide survey.
Grouping the systems we work with by how ready they are for AI, a few clean lines emerge, and they are not the lines the marketing draws.
On the open end are the modern platforms built API-first. An API-first interface may provide a useful starting point, but documentation is only the first test. They are not perfect, even the best of them have real gaps, like field-service platforms that let you allocate a payment but not create an invoice through the API, or a project side whose data model is thinner than the service side. But you can build on them.
For an ERP used as the financial system of record, verify the permitted route for its native postings: a paid API license here, a scheduled-export workaround there, a modern REST layer bolted onto an older core. The relevant test is whether that route supplies the required financial records for the account and edition.
A retained database view can contain fields missing from another permitted interface. That makes field coverage worth comparing; it does not establish that the product has no API, that a newer system is better or that contractors are migrating away.
On the AI itself, be skeptical of the label. A dispatching or document-extraction feature should be evaluated against its specific task. A diagnostic feature and a finance feature have different acceptance tests: diagnostic assistance and invoicing support solve different tasks, so compare each against the actual operating decision. But here is the pattern that matters most: a native feature can work well within its scope while a cross-system finance question still needs additional evidence. The value shows up when someone assembles the complete picture across systems first. That is the whole reason the data layer, not the AI layer, is where AI-readiness is really decided.
Use this in an implementation review
- Define the operating question and required objects for the exact account and edition.
- Check source coverage separately from interface availability and AI feature availability.
- Preserve unavailable evidence as unknown instead of rating the product negatively.
Specific systems to inspect
Operator analysis informed by scoped implementation workflows. The checks explain how to evaluate a financial decision; they are not an industry survey, a capability certification or a claim that every account behaves alike. See the full software index.