Skip to content
opero

AI agents that run your operation overnight.

They read every site, cost the next move, and hold each decision for your approval.

21:14
Operobot
Today

Nightly read finished. Two sites reconciled, one product line flagged:

  • Site A: 30 units available
  • Site B: stock constrained
  • Sales ledger: RM41/day vs RM309/day
21:12

Held for you

Awaiting approval
RM351/day of RM481 estimated21:14

Why an agent, and not a report

01

Every night, decisions go unmade because no one had time.

Stock, purchasing, capacity, exceptions. The numbers are already there, spread across the business. Nobody gets to them in time, and the report only tells you what happened after the month is over.

Works inside the systems you run

  • SAP
  • Oracle
  • NetSuite
  • Odoo
  • Xero
  • QuickBooks
  • Sage
  • Zoho
  • Shopify
  • WooCommerce
  • Shopee
  • Square
  • Salesforce
  • HubSpot
  • Zendesk
  • Google Sheets
  • Airtable
  • Notion
  • WhatsApp
  • Telegram

The decision loop

02

One decision loop, from issue to verified outcome.

The evidence, the options, the approval, the action, and what happened next. All in one place.

Stage 1 of 4

Bring the records together

Pull the relevant numbers from the systems your team already uses, including browser-only back offices.

Read

Site A
30 units available
Site B
stock constrained
Sales ledger
RM41/day vs RM309/day

Sample agents

03

One agent for every decision your team makes repeatedly.

Showing 7 of 30

Ran in pilot Stock

P-1

Transfer before you buy

Move stock you already own before raising an order.

Signal
Checks stock and sell-through for the same line across every site, nightly.
Decision
Moves existing stock to where it sells before any new purchase, as a small first move.
Action
Writes the transfer, notifies both sites, suppresses the duplicate order.
Measure
Confirms arrival and checks sell-through again at both sites.

From the record

30 units moved between two sites before any purchase; RM114/day recoverable, estimated.

Seven agents from the dated multi-site pilot.

Start with this agent

After approval

04

One approval. The work gets done everywhere it needs to.

This is where a chat assistant stops. Opero carries the approved decision into the systems and teams that need to act, then checks that it actually happened.

  1. 21:14:01Approval recordedApproved in Telegram and logged against the decision.
  2. 21:14:02Systems checkedOpero checks for conflicts or duplicate work before making any change.
  3. 21:14:04Task createdThe approved action is entered into the operating system and given a reference.
  4. 21:14:05Team notifiedThe people responsible on the floor and in the warehouse are told what changed.
  5. 21:14:06Records updatedThe decision is reflected in the relevant ledger and dated to when it was raised.
  6. +24hOutcome checkedOpero goes back to the source records to confirm the stock arrived and measure what changed.

Is this your operation

05

Built for operations where the same decisions come up again and again.

Opero works best when a few things are already true.

Requirements

More than one site or system
Two outlets, several branches, or simply a back office and a ledger that no one has time to read together.
Decisions that repeat
Stock, purchasing, capacity, exceptions. The same judgment calls, week after week.
Someone who can make the call
One accountable person who can approve the decision in a channel they already use.
No API required
Browser-based systems, spreadsheets, CSV exports. If your team already works from it, Opero can usually work with it too.

Start read-only. Prove the first decision.

Return date agreed upfront.

  1. Meet your operator

    Choose the first part of the operation to work on and agree what a useful result looks like.

  2. Map the operation

    We learn the records, rules, exceptions, and who has authority to approve what.

  3. Observe

    Opero reads, but changes nothing. You can compare its recommendations with the decisions your team actually made.

  4. First decision

    One real recommendation, with the evidence and expected cost, held for approval.

  5. Act and check

    Once approved, Opero carries it through and comes back to measure what happened.

Questions operators ask first

06

Clear boundaries before anything goes live.

Opero starts by watching. It only gets permission to do more once it has shown that it can make the right call consistently.

  1. Observe

    Reads the operation. Sends nothing. Changes nothing.

  2. Recommend

    Shows what it found, the options, and what each one is likely to cost.

  3. Approve

    Anything consequential waits for a person to say yes.

  4. Limited execution

    Opero can only make changes in the systems and categories you have explicitly enabled.

  5. Earned autonomy

    Routine decisions can become more automatic over time, if you choose.

Some decisions can stay approval-only forever. In our pilot, automatic approval is still switched off.

Questions

If there is something we have not covered, email hello@opero.ai. For deployment, access, and data controls, see the security page.

Does Opero ever act without approval?

Not on arrival. A fresh install sends nothing, writes nothing, and auto-approves nothing. Routine categories can earn auto-approval after at least 95% human agreement across at least 20 decisions on at least 8 nights, and the consequential ones can require your approval forever. In our pilot, auto-approval is still switched off.

What if our systems do not have an API?

No. It is the normal case. Usually a login is enough: Opero drives the back office the way a manager does, through a real browser. Google Sheets and CSV exports count as records too.

What data leaves our premises?

Each customer has a separate installation. Settings, connected-system logins, and operating data live with you and are not shared between customers. Opero reads only the systems you connect, and customer data is not used to train a model shared with other customers. The security page states only the controls the current product supports.

What happens when Opero gets it wrong?

Nothing, until someone says yes. Every recommendation points to the original records and can never alter a number; where a figure is an estimate, it is labelled as one. Your disagreement is logged against the decision, and a category only earns more room by being right, decision after decision.

How do we stop it?

A kill switch pauses the system from the dashboard, and changes to your systems can be switched off per site at any time without removing read access. Every recommendation, approval, change, and reversal sits in a log that can only be added to, with who did it and through which channel.

How is it priced?

Per site. The scope, the boundary, and the price are agreed with you before anything is connected.

Who builds this

07

Built by an operator and a researcher.

One of us spent years running the kind of operation Opero reads. The other builds the systems that read it.

Chief executive

Runs the kind of operation Opero was built for.

Built and operates a multi-site claw machine arcade business, where stock, pricing, purchasing, and capacity decisions were previously made by hand every night.

Credentials

  • Built an eight-figure business within its first year
  • Operates one of the largest businesses in its category
  • Still runs the operation day to day

Chief technology officer

Builds the decision engine behind Opero.

Works in machine learning and computational neuroscience, with published research and top results in large international AI competitions.

Credentials

  • Ranked 1st among 15,000+ participants in an RSNA Kaggle AI competition
  • 8 first-author, peer-reviewed papers in AI and computational neuroscience
  • Silver medalist, International Chemistry Olympiad
  • AI and computational modelling lead, Stanford iGEM team

Start with a real operating week

Send us one week where stock, purchasing, capacity, or another operating decision went wrong. We will work through the records with your operator and come back with one costed decision, the evidence behind it, and what Opero would have done. No integration required.

hello@opero.ai