AI Automation in the Workplace: Script or Agent? One Process, Two Bills
The same bidding process can be handled by a script for two thousand or by an agent for twenty. The choice isn’t determined by technology, but by the number of exceptions in your process. We calculate the costs of both options through to the end, including anything that breaks down after six months.

A request for a quote comes in via email; someone enters the data into the CRM and sends back a quote. This process can be automated with a script for two thousand zlotys or an AI agent for twenty thousand. It’s not the technology that makes the difference. It’s the number of exceptions your process actually has.
Below are both options fully costed out using the same example, including maintenance costs and what typically breaks down in the sixth month.
The Same Process, Two Solutions
The company receives one hundred RFQs per month. Each one takes a sales rep about twelve minutes to handle: read it, extract the data, enter it into the CRM, generate a quote, and send it back. That’s twenty hours per month.
Option one: a script. The automation system scans the inbox, recognizes the form, transfers the fields to the CRM, and sends back a template. Development cost: 2,000–8,000 PLN; monthly maintenance: 100–400 PLN. It works as long as the inquiries come in a predictable format.
Option two: an agent. They read a freely written email, understand what the customer is asking, select items from the price list, and formulate a response. Development cost: 15,000–30,000 PLN; monthly maintenance: 800–2,500 PLN.
The price difference is eightfold. The question is, what are you paying extra for?
The only question you need to ask yourself
Pull up your last 100 inquiries and count how many of them could be handled without a second thought.
If eighty or more come in the same format and require the same response, buy the script. The extra cost for an agent would go toward handling twenty cases, and that doesn’t add up.
If half or fewer are repetitive, the script will handle twenty percent of the work and leave the rest for you. In that case, the extra cost makes sense.
This single number matters more than all the tool comparisons combined. Check it before anyone shows you a demo.
What Goes Wrong in the Sixth Month
Both options have their own pitfalls. Learn about them before you choose, not after.
The script breaks when things change. A customer sends an inquiry in a different format, a supplier changes the form layout, or someone adds a field in the CRM. The script doesn’t report an error; it just quietly stops capturing some of the cases. You’ll usually notice this weeks later.
The agent breaks down when things drift. The price list changes, the offering expands, but the agent continues to respond based on outdated information. This isn’t a failure—it’s a slow divergence between the responses and reality. That’s why the subscription fee for the agent isn’t a fee for access, but for continuous fine-tuning.
If the provider doesn’t explain how it detects these two issues, ask. Their answer will tell you more than the entire price list.
Who maintains it when the developer leaves?
The most common scenario for failure has nothing to do with technology.
Someone at the company built the automation because they were interested in it. It worked for a year. Then that person changed jobs, and no one knows where it’s hosted, on whose account, or what will happen if it goes down.
Before you launch anything, figure out three things: whose account the system is on, who else has access besides the developer, and where the documentation explaining how it works is located. It takes half an hour and saves the project.
How much does it cost to maintain?
The monthly bill has three items, and only one is fixed.
The tool or hosting usually costs 30–150 PLN if you host it on your own server. Language model usage with an agent costs 50–300 PLN in a small company and increases with the number of cases, not the number of employees. Technical support costs 200–1,500 PLN, depending on how many processes you have and how often they change.
With a script, the second item is eliminated because there’s no model to pay for. This is the real reason why a simple process should stick with a script.
What happens when you reach out to us
We start by assessing your specific needs, not by demonstrating the tool. The business owner speaks with us; the conversation lasts 45 minutes and concludes with a recommendation for a solution along with a price range.
If the numbers point to a script, we’ll suggest a script—even though it’s eight times cheaper than a human agent. We’d rather have one working implementation than an expensive one that nobody uses.
The first phase covers a single process. After that, you’ll have the data and can decide whether to move forward. The team subscription starts at 3,875 PLN per month, and you can calculate the cost using the calculator before the call. The guarantee covers repairs at no extra charge.
Questions & Answers(FAQ)
Automation follows a set sequence: if A occurs, do B. The agent chooses its own path to the goal and handles situations that no one has described before. For a process with no exceptions, automation is cheaper and more reliable. An agent makes sense when there are many exceptions.
Automating a single process typically costs 2,000–8,000 zlotys, plus 100–400 zlotys per month for maintenance. An agent for the same process costs 15,000–30,000 and 800–2,500 PLN per month. The price difference is due to the number of exceptions that the script cannot handle.
Free automation tool plans are available and are sufficient for a single, simple, low-volume process. You typically pay based on the number of runs, integrations, and the time spent by the person who builds and maintains the system.
Start by analyzing a single process: how many cases there are per month, how much time each one takes, and what percentage is repetitive. Only after you have these figures should you choose a tool. Doing it the other way around—choosing the tool first—is the most common reason for failed implementations.
For simple workflows between systems, n8n, Make, and Zapier work well; n8n can be hosted on your own server, so data doesn’t leave your environment. For tasks that require understanding content, you need a language model connected to that workflow. The choice of tool is secondary to defining the process.
Got a similar process on your side?
If something in this article sounds like your day-to-day - let's talk. We'll tell you plainly what can be improved, and what's not worth touching.
Services related to this topic
AI automation for business
Repetitive work a machine does faster and error-free. AI only where it pays off.
AI agents with integrations
Not another chatbot. An agent wired into your email, CRM and knowledge base that takes over repetitive work.
Custom software with AI
Off-the-shelf tools force you to compromise. We build a system around your process, with AI where it genuinely gives an edge.