Knowledge sources
The number, type and quality of guides, PDFs, pages and media text, and how often they must be refreshed.
Pricing
Start with a defined scope. Build on what the pilot shows.
Pricing follows the sources you want connected, the investor journeys you want supported and the governance your team needs, not an arbitrary per-user chatbot fee.
- 01Evaluate a bounded pilot
Test answer quality, source traceability and learning with a focused set of content.
- 02Agree implementation and licensing scope
Confirm sources, deployment model, controls and the licensing that fits.
- 03Operate and expand with support
Run it with agreed support, and add sources and journeys as the pilot shows value.
What affects your price
Four things shape the scope.
Connected capabilities
Source adapters, public-register checks, and any separately scoped reporting integration.
Deployment and controls
Managed versus regulator-controlled operation, security and approval requirements, and a data-location review.
Usage and ongoing support
AI usage, agreed support hours, maintenance and change-management requirements.
We separate initial setup, any agreed licensing and usage, and ongoing support so your team can see the full commitment. Not every driver applies to a small pilot, and pilot timing and fees are agreed after discovery.
Prefer to talk it through?
If it’s easier, choose a time and we’ll walk through scope and pricing together.