Usage-based pricing for manufacturing ERP — without the legacy tax
Esvos is built for small and mid-size manufacturers who want real ERP without a six-figure rollout. You pay a flat monthly platform fee plus the operational throughput your team actually uses — no per-seat licenses, no surprise upgrade tiers.
What’s in the pricing model
Every plan has the same shape — only the included amounts and limits change.
A flat base that covers the connected platform — every module you've enabled, all roles, all workflows.
A monthly allowance of operational throughput — work orders, transactions, automations, integrations. Sized to your plan.
Documents, attachments, BOM revisions, traceability records. Generous baseline; add more as you grow.
Agent runs, drafting, and AI analysis draw from a separate AI credits pool — so AI usage never silently competes with operational throughput.
Go over your RU or storage allowance? You see exactly what was used and what it costs — no surprises, no per-seat penalty.
Set a cap. If a runaway integration starts burning credits, your tenant stops at the limit you chose — not at the limit of your budget.
Need isolation, dedicated infrastructure, or a private region? Available as an add-on for teams that require it.
How usage-based pricing differs from per-seat ERP
Most ERP pricing penalizes growth — every new user, every new module, every spike in volume costs more. Esvos is structured so that adding people doesn’t automatically add to your bill.
| Scenario | Esvos | Legacy ERP (NetSuite, SAP, etc.) |
|---|---|---|
| Adding a user | Doesn't automatically increase your bill | Per-seat license + implementation fees |
| Adding a module | Enable it — already included in the platform fee | Separate SKU, separate contract, separate rollout |
| Heavy month of orders | Counts against your Resource Units; transparent overage | Often hidden behind tier upgrades or annual recommits |
| AI / agents | Separate AI credits — clean, capped, predictable | Either unavailable or bundled with everything else |
| Hitting a limit | Tenant-configurable hard caps — you choose what stops first | Surprise invoices, retroactive true-ups |
| Pricing tier shape | Same structure at every tier — just bigger inclusions | Different feature sets locked to higher tiers |
Who this pricing model fits
We built usage-based pricing for the manufacturers most poorly served by legacy ERP — startups and small-to-mid-size shops that don’t need (or want) a six-figure implementation.
You need real ERP — BOMs, inventory, work orders, traceability — without a NetSuite or SAP implementation eating your runway.
You’ve outgrown spreadsheets and QuickBooks but you’re not ready to pay enterprise prices for capability you won’t use for years.
Your BOMs, revisions, and work orders are the real product. You want the system to keep up — not to bill you every time a workflow runs.
Pricing FAQs
Not publicly. Usage-based pricing only makes sense once we understand the rough shape of your operations — number of work orders per month, integration volume, AI usage. Schedule a call and we'll give you a real number, not a calculator-shaped guess.
Not directly. There's no per-seat license. But more users typically means more operations — more work orders created, more transactions, more automations — and that usage is what your plan covers. If your team grows but their throughput doesn't, your bill doesn't either.
A Resource Unit is the abstraction we use to bundle operational throughput — work orders, transactions, automation runs, API calls, integration events. Every plan includes a monthly RU allowance. If you go over, you see transparent overage pricing; if you under-use, the unused RUs don't roll forward.
Because AI can scale unpredictably. By keeping AI credits in a separate pool, we make sure that a runaway agent or a heavy month of analysis never silently eats the operational throughput you depend on. You can cap AI usage independently of your operational plan.
Overages are transparent and itemized. You can see exactly what was used. If you'd rather not exceed, set a hard tenant-configurable limit — the system will throttle or block instead of charging you.
Yes. Most customers start on the shared multi-tenant platform; some grow into a dedicated-resource enterprise option that gives them isolated infrastructure or a private region. The platform behaves the same either way.
NetSuite and SAP charge significant per-seat license fees plus six-figure implementation costs. Esvos charges a monthly platform fee that includes the connected platform and a transparent usage allowance. For most small and mid-size manufacturers, total cost of ownership is a small fraction of legacy ERP — without giving up real ERP capability.
Ready to talk numbers?
Tell us about your operations and we’ll put a real number in front of you — not a calculator-shaped guess.