Automation
Work that stops being done by hand.
Built on the operation the company already has: something arrives through a channel they already use, gets processed, and comes out where they already work. Nothing new to install, no change in how the team works. The assessment costs COP 240,000, is included today, and is credited if the work is hired.
What counts as an automation
One question decides it:
Does someone do this by hand today, more than once a week?
If the answer is no, it isn't an automation: it's a new product feature, and that is quoted differently. And whatever the system already does — charging, invoicing, flagging due dates, scheduling — isn't charged again. If the team is doing it by hand, it's because they don't know they have it, and the workshop solves that.
The pattern
- 01
It arrives
Through the channel the company already uses. In Colombia almost everything arrives by email: the bank notification, the electronic invoice with its XML, résumés, orders.
- 02
It gets processed
Read, understood and checked against whatever applies. No banking credentials, no account access, no API the provider won't give.
- 03
It comes out
Where the team already works. No new inbox to check, no extra system to log into.
What gets built
Five, on the same pattern. The first is the most requested in Colombia; the third is the one Sonika uses for its own mail, every day.
-
Payment receipts, actually verified
The customer pays by Nequi and sends a screenshot. There are apps that generate receipts identical to real ones, and the merchant hands over the goods before the money arrives. You don't verify by looking at the image: you check it against the email the bank sends the merchant — amount, date, time. Real or fake, in seconds.
-
Electronic invoices, sorted all year
Every electronic invoice arrives with its XML. Instead of piling up unopened until the accountant asks, they're read on arrival and stay classified and totalled from January.
-
Mail that sorts and answers itself
Running at Sonika todayReads what arrives at the domain, understands what it's about and drafts the reply inside the same thread. No new inbox, no interface to learn.
-
Social content, with rhythm
Written once; each network gets its version. The work that today makes you post three weeks straight and then never again.
-
Résumés, sorted
They arrive by mail in five different formats. Read, the relevant fields extracted, and left comparable to each other without anyone transcribing them.
How it's charged
- Assessment
- We look at the operation and say what can be automated and what can't. Credited if the work is hired.
- Construction
- Estimated against what has already been built, not by adding up imagined tasks. Most fall between one and five days. Past ten it isn't an automation: it's a new product, and we say so.
- Operation
- For as long as Sonika keeps it alive.
COP 240,000 · included today
by days
COP 100,000/mo each
Why there's a monthly fee on something already built
Because automations break silently. The bank changes its email format, a supplier changes a form, and it stops working without telling anyone. The fee pays for someone to notice and fix it before the company does. It's the price of two or three coffees a day, against the COP 2,715,572 a month the person doing that work would cost.
Questions
- What counts as an automation?
- One question decides it: does someone do this by hand today, more than once a week? If yes, it is an automation. If no, it is a new product feature and it is quoted differently.
- How much does automating a process cost?
- The assessment costs COP 240,000, is included today and is taken off the total if you hire the work. Construction is estimated by days and starts at COP 540,000. After that there is COP 100,000 per month per automation.
- How long does it take?
- Most automations land between one and five days of work. The estimate comes from comparing against what has already been built, not from adding up imagined tasks. Past ten days it stops being an automation, and we say so.
- Why is there a monthly fee on something already built?
- Because automations break silently. The bank changes its email format or a supplier changes a form, and it stops working without warning. The fee pays for someone to notice and fix it before you do.
- Do we have to change tools or install anything?
- No. The automation comes in through a channel the company already uses and comes out where the team already works. Nobody changes habits: that is the condition for it to be adopted.
- What if the system already does what I need?
- It is not charged again. Charging, invoicing, flagging due dates and scheduling are already included. If the team is doing it by hand, they do not know they have it, and the workshop solves that.
What are you doing by hand?
Tell us the process and we'll say whether it can be automated, how long it would take and what it would cost. If it can't, we say that too.
Let's talk