On-Prem AIFree calculatorPDF, Excel, Word exportMicrosoft Dynamics 365 Business Central (on-premises)

Business Central On-Prem AI Assistant Sizing and Value Calculator

This calculator estimates the hardware and value of a private AI assistant on Business Central on-premises. Enter users and question volume, and it returns GPUs, tokens, index size, hours saved and payback.

Your numbers

users
30 %
questions
tokens

API results and retrieved passages add to the prompt.

documents
pages
min
per hour
per GPU
tokens/s
one-time

Your results

GPUs needed (before redundancy)
1
Monthly net value after GPU cost
$25,478
Daily active users
36
Questions per day
432
Tokens per day
1,728,000
Peak concurrent requests
0.48
Retrieval index size
4.4237
Hours saved per month
634 hrs
Monthly value of time saved
$27,878
Simple payback
2.2 months

Planning estimate. Measure throughput on your hardware, plan redundancy and validate time savings with a pilot.

Save results:

Monthly net value vs questions per active user

Sweeps Questions per active user per day from 2 to 50, holding your other inputs fixed.

Get a sizing review for your Business Central estate

Optional: share your inputs and we will check GPU count and rollout assumptions.

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

How to use it

Start with named users and the share who will use the assistant on a typical day. Questions per user depends on how often people look up orders, items and balances. Because API results are added to the prompt, tokens per question often run higher than for plain chat. Replace the default throughput with a measured value from your model and card.

  • Use pilot data when you have it
  • Raise tokens for document questions
  • Compare one-GPU and two-GPU outcomes
  • Keep the 22-day month in mind

The formulas

Questions per day equal active users times questions each. Peak tokens per second equal 20% of daily questions times tokens per question divided by 3600. GPUs equal that figure divided by throughput per GPU, rounded up. Index size equals pages times two chunks times 4096 bytes with 50% overhead. Net value equals hours saved times hourly cost minus GPU cost.

Reading the result

Look at the chart to see how value moves with usage: it rises with questions until a GPU step adds cost. If net value stays low, consider whether built-in reports and search cover the same questions. Payback shows how quickly the one-time build is recovered at the chosen inputs.

Frequently Asked Questions

Does API use change the sizing?

It affects tokens, because returned records are added to the prompt, and it adds load on the server instance. Keep result sets small and filtered.

Why does the value chart have steps?

GPU count is a whole number, so cost jumps when load crosses a capacity limit. The net value line shows those jumps as dips.

What default throughput is realistic?

It varies widely by model, quantisation and card. The default is a placeholder for planning; measure your own.

Is the index size the full storage need?

No. It covers vectors and metadata only. Keep the original documents and logs in your capacity plan too.

If you want these inputs tested against your Business Central environment, Netray can run a short sizing review with your IT team.

Keep exploring

Free tools

ERP fixes and how-tos

AI on your ERP

Integrations

Comparisons

Software