What an AI assistant for a department costs and what makes up the price

What an AI assistant for a department costs and what makes up the price

The client asks the price and there is nothing to justify it with: it is unclear what it is made of. Below is the composition of the work, in which assembly is the smaller part, six parameters determining the sum, and what that sum gets compared against so it stops seeming large.

The client asks the price and there is nothing to justify it with: it is unclear what it is made of. Below is the composition of the work, in which assembly is the smaller part, six parameters determining the sum, and what that sum gets compared against so it stops seeming large.

"And how much will an assistant for a department cost?"

The question most contractors freeze on when first selling an assistant to a company.

There is nothing to name a figure from: it is unclear what it consists of. Your own time is easy to count — but the client is not buying your hours.

The client does not understand either. He has seen free chats and does not see what to pay for when "it is just AI".

Let us go through the composition: what the work involves, what determines the price and what to compare that sum against.

What the work consists of

Six parts. The first two are not technical, and they are also the longest.

1. Analysing the process

What the department is, which tasks recur, where people waste time, which questions they ask each other ten times a day.

That is an interview rather than technical work. And without it the assistant will be about what seemed important to you rather than about what hurts.

The typical finding at this step: half of what was requested is not needed, and what is needed nobody named.

2. Gathering knowledge

The most labour-intensive part of the whole project.

The knowledge sits in staff heads, in scattered files, in message threads. It has to be extracted, consolidated and structured: services, rules, procedures, frequent questions in real phrasing, handling of exceptions.

An assistant with no base answers in generalities and irritates people more than silence. That is the main cause of failures, and it is not about the model.

It is extracted by interview: the person does not have to write anything, only answer questions — what do you do, in what order, what goes wrong.

3. The instruction

Role, base, reasoning algorithm, output format, handover triggers, constraints.

The last block is the one that makes assistants invent things that do not exist. A model fills gaps with something plausible if it has not been told not to.

4. Debugging on live conversations

The first version is always full of holes. Only a run on real questions works: where it did not understand, where it invented, where it did not hand over in time.

That is what separates a working assistant from one assembled in an evening. And what cannot be skipped, however much the client hurries you.

5. Integration

Where it is embedded: a chat on a site, a messenger, an internal system. How it passes a conversation to a human and what it supplies with it — a summary, a contact, the history.

6. Handover and training

Instructions for staff, short training, rules for updating the base.

Skipped most often — and that is exactly why systems die within a month. An employee who has not understood the system routes around it within a week.

What determines the price

Six parameters. They are what the sum is justified with in conversation with a client.

The size of the knowledge base. One price list or five areas of activity with exceptions is a difference of several times over. That is the main multiplier.

The number of scenarios. Answering questions is one thing. Answering, qualifying and booking is another.

Integrations. A standalone chat or a link with an existing records system.

Whether debugging on live traffic is needed or a basic check will do.

Maintenance. A one-off handover or monthly support with base updates.

The number of staff to be trained.

A practical technique in conversation: do not name a figure straight away. Name three parameters it depends on, tie the cost to the client's expenses and propose a short call with two specific slots. A figure with no justification turns the conversation into haggling.

What to compare the sum against

Here is the main argument, and it is not about the technology.

The comparison is not against zero but against an existing line of expenditure.

A real example from practice. The client is Zakhar Fomin, owner of a dental clinic. The task: a receptionist that answers around the clock, qualifies enquiries and books appointments.

Sold for $1 900 a year, payment received in full; the contractor was Denis, the founder. The clinic bought a CRM later as a separate order — about $3 200.

Why he agreed: the alternative is an in-house team, a marketer plus a social media specialist plus a remote administrator, around $720 a month plus taxes, holidays, sick leave and the human factor. The system works around the clock and does not fall ill.

The phrasing that works: "a full build pays for itself in the first month, because it replaces the functions of a front-desk administrator while working with no weekends, around the clock".

The anchor is set before the figure rather than after. When the sum sounds, it lands in a prepared frame.

The order of market prices

From my scrape of 5 986 jobs over four months: a system or a pipeline $490–1 460, against a median one-off job of around $60.

