Sage 100 and Sage 300 AI Assistant Sizing and Value Calculator
Estimate GPUs, index size and value for a private AI assistant on Sage 100 or Sage 300. Smaller sites often need very little hardware, and this calculator shows how little. It uses plain formulas you can check and change.
Your numbers
Share of named users who ask the assistant something on a given day.
Includes retrieved context. Short SQL answers run lower; document questions run higher.
Time the user would otherwise spend finding the answer. Measure it in a pilot.
Amortised hardware plus power and hosting per GPU, or the monthly rate for private cloud GPUs.
Aggregate throughput with batching for your chosen model and quantization. Measure with vLLM on your hardware.
Your results
Planning model. Formulas: questions/day = users x active share x questions each; tokens/day = questions x tokens; GPUs = ceil(peak-hour tokens per second / tokens per second per GPU); value = questions/day x 22 working days x minutes saved / 60 x hourly cost. The 20% peak-hour share and 20 second request time are fixed assumptions. Validate throughput with your own model and prompts.
Monthly value vs named users
Sweeps Named Sage 100 and Sage 300 users from 10 to 600, holding your other inputs fixed.
Validate my sizing
Optional: have the numbers checked with a measured pilot on your hardware. The calculator works fully without it.
Optional. The tool and every export work without this. No spam.
How to use it
Enter the number of named Sage 100 and Sage 300 users and the share who use the assistant daily. Add questions per active user, average tokens per question, documents and pages for the index, minutes saved, loaded hourly cost and GPU monthly cost. The tokens per second per GPU input is the most important assumption, so replace the default with a number from a test on your hardware.
- Start with a pilot group size and read hours saved.
- Raise tokens per question if you use long documents.
- Use the chart to see how demand scales with users or usage.
The method behind it
Daily tokens are questions times tokens per question. Peak load assumes 20% of daily questions land in the busiest hour, converted to tokens per second and divided by per-GPU throughput. Concurrency uses the same arrival rate times a 20 second request time. Index size assumes about three chunks per page, each around 9 KB for text and vectors. Value is minutes saved converted to hours, times 22 working days and hourly cost.
How to read the result
Typical Sage 100 and 300 questions cover customer balances, open orders, item availability by warehouse and purchase receipts, so answers are short and context windows are modest. If the GPU count is one, plan a second for resilience once the assistant is relied on. If payback days exceed 30, either the usage is low, the time saved is small, or the hardware is oversized for the load.
Common mistakes
Counting named users as active users, ignoring retrieved context in the token count, trusting vendor throughput numbers for a different model, and claiming time saved without a pilot measurement. Another is forgetting that model quality, not just speed, decides whether people keep using the tool. Treat value as a hypothesis until a pilot confirms it.
Frequently Asked Questions
Why is tokens per second per GPU an input?
It depends on the model, quantization, context length and batching. Public numbers rarely match your workload, so measure with vLLM on your hardware and enter the sustained figure.
Does the GPU estimate include redundancy?
No. It is the minimum for peak-hour load. For a production assistant, add at least one spare GPU or a failover plan.
How reliable is the value figure?
It is only as good as minutes saved per question. Measure that in a pilot by timing a sample of tasks with and without the assistant.
What does the index size include?
An estimate of text chunks and vectors for the documents you enter. It excludes the ERP database copy, which is sized separately by your DBA.
Want these numbers tested against your real Sage 100 and Sage 300 data and prompts? Netray can run a measured pilot on your own GPUs and report throughput and accuracy.
Related Tools
Sage 100 and Sage 300 Private AI Layer Blueprint Generator
Generate an architecture plan for a private AI assistant on on-prem Sage 100 or Sage 300: reporting copy or ODBC extract, Web API or BOI, retrieval, local GPU model and audit.
On-Prem AIOn-Prem GPU Sizing Calculator for ERP AI
Work out how much GPU memory and how many cards you need to serve an open-weight model to your ERP users on-prem.
On-Prem AIvLLM Throughput Estimator
Estimate aggregate tokens-per-second throughput for a vLLM deployment from model size, GPU class, and batch depth, accounting for continuous batching gains.
On-Prem AIOn-Prem AI ROI Calculator
Turn hours saved per employee into annual net benefit, payback months, and 3-year ROI for an on-prem AI investment.
More Other ERPs tools
See all- Infor VISUAL Work Order Status and Structure Reference
- Infor VISUAL Manufacturing Scheduling Checklist
- Infor XA (MAPICS) Period End Close Checklist
- Infor VISUAL Database Table Reference
- Infor XA (MAPICS) Application Module Reference
- IBM i Commands for Infor XA Administrators Reference
- Acumatica Generic Inquiry Design Template
- Acumatica Manufacturing Edition Setup Checklist
- Sage X3 Import Template Worksheet
Keep exploring
Free tools
- Sage 100 and Sage 300 Private AI Layer Blueprint GeneratorGenerate an architecture plan for a private AI assistant on on-prem Sage 100 or Sage 300: reporting copy or ODBC extract, Web API or BOI, retrieval, local GPU model and audit.
- Sage 300 Database Table ReferenceA quick lookup of well-known Sage 300 SQL table names, the module they belong to and what each stores, for reports and integrations.
- Sage X3 AI Assistant Sizing and Value CalculatorSize GPUs and estimate value for a private AI assistant on Sage X3. Enter named users, usage and cost assumptions to get concurrency, tokens per day, index size and payback.
ERP fixes and how-tos
- How to Add AI to Sage 100 and Sage 300 On-PremPrivate AI architecture for on-prem Sage 100 and Sage 300: ODBC or SQL extracts, Sage 300 Web API, Sage 100 BOI, local GPU model, permissions and audit log.
- How to Add User Defined Fields (UDFs) in Sage 100How to add a user defined field in Sage 100 with Custom Office, place it on a panel, and expose it to reports, ODBC and imports, with the usual UDF pitfalls.
- Fix Sage 100 SOTAMAS90 ODBC Connection ErrorsFix Sage 100 ODBC failures on the SOTAMAS90 DSN: 32-bit versus 64-bit driver mismatch, wrong company code, path rights, and external access security.
AI on your ERP
- AI for Sage 300, Built for Multi-Entity ManufacturersGround a private LLM on Sage 300 (Accpac) financial and operations data. On-prem AI for multi-currency, multi-entity manufacturers without a public API.
- AI for Sage 100, Grounded in Your MAS90/200 DataPut AI on Sage 100 and the Sage 100 Manufacturing (MRP) data set without sending data to a public model. Private LLMs and agents grounded in your MAS90/200 tables.
Integrations
- How to use ChatGPT with Sage 100How to use ChatGPT with Sage 100: exports versus live access, custom GPT actions, enterprise data controls, and when a private model is the safer choice.
- How to use Claude with Sage 100How to use Claude with Sage 100 through an MCP connector, the Anthropic API, Bedrock or Vertex, and what to do when the data must stay on-prem.