Advertising measurement cookies

With your permission, we use Google Ads cookies to measure whether our ads lead to an enquiry. Rejecting does not affect the contact form. You can change your choice later through Cookie preferences. Read our privacy statement.

Skip to content
KeyClicks

KeyClicks · automation for recurring work

You gain capacity, without having to find someone for it.

For the work that comes back every week: reading portals, comparing prices, filling in forms, putting reports together. You show us once how it goes.

We build it, we run it, and we keep it running when your supplier changes their portal. Your people learn nothing new.

recurring workMONTUEWEDTHUFRIall togetherKeyClicks
Where the week goes.
hatched
the work that comes back every week
outlined
one working day, Monday to Friday

Situations

Three situations where this pays off straight away.

If you recognise one of them, the conversation is worth having. If you recognise all three, we are probably talking about more than one process.

vacantstill open

The vacancy that stays open

You are looking for someone to do work that is mostly retyping, and nobody applies. Meanwhile someone is doing it on the side. This part no longer has to wait for an applicant.

invoice128.5064.00administration128.5064.00the same figures, again

The pile nobody misses

Logging in, copying figures across, comparing, filling in, sending. It has to happen and it produces nothing new. That is exactly the part we take away; the work the company lives on stays where it belongs.

extensionadministration

The business grows, and so does the admin

Twice as many suppliers is currently twice as much checking. Once this part is automated, it does not grow with you. You can take on more without adding a person at every step.

What it is worth

What it gets you.

No percentages and no promises about saving. This is what concretely changes about your week.

It is there before the first coffee is finished.

The job runs at a fixed moment, Monday morning at seven for example. By the time your people come in, the files are there.

Checking at a scale no one can sustain.

A person checks a sample and stops when the time is up. The system sets every line against what was agreed, every single time. If something is off, it is there in figures, with the proof beside it.

The process stays, even when the person who did it has gone.

At a lot of companies a process like this lives in one person’s head. We write it down and we keep it up to date. When someone leaves, the work does not leave with them.

Your people learn nothing new.

No program, no account, no rollout. Nothing changes about how they work, except that this part is no longer part of it.

Work this suits

Anything that happens on a computer.

There is no fixed list. Often it is work that comes back every week or every month, that runs through more than one system, and where someone currently copies data from one screen into another. But that is a pattern, not a requirement. Three examples, written out the way they actually go.

  • 01

    Process an order from start to finish

    Read an order from an email, check stock, enter it in your system and prepare the confirmation. If something is missing, you receive a specific question.

  • 02

    Turn incoming emails into completed work

    Recognise a request, read the attachments, look up information and carry out the right steps in your systems. When a decision is needed, the system asks for your approval.

  • 03

    Files and documents

    Retrieve and upload files, update spreadsheets and create documents.

  • 04

    Checks and administration

    Compare prices, orders and agreements, with discrepancies in an overview.

See more examples

Yours not here? Surprise us with your workflow. If it happens on a computer, we will gladly work out how to rebuild it.

In short

Five steps, and one gate you have to pass.

The system logs in, reads what is there, compares it against what was agreed, fills in and delivers. At steps that cannot be undone, it stops and asks for your approval.

log inreadcomparefill insendyour approval

The course of one job.

How it works, in full

The film

See how it works

What you get

The files. And one page where you see what happened.

No program to learn and no account to manage. You open a link and see, per automation, the most recent jobs with the files that came out of them beside each one. If something fails, it says so plainly, and we are already on it before you call.

  • done
  • running
  • waiting for approval
  • failed
  • stopped
Example · overview

This work is done.

The results of your tasks in one place.

  • Order processed

    Entered in your order system.

    Completed
  • Email requests processed

    Details and attachments transferred.

    Completed
  • Overview compiled

    Your spreadsheet is ready.

    Completed
View the results

Your hand on the switch

Nothing irreversible without you.

Sending, ordering, paying, making something final: at steps like those the job stops and the question reaches you, with the details it concerns. Say yes and it continues. Say no and it stops there.

If no answer comes, the step does not go ahead anyway.

Safeguards and limits

Introductions

Show us one process.

No quote from a distance and no estimate up front. You show us how the work goes now, we tell you whether we can do it and what it costs. If we do not see it working, we say that too.

Book an introduction