A caveat: an explicit budget appears in 17% of listings, and by individual type of work there are between twenty and three hundred observations with a sum. The median is reliable; the breakdown is a guide.

And the $1 900 from the example is the price of one specific project by our methodology rather than market statistics. The two figures must not be confused.

What separates the bottom of the range from the top: not the difficulty of assembly but the size of the knowledge base and whether maintenance is included. An assistant on one price list with no support and a system with five areas and monthly updating are different products.

What is delivered to the client

A list worth showing in full in a proposal — it justifies the price better than any words:

A client who sees seven lines instead of one sum argues with the items rather than with the total. That is already a normal working conversation.

Where the main money is

Not in the first sale.

In maintenance. Prices change, services change, new questions appear. Without updating the base goes out of date within six months and the assistant starts lying to customers. That is a recurring payment and an honest one.

In expansion. The assistant for one department works, and a request comes for a second. Then for an integration, then for analytics.

In my scrape 23% of clients are explicitly looking for somebody long-term and 12.9% talk about ongoing volume. A third of the market does not fit into one-off work.

What the platform offers for a department assistant

Over 200 ready assistants across 14 categories — before building your own, look at the ready ones. A substantial share of tasks is covered, and sometimes a selected set is enough for a client rather than development. That is also a service, only cheaper and faster.

The Bot architect from the "Engineers" category — it writes system instructions with an algorithm, handover triggers and constraints. Access from the Basic plan.

Creating your own assistants for a company, with its knowledge base — the Creator+ plan.

The “Personal AI bureau” express course — designing instructions and selling assistants to clients. $9, Creator plan. Not included in the three free days of Basic.

The “Sales” course (main module — ten lessons) — the four client types, handling the price objection, shaping an offer to demand. Included in Basic.

Registration is free and opens three days of full Basic access.

Where to start today

One action. Take a company you know — your own or a client's — and calculate one figure: how many enquiries arrive outside working hours and what happens to them.

That figure is your quote. Not "what does an assistant cost" but "what does not having one cost".

That is where a conversation begins in which price stops being the main question.

What to compare your price against

The client asks why it costs that much. You can honestly compare against two figures that have a source: a real order — the system for Zakhar Fomin's clinic, $1 900 a year — and the scrape of 5 986 jobs over four months, where a system or a pipeline is $490–1 460. They are different figures: the first is the price of one specific project by our methodology, the second is a market range from listings.

What that gives you in conversation. You are not naming a price out of the air but showing what a solution of this class is valued at and where the figure comes from. The discussion then moves to scope rather than to the sum.

And an honest fork worth stating to the client. Some of these solutions exist ready-made: they open pre-configured, you enter the credentials and they run. If the task is standard, he does not need development from scratch, and saying so plainly is more profitable than selling him something surplus. A bespoke build is needed where the processes are non-standard.

What need not be bought

Part of the work is covered by what is ready. In the catalogue, Basic plan — over 200 assistants across fourteen directions: for sales, HR, legal, marketing, e-commerce. If the task is standard, an assistant solves it with no development.

Development is needed where the assistant has to know your data, work to your procedure and live in your system. That is the part of the quote that cannot be cut.

The skills section states the income model directly: you go to a client, assemble a set of skills for his processes, train the team — a ready service with a clear result.

What the work consists of

Five lessons of the “AI-Assistants” course show the full cycle: system instructions, copywriting, scriptwriting, marketing and assembling a selling bot that carries a client along a staged funnel.

The key part is not the assembly but the knowledge base. Almost anybody can assemble a bot; extracting from a company what only two people know and reworking it for retrieval is what people pay for.

The “AI-Assistants” course — Creator plan; automation templates — Creator, Make, N8N and Full.

What to take on the platform for this task

What to read next

A company knowledge base as a service — the most labour-intensive part of the project.

The anatomy of a system instruction — the technical part of the work.

AI agents: how they work and what they cost — a real $1 900 deal.

An itemised quote instead of buttons — how to break a price into items.

Also on AI SKILLS