Process automation
Data flowing from system to system without anyone copying and pasting.
Most companies do not have one big problem. They have twenty small ones: a file to move, a field to type in twice, a message to forward. Each takes three minutes, and together they take a working day every week.
We find them, and we remove them. That rarely calls for new systems — it calls for the systems you already have to start talking to each other.
Walking the workflow
We follow a task from the moment it appears to the moment it is done, noting every time a person moves data without adding anything.
Prioritising by time saved
Not everything should be automated. We put numbers on what each one saves, so you can take the three biggest and leave the rest.
Mapping the systems
What can talk to what, what cannot, and where there is a back door. That decides what is cheap and what is expensive.
Integrations between systems
We connect your tools so information is entered once. Commerce platform, finance system, CRM, spreadsheets, CMS.
Triggers and events
When something happens in one place, the right thing happens in another. A new order creates a task, a submitted form creates a customer, a failed payment sends a message.
Monitoring what runs
Automations that fail quietly are worse than no automation. Everything we build speaks up when it goes wrong.
One automation in a week beats ten in six months
We start with the single task costing you the most time, and have it running within a week. Then you can feel the difference before deciding how much more to automate. It is also the cheapest way to find out whether we work well together.
See packages and pricingHow we deliver
The same approach whatever the area. You can stop after each phase, and you know what the next step costs before agreeing to it.
We map it out first
Ninety minutes going through your processes to work out what can genuinely be automated. You get a clear picture of what is possible and what it would cost.
We build on a fixed price
One- to two-week sprints, each ending in a demo. You know the cost before we start, and you own the code afterwards. No lock-in, no long contract.
We keep it running
Service plans covering maintenance, support and extensions as the business changes.
Is this the right place to start?
If two or more of these sound familiar, there is usually something to gain. If none do, we would rather say so now than after a proposal.
- The same information is typed into two or more systems
- Someone exports a file in order to import it somewhere else
- Errors happen because one system is a day behind another
- You spend time gathering numbers rather than using them
What we have built
Questions we get asked
Do we have to replace our systems?+
Rarely. That is more expensive, takes longer and meets more internal resistance. We build on top of what you have by default. If a system is so closed that it cannot be done, we say so — but that is the exception.
What happens when an automation stops?+
You should know before your customers do. Everything we build speaks up when it fails, rather than failing quietly. How critical it is decides whether the message goes to an inbox, a chat or a phone.
How long does it take?+
A single automation usually takes a week from the start. A coherent set of three or four takes about three weeks. We always begin with the one that saves the most time, so you see the effect before the rest is finished.
Can we change it ourselves afterwards?+
Up to a point. We usually put the things that change often — thresholds, recipients, wording — in a spreadsheet or file you can edit. The logic itself needs us or another developer.