"Add AI to our website" sounds like a line item on an engineering roadmap. For most small businesses, it isn't one — and treating it like one is the main reason it never gets done.
What you actually need before you start
Not a developer. Not a project brief. What you need is the same information a new front-desk hire would need on day one: your hours, your prices, the services you offer, your policies, and how your booking process works. If you can explain your business to a new employee in twenty minutes, you have everything AIVA needs to get started.
What "three lines of code" really means
AIVA's web widget embeds with a snippet you paste into your site once — three lines, dropped in wherever your site's template lives. Whether your site runs on WordPress, Squarespace, Wix, or something custom-built, the step is the same: paste it in, save, done. It's not a development project with a timeline and a sprint. It's closer to adding a tracking pixel than building a feature.
If you already have someone who occasionally updates your site — even if "developer" isn't their job title — this is a five-minute favor to ask them, not a project to scope.
Where the snippet actually goes, roughly
You don't need to know how your website is built to figure this out. Most site builders — WordPress, Squarespace, Wix, and the rest — have a section for "custom code," "header scripts," or "tracking code," often somewhere under settings. That's usually the exact spot a snippet like this goes, the same place a business would already paste something like an analytics tag. If you genuinely can't find that setting, that's the moment to hand it off rather than the moment to give up — it usually means someone else manages that part of the site, and they'll recognize the spot immediately.
A rough guide by platform
The exact wording varies by builder and changes over time, but the shape is consistent enough to know what you're looking for:
| Platform | What to look for |
|---|---|
| WordPress | A header/footer script plugin, or a "custom code" area in your theme settings |
| Squarespace | Something named "code injection," usually under site-wide settings |
| Wix | "Custom code," usually under settings, available on most paid plans |
| Custom-built site | Whoever manages the template — a one-time favor for them, not a rebuild |
If none of that matches what you see, the fastest path is still just asking whoever last touched your website "where do I paste a tracking-style script?" — they'll usually know immediately, even if the exact menu name has moved since this was written.
Does adding this slow down your website?
A reasonable worry, before anything else: does bolting a chat widget onto a site slow it down for everyone who never even opens it? The snippet is built to load asynchronously — it doesn't block your page's own content from rendering while it fetches in the background, the same pattern browsers already use for tools like analytics scripts. A visitor who never clicks the widget barely notices it's there; the interface itself only loads its full weight once someone actually opens the chat window, not on every page view.
If your site is already slow for reasons that have nothing to do with a widget — a bloated image gallery, a theme with too many plugins — adding AIVA won't fix that, and it's worth checking your site's actual load time separately if that's a real concern. But a business running a normal, reasonably well-built site won't notice a measurable difference after adding the snippet. If you want to confirm it yourself rather than take our word for it, most browsers have a built-in way to check page load time before and after — it takes five minutes and settles the question for your specific site instead of a general answer.
What "no developer" doesn't mean
It's worth being precise about what this claim covers and what it doesn't. It means no coding knowledge is required and nothing needs to be built. It doesn't mean zero technical steps ever — you (or whoever manages your site) still need basic access to paste the snippet in. If your site was built by an agency years ago and nobody currently has the login, that's a real obstacle, but it's a pre-existing one about your own site access, not something specific to adding an AI assistant. Fixing that is worth doing regardless of what you install next.
What you're actually configuring, not coding
Everything that makes the assistant sound like your business — your FAQs, your hours, your prices, your booking rules — is set up through a dashboard, not code. You type in answers the way you'd type them into an email. There's no logic to write, no flows to wire together, no prompts to engineer. If you can fill out a form, you can configure it.
What this looks like on a phone
Most of your visitors are probably on a phone, not a laptop, so it's worth knowing what changes there. The widget resizes to fit a phone screen rather than the desktop-sized window it uses on a larger display, and it stays out of the way of a visitor's thumb — tucked into a corner rather than blocking the middle of the screen. A visitor scrolling through your services on their phone during a bus ride can open it, ask a quick question, and close it again without losing their place on the page. Given how much small-business web traffic in India is now mobile-first, this isn't a secondary consideration — for a lot of businesses, it's the primary way the widget actually gets used.
The one-time setup is the widget snippet on your site. Everything after that — updating a price, adding a holiday closure, changing your hours — is an edit in a dashboard, not a request back to whoever installed it.
How long this actually takes
Most of the time isn't spent on the widget — it's spent deciding what to tell it. Writing down your actual hours, your actual prices, and the ten questions you get asked most often usually takes longer than pasting in the snippet itself. Businesses that walk in with that list already written go live the same afternoon. Businesses starting from a blank page usually still finish within a day, not a week. If you want the fuller, more honest breakdown of what "live" versus "actually good" means as a timeline, we've written about that separately.
A worked example: two businesses, one afternoon
It's easier to picture this as two specific afternoons than as a general process. A four-chair salon owner decides to add the widget on a Tuesday morning. She spends twenty minutes with a notebook, writing down her actual price list — cut, color, the combo packages — plus her real hours, including the Monday closure and the shorter Sunday shift. Her nephew, who set up her Instagram page a year ago, pastes the snippet into her Wix site's custom code section during his lunch break. By 3 PM, the widget is live, answering exactly the questions her front desk fields most: is Saturday afternoon booked up, what does a keratin treatment cost, is the shop open on a public holiday. Total time spent: about ninety minutes, most of it hers, not his.
A diagnostic lab across town has a slightly longer list — fasting requirements for a dozen different tests, home-collection availability by pincode, report turnaround times that vary by test type — so the FAQ-writing step takes closer to two hours instead of twenty minutes. The snippet itself still takes the same five minutes to add, handled by the same freelancer who built their WordPress site two years ago. The lab goes live the same day, but doesn't feel fully confident in the answers until the second day, once a few real visitor questions have shown which FAQs needed a second pass.
Neither business needed a developer on staff, a project timeline, or a meeting to scope requirements. The difference between them wasn't technical complexity — it was how much the business itself had to think through before it had something worth configuring.
What the first day actually looks like
The widget shows up on your site the moment the snippet is live — but it won't sound like your business until the dashboard side is filled in. A visitor chatting with it on day one, before you've added your prices, will get vague or incomplete answers, the same way a brand-new hire would on their first hour without a briefing. That's not a bug to report; it's the reason the configuration step matters as much as the install step. Once your hours, prices, and FAQs are in, the difference is immediate — the same visitor asking the same question gets your actual answer instead of a placeholder.
If you're easing into this rather than flipping the switch all at once, running it as a short pilot first is a reasonable way to confirm it sounds right before pointing all your traffic at it.
How this compares to building a chatbot yourself
It's worth being specific about what this replaces, because "add a chatbot to your site" isn't a new idea — plenty of tools have offered some version of it for years. The difference is in what those tools ask you to build. A typical DIY chatbot builder hands you a flow editor: boxes and arrows, if-this-then-that logic, a tree of possible questions you have to anticipate and wire together yourself before the bot can handle anything beyond the exact paths you drew. Getting it to handle a question phrased slightly differently than you expected usually means going back into the flow and adding another branch.
AIVA's widget skips the flow-building step entirely, because it isn't answering from a decision tree — it's answering from the same hours, prices, and FAQs you'd hand a new employee, the same information described earlier in this piece. A visitor asking "do you have anything free this weekend" and one asking "any slots left before Sunday" both get handled without you having to have predicted both exact phrasings and built a branch for each. That's a meaningfully different amount of ongoing work: a flow-based chatbot tends to need maintenance every time a business notices a question it didn't handle well, while a FAQ-based setup mostly needs an update when the underlying fact changes — a new price, a new service, a holiday closure.
The trade-off is real, not one-sided: a hand-built flow gives a technical team precise control over exactly what gets said at each step, which matters for some complex processes. For the FAQ-and-booking shape of most small business questions, though, that precision costs more setup time than it returns in value.
If you still want it off your plate entirely
You don't need to do any of this yourself. Handing the three-line snippet to whoever already touches your website — even if that's a freelancer you use twice a year — is a task that takes them minutes, not a proposal-worthy project. The configuration, your FAQs and hours, is still yours to fill in, because nobody else knows your business as well as you do.
What businesses ask before doing this
The two concerns that come up most aren't technical. One is whether it'll look bolted-on and generic — it's custom-branded to match your site rather than shipping with a default bot avatar, and most businesses change the colors within the first day. The other is whether it'll interrupt visitors the moment they land — it won't, by default; smart triggers decide when the widget actually shows itself, rather than popping up on page load for every visitor.
Mistakes worth avoiding
A few patterns show up often enough to flag directly. The first is waiting for a free afternoon to "sit down and do it properly," when the honest version is a five-minute favor plus an hour of writing down FAQs you already know by heart — waiting rarely makes it easier, just later. The second is installing the snippet and stopping there, then judging the assistant on vague answers it gives before anyone has filled in the dashboard — that's a configuration gap, not a product problem. The third is skipping the branding step and assuming visitors will treat a default-colored widget the same as one that matches the site; they usually notice more than businesses expect, which is why most businesses adjust the widget's appearance within the first day.
Try it before you commit to anything
The clearest way to know whether this is really as simple as it sounds is to do it once. Start free with ₹500 in credit and no card required, and see how far you get in one sitting. If you want the broader case for what a web AI assistant actually does once it's live, read the full rundown here.