What is the practical answer?
A chatbot quote is easier to judge when you know what the assistant is expected to do. Answering questions from a small set of approved pages is a different project from looking up bookings, changing records or supporting several customer channels.
Start with a useful, specific job
Write down the questions customers repeat and the next step you want the assistant to help with. For a service business, that might be explaining an offering and directing someone to an inquiry form. For an appointment business, it might mean helping someone find the booking page.
Describe what the assistant should leave to a person too. A clear handoff is part of the scope. It gives the customer somewhere to go when the information is missing or their request needs a decision.
Separate the build from the running costs
The initial project can include interface design, knowledge preparation, website integration, evaluation and launch. Ongoing costs can include model usage, hosting, connected tools, monitoring and agreed support. Ask for those categories separately so you can see which costs change with usage.
- The source material: approved pages, FAQs and business documents
- The channels: one website or several places where customers ask questions
- The integrations: links to existing tools or actions through their APIs
- The expected use: conversation volume, message length and stored history
- The upkeep: who approves new information and investigates a poor answer
An integration changes the work
Sharing a link to your booking page is a small, clear interaction. Reading availability or making a booking adds access rules, validation and failure handling. The same distinction applies to a CRM: collecting an inquiry is different from changing an existing customer record.
Bring the names of the systems you already use. We need to check what their supported APIs allow and what access the project will require. A useful proposal states these dependencies before promising a connected workflow.
Ask how answers will be checked
Prepare representative customer questions, including unclear wording and requests the assistant should hand over. Check whether answers stay within the approved source information and whether links lead to the correct service or action.
Keep the evaluation after launch practical. Review unanswered questions, incorrect answers, handoffs and whether the conversation leads to a useful inquiry. A low running cost does not make an assistant useful if people still cannot get the help they came for.
Send enough detail for a meaningful quote
Send your website, the questions you want covered, the systems the chatbot would need to connect and an estimate of likely use. Tell us who will approve the answers and maintain the information. We can then separate an initial release from features that can wait.
Melos scopes custom AI chatbot projects for businesses throughout the United States. Your location helps us plan review times; the quote follows the actual work, integrations and support requirements.
