🎉 Black Friday Sale starts soon! 23 Save the date

0Days

0Hours

0Minutes

0Seconds

Home / Services / AI and automation / Workflow automation

Workflow automation

The copy, paste and chase work, done by software

We map a process as it runs today, then automate the steps that follow rules: through APIs where systems offer them, RPA where they do not, AI for steps that need reading, and a person for the decisions.

What you get
  • A map of the current process and the automated version
  • Automations built on a platform agreed with you, such as Power Automate, n8n, Make or custom code
  • Exception queues and review screens for steps that need a person
  • Run logs, alerts and a named owner for each workflow
  • Runbooks explaining how each automation works and how to pause it
  • Training for the team that will own the workflows

What is included

The work, piece by piece.

Process mapping

We sit with the people doing the work, record each step, and agree which steps to automate, which to keep and which to drop.

Approvals and routing

Purchase requests, leave, expenses and discounts routed by amount, department and role, with reminders and escalation in Microsoft Teams, Slack or email.

System-to-system flows

Orders, customers, stock and payments synced between your store, ERP, CRM and accounting system, with retries when a call fails.

RPA where there is no API

Software robots that work through the screens of older desktop or web applications, monitored so a changed screen is noticed the same day.

AI steps inside the flow

Classifying requests, extracting fields from attachments and drafting replies, each with a confidence threshold and a review step below it.

Run logs and alerts

Every run recorded with its inputs, outputs and decisions, and an alert to the owner when something fails or waits too long.

Signs you need this

When teams usually call us.

01

Only one person knows how the process works

When they are on leave, the work waits, and nothing about it is written down.

02

The same data is typed into two systems

Orders entered in the store are keyed again into the ERP, and the two rarely match at month end.

03

Approvals stall in someone's inbox

Requests sit unread for days, and nobody can see where they are without sending another email.

How we work

No surprises, start to finish.

Talk to the developers doing the work, by email or call, whenever you need.

01

Talk

Tell us what you need. We ask questions until the scope is clear.

02

Plan and quote

A clear scope with an hourly, fixed or monthly-hours price.

03

Build on staging

Every change is built on a staging site first, never on your live site.

04

Sign off and launch

You review and approve. Then we go live with zero downtime.

05

Care

We stay on for updates, fixes and new features, if you want us to.

For agencies

Your development team for WordPress, under your name.

Agencies around the world send us their builds on WordPress. We do the work, you keep the client, and our name appears nowhere.

White-label

Your brand on everything. No Elicus credit, ever.

NDA-friendly

Happy to sign yours before we see a brief.

Scale on demand

We grow the team to fit the project.

Your terms

Something specific in mind? We'll talk it through.

Questions

Before you ask.

Which automation platform do you use?

It depends on your systems and who will maintain them. Power Automate suits companies on Microsoft 365, n8n fits when you want to self-host, and custom code fits flows with heavy logic. We recommend one in writing, with reasons.

Is RPA a good idea?

Only where there is no API. Screen-based robots break when a screen changes, so we treat them as the last option and monitor them closely.

What happens when an automation fails?

The run stops at a safe point, the item goes to an exception queue, and the owner gets an alert. Retries are designed so the same entry is never posted twice.

Can our team change the workflows later?

Yes. Each workflow is documented, and where the platform allows it, your team can adjust rules, amounts and recipients without a developer.

Start a project

Tell us what you’re building.

A few lines is enough. The developers who will do the work read every message.

What do you need?