AI Chatbot and AI Agent Development in the US
We are an Indian engineering team working with businesses in the US. Written scope before any code, and a fixed quote in USD.
Working hours
Our day ends at 07:30 in the US (08:30 on summer time), before yours begins, so we work asynchronously: written updates land overnight and are waiting when you start.
Quoted in USD
There is no general VAT in the US at present, so the quote is the amount you pay.
Data protection
Work for this market is scoped against state privacy law, principally the CCPA and CPRA in California, agreed before development starts rather than retrofitted afterwards.
Written scope
Every engagement starts with a written scope and a fixed USD quote within 24 hours, so the price is set before work begins.
About AI Chatbot and AI Agent Development
A chatbot that answers from your own help docs, catalogue and policies instead of making things up. An agent that can check an order, book a slot or update a CRM record, and nothing you didn't allow. We've shipped 18 production AI integrations, and every one has a running-cost cap.
What the engagement includes
- Answers come from your content only, with the source shown, so it can't invent a refund policy you don't have
- A confidence threshold and a clean hand-off to a human when the question is outside what it knows
- An evaluation set of real customer questions, run before every change, so a prompt tweak can't quietly break answers
- Hard monthly spend limits and per-request cost tracking, so the model bill can't surprise you
- Agents get the narrowest permissions that work, and anything touching payments needs a human to approve
- Your data stays within the provider settings you choose, and nothing is used for model training
Send the scope and you get a written scope and a fixed USD quote back within 24 hours.
Get a quote in USDWhat US disclosure, wiretap and robocall rules change about a chatbot
In the US the first line a chatbot sends is a legal decision, and the states make it one at a time. Maine's 2025 statute makes it an unfair trade practice to use a chatbot in trade in a way that could lead a reasonable consumer to think they are talking to a person, unless they are told clearly and conspicuously that they are not. Utah, after its 2025 amendments, requires disclosure when a consumer clearly and unambiguously asks whether they are dealing with AI, and up front when a regulated profession uses it in a high risk interaction, with a safe harbour for a business that discloses at the start and throughout. A second group of laws covers companion chatbots: New York's since 5 November 2025, California's SB 243 since 1 January 2026, and Washington's and Oregon's from 1 January 2027. They add repeated not-human reminders, every three hours for a known minor in California, and a published protocol for a user who talks about self-harm, and California and Oregon let an injured user sue for $1,000 per violation. All of them exclude bots used only for customer service, but the definitions follow what the bot does rather than what you call it, so a support bot that remembers people across sessions and asks how they are feeling is drifting toward them. We build to the strictest version: the disclosure sits in the first message and in the widget header, and "am I talking to a real person?" is a test case the bot must answer truthfully before release.
What you say about the bot is advertising, and the FTC has shown it will test it. Its Operation AI Comply sweep of 25 September 2024 included DoNotPay, sold as "the world's first robot lawyer" without ever being tested against a human lawyer's work, and the order finalised in January 2025 carried $193,000 in relief and bars claims that it can stand in for a professional without evidence behind them. So "resolves most tickets without an agent" on your pricing page needs the evaluation run that proves it, and we hand that over with the bot. The larger exposure for a chat widget is older than generative AI. California's Invasion of Privacy Act allows $5,000 per violation when a conversation is recorded or read by a third party without consent, and plaintiffs aim it at the vendor behind the chat. Federal judges in San Francisco let such claims go forward against AI customer service vendors in Ambriz v. Google in February 2025 and Taylor v. ConverseNow in August 2025, reasoning that a vendor able to use the conversations to improve its own product can count as a third party. The Ninth Circuit ruled for the defendant in a chat case the same year for want of evidence the vendor read anything, so the question is open. Our answer is consent shown before the first message is sent rather than a privacy link in the footer, and model and hosting terms that bar training on your transcripts.
A voice agent brings federal telephone law. On 8 February 2024 the FCC ruled that AI-generated voices are "artificial" under the Telephone Consumer Protection Act, so an outbound call from a voice bot is treated like a prerecorded robocall: it needs the called person's prior express consent, prior express written consent if the call is telemarketing, and the statute allows $500 per call, trebled where the violation is wilful. The consent record, the number it covers and the date it was given become a check the dialler runs before every call rather than a spreadsheet in marketing. Inbound calls sit outside that rule but not outside the wiretap question above, so the greeting says the caller is talking to an automated system and whether the call is recorded. If the bot does more than answer, screening a rental application, a loan enquiry or a job candidate, Colorado's SB 26-189, signed on 14 May 2026, covers automated decision-making technology in consequential decisions from 1 January 2027, with notice at the point of interaction, a plain-language explanation within 30 days of an adverse outcome and a route to human review. It replaced the 2024 Colorado AI Act before that took effect, and dropped its general duty to disclose AI to consumers. Executive Order 14365 of 11 December 2025 set up a Justice Department task force to challenge state AI laws, but an order does not repeal a statute and Congress has passed none that does, so the laws above still apply. Which of them reach your users is for your own counsel.
How we work with US clients
A US engagement gets agreed twice. Once with the person who wants the thing built, and then again with legal, security, procurement and finance, who arrive separately and rarely in the same week. That second round is where a supplier outside the country loses the calendar: a master services agreement to redline, a security questionnaire, a certificate of insurance, and a vendor portal that assumes everyone it onboards can sign a W-9. Send all of it while the scope is still being written rather than in the week you wanted to start, and where the honest answer to a row is that we do not hold something, we write that in rather than leaving it blank.
You are also buying from a company you cannot drop in on, so the evidence has to do the work an office would otherwise do. What we send is live production URLs rather than a deck, a written scope with one fixed number against it, and the names of the people who will do the work rather than a bench that changes after signature. What we will also tell you is the shape of what you are hiring: a small team in Noida that has been building since 2021, not a firm that can put four more people on your project next Monday. If that is what your timeline needs, we say so before the contract rather than after it.
Send the scope and you get a written scope and a fixed USD quote back within 24 hours.
Get a quote in USDFull service detail
This page covers how we work with clients in your market. The complete AI Chatbot and AI Agent Development page, with the full technical detail, process and frequently asked questions, is written in English.
Read the full service page (English)Questions US clients ask
Does our site have to meet ADA accessibility requirements?
If you are consumer facing in the US, build as though it does. Demand letters over inaccessible websites are routine and cheap to send, federal work brings Section 508 with it, and the Department of Justice rule under Title II sets WCAG 2.1 AA for state and local government entities on a timetable your counsel can confirm for your size band. We work to WCAG 2.2 AA and test with a screen reader rather than relying on an automated scan, because automated tools catch perhaps a third of real issues and the other two thirds are the ones that end up in a letter.
How do we know you will still be here in two years?
Nobody can promise you that, and a supplier who does is selling something. We have been building since 2021 and we maintain what we build, which is the honest version of the answer. The useful version is that it should not have to matter. The repository is in your GitHub organization, the domain and hosting accounts are in your company name, the stack is Next.js, Laravel, Flutter and Postgres rather than anything only we can read, and the handover document exists before you ask for it. If we vanished tomorrow, another agency could pick it up without needing to call us.
Can you sign our NDA and work under our MSA?
Yes to the NDA. Send your standard one and it comes back signed within 24 hours, before you describe the project in any detail. Yes to the MSA too, with the caveat that we read it properly rather than signing to be agreeable. The two clauses we usually come back on are unlimited liability, where we ask for a cap tied to the fees, and an IP clause drafted broadly enough to sweep in the internal tooling we bring to every project. Everything built for you transfers to you in full on final payment. We mark up those two and sign the rest.
Something breaks at two in the afternoon in Chicago. What actually happens?
Two in the afternoon in Chicago is past midnight here, half past midnight in summer and half past one in winter, so the truthful answer depends on what you are paying for. Monitoring does not keep our hours and the alert fires whatever the clock says. Whether a person is awake to act on it depends on your plan, because we are not a 24/7 on-call operation as standard, and we would rather tell you that while you are choosing a plan than while your checkout is down. Without out-of-hours cover written into the contract, the realistic answer is that it is picked up at the start of our day, which is the middle of your night, and you should price that in when you decide.
AI Chatbot and AI Agent Development: common questions
How much does it cost to build an AI chatbot?
$460to $1,000for a website chatbot grounded in your own content, plus $23to $170a month to run depending on traffic and model. Agents that take actions in your systems cost more to build because of the permission and testing work.
Which AI model do you use?
It depends on the job. Claude and OpenAI models for most customer-facing work, smaller and cheaper models like Claude Haiku or GPT mini tiers for high-volume simple questions, and open models when data can't leave your servers. We pick on accuracy and running cost, and we can switch later without a rebuild.
Will the chatbot make things up?
Not if it's built properly. Ours answer only from your content, show where the answer came from, and hand over to a person when they aren't confident. We test against a set of real questions before launch and after every change.
Can it work on WhatsApp?
Yes. We connect it to the WhatsApp Business API through Meta or a provider like Gupshup or Interakt. The same brain can serve your website and WhatsApp, so you maintain one set of content.
What's the difference between an AI agent and a chatbot?
A chatbot answers questions. An agent takes actions: it checks an order, books a slot, creates a ticket or updates a CRM record through tools we define. Agents are more useful and need tighter controls, so we usually start with a chatbot and add actions once it has proven itself.
Send the scope and you get a written scope and a fixed USD quote back within 24 hours.
Get a quote in USDOther markets we work in
Tell us what you are building in the US
Send the scope, or just the problem. You get a written scope and a fixed USD quote back within 24 hours, from the engineers who would do the work.