Turn operating procedures into reviewable ERP workflows with source-linked actions
Breez is an ERP agent for operational work that moves between spreadsheets, inboxes and business systems. Its product page focuses on Microsoft Dynamics 365 and NetSuite, where teams often repeat a procedure manually even though the underlying records already exist elsewhere. Rather than replacing the ERP, Breez acts as a layer that follows the organization's procedure around it.
A standard operating procedure becomes a playbook with explicit triggers, matching rules and stopping conditions. The team can review those steps as a document and edit them when the process changes. Examples include entering spreadsheet rows into an ERP, drafting sales orders from email, matching purchasing documents and preparing collections follow-up. These examples illustrate possible workflows rather than a promise that every company's process works without configuration.
The platform describes citing entries back to the cell, email or document from which they came. Ambiguous cases are directed to a human queue. Its staged approach moves from reading to drafting and then acting, with promotion controlled for each playbook. This makes the source and the proposed action visible together, which is especially important for payment details, vendor records and other sensitive operational changes.
Breez states that it runs within customer infrastructure, using the customer's network, keys and retention rules. Initial connectors are read-only, and shadow runs show what the system would have done before operational changes are enabled. The website names its subprocessors and explicitly says Breez has not completed its own SOC 2 audit. A customer's security assessment should preserve that distinction instead of confusing provider certifications with a certification held by Breez itself.
The vendor offers a paid pilot around one procedure and prices by workflow rather than seat. A useful evaluation defines acceptable error and escalation rates in advance, then reviews the run logs against actual source material. The workflow should remain limited until the operational owner is satisfied with matching, exceptions and approval behavior.
