Most failed operations software purchases were the right product bought two years early. A manager inherits missed handoffs, buys a workflow tool, then discovers nobody agrees what the workflow is. Six months later the tool is a very expensive list.
So start from where your processes actually are. This page uses four plain levels: ad hoc, documented, measured and automated. Formal models go further, and the CMMI levels run from "ad hoc and unknown" up to "stable and flexible". An ops manager at a small or mid-sized company rarely needs that much ceremony, though the idea holds: fix the level you're on before paying for the next one.
Find your level before you shop
Pick one process that matters, such as customer onboarding or vendor payments. Don't assess the whole company at once, because different processes sit at different levels. Then ask the questions in order and stop at the first no.
| Level | Test question | What it looks like | Software that fits | Don't buy yet |
|---|---|---|---|---|
| Ad hoc | Would two people do this the same way? | Lives in someone's head. Depends who's in today | A shared doc and a simple task board | Workflow automation, ERP |
| Documented | Can a new hire find the steps and follow them alone? | Written SOPs that people use | SOP or training tool, recurring checklists | Dashboards built on data nobody records |
| Measured | Can you say how long it took last month, and how often it failed? | Owners, deadlines, status, a monthly number | Work management with reporting | Agents acting on steps you haven't standardised |
| Automated | Has it stayed stable for three months, with the exceptions known? | Software does the routine steps, people handle exceptions | Integration tools, and an ERP if transactions justify it | A second overlapping automation tool |
Your answer may be uncomfortable. Plenty of companies with 40 people and expensive software are still ad hoc on the processes that hurt most. That's useful to know, and it saves money.
Repeat the test on your three most painful processes, then buy for the level most of them share. If they're split, fix the lowest one first, since a measured process that depends on an ad hoc one will still miss its dates. Give each process one named owner while you do this. A process owned by a committee rarely moves up a level.
SOPs vs ERP vs work management: what is the difference?
These three solve different problems, and vendors like to blur them. SOP tools hold how a job should be done. Work management tracks who is doing what by when. An ERP records transactions, such as orders, stock and ledger entries, on one database. Our guide on business OS vs ERP vs project management follows one order through each system, so this section stays on what an ops manager should do about it.
The test is the question you're trying to answer. "How do we refund a customer?" is an SOP question. "Who has the Acme refund and is it late?" is a work management question. "What did refunds do to this quarter's margin, by product?" is an ERP or finance question. Business operations management software rarely answers all three well, so expect to own at least two.
Level 1: ad hoc, where a checklist beats software
Spend almost nothing here. The goal is agreement, and agreement comes from a one-hour conversation with the people doing the work. Write the steps in a shared document, name an owner, and try it on the next three real cases.
A $0 option is enough. Asana's Personal version is $0, and Notion has a $0 per-member version. monday.com has one for up to 2 seats. Use any of them, or a spreadsheet. The warning sign that you've skipped this level is a meeting about which status colours to use before anyone has written down the steps.
Level 2: documented, where people need to find it
A written process only counts when people use it without asking you. At this level, you're paying for findability, version history and a way to check that people read the thing.
- Notion works if your team already lives there. It lists Plus at $10 and Business at $20 a member a month as of November 2026, and you could run SOPs on the $0 version for a while.
- Trainual is built for training and documenting how the company works. Its page says it's best suited to companies with 25 to 1,000 employees. Prices aren't published and need a demo. It also lists a one-time implementation fee of $1,000.
- Process Street turns a procedure into a checklist people run each time, which helps when skipping a step has a cost. Every plan says contact sales, so no price is published. Its Startup plan is aimed at businesses under 15 employees and under $2 million in revenue.
Our preference is to start in whichever tool people already open daily. A separate SOP system is worth it once you have staff turnover, or when a mistake has legal or customer consequences.
Level 3: measured, where work management earns its fee
Once steps are stable, you can start to count them. You want each case to have an owner, a date and a status, so you can report cycle time and failure rate without chasing people. This is where work management pays.
| Tool | Published price, billed annually | Worth noting for ops |
|---|---|---|
| Asana | Starter $10.99, Advanced $24.99 a user a month | Forms turn requests into tasks. Advanced adds form branching |
| monday.com | Basic $9, Standard $12, Pro $19 a seat a month, from 3 seats | Automation actions: 250 on Standard, 25,000 on Pro |
| ClickUp | Core $9, Business $17 a user a month | Every plan comes with a monthly AI credit allowance |
Choose two numbers per process and stop there. Cycle time and error rate are usually enough. A dashboard with fifteen metrics at this level tends to get opened once. If nobody changes anything after seeing a number, drop it.
Level 4: automated, and whether you need an ERP
Automate last, and only the steps that have stayed stable. Integration tools such as Zapier, Make and n8n connect systems you already own. We cover choosing the right ones in startup workflow software and the agent question in AI workflow management platforms, so here's the one rule that matters for an ops manager: every automation needs a named owner and an alert for when it stops, because a broken automation fails silently.
An ERP is a different decision. You need one when transactions drive the business: stock across locations, production, multi-entity accounts, or finance closing slowly because numbers live in six places. Odoo's app groups include finance, inventory and manufacturing, and it lists Standard at Rs 580 a user a month billed yearly on the view we read, with implementation excluded. We tried to read NetSuite's pages and couldn't load them, so we can't say anything current about it here. For a company with no stock and simple accounts, an ERP is usually overkill, and a good accountant plus work management goes further.
One process, four levels: a worked example
Take vendor invoice approval at an illustrative 30-person company handling about 60 invoices a month. All the numbers here are made up to show the shape of the change.
- Ad hoc. Invoices arrive at three inboxes. The finance lead chases people on chat. Late fees and duplicate payments show up every month.
- Documented. A one-page SOP says send everything to one address, with approval by the budget owner under $2,000 and the finance lead above it. Nothing new is bought. Duplicate payments mostly stop.
- Measured. Each invoice becomes a task with an owner and a due date. The monthly report shows average approval takes nine days, and one department accounts for half the delay. A conversation fixes that.
- Automated. Now that the path is stable, an integration creates the task from the inbox and routes it by amount. A person still approves anything unusual, and an alert fires if nothing has arrived for two days.
Notice that the big gains came at the first two steps, and neither required new software. That's the usual pattern, and the reason to resist starting at step four.
Business operations management software in Nautis
Nautis is an AI business operating system for startups, so it fits a narrow part of this page. If you're an operator at a startup of up to 25 people, it can hold levels two and three in one workspace: task boards, Notes for procedures, Expenses with approval chains, Invoices, and Employee management. Routines run recurring jobs on a schedule or on an event, and writes ask for approval by default.
Limits matter here. There's no dedicated SOP or training product in its guides, no ERP functions such as inventory or production, and no bookkeeping. It doesn't teach or enforce a management method. A dedicated tool will often go deeper in one function. Plans run from $49 to $129 a month, and established firms with mature processes should look at the tools above first. Nautis for startup operators covers who it does suit, and our startup operations platform page has a recurring-process audit you can use with any tool.
FAQ
What is business operations management software?
It's the software a company uses to run repeatable work: writing down procedures, tracking who does what, measuring results and automating routine steps. It isn't one product category. Most companies combine a documentation tool, a work management tool and, if transactions justify it, an ERP.
When does a company need an ERP instead of work management?
When transactions drive the business, such as stock across locations, production or several legal entities. If your main problem is who is doing what by when, work management is the right tool. An ERP is much harder to implement, so buy it only for a transaction problem you can name.
Should we write SOPs before buying software?
Yes. A shared document and one conversation with the people doing the work will expose most of what's broken, for no cost. Software bought before that step usually just records the confusion in a nicer format.
Which processes should an ops manager automate first?
Start with processes that have stayed stable for about three months, run often and have known exceptions. Good candidates move data between systems or route requests by a simple rule. Keep anything involving money leaving the company behind a human approval.