Works with the ERP you already run
Plugs into your ERP. Speaks to your team.
No migration, no new app. OpsJi reads your ERP every hour, read-only, and sends one clear line on WhatsApp, mail or Slack.
What OpsJi reads
Every hour, the whole plant. One building at a time, one line to the person who acts.
What you get
Which of these happened at your plant this month? Pick one and watch the noise turn into one clear message.
Slack automations
Ask in Slack. OpsJi does it in your ERP. Every change waits for one tap.
How it starts
Four steps, about three weeks. No migration, no new software for the team.
Forty minutes on your own numbers. The fixed price and the first tool are agreed on the call.
A read-only user on your ERP, or a nightly export. Nothing leaves your network.
One person gets the line. We take out the noise until it is worth reading.
Code on your server and your team shown how it works. Upkeep is optional.
What it costs
One fixed price, set on your plant. You see it in writing before anything starts.
- 01Priced per tool, fixed before day one
After the walkthrough you get one page: the tools, the scope, the live date and the price. It does not move once you say yes.
- 02Start small with the Ops audit
One week on your export. The report is yours either way, and the audit is credited if you continue.
- 03Upkeep only if you want it
Billed monthly, cancel any month. You own the code with or without it.
Who it's for
Plants of 20 to 300 people with an ERP already running. Honest about where it does not fit.
A good fit
- Purchase, stores, production or quality still partly on sheets or WhatsApp
- A founder, plant head or finance head who can approve a fixed price
- One person on your side who will read a morning message and act
- Lot or serial tracked products, if you want trace and recall
Not a fit
- Replacing your ERP, or a fresh implementation
- Accounting-only work, payroll or GST filing
- Open-ended custom modules, or someone on site full time
About
Built inside a factory's ERP team. Sold one plant at a time.
OpsJi started as the layer I built for my own team, running ERP operations at a hardware manufacturer. Late POs, stock running out on the same ten materials, a stock value nobody could explain, shift sheets typed in a day late. The ERP knew most of it. Nobody had time to read it.
Now it is packaged so other plants can have the same, at a fixed price, on the ERP they already run. You talk to the person who builds it, and we take one client at a time.
Questions
Six straight answers.
Does OpsJi change anything in our ERP?
No. It is read-only by default. Any write, such as a draft PO or a posted shift sheet, is a proposal a person approves. It is logged and can be undone.
Where does it run? Does our data leave?
On your server or inside your network, or from nightly exports. Messages carry only what the person needs to act. NDA on request.
Which ERPs does it work with?
Odoo 14 to 18, Zoho Books and Inventory, Tally Prime and SAP Business One. Anything that can export to CSV or Excel works too.
How soon do we see something?
The first message usually reaches one person in week one. Most tools are live in one to three weeks.
What if it is not useful?
Stop at any weekly demo. The audit report is yours either way, and the audit fee is credited if you continue.
Who looks after it after go-live?
Thirty days of fixes are included. Upkeep after that is optional, billed monthly, and you can cancel any month. You own the code either way.
Get started
Pick one tool, or start with the audit.
Forty minutes on your own export. The fixed price and the first tool are agreed on the call.