On-Prem AIFree calculatorPDF, Excel, Word exportOdoo

Self-Hosted Odoo AI Assistant Sizing and Value Calculator

This free calculator estimates GPU count, token load, attachment index size, hours saved and payback for a private AI assistant on self-hosted Odoo. Use the chart to see how cost and value change with user count.

Your numbers

users

Licensed or named Self-Hosted Odoo users who could use the assistant.

45 %

Percent of named users who ask at least one question per day.

questions
tokens

Include retrieved context. Typical range 1000 to 3000.

documents
pages
minutes

Measure in a pilot; this is the most uncertain input.

per hour
per GPU per month

Amortised purchase plus power, space and support, or a private cloud rate.

tokens/s

Assumption: depends on model, quantisation and batching. Measure on your hardware.

once

Integration, indexing, testing and rollout effort.

Your results

GPUs needed
1
Larger of the GPUs needed to hold the model and load divided by throughput per GPU.
Net monthly value
$6,984
Active users per day
36
Questions per day
288
Tokens per day
518,400
Questions per day times average tokens per question.
Peak concurrent requests
1
Assumes 25% of daily questions in the busiest hour and 20 seconds per answer.
Peak load
40
Tokens per second: the larger of 40 tokens/s per concurrent stream and busy-hour token volume.
GPUs with a standby replica
2
Adds one more model replica for resilience.
Vector index size
1.44
GB, assuming 2 chunks per page and about 6 KB per chunk including vectors and metadata.
Hours saved per month
302 hrs
21 working days per month.
Monthly value
$10,584
Monthly GPU cost (with standby)
$3,600
Simple payback
5 months
Setup cost divided by net monthly value. Zero means value does not cover running cost.

Planning estimate. Throughput, minutes saved and token counts vary widely; measure them in a pilot before committing budget.

Save results:

Monthly value vs GPU cost by named users

Sweeps Named users from 10 to 1000, holding your other inputs fixed.

Optional Odoo pilot scoping

We can help turn these estimates into a measured pilot on your Odoo data.

Optional. The tool and every export work without this. No spam.

How to use the calculator

Enter Odoo named users and the share that use the assistant each day, plus questions per active user and tokens per question and answer. Add the attachments you plan to index and their average pages, then minutes saved, loaded hourly cost, the monthly GPU cost and a one-time setup cost. Outputs show peak concurrency, GPUs with a standby, index size, hours saved and payback.

Formulas and assumptions

Active users are named users times the active share. Daily questions multiply by questions per user. The busiest hour is assumed to carry 25 percent of daily questions at 20 seconds per answer. Load is the larger of concurrency times 40 tokens per second and busy-hour tokens per second. GPUs are the larger of the model requirement and load over throughput per GPU, and the standby adds one model replica. Index size is 2 chunks per page at about 6 KB. A month is 21 working days. API call load on Odoo is not included.

Reading the result

Odoo sites are often small enough that one GPU covers load, so cost is dominated by setup and attachment indexing. The value depends on minutes saved per answer, which you should measure on real tasks. If payback is zero, value is below running cost for these inputs. Try fewer GPUs, a smaller model or a narrower scope.

Frequently Asked Questions

Does the Odoo server need extra capacity?

Assistant calls become extra API requests. For modest use this is small, but heavy search_read calls on large tables can matter, so limit fields and rows and consider a replica for aggregates.

How many attachments should I index?

Start with documents users actually search, such as vendor quotes, certificates and work instructions. Index size is small compared with model memory, but ingestion time grows with volume.

What throughput per GPU is realistic?

Aggregate throughput depends on model size, quantisation and batching. A range of 800 to 2500 tokens per second is common for mid-size models; measure on your hardware.

Can I compare scenarios?

Yes. Change users, questions per day or minutes saved and watch the outputs and chart update. Export the result to share with finance.

If you want these estimates checked against your Odoo usage, Netray can help scope a pilot. The calculator is free and needs no contact.

Keep exploring

Free tools

ERP fixes and how-tos

AI on your ERP

Integrations

Software