We don’t publish a price list. The reason is honest: a per-seat number on a /pricing page would tell you the wrong thing about how oozmi is bought. The platform is the product, the modules are configurations of it, and the engagement is sized to the modules you turn on and the operation you run on top — not to the number of people who log in. The CEO reading this page should leave knowing the shape of the conversation. The 25-minute call fills in the numbers.
How pricing works
- Per module, not per seat. You license the modules your business uses — CRM, ERP, ecommerce, OMS, CMS, channels, PA, AI Builder, marketplace, workflows, ticketing. Headcount doesn’t drive cost: a finance team of three and a finance team of thirty pay the same for ERP. The platform is built so every employee has the no-code surface; that’s the point of the product, not a meter on the bill.
- Adopted incrementally. Most engagements start with one or two modules — typically the system you most want to replace plus one adjacent — and expand over time as the value clears. You don’t have to commit to the full suite on day one to get the unified-data benefit on day one.
- Implementation is co-built, not retainer-billed. First deployments are co-built with our engineering team in weeks, not quarters. We don’t run a services arm that earns more than the product. The configuration of your modules — the entity model, the workflows, the dashboards, the AI prompts — is part of the platform and is preserved through upgrades.
- Transparent at the platform level. On the quoting call, you see the breakdown: which modules, what scale assumption, what implementation scope, what support tier. No bundle obscures another bundle. If you remove a module, the line item disappears.
- Annual or multi-year terms. Standard terms are annual, with multi-year available where it makes sense. No hidden auto-renew penalties; renewal is the point at which you re-scope, not the point at which we lock you in.
What a typical engagement looks like
A first deployment typically combines one storefront-side module — usually ecommerce or CMS — with one system-of-record module — CRM or ERP — and adds OMS or channels where the operation needs them. The Laguna deployment, for context, is the full retail suite (ecommerce + CMS + ERP + CRM + OMS) with the AI Builder running on top; non-technical teams ship the changes there every day. Read the full Laguna story.
Implementation runs in weeks, not quarters. The pattern is co-build first, then autonomous operation: our engineers and your operators sit in the same Slack channel for the first phase, configure the modules against your real data, and hand over once the team is self-serving. From that point you own the platform. New modules added later follow the same pattern at a smaller scale.
What you’ll discuss on the call
The 25-minute quoting call is structured. The topics:
- Module mix. Which modules you want on day one, which you expect to add in year two.
- Scale of the operation. Orders per month, SKUs, users, channels — the numbers that drive sizing on the platform side.
- Implementation scope. What needs to come over from your current systems, what data lives where, what the migration shape looks like.
- Support tier. Standard or dedicated, and what your existing internal capacity covers.
- Timeline. When you want to be live and what blocks that — your decision cadence, our co-build availability.
You leave the call with a written quote that itemizes each of the above. No follow-up “to be priced separately” surprises.
What we won’t do
- No per-seat scaling. The CRM module costs the same whether ten or two hundred people use it. The platform is for everyone in the company; the price doesn’t punish you for that.
- No separate “AI add-on” tier. The AI is the platform. Agents read the same model the runtime reads. There is no version of oozmi without it, and no upcharge to turn it on.
- No mandatory training packages. We don’t sell certifications. Documentation is public, and the no-code surface is the training surface.
- No lock-in penalties. Your data, your model, your configurations are exportable. Annual terms end on annual terms.
- No quotes we won’t explain. If a number on your quote is bigger than you expected, we’ll show you the assumption that drives it. Pricing is a conversation, not a wall.
Get a quote
The fastest path is the demo request — most quoting calls run inside the same 30-minute walkthrough, because the modules in scope and the scale of the operation are the things we cover anyway. If you’d rather talk pricing first, the contact form routes to the same person.
For more on the platform itself, /platform is the right starting point. For asynchronous reading, see /resources — architecture brief, one-pager, and sandbox access.