Keep the commercial facts connected.
Preparing a quotation means bringing together customer context, products, prices and commercial exceptions. When those facts move between conversations and spreadsheets, reviewers can lose track of which version they approved. ORYH gives the agent and the approver a shared business record to work from.
This is AI-native ERP in a familiar workflow: a person works with an agent, and the agent uses ORYH's permitted capabilities to read and act on company records.
From a request to a recorded decision.
"Prepare the Meridian renewal quotation with the agreed service bundle, apply the commercial exception, and send the full document to me before approval."
Agent resolves the customer, products, and current price evidence
ORYH validates line items, quantities, currency, and ownership
The agent presents the complete quotation for confirmation
ORYH stores the submission; a workflow agent reads the rules and assigns the approver
The approver reviews the same durable quotation facts
After acceptance, the quotation-to-sales-order workflow can carry the accepted facts into an order with a link back to the source quotation.
Review the whole quotation before submission.
- Customer and scope
- Confirm the customer, contact, service bundle and source commercial instructions.
- Lines and pricing
- Review products, quantities, unit prices, currency, discounts and the resulting totals.
- Exceptions and approval
- Check the reason for any commercial exception and the company's configured approval route.
The agent prepares and explains the proposal. Confirmation belongs to the employee; approval belongs to a person with the required authority. ORYH's permissions and workflow controls govern which actions the system accepts.
The record survives the conversation.
Commercial context, exceptions, revisions, and approval remain attached to one durable quotation.
- Business record
- Customer quotation with customer and product references
- Commercial evidence
- Confirmed lines, price evidence and exception context
- Decision trail
- Quotation revisions, approval facts and commercial status
To evaluate the result, inspect the saved business record, its state and the associated audit evidence. A persuasive agent response alone does not establish that a submission or approval occurred.
Check the exceptions as carefully as the normal path.
A price or term is missing
The agent asks for the missing information before presenting the quotation for confirmation. It should not invent a commercial agreement.
A discount needs an exception
The company's configured workflow determines pricing authority and exception thresholds. An instruction in chat does not grant authority.
The customer requests a change
Revise the quotation and inspect its new terms and approval requirements. Keep the earlier revision and its decision context traceable.
The quotation is ready to send
Approval and external customer delivery are separate actions. Document generation or delivery depends on an implemented integration or an authorized human handoff.
Evaluate the workflow with your agent.
Use a compatible, company-approved client such as Codex, Claude Code, Hermes or OpenClaw. Connecting a client and validating this scenario are separate steps. See the runtime connection options, including the current connection boundary for Claude Cowork.
- Bring a redacted quotation, the relevant product and price information, and one commercial exception.
- Run the normal path and a missing-price or approval-return case with your chosen agent.
- Inspect the saved quotation and decision history, then review the accepted-quotation-to-sales-order handoff.
Measure review effort, corrections, completion and the quality of the resulting evidence against your current process. Agree on acceptance criteria with the process owner before expanding the enterprise pilot.