All articles

Automation

Five everyday tasks worth automating first

July 14, 20266 minute readNexwawe Infotech

The first thing a team automates should not be the most impressive thing they can think of. It should be the thing that happens every day, follows the same rules every time, and annoys someone. Those three properties make it cheap to build, easy to verify, and obvious when it works.

1. Copying data between two systems

Someone exports from one tool and pastes into another: an order into the accounting system, a lead into the CRM, a delivery into a spreadsheet. It is the single most common piece of manual work we are asked to remove, and it is usually the easiest, because both systems already have APIs.

The reason it is worth doing first is not the time saved. It is that the copy step is where data quietly diverges. Once the two systems are connected, the reports on both sides start agreeing with each other.

2. Generating the same document with different names on it

Invoices, certificates, letters, invitations, statements. The template is fixed, the data comes from a list, and a person is doing a mail-merge by hand because the real version has to look right.

We built exactly this for a campaign product: recipients imported from a spreadsheet, personalized documents generated per recipient, and delivery tracked per person. The build is modest, and the manual version scales terribly. 500 recipients is 500 opportunities to put the wrong name on the wrong document.

3. Chasing people for a response

Reminders before a deadline, follow-ups on an unpaid invoice, nudges for an unanswered RSVP. This is work that has to happen on a schedule, which is precisely what people are worst at and software is best at.

The trick is to automate the sending but keep a person in charge of the exceptions. Scheduled reminders go out on their own; anything that comes back confused lands in a queue for a human.

4. Reading numbers off documents

Invoices, labels, forms, delivery notes, receipts. Someone is looking at a document and typing what it says into a field. OCR handles the reading, and rules or a model handle the interpretation.

This is the one place where we insist on a confidence threshold and a review step. Extraction is usually accurate, but a confident wrong number in a financial or inventory system is worse than no number at all, so anything ambiguous gets escalated rather than guessed.

5. Assembling the weekly report

Every Monday someone pulls figures from three places into a deck or a spreadsheet. The inputs are always the same, the format is always the same, and the work is always done by the person whose time is most expensive.

Automating the report has a second benefit: once the numbers are generated on a schedule, people start looking at them more than once a week.

How to choose between them

If more than one of these applies to you, pick using frequency and blast radius rather than ambition. Something that happens daily and cannot break anything important is the ideal first project. You find out whether the approach works before you have bet much on it.

  • How many times a week does it happen?
  • Does it follow the same rules every time, or does it need judgement?
  • If the automation got it wrong, who would notice, and how fast?
  • Is the data already in a system, or does it start on paper?

Talk it through

Is this the problem you are working on?

Describe your workflow and we will tell you what we would build first, and what we would leave alone.

Start a project