Bots and AIfor business

AI assistant development
for business.

An assistant for your team: finding information in documents, preparing drafts and helping with repetitive tasks. Before we start, we agree on data sources, access, capabilities and running costs.

Discuss the assistant's task

from $200

Let's start with one clear task

These are examples of possible tasks, not completed client projects. For the first launch, we choose one main scenario.

Find a rule

An employee asks a question about an instruction and gets an answer with the source, in a supported, agreed format.

Prepare a reply

The assistant assembles a draft from approved materials; a manager checks the facts before sending.

Create a document draft

The assistant fills in an agreed template from the source information; an employee reviews and approves the result.

How wework

How a scenario might work

An example for discussion. We define the sources, actions and human involvement for your task before development.

Employee's question
An authorized user contacts the assistant through the chosen private interface.
Search
The assistant looks for information in the agreed set of available materials.
Answer or draft
Prepares the result and cites the source where the chosen solution supports it.
Human review
An employee checks the facts, clarifies contradictions and makes the final decision.
Use
The employee uses the approved result. Sending emails or changing systems requires a separate scenario.

01 / 04

One process, one group, one interface

The base scope is one work process, one group of employees with identical permissions, one interface and an agreed set of materials. For example, a private chat on the website or a Telegram bot for authorized users.

We'll set up answer search across the materials and draft preparation from agreed templates. Included are two rounds of compiled revisions within the approved scope, testing, launch, access and short instructions. We'll confirm whether source links are possible and in what format before work begins; if they aren't available, we'll agree on the limitation and another way to verify in advance.

02 / 04

Materials must be suitable for use

You decide which instructions, product descriptions, regulations and templates are permitted. After reviewing a sample, we'll fix the volume, formats, freshness and update method. We don't set a universal limit on documents or users.

Scans, complex tables and contradictory instructions may need separate preparation. New sources and regular knowledge base updates are estimated separately. Automatic updating of materials is not implied: if needed, we'll include it in the estimate as a specific feature.

The employee checks the result and decides

03 / 04

The first launch covers reading materials and preparing drafts. The assistant helps find and compile information, and an employee checks it before use. The model can make mistakes; we don't promise error-free operation, full replacement of an employee or a specific number of hours saved.

Changing a CRM, sending emails, creating orders and other actions are separate scenarios. For each, we agree on permissions, employee confirmation and action logging. We check what ready-made integrations can do before including them in the scope.

04 / 04

Document access based on permissions

We agree on sources and permissions before starting

The client defines the users and the permitted materials. If a head and a manager need different sets of documents, we estimate, implement and test the permission separation separately. We don't rely only on asking the model not to show a private document.

Before we start, we agree on the external services that process documents and correspondence, where data is stored and how it's deleted. Terms depend on the chosen platform; we don't automatically promise local storage. Where possible, we register accounts under the client.

We agree on the checks before development

We define test cases and expected behavior in advance. At handover we check them on the finished solution; these are criteria for the future work, not results already achieved.

The answer is in the materials, and the source is cited in the agreed, supported format.
If there is no answer, the assistant says so.
Documents that contradict each other are flagged rather than turned into a confident conclusion.
A user without permission does not get private materials.
An action outside the permitted authority is not performed.
The draft matches the template and the source facts; the final decision remains with the employee.

An estimate for your task

from $200

Tell us what problem you need to solve and what result you want. After we discuss it, we'll agree on the scope of work, a fixed price and a deadline. A detailed technical specification isn't required for your first inquiry.

If we need to study the process in detail, review sample materials or check connections, we'll agree in advance on a paid assessment and its deliverable: a solution outline, the boundaries of the work and an estimate. The assessment is paid in full before it starts. You can receive it as a standalone deliverable; if you order the implementation, the payment is credited toward the total price.

Terms of
work.

Implementation and running costs are separate

We subtract the already paid assessment from the total agreed price. The remaining amount is split: 25% before implementation and 75% after the result is checked. The assessment is not paid for twice. We estimate additional scenarios and scope changes before work begins.

Platform subscriptions, the AI model, API, hosting, storage and paid connections are billed separately. Before the start, we'll show the expected costs for the agreed number of requests or operations and state our assumptions. Costs may change as the load grows; we'll set up limits and notifications wherever the service allows it.

Launch, handover and fixes

We'll hand over the working agreed scenario, client access and short instructions. Where possible, accounts are registered in your name. Acceptance is recorded by your dated confirmation in the agreed channel. For 30 days from confirmed acceptance, we fix errors in our implementation free of charge, within the agreed scope.

New tasks, material updates, adapting to changes in third-party services and ongoing support are estimated separately. If the planned failure handling was implemented incorrectly by us, that is our error. Website support plans do not automatically apply to bots and automation.

If the project is handed over without further maintenance, you revoke our permissions and change the passwords and keys known to us, following a list. We record what was handed over, ask for confirmation and remove our own access where we can. For agreed ongoing support, we keep only the necessary permissions.

Before launch.
Questions and answers.

How is this different from a visitor bot?

The internal assistant works on an employee's task and the team's approved documents. The website customer consultant is a separate service.

Can we upload all documents at once?

First we review a sample, quality, formats and rights. We define the contents of the knowledge base and its preparation for each order, with no blanket promise to handle any volume.

Will it provide source links?

We confirm support and format before work starts. If the chosen solution doesn't support them, we agree on the limitation and an alternative way to verify answers in advance.

Can the assistant send emails and change the CRM?

The basic mode is reading and drafts. Actions are estimated separately, with permissions, employee confirmation and a record of the result.

Will documents update automatically?

Only if this update method is included in the agreed scope. Regular manual updates and new sources are discussed separately.

Will our documents stay local?

That depends on the chosen architecture and services. We agree on storage location, external processing and deletion before starting; we don't promise local-only storage by default.

Other tasks

Describe your task in your own words

Describe the process, website or channel, the systems you use and the result you need. We'll discuss sample documents and access later in an agreed channel. Don't send passwords, keys or confidential materials through a public form.