ONYX in-house · ERP · mail · wiki · tasks

ONYX runs its own company on this model.

We run the model we offer to customers in our own company first. The agent prepares the draft, a human makes the decision.

30 min · free
  • Proposal → approval → execution
  • Every step in the log
ONYXApproval queuediagram
ERPMailWikiTasks
Commercial proposalprepared by the agent · approved by: sales
Draft
Invoiceprepared by the agent · approved by: accountant
Draft
Stock movementprepared by the agent · approved by: warehouse manager
Draft
Log

    Schematic view. Real screens below.

    Four systems. One rule.

    ONYX ERP

    quotes · invoices · stock

    Corporate mail

    reads · writes drafts

    Wiki · Outline

    rules · documents

    Task system

    tasks · status

    Agentreads · prepares drafts
    Humanapproves or cancels
    Logevery step is recorded

    The agent prepares. A human approves.

    Document01 · Proposal02 · Approval03 · Execution

    Commercial proposalsERP · mail

    Agent prepares
    Sales approves
    Applied in ERP

    InvoicesERP

    Agent prepares
    Accountant approves
    Applied in ERP

    Warehouse operationsERP · stock levels

    Agent prepares
    Warehouse manager approves
    Applied in ERP
    No draft is executed without approval. Every step is written to the log.

    Real screens.

    Not numbers but the workflow: query → check → approval → trace in ERP.

    The agent reviewing a quote: check table, proposed date change and questions
    Query and checkThe agent reads the quote in ERP, finds the problem and prepares a change
    Prepared changes and the "Do you approve?" question
    ApprovalThe change waits for a human's approval. Prices and totals stay untouched
    ONYX ERP quote page with Claude (MCP) in the Created by field
    Trace in ERPThe document stays in ERP and the author is recorded

    Real screens · customer name and amounts hidden

    The decision stays human.

    The decision is always the human's. The agent can prepare it in ERP, and it is applied only after approval. The one exception is payments and bank operations: they are outside ERP and the agent does not touch them.

    • Final price and discountThe agent can prepare it in ERP; a human decides. A human confirms the final price.
    • Sending a letter to the customerThe agent can prepare the letter draft in ERP; a human decides and sends it.
    • Payments and bank operationsThe agent does not touch these operations — they are outside ERP.
    • Contract signingThe agent can prepare the contract draft in ERP; terms and signature belong to a human.
    • Changes in customer systemsThe agent can prepare it in ERP; an engineer decides and makes the change.
    • First meeting with a new customerThe agent can prepare notes in ERP; introductions and negotiation stay with the team.

    The same principle, in your system.

    How it works: data, model, approval

    Result: an AI readiness map for your company within 1 business day. No access to your systems required.

    • PrincipleProposal → approval → executionThe rule that works at ONYX is the same for you
    • StartOne system, one roleread-only mode
    • NextApproved draft typeseach type is added at your decision

    Questions.

    This page gives no numbers. What it shows is the workflow.

    Does this really work?

    ONYX uses this model in its own processes. Concrete results are measured in your pilot.

    How does it start in your company?

    With one system, one role and read-only mode. The pilot starts within 7 days and lasts 30–60 days.

    Run it the same way in your company.

    First, a free 30-minute AI readiness check. The pilot starts within 7 days.

    First task · optional

    Result: an AI readiness map for your company within 1 business day. No access to your systems required.

    • Read-only
    • Connector on your server
    • You choose the model
    ONYX · AI agents · ONYX in-housesales@onyx.az · +994 12 310 20 40