Morsa is priced on the value it creates in your plant, not per user and not per module. We run a pilot on one live problem or one line to show you the value Morsa can create, measured in your own numbers, and we take a share of that value as our fee. If the pilot shows no value, there is no fee. There is no public price list and no seat count. The share, and how the value is measured, are agreed on the call. Our promise: we make you a lot of money, or we pay you for your time.
On this page
How does value-based pricing work at Morsa?
How is the value measured?
Why not per seat?
What does the pilot cost, and what is the promise?
What does the pilot involve?
What drives the value after the pilot?
What is included?
What is not included?
How does this compare with what a plant already pays for software?
When is Morsa not worth it?
What happens on the call?
Sources, Changelog
How does value-based pricing work at Morsa?
Three steps, in order.
A pilot on one live problem. Usually material availability and supplier recovery on one line, because that is where a plant loses the most, fastest. Morsa, the AI that operates the factory for you, joins the group chats the plant already runs, reads the ERP and the other systems, and starts catching and closing work. J4S went from first connection to live actions in two days.
The value, in your numbers. During the pilot we count what Morsa caught, chased and closed, against what the plant was doing before, using measures the plant already trusts. At J4S, a 120-person glass plant, on-time completion of operational commitments rose from about 30% to about 75% in the first four weeks, across about 900 commitments.
A share of that value. Morsa’s fee after the pilot is a share of the value it created, agreed with you once the pilot numbers are in. Not a license, not a seat count, not a module list. If the pilot shows no value, there is no fee.
How is the value measured?
In the plant’s own numbers, chosen with you before the pilot starts so nobody argues about them after. The rule is simple: Morsa either saves the plant a lot of money or makes it a lot of money, through the specialized agents it runs for purchasing, planning, production, quality and maintenance. Which number that shows up in depends on the plant. Three examples of measures plants use:
Measure | What it counts | Where it comes from |
|---|---|---|
Commitments closed on time | Promises made in the plant’s groups and systems that were met by their date, with proof | Morsa’s record of every commitment, owner, date and closing evidence |
Shortages caught before they stopped a line | Material, supplier and plan changes connected to the orders they affected and acted on before the date | The ERP’s orders and receipts, the group chats, and the jobs Morsa opened and closed |
Hours not spent chasing | Time managers and planners no longer spend reconstructing yesterday and following up across departments | The plant’s own estimate before the pilot, checked against Morsa’s record of who was chased, when, and by whom |
Other plants measure customer deliveries not missed, expedites and premium freight avoided, rework backlog cleared, output from the same people and machines, or whatever the pilot’s problem costs them today. The only requirement is that the measure is one the plant already believes, taken from records it already keeps. The measure and the share are agreed on the call. Sunil K Verma, Plant Head at J4S: “I used to spend the first hour of every morning reconstructing yesterday. Now the chasing happens in the WhatsApp groups my supervisors already use, whether or not I remember.”
Why not per seat?
Because nobody in the plant installs an app or learns a dashboard. A supervisor on the night shift, a stores in-charge, a purchasing head and a dispatch planner all “use” Morsa without a login. Charging per user would mean either counting people who never see a screen or pushing plants to keep people out of the loop, which is the opposite of the point. Production Head Anil Kohli at J4S: “Our people don’t have to learn any new software. The chasing happens in the group chats they already use.”
Value-based pricing also lines our interest up with yours. Morsa earns more only when the plant closes more commitments on time and stops fewer lines.
What does the pilot cost, and what is the promise?
The pilot is free when no implementation work is needed, which is the usual case: Morsa joins the groups the plant already runs and reads the systems it already has. Where implementation work is needed, for example a connection that has to be built to a system with no API, there is a minimal implementation cost, and it is refunded if the pilot shows no value. The pilot’s length is set on the call for the line or problem chosen.
The promise: we make you a lot of money, or we pay you for your time. The pilot starts on one live line or one workflow. Morsa reads the systems and the groups, and when material, a supplier or a plan moves off what was promised, it connects the change to the orders it affects, tells the owner, and chases until the fix is proven. At JRG Automotive, an automotive and plastic body-parts manufacturer serving OEMs, Morsa identified 5 of 8 production-stopping material shortages early enough to act, and saved the plant $2 million. The 3 it did not catch in time are how the plant’s rules got better.
What does the pilot involve?
Four steps, and the first plant did the whole setup in two days.
Step | What happens | What you see |
|---|---|---|
1. Connect | Morsa reads the plant’s systems and one live workflow: the ERP, the MES if there is one, and the groups the plant already uses, whatever it runs on | Morsa reading, not writing |
2. Configure | Owners, rules and approval boundaries are mapped, and the pilot’s value measures are agreed. Configuration, not bespoke code | A rule set your managers have signed, and the numbers we will both count |
3. Shadow (optional) | Morsa runs the full loop without consequential actions, and its understanding is compared with the plant’s | A daily comparison of what it saw against what the team saw |
4. Live | Approved actions and verification are turned on for the pilot scope | Commitments with owners, dates and proof; misses reported; the value measures updated as the pilot runs |
At J4S, Connect, Configure and Live took two days: Morsa joined the Production, Stores, Purchase and Dispatch groups and connected to the ERP on day one, and the four weeks in which results were measured started at go-live. No migration, no training program, no rollout.
What drives the value after the pilot?
The share is agreed on the value, so the fee moves with the value. Three things move how much value there is to share, and we ask about each on the call.
Driver | What we ask | Why it moves the value |
|---|---|---|
Plant size | How many people, lines and shifts; roughly how many jobs and commitments a week | More people and lines mean more commitments to close, more shortages to catch, and more hours not spent chasing |
Systems connected | Which ERP or MRP; whether there is an MES, CMMS, QMS or WMS; which group chats and email the plant runs on; whether machines, PLCs or sensors are in scope | Each connected system is another place Morsa can read a change early and act on it |
Deployment model | Morsa’s cloud, your private cloud, or fully on-premise with the AI models and databases inside your perimeter | On-premise means we run the whole stack on your hardware, which is the right answer under ITAR, CMMC or a strict IT policy, and it is a cost we account for in the agreed share |
Two things do not move it: the number of people who message in the groups, and the number of channels. WhatsApp, Microsoft Teams, email and SMS are examples of what a plant runs on, not tiers.
What is included?
The pilot on one line or workflow, free where no implementation work is needed, with the value measures agreed and counted
The connections to the systems in scope, built and maintained by us
Morsa’s presence in the plant’s groups and email, in whatever channels the plant already uses
The full loop on every signal in scope: read, connect to the plant’s state, work out the consequence, decide within approved rules, act across systems and people, verify on proof
Chasing and escalation before due dates, up the reporting line the plant defines
Shift handovers and daily reviews with carry-overs, open jobs and blockers already listed
Plan versus reality: the demand plan, production plan, schedule and dispatch record compared continuously
Reliability tracking for people and vendors: promises made against dates met, who moved dates, who goes quiet
Plain-English questions about orders, inventory, jobs and people, answered from the connected systems
Onboarding, configuration changes as rules evolve, and support
What is not included?
Licenses for the systems Morsa connects to. Your ERP, MES and other systems stay yours and stay the record. Morsa does not replace any of them.
Hardware for an on-premise deployment, which you provide to a specification we agree
Custom software development beyond the pilot’s implementation work. Morsa is configured per plant, not rebuilt. If a plant needs code written, we say so before the pilot, not after.
How does this compare with what a plant already pays for software?
Most plant software is priced per user or per interface, before any value is shown. The figures below are from each vendor’s own pricing page and are here so the call starts from facts, not so they can be compared line for line with a share of value.
Microsoft Dynamics 365 Business Central
How it is priced: Per user per month, paid yearly
Published figure: Essentials $80, Premium $110
Read on: 19 September 2026, MES vs ERP
Odoo
How it is priced: Per user per month, yearly term
Published figure: Standard $24.90 billed yearly or $31.10 billed monthly, Custom $49.00 yearly or $61.10 monthly (list $31.10 and $38.90, $61.00 and $76.20); the discount “is valid for 12 months, for initial users ordered”
Read on: 21 September 2026, Odoo pricing
MRPeasy
How it is priced: Per user per month
Published figure: $49 to $149 across four plans, “From the 11th user $79 per 10 users”
Read on: 20 September 2026, MRPeasy pricing
Katana
How it is priced: Per month, plus add-ons
Published figure: Core “Starts at $299/month”; Manufacturing Management add-on “$199 / mo”
Read on: 20 September 2026, Katana pricing
Tulip
How it is priced: Per interface per month, billed annually, ten minimum
Published figure: Essentials $100, Professional $250
Read on: 20 September 2026, Tulip pricing
Rasset
How it is priced: Per factory per month, annual
Published figure: From $199; Professional $799; Enterprise “$5,000+”
Read on: 20 September 2026, Rasset pricing
SAP Business One
How it is priced: Through partners; no list price found
Published figure: “Available exclusively through SAP partners”
Read on: 20 September 2026, SAP solution brief
The larger cost is rarely the license. Panorama Consulting’s 2026 ERP Report, based on 170 organizations, found the median ERP project ran nine months and that “more than a quarter of organizations reported that their project was over budget” (verified 19 September 2026 on manufacturing ERP software). Morsa’s pilot is measured in days because it changes no system and trains no one, and its fee is measured after the value, not before.
When is Morsa not worth it?
Three cases, so the call is short.
One line, one shift, one planner who sees everything. If the whole plant fits in one person’s head, there is no coordination gap to close and no value for a pilot to measure. Rockwell Automation’s July 2026 survey of 1,560 manufacturers found 44% rank integration as their top MES buying requirement (Rockwell Automation); a plant that small does not have the integration problem yet.
No system of record at all. Morsa reads an ERP or MRP. If orders, stock and purchase orders live only in a notebook, buy the record first. The options are compared on manufacturing ERP software.
The pain is a machine, not a decision. If the cost last quarter was a bearing or a press, machine-health tools are the answer, and they are scored on best AI software for manufacturing operations.
What happens on the call?
Fifteen minutes. You bring one problem from the last month: a shortage, a slipped delivery, a line behind plan. We show you, step by step, how Morsa would have caught it using the systems and channels your plant already runs on. Then we agree the pilot: which line or workflow, how long it runs, which numbers we will both count, and whether any implementation work is needed. The share of value comes after the pilot, when the numbers are in. No slides.
Bring one problem from your plant. We’ll show you how Morsa would have caught it. Book the call with Vedant.
Sources
Odoo, pricing, https://www.odoo.com/pricing (fetched 20 September 2026)
MRPeasy, pricing, https://www.mrpeasy.com/pricing/ (fetched 20 September 2026)
Katana, pricing, https://katanamrp.com/pricing/ (fetched 20 September 2026)
Tulip, pricing, https://tulip.co/pricing/ (fetched 20 September 2026)
Rasset, pricing, https://rasset.ai/pricing (fetched 20 September 2026)
SAP, Introduction to SAP Business One solution brief, 2024 (fetched 20 September 2026)
Microsoft, Business Central pricing, https://www.microsoft.com/en-us/dynamics-365/products/business-central/pricing (verified 19 September 2026 for the MES vs ERP rewrite)
Panorama Consulting Group, The 2026 ERP Report (verified 19 September 2026; the report landing page returned no content on 20 September 2026)
Rockwell Automation, 93% of Manufacturers Have MES, But Only 23% Have Fully Integrated It, 14 July 2026 (fetched 20 September 2026)
Morsa, J4S customer story, /customers/j4s
Changelog
21 September 2026: Odoo prices corrected. Its published ladder moved up a step to Standard $31.10 per user per month against a $38.90 list and Custom $61.00 against a $76.20 list, replacing the $24.90 and $49.00 figures read on 20 September 2026; the vendor page was re-read on 21 September 2026.
21 September 2026: third draft, final. Pilot cost stated (free where no implementation work is needed; a minimal implementation cost where it is, refunded if the pilot shows no value); pilot length set on the call; value measures stated as examples with the rule that Morsa saves the plant a lot of money or makes it a lot of money; all bracketed decisions removed.
21 September 2026: second draft. Rewritten around value-based pricing: a pilot proves the value in the plant’s own numbers and Morsa’s fee is a share of it, agreed after the pilot. No percentage and no dollar figure stated.
21 September 2026: first draft. Per-plant model, drivers, guarantee, onboarding and inclusions.
24 September 2026: replaced the shortage guarantee with the current promise, we make you a lot of money, or we pay you for your time. Corrected Odoo’s prices: $31.10 is Odoo’s monthly-billing Standard price; billed yearly it is $24.90.
