AI Chatbot Proposal Template
For developers quoting a business that wants to answer its own customers automatically and overestimates how much usable documentation it has.
- Who it is for
- AI developers
- Ideal client
- A business answering the same questions all day
- Category
- AI & Automation
- Packages
- 3
The hardest part of a chatbot project is not the bot. It is the documentation it gets trained on, and almost every client overestimates how much of theirs exists in a usable state.
What the client reads
The scope
This is the wording the template arrives with. Yours replaces it.
The packages
3 to choose from
The client picks one, and the one they pick is the one they approve and pay on.
FAQ Bot
Knowledge-base bot
A$1,500
1 week
- Train on your docs/FAQ
- Website widget
- Up to 100 pages ingested
- Basic analytics
- 30-day support
Smart Assistant
AI-powered assistant
A$4,000
3-4 weeks
- Advanced NLP
- CRM integration
- Human handoff
- Multi-language
- Analytics dashboard
- Custom personality
- 60-day support
Enterprise Bot
Full AI solution
A$10,000
6-8 weeks
- Custom model fine-tuning
- Multi-channel (web, Slack, email)
- Advanced integrations
- Sentiment analysis
- Conversation analytics
- A/B testing
- SLA & uptime guarantees
- 90-day support
The whole thing, live
The page your client opens
Not a screenshot. This is the real client page running on an invented deal. Pick a package and press approve to see what your client would see; nothing is sent or charged.
How it gets paid
Deposit, then balance
40% is due when the client approves, and the balance when you mark the work delivered. Both payments happen on the same link the proposal is on.
Card or bank transfer, and you choose which per deal. If you want a package to bill every month instead of once, you set that on the package itself when you build the deal, and the client can cancel it from their own link.
Prices are a starting point in Australian dollars. Change the figures, the inclusions and the number of packages to suit what you sell.
The starting terms
What approving the page records
These sit above the approve button. The client reads them, and approving records that they accepted them.
These terms cover the package you approve on this page.
- Scope. The work is the package described above. Anything outside it is quoted separately before it starts.
- Payment. The deposit shown on this page is paid on approval and the balance when the work is delivered.
- Third party costs. Model usage, API credits, software subscriptions and platform fees are yours and are not included in this price. You keep the accounts in your own name.
- What automated output can do. Generated output is reviewed before handover, and no particular accuracy, ranking, conversion or saving is promised. You stay responsible for checking output before you rely on it.
- Access. You provide the accounts, data and permissions the work needs. Time lost waiting on access moves the delivery date.
- Ownership. Prompts, workflows and configuration built for you are yours once the balance is paid. Tools and libraries keep their own licences.
- Changes and cancellation. A change in scope is quoted as a new deal. If you cancel, you are charged for the work already done and the deposit is applied to it.
Approving this page records that you accepted this scope, this price and these terms.
Starting terms, not legal advice. Read them, change what does not match how you work, and have a lawyer look at them if the work is large enough to warrant it. Your own default terms in Settings replace these automatically.
Pricing it well
What decides whether this job is profitable
That is why the smaller package counts pages ingested. It is a quantity a client can check before you quote, and discovering afterwards that their knowledge base is four outdated documents and a shared inbox is precisely how these projects go wrong.
The handover to a human in the larger tier is the clause worth defending. A bot with no escape route makes a customer angrier than no bot at all, and a client hoping to remove it and save on support headcount is buying a worse outcome than they realise. Say so in the proposal rather than six weeks later.
Before you send it
What to change first
The parts of this template most likely to be wrong for you.
- How many pages or documents you will ingest, which is the real unit of work
- Who maintains the content afterwards, since a bot decays with its source
- Model and hosting costs, which recur and scale with how much it is used
- What accuracy you are and are not promising, which belongs in the terms
Related
Ready to close deals faster?
Create your first deal page in minutes. No credit card required.
Get started free