Business Process Automation When a Company Has No IT Staff
Guides on automation start with mapping the process. At a company with 25 employees, the process isn’t documented anywhere, and there’s no one to do it. We show you how to choose your first process without an analyst on the team, how much it actually costs to handle it manually, and how to back out of automation that didn’t work out.
In a company with 25 employees, the most expensive systems are usually a spreadsheet and someone’s email inbox. No one calculates it that way, because the cost is spread out over twenty people at twenty minutes a day. Calculate it honestly just once, and you’ll find it amounts to a full-time position per year.
Every guide to automation starts the same way: map out the process. The problem is that in a small company, the process isn’t documented anywhere, and the person who knows it is currently on vacation. Below is a version for companies without an analyst or an IT department.
How to find the first process when no one has documented it
Don’t try to map the entire company. Ask one question to three people from different departments.
The question is: What are you doing this week for the umpteenth time, and in exactly the same way every time? Not “what’s the problem,” because everyone will give a different answer to that. It’s about repetition.
The answers are usually similar. “I’m transcribing data from an email into the system.” “I’m looking for an attachment someone sent last month.” “I’m compiling a report from three different sources.” “I’m following up on documents.”
Pick the ones that came up at least twice. You’ve got a candidate without a single skill.
How much does this process really cost?
Now do the math, because without numbers, there’s still nothing to talk about.
Take three figures: how many times a month this happens, how many minutes each repetition takes, and how much that person’s hourly wage costs, including overhead. Multiply them.
A real-life example: A salesperson transcribes 100 inquiries per month, spending 12 minutes on each, at an hourly rate of 90 PLN. That’s 20 hours and 1,800 PLN per month—or over 21,000 PLN per year—for tasks that no one even notices.
You also have to factor in errors. A single mistake in a quote can cost more than an entire month of data entry.
What Not to Automate First
We advise against automating these three types of processes at the start, even though they seem tempting.
Rare processes. Something that happens once a quarter won’t pay for the implementation costs, even if it’s the most annoying thing imaginable.
Controversial processes. If two people describe the same sequence of events differently, that’s not a technical problem—it’s an organizational one. Automation will lock in one person’s version.
Processes involving decisions about people. Hiring, employee evaluations, granting discounts to customers. This isn’t about technology; it’s about the fact that the AI Act requires human oversight of such decisions, and that oversight must be designed.
Who will maintain it when the creator is gone?
The most common failure has nothing to do with technology.
Someone built an automation system because they were interested in it. It worked for a year. Then they changed jobs, and no one knows where it is or what will happen if it breaks down.
Determine three things before launching: Who owns the system? Who else has access besides the creator? Where is the documentation explaining how it works? It takes half an hour of work, but it saves the project.
How to back out if it didn’t work out
No one writes about this, yet the question comes up in every conversation.
Good automation can be turned off without paralyzing the company. Check this during the project phase, not a year later. Ask whether the data remains in your systems or in the vendor’s tool. Can you export the history? Can people still do this manually if they need to revert?
If the company grinds to a halt after turning off the automation, then it wasn’t process automation. It was simply moving the process to someone else’s system.
What happens when you reach out to us
We start with your numbers, not by demonstrating the tool. The business owner speaks with us; the conversation lasts 45 minutes and ends with identifying the process that will pay for itself the fastest, along with a price range.
If the conversation reveals that your situation fits neatly into a template in a spreadsheet, we’ll tell you straight up. Not every problem requires a full implementation.
The first scope 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)
It involves shifting repetitive, rule-based tasks from people to a system. Instead of manually transferring data between email, spreadsheets, and a CRM, this is handled by an event-triggered workflow. Automation makes sense for processes that occur frequently and have a quantifiable cost.
Start with one question asked of three people: “What are you doing this week for the umpteenth time, and in exactly the same way each time?” Whatever comes up twice is your top candidate. Then do the math: number of repetitions times duration times hourly cost.
Traditional automation handles rules: if A occurs, do B. AI adds a layer of interpretation where data is unstructured: recognizing the intent of an email, extracting data from a document, classifying a ticket. In a process with no exceptions, AI is an unnecessary expense.
A simple data flow between two systems typically costs 2,000–8,000 zlotys and 100–400 zlotys per month. Three factors drive up the price: the number of integrations, the number of exceptions in the process, and the condition of your data. Cleaning up the data can sometimes be a bigger expense than the development itself.
Rare processes, because they won’t be cost-effective. Processes that two people describe differently, because the problem is organizational, not technical. And decisions involving people, such as hiring or employee evaluations, where the AI Act requires designed human oversight.
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.
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.
AI agents with integrations
Not another chatbot. An agent wired into your email, CRM and knowledge base that takes over repetitive work.