Dynamics GP AI Assistant Sizing and Value Calculator
Small and mid-size GP sites rarely need large GPU clusters. This calculator shows what a private AI assistant needs for your user count and question volume, and what time saved is worth against the cost.
Your numbers
Lower default for a 24 GB class card running a mid-size quantised model. Measure yours.
Your results
Estimate for planning. Measure real throughput, include redundancy and confirm time savings with a pilot before committing budget.
Peak concurrent requests vs named users
Sweeps Named GP users from 10 to 500, holding your other inputs fixed.
Get a sizing review for your GP estate
Optional: share your inputs and we will check GPU count, index design and rollout assumptions.
Optional. The tool and every export work without this. No spam.
How to use it
Enter named GP users and the portion who will use the assistant daily; finance teams often have higher usage than the rest. Count questions per user based on current requests for reports and lookups. Set tokens per question higher if you plan to summarise documents. Use a measured throughput from your own GPU.
- Finance users usually ask more
- Keep minutes saved conservative
- Compare one and two GPU scenarios
- Include the build cost for payback
The formulas
Questions per day equal active users times questions each. Peak concurrency equals 20% of daily questions divided by 3600 and multiplied by 20 seconds of processing per request, an application of Little's law. GPUs equal peak tokens per second divided by GPU throughput, rounded up. Monthly value equals hours saved times hourly cost with 22 working days.
Reading the result
At GP scale the GPU count is often one, and concurrency is a handful of requests. That means latency and quality matter more than raw capacity. If value is marginal, test whether SmartList, SSRS or Power BI already covers the highest volume questions before building anything.
Frequently Asked Questions
Why show peak concurrency?
It tells you how many requests overlap at the busiest moment, which drives latency. Even small teams can see a handful of overlapping requests.
Is a 24 GB GPU enough?
For a small team and a quantised mid-size model, often yes. Quality needs and context length decide, so run your own test questions.
What does the chart show?
Peak concurrent requests as named users grow, with other inputs fixed. Use it to see when you might need a second GPU.
Does it include power and cooling?
Only if you include them in the GPU monthly cost. Enter an all-in amortised figure for a fair comparison.
If you want a second pair of eyes on these numbers for your GP estate, Netray can review the inputs with your IT team.
Related Tools
Dynamics GP Private AI Layer Blueprint Generator
Enter your GP environment and get a plan for a private AI assistant: curated views, tool server, model serving, controls and rollout.
On-Prem AIGPU Sizing Calculator for LLM Inference
Work out how many GPUs you need to serve a given open-weight model to your user base, based on memory footprint and token throughput.
On-Prem AIOn-Prem LLM Total Cost of Ownership Calculator
Model the full multi-year cost of running LLMs on your own hardware, including GPU capex, power, cooling, support contracts, and operations staffing.
Microsoft DynamicsDynamics GP Unsupported Risk Exposure Calculator
Adds up support fees, compensating controls, manual workarounds and expected incident loss to show what another year on Dynamics GP really costs.
More On-Prem AI tools
See allKeep exploring
Free tools
- Dynamics NAV AI Assistant Sizing and Value CalculatorWork out the GPUs, index size and monthly value of a private AI assistant on NAV from your users and question volume.
- Dynamics GP Private AI Layer Blueprint GeneratorEnter your GP environment and get a plan for a private AI assistant: curated views, tool server, model serving, controls and rollout.
- Business Central On-Prem AI Assistant Sizing and Value CalculatorSize GPUs, index and monthly value for a private AI assistant on Business Central on-prem from user and question volumes.
ERP fixes and how-tos
- Adding a Private AI Layer to Dynamics GP On-PremAdd AI to Dynamics GP on-prem without cloud: curated SQL views, eConnect for writes, retrieval index, local LLM, mirrored GP security, approved write-back.
- Dynamics GP POP Tables: Purchase Order Processing Reference and Sample SQLReference for Dynamics GP Purchase Order Processing tables: POP10100, POP10110, POP30100, POP30110, receipt tables, key joins and sample SQL queries.
Integrations
- How to use ChatGPT with Microsoft Dynamics GPConnect ChatGPT to Dynamics GP safely: export versus live access, custom GPT actions over an API gateway, enterprise data controls, and when to go private.
- How to add an AI chatbot to Microsoft Dynamics GPAdd an AI chatbot to Dynamics GP for staff or customers: grounded in SQL data and documents, role aware, hosted on-prem with open models, with honest trade-offs.