Guide

AI chatbot: build it yourself or have it built?

Much of what goes into an AI chatbot can be built in-house — the question is whether it pays off. When internal effort makes sense, where the line is, and which approach costs the most.

Request assessment ↗AI chatbot

Quote upon request2 to 4 weeksStatus 2026

In short

Building an AI chatbot yourself makes sense when the project stays small, someone in your business has time for it, and no one depends on it going live by a specific date. As soon as other systems need to be involved or someone is liable if it fails, external implementation is usually more cost-effective — the most expensive path is the half-finished one.

01 — In-house effort

Build yourself or have it built?

Building yourself makes sense when someone in the business has the time and interest, the project stays small, and no one depends on it being live by a specific date.
Ready-made platforms get you to a first result quickly, but hit limits where custom processes, custom data, or integrations with existing systems come into play.
External implementation pays off as soon as the AI chatbot needs to communicate with other systems, as soon as someone is liable if it doesn't work, or as soon as the internal effort becomes more expensive than external implementation.
The most expensive path is the halfway one: built in-house for months on the side, then abandoned and rebuilt externally. If you decide on in-house effort, set a time budget and an abort point.
Hybrid approach: concept and setup external, maintenance internal. This is often the most economical path for an AI chatbot — provided the handover is documented.

02 — Requirements

What you need for an AI chatbot

A clearly defined trigger. Not “we should do something with AI,” but a process that demonstrably costs time or orders today.
Existing content or data. An AI chatbot works with what's already there. The more complete your starting point, the shorter the setup.
Access to the systems involved. Whoever manages the credentials needs to be involved from the start — this is, in our experience, the most common cause of delays.
One decision-making contact person. One, not three.
Willingness to refine after launch. The first weeks in real operation show what was missing in the concept. That's normal and accounted for.

03 — Calculation

How to calculate it

Four numbers are enough: How often does the process occur? How long does it take? What does an hour cost internally? And what does the solution cost — one-time plus operation over three years?

An example: A process that occurs twice a week and takes 40 minutes each time ties up around 69 hours per year. At an internal hourly rate of 45 euros, that's roughly 3,100 euros per year locked in there. If a solution reduces this effort by two-thirds, it often pays for itself — depending on the actual quote — within one to two years. We'll give you the exact figure for your case after the initial meeting.

This calculation is deliberately conservative: it only accounts for the time saved, not the errors avoided or the orders that come through due to faster response. In practice, the benefit is usually higher — but you shouldn't count on it before you've measured it.

04 — Questions

Frequently asked questions

What if the bot answers a question incorrectly?

You see every conversation. Incorrect answers are refined by making the knowledge base more precise. This happens a few times in the first weeks, then rarely after that.

How much work does this create for us?

At the start, about two to three hours for gathering content and one alignment round. After that, nothing regular — unless you want to add new topics, which works through a simple document.

Doesn't an AI chatbot just make up answers?

A free-running language model does. That's why we build the bot so it only answers from a verified knowledge base and provides the source. If it finds nothing, it says so and redirects — that's the most important part of the configuration.

Does this even pay off for us?

The calculation is simple: requests per week times processing time times hourly rate. With twenty repeat questions per week and seven minutes each, that's a good two hours of work — every week. We calculate this with your real numbers before the quote.

Do we have to label the chatbot as AI?

Yes. Since August 2026, the transparency requirements of Article 50 of the EU AI Act apply: Anyone communicating directly with an AI system must be able to recognize it. We build the labeling in as standard, it costs nothing extra.

Does this also work on a WordPress site?

Yes. The integration is a single code snippet in the footer and works the same on WordPress, Shopify, Webflow, Wix, TYPO3, or a custom-built site.

Can we turn the bot off again?

Anytime, with one click. The snippet remains, the bot is gone. There's no minimum term that binds you.

05 — Decision

How to move forward

The most affordable next step is a conversation, not a quote. Twenty minutes is usually enough to clarify whether a project makes sense, what scope it involves, and whether we're the right fit.

If we're not, we'll say so. An honest no costs less than a project you abandon after three months — for both sides.

06 — Next

AI chatbot by region

Next step

We'll look at your starting position.

Tell us what's eating up time today. That becomes an assessment with effort and benefit — and only then an offer.

Send inquiry ↗ office@pipeline-solutions.at OR +43 681 207 64 203