Compare the complete cost of an accepted and maintained journey, with usage assumptions clearly identified.
Design and installation
This work includes business scoping, information preparation, conversation rules, interfaces, connections and acceptance checks. It depends on existing tools, data quality and the selected actions.
Ask which deliverables are included, what you must provide and how acceptance will be established. A prototype, an internal installation and a public service have different scopes.
Usage and third-party services
Depending on the architecture, usage may involve telephony, transcription, a conversation model, speech synthesis, messaging and hosting. Providers and their terms should appear in the proposal. This guide establishes no universal price per call.
- Relevant channels, languages and countries.
- Expected conversation volume and duration.
- Simultaneous sessions and opening hours.
- Limits, alerts and behaviour at the limit.
Maintenance and changes
Technical maintenance covers agreed operations after installation: monitoring, corrections, updates and component follow-up. Human handling of enquiries and updates to your business information also need an owner.
Adding a channel, integration or action may change the scope. Separate these changes from corrections included in the agreement, rather than assuming a subscription covers everything.
Compare proposals on useful grounds
Relate the budget to the journey actually accepted: the need addressed, answer quality, receipt of the action and work left for the team. Time savings or cost reductions still need measurement in your context.
To scope the project, prepare an example enquiry, your current tools and a usage estimate if available. We will identify unknowns and checks needed before preparing a quote.
Your next step
A need. A scope to define.
The first discussion clarifies your enquiry, the tools to connect and the intended outcome before proposing a delivery.
Prepare my project scope