Licence
The right to use and update GriotAI for the agreed team and environment.
Transparent project scope
The real price includes more than a model licence
A reliable estimate begins with users, data volume, integrations, hardware and expected support—not with a generic token price.
Direct answer
GriotAI is scoped from the number of users and the deployment context. Hardware, data preparation, connectors, migration and support are separated so that the customer can see which costs are one-off, recurring or dependent on usage.
The six cost components
Hardware
Existing or dedicated equipment sized from measured corpus and workload needs.
Data preparation
Cleaning, ownership, access rules and removal of obsolete versions.
Integrations
Microsoft 365, Odoo or other systems, including account and permission setup.
Deployment
Installation, security configuration, tests and initial user training.
Operations
Monitoring, backups, updates, evaluation and support over time.
How to obtain a meaningful estimate
- Name the first process and its owner.
- Count active users rather than the whole organisation by default.
- Estimate documents, formats, growth and update frequency.
- List integrations and the permissions they require.
- Measure current time, errors or delays to establish a baseline.
- Distinguish pilot, production and wider rollout costs.
Avoid false precision
A public price without corpus size, hardware, integration effort or service level can be misleading. The estimate should record its assumptions and identify which elements can change.
The cost page therefore explains the structure rather than inventing a universal figure. A proposal follows a short technical and business scoping step.
Frequently asked questions
Is hardware always included?
No. Existing equipment may be suitable, or dedicated hardware may be recommended after measurement. The proposal should state this explicitly.
Can the project begin with a pilot?
Yes. A bounded pilot is the preferred way to validate sources, performance and business value before expanding the scope.
Continue exploring
Start with one measurable process
Choose one use case, a controlled document set and a result that your team can verify.
Request a demo