Starter
USD 500-1,000 Simple Telegram workflow, FAQ, notification, or proof-of-concept bot
24 hours
Bot development pricing
Bot pricing: simple bots in 24 hours, complex builds in phases.
Compare realistic starting ranges for Telegram bots, WhatsApp chatbots, bot rescue, and custom AI automation. Every project is scoped around the channel, integrations, AI behavior, and support needs.
- Written scope
- Build cost separated from monthly cost
- AI and API costs visible
- Repair before rebuild
Package board Scope before quote
AI Build
USD 1,000-3,000 AI bot for answers, qualification, summaries, or routing
2-5 days Rescue
Audit first Diagnostic sprint for a broken or underperforming bot
48h-1 week Custom
Custom quote Multi-system automation, payments, dashboards, or high-volume support
1-3+ weeks Scope
How TUNDRÄ estimates bot projects
We price a bot by the job it has to perform reliably. A simple menu bot and an AI WhatsApp sales assistant may both look like chatbots, but the technical risk is completely different.
- Start small enough to launch fast, then expand after real usage.
- Separate one-time build cost from hosting, AI usage, WhatsApp fees, and maintenance.
- We recommend no-code, repair, or a smaller MVP when custom development is not the right first step.
Scope estimator
Estimate the scope before the quote call.
This estimator is not a checkout price. It helps you see whether the project is closer to a starter bot, an AI build, a rescue sprint, or custom automation.
Likely package Bot Starter
from USD 500-1,000, usually 24 hours for a simple bot when the scope is ready.
- One platform and one workflow.
- Simple commands, buttons, data capture, or notifications.
Estimate logic
The quote gets clearer when the workflow is named.
Use the scope estimator as a pre-call filter. It separates a narrow bot from a workflow that needs integrations, AI, payments, or ongoing support.
Telegram is usually cheaper to run
Telegram has no standard Bot API platform fee. WhatsApp can require Business API setup, provider costs, templates, and conversation-cost planning.
- Telegram Bot API
- WhatsApp Business API
- Website chat
- Multi-channel
One useful workflow keeps the estimate clear
Lead capture, booking, support, payment, and AI support should not be priced as one small bot when they ship together.
- Lead capture
- Booking
- Support
- Payments
- AI answers
External systems need real QA
CRM, calendars, spreadsheets, payment providers, inventory, and private APIs add authentication, mapping, retries, and failure states.
- CRM
- Sheets
- Calendar
- Payments
- Private API
All ranges are planning ranges. Final quotes depend on confirmed scope and support expectations.
Cost clarity
Build cost is not the whole budget.
A useful estimate separates implementation from pass-through and operating costs so the monthly number does not surprise the team after launch.
What belongs in the build
Conversation design, implementation, testing, deployment path, admin alerts, launch notes, and the first production fixes.
- Flow map
- Bot build
- QA pass
- Deployment
- Launch fixes
What can continue after launch
Hosting, AI API usage, WhatsApp provider fees, conversation costs, monitoring, maintenance, and optimization.
- Hosting
- AI usage
- WhatsApp fees
- Monitoring
- Support
What should stay visible
Payment-provider fees, SaaS subscriptions, ad spend, CRM seats, and client-owned infrastructure should be shown separately.
- Stripe fees
- CRM seats
- Provider plans
- Ad spend
- Infrastructure
Package comparison
Compare by outcome, hidden work, and buyer readiness.
The headline price is only useful when it shows what is included, what is excluded, and what the buyer has to prepare before development starts.
| Package | Best for | Price | Timeline | Includes | Not included | Buyer provides |
|---|---|---|---|---|---|---|
| Bot Starter | One Telegram or website-chat workflow | from USD 500-1,000 | 24 hours when scope is ready | Conversation flow, commands or buttons, simple capture, deploy notes | Heavy AI, payments, dashboards, private APIs, managed support | Final copy, bot access, destination for leads or alerts |
| AI Bot Build | Support, Q&A, qualification, summaries, routing | from USD 1,000-3,000 | 2-5 days when sources are ready | AI behavior, knowledge prep, guardrails, fallback and handoff logic | Large content cleanup, complex CRM, payment state, multi-agent inbox | Approved source material, escalation contact, example conversations |
| Bot Rescue | Broken bot, bad answers, failed handoff, missed leads | fixed audit, then repair quote | 48h-1 week diagnostic | Flow audit, prompt review, logs, integrations, repair-or-rebuild plan | Production fixes before diagnosis, secret recovery, unsupported vendor work | Symptoms, failed chats, admin access, code or platform access where possible |
| Custom Automation | Payments, CRM, booking, admin tools, WhatsApp, multi-system workflows | scoped quote | 1-3+ weeks | Architecture, integrations, QA paths, monitoring plan, documentation | Provider fees, SaaS subscriptions, ad spend, client-owned infrastructure | System owners, API access, acceptance checks, launch priority |
Sample quotes
Example budgets show why two bot quotes can be far apart.
These examples are planning scenarios, not checkout prices. They make the scope assumptions visible before a call.
Final quotes should name acceptance checks and exclusions, not only a single number.
| Scenario | Likely range | Why | Monthly considerations |
|---|---|---|---|
| Telegram FAQ and lead capture | USD 500-1,000 | One flow, prepared questions, simple admin notification, no AI memory | Small hosting, optional support, no Telegram platform fee |
| AI support bot with handoff | USD 1,000-3,000 | Knowledge prep, prompt rules, escalation, unanswered-question logs | Hosting, AI API usage, prompt improvements, monitoring if critical |
| WhatsApp lead bot with CRM | USD 2,500-7,000+ | Business API readiness, templates, opt-in, CRM mapping, handoff | Provider plan, message costs, CRM seats, support ownership |
Budget split
Separate one-time build cost from monthly and pass-through costs.
This keeps a small build from looking cheap on paper and expensive after launch.
| Cost type | Examples | How to treat it |
|---|---|---|
| One-time build | Conversation design, bot development, integrations, QA, deployment notes | Quoted after scope is confirmed |
| Monthly operations | Hosting, database, AI usage, monitoring, maintenance, small improvements | Estimated by traffic, risk, and support expectations |
| Pass-through costs | Payment-provider fees, WhatsApp provider fees, CRM seats, SaaS tools, ad spend | Owned by the client and shown separately |
| Excluded unless scoped | Dashboards, migrations, multilingual content, legal review, full support inbox, custom analytics warehouse | Added only when it has a named owner and acceptance check |
Packages
Pick the package by operational risk, not by feature count.
The same chat screen can be a 24-hour starter bot or a production system. These ranges separate simple launches from bots that touch AI, money, customer data, or business systems.
Simple Telegram workflow, FAQ, notification, or proof-of-concept bot
For commands, simple menus, data capture, notifications, and low-risk workflows with limited integrations.
from USD 500-1,000 24 hours
- One main workflow
- Basic commands or buttons
- Simple data capture
- Deployment guidance
- Handover notes
AI bot for answers, qualification, summaries, or routing
For Telegram or WhatsApp bots that need knowledge-based answers, guardrails, memory, handoff, or lead qualification.
from USD 1,000-3,000 2-5 days
- AI behavior design
- Knowledge prep
- Guardrails
- Human handoff
- Unanswered-question logs
Diagnostic sprint for a broken or underperforming bot
For existing bots that give wrong answers, lose leads, fail to escalate, crash, or cost too much to operate.
fixed audit, then repair quote 48h-1 week
- Flow audit
- Prompt review
- Integration checks
- Repair plan
- Rebuild trigger call
Multi-system automation, payments, dashboards, or high-volume support
For projects that connect several systems and need admin tooling, reporting, reliability, or staged rollout.
scoped quote 1-3+ weeks
- Architecture
- API integrations
- Admin tools
- Monitoring plan
- Documentation
Cost drivers
What moves the price up
The price changes when the bot moves from a simple conversation into AI behavior, payments, integrations, admin tooling, or platform-specific compliance.
AI behavior and knowledge
AI adds prompt design, source cleanup, memory, guardrails, fallback logic, rate limits, and usage tracking.
- Knowledge base
- Guardrails
- Memory
- Fallbacks
Payment and subscription logic
Payment flows require testing for success, failure, cancellation, refunds, receipts, and access state.
- Checkout
- Webhooks
- Access rules
- Refund paths
Admin panels and reporting
Private admin tools add build time but reduce operational pain when non-technical staff need control.
- User management
- Broadcasts
- Content editing
- Analytics
Monthly costs
Running costs depend on the channel.
Telegram is usually the lowest-cost custom bot channel. WhatsApp can have stronger customer reach, but Business API setup and provider economics must be planned.
Low platform cost
Telegram Bot API has no standard platform fee. Monthly costs usually come from hosting, AI usage, and support.
- USD 0 Bot API
- Hosting
- AI API
- Maintenance
API and provider planning
WhatsApp may include Business API setup, provider plans, template rules, and conversation-related costs.
- Business API
- Templates
- Provider fees
- Conversation volume
Maintenance for critical bots
Business-critical bots benefit from monitoring, bug fixes, prompt improvements, API updates, and small iterations.
- Monitoring
- Bug fixes
- Prompt updates
- API changes
Comparison
Custom bot, no-code tool, or agency?
The right option depends on whether the bot is a temporary flow, a production channel, or a larger business system.
| Option | Best for | Risk | TUNDRÄ view |
|---|---|---|---|
| No-code platform | Simple FAQs, short campaigns, basic lead forms | Limited custom logic, platform lock-in, fragile integrations | Use when the team wants to operate the tool itself |
| Freelancer or specialist studio | Focused custom builds with clear scope | Quality depends on production experience and documentation | Good fit for most practical bot MVPs |
| Full agency | Enterprise rollout, brand campaign, or large product program | Higher overhead and slower start for small bots | Use when the bot is part of a bigger multi-team project |
Process
From a rough budget to a build-ready scope.
The pricing flow is designed to remove surprises: choose the likely package, confirm access, then agree on acceptance checks.
Send the workflow
Channel, goal, integrations, AI needs, current access, deadline, and examples.
Confirm the scope
We separate MVP work from custom features before development starts.
Build and test
Happy path, wrong inputs, handoff, integration failures, payment states, and analytics.
Launch and support
Deploy, monitor early conversations, document ownership, and plan improvements.
FAQ
Pricing questions buyers should ask early.
Can you give an exact price immediately?
Yes, for very small scopes: one channel, one workflow, ready copy, ready access, and no heavy AI, payments, WhatsApp verification, dashboard, or private API work.
Why is WhatsApp usually more expensive to run than Telegram?
Telegram has no standard Bot API fee. WhatsApp uses the Business API ecosystem, which can include provider fees, template rules, and conversation-related costs.
Can we start with a smaller MVP?
Yes. The preferred approach is to launch one useful workflow first, then add AI, payments, analytics, or more channels after usage proves the value.
Do you offer maintenance?
Yes, when the bot is business-critical. Maintenance can include monitoring, bug fixes, prompt improvements, template updates, API changes, and small iterations.
Next step