Twice the work, with the same people.
Your team doesn't get more efficient by working longer hours — it gets more efficient by taking fewer manual steps. We take the re-typing, the chasing and the forgotten follow-up out of the process.
Where does the time leak away?
Not on the big things. On the ten- and twenty-minute steps nobody counts, because “I'll just type it in quickly”.
Manual re-typing
The same data three times: it arrives by e-mail, goes into a spreadsheet, then into the invoicing system. Every round is another chance for a typo.
Forgotten follow-up
The quote went out and then nobody chased it. The lead wasn't lost because they didn't want it — but because nobody got back to them in time.
Status chasing
“Where are we on this?” — and round goes the group e-mail. The answer is already in the system; it just doesn't reach the people who need it on its own.
Cobbling reports together
A few hours every month: copy out the ad data, assemble a document, send it. The same sequence of moves, month after month.
Payment reminders
Somebody has to notice the overdue invoice, then write an awkward e-mail. Usually late, sometimes never.
Onboarding from memory
A new client starts and the twelve-step list lives in someone's head. Whatever gets missed surfaces two weeks later.
What exactly do we automate?
Every workflow is built the same way: there's a trigger, it runs a sequence of steps, and it produces an outcome nobody has to remember. Open any of them.
Client acquisition
2 workflows- Trigger: someone submits the contact form.
- The lead lands in the CRM, tagged by source and campaign.
- A confirmation e-mail goes out within thirty seconds — not boilerplate, but a reply to what they actually filled in.
- The colleague responsible gets a notification on WhatsApp or Slack with the lead's details.
- If nobody has opened it within 15 minutes, the system escalates to the manager.
- Trigger: the lead's status changes to “quote requested” in the CRM.
- The system fills the quote template from the CRM data and generates a PDF.
- The quote goes out by e-mail, with opens tracked.
- If there's no reply: reminders on day 3, 7 and 14 — each in a different tone.
- As soon as they reply the follow-up sequence stops and the colleague is notified.
Project management
2 workflows- Trigger: a project changes phase (e.g. “shoot complete” → “post-production”).
- The tasks belonging to that phase are created automatically, with an owner and a deadline.
- The owner gets a notification, and a reminder one day before the deadline.
- If the deadline passes with the task still open, the project lead is alerted.
- The project status updates itself — nobody has to ask.
- Trigger: the contract is signed and the deal moves to “won”.
- The project's folder structure is created, with the right access rights.
- The client receives the intake list (logos, access, contacts).
- A proposed time for the kick-off call goes out.
- Whatever is missing from the intake list is chased by the system — not by the project lead.
Finance
2 workflows- Trigger: delivery is marked complete on the project.
- The invoice is issued and sent from the CRM data, with no manual entry.
- A friendly reminder 8 days after the due date.
- A second, firmer reminder after 15 days.
- After that it escalates internally so someone can settle it by phone.
- Trigger: a check that runs after the daily close.
- The system totals Google and Meta spend by account.
- It compares that with the monthly budget and the run rate so far.
- If an account runs over the threshold, an alert goes straight to the campaign manager.
- A weekly summary of budget status, client by client.
Marketing operations
4 workflows- Trigger: the close of a week or a month.
- The system pulls the Google Ads and Meta data from the client's accounts.
- It assembles the report in the usual structure, compared with the previous period.
- The campaign manager reviews it and adds the written analysis.
- Once approved, the PDF goes out to the client.
- Trigger: the client approves a post in the calendar.
- The post is scheduled automatically to the right platforms.
- After publishing, the calendar entry switches to “published”.
- After 48 hours the performance data is written back into the calendar.
- At the end of the month you can see which content type worked.
- Trigger: the project is closed and handover is complete.
- A few days later a short question goes out: how satisfied were they?
- If the answer is positive, the Google review link follows.
- If it's negative, it doesn't ask for a public review — it raises an internal flag instead.
- The feedback is recorded in the CRM on the client's record.
- Trigger: a value changes in any of the connected systems.
- The related records are updated across the CRM, the invoicing system and the ad accounts.
- On a conflict it doesn't overwrite blindly — it flags it.
- Changes are logged and traceable.
- A monthly check looks for discrepancies between the systems.
The anatomy of a workflow.
This is what the lead-response process looks like. One trigger, one decision point, parallel actions, and finally a notification plus a safety net for when something stalls.
Wide diagram — scroll sideways on a narrow screen
Run it on your own numbers.
Set how many people do repetitive admin at your company and how much time it takes. The calculator works from your inputs — there's no promise baked into it.
Not just assistants — anyone who re-types data or writes reminders.
The sum of those ten- and twenty-minute steps on an average working day.
Total employer cost, per hour.
- Per year0 h
- In wage cost / month0 HUF
- In wage cost / year0 HUF
That's the equivalent of 0 full-time people — capacity freed up to take on new work.
hours freed / month = people × hours per day × 21 working days × 0.7 · the 0.7 is the assumed share that can be automated
The calculator works from the inputs you give and is indicative only. Actual savings depend on your processes and the systems you use — the process audit is what measures that precisely.
What does this look like in practice?
A modelled scenario with typical values so the logic is visible — not any specific client's data.
An 8-person team, 2 of them mostly on admin
The starting point: two people's time goes every day on lead response, quote follow-up, reporting and invoice reminders. These are the four processes we automate.
This many steps across the four processes run without human intervention in the model.
70% of two people's time — which isn't a headcount cut, it's labour that can be redeployed.
If the freed capacity moves to sales and delivery, without adding headcount.
A modelled example with typical values, not any specific client's data. The ≈+30% follows from the freed ≈1.4 FTE being ~17% of an 8-person team's working time, which — redeployed to value-creating work rather than admin — produces proportionally more output. Your own case depends on your processes; the audit is what measures it.
What we don't automate.
An automation is good because we know where to stop.
Creative decisions
What the message should be, what the image should look like, what the brand sounds like — that's a human job. Automation at most delivers it to the right place.
Client negotiations
Handling objections, pricing, delicate situations. A canned reply costs more here than it saves.
A messy process
A bad process automated is just bad faster. We sort it out first, then connect anything.
Sending without review
Anything that reaches the client keeps a human approval step. The report assembles itself — but it doesn't go out unread.
How we work.
We start with one process, not the whole company. That way results show up quickly and the team gets used to it.
Process audit
We go through how things work today and where the time goes. Typically one week.
Workflow map
You get what's worth automating, in what order, and what each one returns.
Pilot
One process taken live — the one with the biggest gain and the smallest risk.
Go-live and training
The team learns what happens by itself and what stays with them. Error handling and notifications configured.
Measure and tune
We check whether it actually saved time, and move on to the next process from there.
Transparent packages.
Prices are indicative starting points — the exact quote depends on the number of processes and the systems to be connected.
- Process audit with interviews
- Workflow map with priorities
- Estimated saving per process
- Credited against the next stage if you continue
- One process fully automated
- System integration and testing
- Error handling and notifications
- Training for the team
- 30 days of follow-up
- 4–6 processes automated
- Data sync between systems
- Documented process descriptions
- Monthly maintenance from 39 000 HUF/mo
- Quarterly review
Frequently asked questions.
Which systems does it work with?
Most systems that have an API or a webhook: Google Workspace, Meta and Google Ads, invoicing software, online stores, Slack, WhatsApp, e-mail. With our own CRM, deeper integrations are available too. At the audit we go through whatever you use today.
How long until the first workflow is live?
The process audit typically takes a week, and the first live workflow another one to two weeks after that. We deliberately start with a single process: results show up quickly and the team gets used to it.
What happens if an automation breaks?
Every workflow gets error handling and notifications: if a step fails, a human is alerted and the process doesn't die quietly. Fixing failures is included in the maintenance package.
Do we need a developer or IT person in-house?
No. We handle the integration and the running of it. What we need from you: access to the systems, and one person who knows the process we're automating.
What if our processes are a mess?
Then we sort them out first. A bad process automated is just bad faster — the audit exists precisely so this comes out before anything is connected.
Let's start with a process audit.
We look at where your time goes and what's worth automating first. If we don't find a meaningful saving, we'll tell you that too.