Operant

How it works

The same story, without any motion.

The animation on the home page is a convenience. Here is the identical sequence as labelled frames, plus the capabilities behind each step.

The sequence

One customer request, four frames.

This is one entry point into Operant — a request that needs checking before a quote goes out. It is not the whole product.

  1. Frame 1 · Arrives

    A request lands in one card

    • Northwind Rail, by email, 09:12
    • Three requested items read into lines
    • Source and arrival time kept with the card
  2. Frame 2 · Flagged

    One item cannot be trusted yet

    • “the seal for the pump, same as last time”
    • Marked Needs clarification, not guessed
    • The quote is held rather than sent wrong
  3. Frame 3 · A person decides

    The next step has a name on it

    • Sales operations lead is responsible
    • Operant suggests a catalogue match
    • The person confirms or rejects it
  4. Frame 4 · Ready

    The quote is prepared for review

    • All three lines priced from the same data
    • Marked Ready for review, not sent
    • Order and payment are the steps after

Operant workspace · Product preview.

Where a person is required

A suggestion and a decision must never look the same.

Operant is designed to read, sort, and propose. Changing a price, an order, a financial commitment, or master data is meant to require a person who is allowed to do it.

Suggested by Operant

What software may do

  • Read a message into requested lines
  • Say which field is missing or ambiguous
  • Rank supplier options and show why
  • Draft a quote for someone to review
  • Show what is waiting and how long it has waited
Reserved for a person

What a person must do

  • Confirm what an unclear line actually is
  • Choose a supplier and own the choice
  • Approve a price or a commercial term
  • Release a quote or an order to a customer
  • Accept a financial commitment

This is a design requirement for Operant, not a description of a verified implementation.

The preview

The view this all leads to.

A queue of work that needs a decision, one open request, and a visible line between what Operant proposes and what a person authorised.

Operant · RequestsSample workspace

Work queue

  • REQ-2041Northwind Rail · 3 itemsNeeds clarificationSales operations lead14m
  • PR-0318Bearings · 40 unitsNeeds reviewProcurement manager1h
  • ORD-1180Kestrel Plant · orderReady for reviewCommercial lead2h
  • INV-0994Payment overdue · 6 daysWaitingFinance3h

Operant workspace · Product preview.

Readiness

What exists, and what is only a drawing.

Capabilities behind the sequence — what Operant covers on the path from request to payment.

  • Requests in one card

    Channel, attachments, source, requested items, owner, and status held together.

    ReadyAvailable
  • Reading a request into lines

    Pulling items, quantities, and dates out of a message and saying what is missing.

    ReadyAvailable
  • Exceptions and clarification

    Flagging an unclear line instead of guessing, and naming who resolves it.

    ReadyAvailable
  • Owner and approval

    A responsible person per decision, with the history of what was approved and when.

    ReadyAvailable
  • Supplier comparison

    Options side by side on price, lead time, and terms, ranked but never chosen automatically.

    ReadyAvailable
  • Order, invoice, payment status

    The same lines carried forward so nothing is retyped, with payment state visible.

    In pilotIn pilot
  • Integrations and analytics

    Connections to the systems you already run, and process metrics on top of them.

    In pilotIn pilot

Questions

What people ask first.

Is Operant available today?

Yes. Start with a pilot on one process you already run, or download the desktop apps once our cloud migration window closes. Email us to get started — and claim 1 000 000 free tokens while the move is underway.

What does the animation actually show?

One entry point: a customer request with an item that needs checking before a quote is prepared. It is one example of how Operant keeps the next step visible across the wider product.

Would software change a price or an order on its own?

No. Operant suggests and shows what is missing. Changing a price, an order, a financial commitment, or master data requires a person with the authority to do it.

What would a pilot discussion cover?

One real process, what it costs you today, how we would measure improvement, and which Operant capabilities map to that slice.

Which numbers on this site are real?

The formulas are the ones we use in conversation. Scenario numbers are examples you can replace with your own — bring your volume, times, and costs to a pilot discussion.