Augur Intelligence reads Prophet 21 directly, not through a bolted-on layer

Vendors bolt most AI features onto the product's own screens and reports. For software built to serve many kinds of businesses, that is a reasonable tradeoff. A question one screen already answers comes back fast. A question that spans two or three screens does not. The assistant sees only what each screen shows.

Augur Intelligence reads the Prophet 21 database directly, the same live production database behind every screen. It does not matter whether the numbers a question needs live on one screen or several. If the data connects, the assistant can follow it.

“Which customers received a quote for this item but never ordered it?” Distributors ask that one. Answering it means comparing who got a quote against who placed an order, for the same customer and item. Prophet 21 has a screen for quotes and a screen for orders, not one for the difference between them. An assistant limited to a fixed set of screens and reports needs a new report built for a question like that. Asked of Augur Intelligence, it is one question and one answer, read from P21 itself.

Prophet 21 lets distributors customize screens, but no screen or report can expose every field in the database. Screens and reports get built for specific jobs, not as a complete window into everything P21 stores. Some data exists only in the database itself, outside every screen, report, and export.

An assistant built on those screens and reports inherits the same limit: if none of them was ever built to show a field, the assistant cannot show it either. Reading the database directly does not carry that ceiling. If the data is there, a distributor can ask Augur Intelligence about it, including data nobody thought to put on a screen. Reaching more data does not mean reaching it without limits: only the users a distributor approves can connect.

SimpleApps builds only for Prophet 21. Supporting one ERP makes a direct connection practical. A vendor built to serve many different kinds of businesses cannot safely open that kind of access once and trust it everywhere: every customer's setup is different enough that the same connection would need separate testing and trust for each one. A vendor built around a single system starts from a much smaller gap to close. Augur Intelligence connects straight to the Prophet 21 database. The connection is read-only: the assistant answers from the data and cannot change it. It works against live production data, not a copy. It does not pull from a fixed set of screens and reports; instead, it writes its own queries against the data. The Augur Intelligence page covers how the connection works.

Reading a database directly is not automatically more accurate than reading a screen. A screen already applies the business's own rules before it shows a number: what a status means, which values get excluded from a total, what a blank field stands for. An assistant that reads raw data without knowing those rules can return an answer that looks right and is not.

The difference is experience. SimpleApps has spent years working directly in Prophet 21 databases. That experience, how a price gets calculated across contracts and price libraries, what a quote is versus what an order is, the conventions that make P21 what it is, is what goes into Augur Intelligence. It also means recognizing what is specific to one distributor, beyond what is standard across every P21 install: a distributor's own user-defined fields are read the same way, without being told about them in advance. Direct access without that experience would carry the same risk as any other raw connection. Built on it, the connection carries the rules a screen would have applied, so the assistant is not left to infer them. And it still reaches further into the data than a screen built for one purpose ever could.