What happens after launch?

You own it. Most clients take the care plan (from $500/mo): monthly transcript reviews, new intents added, drift fixed. Skip it and the bot keeps running — you handle updates yourself with the runbook and Loom walkthroughs we hand over.

AI Chatbot Development — Trained on Your Docs

Delivery blueprint

Visual summary of what this build includes from quote to handover.

Scope

Written

Deliverables and acceptance checks are fixed before build.

Execution

Instrumented

Retries, logs, and alerts are configured for production.

Controls

Approved

High-risk actions are gated by named human approvers.

Transfer

Owned

Runbook and account ownership move to your team at launch.

168 hours of questions. 40 hours of answers.

There are 168 hours in a week and your team covers about 40 of them. For the other 128 — evenings, weekends, 3 am — every visitor asking about pricing, turnaround, or “do you work with X” hits a contact form and waits. Most don’t wait: they open the next tab in the search results.

The questions themselves aren’t hard. Pull your chat logs and inbox and you’ll find the same 20–25 questions on repeat — roughly 65% of what your team answers by hand is routine (typical for this type of automation). That’s paid staff time spent retyping answers that already exist in your docs.

What we build — and wire into your stack

A concierge trained on your docs and pricing

We index your real material — service pages, price list, policies, past email answers — so the bot replies with your facts, in your tone. Pricing answers come from a locked table, never improvised, and anything off-script gets an honest “let me get a human.”

Claude · Postgres + pgvector · Notion · Google Drive

Actions, not just answers

The bot books calls straight into your calendar, writes qualified leads into the CRM, and opens WhatsApp with context pre-filled. Every conversation ends at one of three exits — lead captured, call booked, or human reached. No dead ends.

Cal.com · HubSpot · WhatsApp · n8n

Human handoff with the full transcript

When the bot hands off, your team gets the whole conversation in Slack — no “can you repeat that?” for the visitor. Every chat is logged and tagged, so you can see what people actually ask and fix the page that keeps confusing them.

Slack · Google Sheets · n8n

How this ships

Week 1

Audit

Top-25 question inventory from your real inbox and chat logs, ranked by volume, with the 5 highest-value automations flagged

Week 2

Blueprint

Conversation flows, tone rules, escalation paths, and the integration map (calendar, CRM, WhatsApp) — signed off before we build

Weeks 3–4

Build

The bot live on your site: trained on your docs, wired to Cal.com and your CRM, tested against 100 real past conversations

FAQ

What does a chatbot build cost?

Most chatbot builds land at $2.5–6k fixed, quoted in writing after a free audit. Ongoing cost is tool fees only — typically $20–80/mo for hosting and LLM usage with prompt caching. No per-seat fees, no retainer required.

How long until it’s live on my site?

2–4 weeks from kickoff. Week 1 is the audit of your real questions, week 2 the flow design you sign off, weeks 3–4 the build and testing. If a first version isn’t live in 30 days, you don’t pay.

What tools is it built on?

Claude for language, Postgres + pgvector for your document index, n8n for actions like CRM writes and notifications, Cal.com for booking. Every account is in your name — no black box, and firing us doesn’t kill the bot.

Where does our data go?

Your documents are indexed into a database you control. Conversations are logged with PII scrubbed first, chat history stays in the visitor’s browser session, and the system prompt never leaves the server. We’ll sign your DPA; API traffic isn’t used to train anyone’s models.

AI chatbots that answer in under 1 second