Pass on a request
Receive data from a form, check required fields, create a record in the agreed system and notify the person responsible.
Automationbusiness processes
Business process
automation.
Requests, notifications and data transfers don't have to be handled manually. We'll connect the systems you use and implement one repeatable scenario with a clear result and human involvement where it's needed.
Describe your processFrom $200
One process.
A clear result.
These are examples of possible tasks, not completed client projects. For the first launch, we choose one main scenario.
Process a document
Extract the agreed data, prepare the result from a template and pass it to an employee for review.
Connect services
Pass selected data between systems in the agreed direction, with checks for duplicates and errors.
What do you do manually every day?
Describe your processThe logicof the process
From event to result.
An example for discussion. We define the sources, actions and human involvement for your task before development.
Source
A request arrives from a form or an event from a connected system.
Check
The scenario checks the fields and determines whether the event has been processed before.
Action
Writes the agreed data to the target system.
Result
Records completion and sends the planned notification.
Exception
On error, notifies the person responsible; retry and manual recovery follow the agreed rules.
First, we'll sort it out.
One operation with a clear result
We start with a small process: we define the source, trigger event, actions and result. We agree on test data, exceptions and the employee's role, then test the scenario on a limited volume before launch.
Full CRM implementation and sales department setup are not part of this offer. Additional operations, exchange directions and custom integration modules are estimated separately.
Not every automation needs AI
If a task can be described by exact rules, we use regular automation. We add AI when needed, for example to interpret free text or prepare a draft for an employee.
n8n and Make are tools that can connect the steps of a process. We choose a solution based on connections, load and costs, not for the sake of a particular name. A person reviews AI output where the scenario provides for it.
We check connections before promising a result
We find out what data can be received and sent, whether an API is available, and what permissions, limits and plan are needed. We use a ready-made integration if it covers the task; a service name appearing in an integration catalog does not by itself confirm the needed function.
We define in advance the exchange direction, duplicate handling rules, log, notifications, retries and a manual recovery method. One-way data transfer does not mean full two-way synchronization.
Data and operation under your control
We agree on the permitted data, external services, storage location, access and deletion procedure. We determine the necessary permissions and a secure way to share keys separately from the public form.
We'll assign someone responsible for notifications and manual exceptions. Regular monitoring, process changes and support are not implied by one-time development; we agree on their scope and cost separately.
We'll test the scenario.
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.
- Normal input produces the agreed result.
- A repeated event is handled by the rules, without accidental duplicates.
- Invalid or incomplete data does not trigger an unconfirmed action.
- Service unavailability triggers the planned retry or notification.
- The log and manual recovery help sort out an unfinished operation.
- If AI is used, it passes the agreed test cases and hands a disputed result to a person.
Price, launch
and handover.
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.
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.
Do I need AI to route requests?
Not necessarily. Regular automation is enough for clear rules. We consider AI if you need to work with free-form text and other unstructured material.
Can you connect our CRM?
We'll check the available API, ready-made integrations, permissions and plan. We'll confirm the specific data and actions before adding the connection to the order.
What happens if something fails?
Before development, we'll agree on retries, duplicate protection, notifications and manual recovery. At delivery, we'll test the planned situations.
Can we start with one operation?
Yes. We'll pick one scenario and a set of test examples. Once it's verified, the next processes can be estimated separately.
Who maintains the scenario after launch?
You or your specialist, following the instructions we hand over, or us under a separate agreement. Fixing our errors during the first 30 days from confirmed acceptance is included.
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.
Describe your process