We build an assistant that answers questions using your own documents, policies and product data, books or captures leads where it should, and passes the conversation to a person when it can't help. It runs on your website or inside your team's tools.
Tell us what you needSee typical projectsA written scope before we start, so you know what you're getting before work begins.
What we hear from businesses before a project like this starts.
The requests that come up most often for this kind of work, and what each one takes to work properly.
Your help pages, policies and product data indexed so answers come from them, with the source shown.
Questions answered, contact details collected and a booking or callback created in your CRM.
A clear route to a human by email, chat or ticket when the bot is unsure or the customer asks.
Staff ask in Slack or Teams and get answers from internal documents, with links to the source.
Topics it won't discuss, phrases it won't use and a refusal when the answer isn't in your material.
Every conversation saved, with unanswered questions listed so your content can be improved.
Tools that come up most: OpenAI, Claude, Gemini, vector search, website widgets, Slack, Microsoft Teams, WhatsApp, Intercom, Zendesk, HubSpot and GoHighLevel.
Concrete pieces, each one something you can open and check when it's done.
Your documents and pages loaded, split and indexed so the bot can find the right passage.
Vector search, document loadersInstructions, tone and guardrails written with you and tested against real questions.
OpenAI, Claude, GeminiA website widget, Slack or Teams bot, or WhatsApp number, depending on where your people already are.
Widget, Slack, Teams, WhatsAppContact details and questions written into your CRM or helpdesk.
HubSpot, GoHighLevel, Zendesk, IntercomA conversation log and a list of questions it could not answer.
Log, weekly reportA simple way to pause the bot and show a contact form instead.
Admin settingExample packages to show the shape of the work. These are examples, not past clients; yours gets its own written scope.
Example package
A chatbot on your site that answers from your help content and hands off to a person.
You get
Example package
Visitors' questions answered and their details captured into your CRM with a booking link.
You get
Example package
A Slack or Teams bot that answers staff questions from your internal documents.
You get
Example package
Your current chatbot reviewed and rebuilt so it stops inventing answers.
You get
The habits that keep this kind of project from going wrong.
The bot answers from your material and says when the answer isn't there, instead of guessing.
We collect real customer or staff questions and check the answers before launch.
Customers can always reach a human, and the bot never pretends to be one.
Model usage is billed to your own account, and we estimate the monthly cost in the scope.
You describe it. We write it down, build it, and hand it over.
Tell us what you need in your own words, and which tools you already use. A few lines is plenty to start.
We reply with a short written scope: what gets built, what is out of scope, which accounts we need, and how we'll both know it works. You know what you're getting before work begins.
The work is split into milestones. At each one you see it working in your own account and sign it off before we go on.
You get the working system, its documentation and a walkthrough. If anything we built breaks in the next 30 days, we fix it at no charge.
Pushbuild has built software for businesses since 2010, for more than 40 clients. Every project is led by a former public-company CTO, from Groton, Massachusetts. See products we've built.
It is built to answer only from your material and to say when it doesn't know. We test this on real questions before launch and keep a log so you can check.
You can. Logs are stored in your own systems or accounts, and we describe exactly where in the handover notes.
It can create bookings, leads or tickets in your tools. Taking payment inside a chat is usually better handed to a checkout link.
Model and hosting usage is billed to your own accounts; for most small sites it is modest. We estimate it from your traffic in the scope.
Usually one to three weeks from the signed scope, mostly depending on how much content there is and where it lives.
For 30 days we repair anything we built that does not work as the scope describes, at no charge. After that, further work is scoped the same way and agreed with you before we start.
Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.
hello@pushbuild.com