The work somebody in your company does by hand every week, and which to automate first

Most companies do not have an AI problem. They have a person who spends part of every day copying things from one place to another, and nobody has ever asked why a person is doing it. This post is for the owner who suspects that is true of their business and does not know the words for what comes next. No vocabulary is needed to read it.

How to recognise one

The jobs worth automating share a shape, and you can see it without understanding anything technical.

• It happens the same way every time. Not similar. The same. The person doing it could describe the steps to a new hire in an afternoon.
• It moves information between two systems that do not talk. An inbox and the accounting software. A form and the calendar. Ads Manager and a spreadsheet. The person is the join.
• Nobody decided it should work this way. A spreadsheet was made once to answer one question, the question kept coming back, and the copying became somebody's job.
• It is done by someone hired for something else. An engineer retyping site data into a template. A salesperson chasing invoices. The owner answering the phone from under a sink.

If a job ticks three of those four, it is a candidate. If it ticks all four, it is probably the first one.

Five that show up in almost every company

The Monday spreadsheet. Somebody opens two or three systems and copies numbers into a fourth so the company can find out what last week earned. After: the numbers are pulled overnight and reconciled by a written rule, and a one-page summary arrives with the problems marked. We wrote up one of these on a skincare brand's ad account, and the win was not the hour saved, it was that a bad ad set got noticed the day it slipped instead of at month end.

Quotes written from the last quote. Open the last similar one, change the names, change the numbers, check the price book, hope nothing from the previous client survived the copy. After: the draft is built from your own price book in your own template, with the client's details pulled from the enquiry, and the reviewer edits instead of writes.

Documents assembled from a template by an expert. Regulatory filings, inspection reports, compliance packs: the same document set every time, filled with this job's data, produced by a qualified person over several hours. After: the set is drafted in the house format in minutes and the expert reads it. A drilling firm we built this for has put 168 documents through it and came back for a second system.

The phone that rings while you are on a job. It goes to voicemail, the caller does not leave one, they ring the next number. After: the call is answered, the appointment lands in the real calendar, the caller is written into the CRM, and a summary is waiting in the morning. We run one of these on our own line, and it is the one job where the cost of doing nothing is easiest to count: it is the calls you never knew you missed.

The one person who knows. The information lives in a system nobody else wants to open, so every question goes to the one person who can read it, and waits when they are away. After: anyone with permission asks in plain language and gets the answer from the live data. The person who used to be the lookup goes back to the job they were hired for.

How to pick the first one

Do the arithmetic on paper before you talk to anyone. For each candidate, write down three numbers: how many times a week it happens, how many minutes it takes, and roughly what an hour of that person's time costs. Multiply them. A task that happens 40 times a week and takes 15 minutes is ten hours of someone's time, and at $30 an hour that is about $15,600 a year. Put that figure next to what a build would cost and the decision usually makes itself.

Then ask one more question, which the arithmetic misses: what happens when it is done wrong? A quote with the previous client's name in it, a missed emergency call, a document that reaches the regulator with last project's numbers. The job where a mistake is expensive and quiet is often worth more than the job that takes the most minutes.

Pick one. Not a program, not a platform, one job with a number attached, delivered for a price agreed in writing before work starts. If a single build cannot prove its value, a bigger one will not either; it will only take longer to admit it. That reasoning, with the abandonment statistics behind it, is in why AI projects fail.

What to leave alone for now

Anything three people currently do three different ways. Automating it encodes the disagreement in software, and the argument that should have happened in a meeting happens instead as a bug report. Settle the process first.

Anything where a wrong answer costs more than a month of right ones and no person checks the output. The model can draft, sort, extract and answer. It should not decide, and it should not send anything to a customer or touch money without a person approving it, until the error rate has been measured on real work.

Anything that happens twice a year. The build costs the same whether the job is weekly or annual, and the annual one never pays back.

What it costs, roughly

A single job of the kind above is usually one build, and the bands are on the pricing page with nothing to fill in. The monthly running cost afterwards is small and visible on your own accounts, and what makes it up is in the running costs nobody mentions. If you cannot tell which job is the first one, a free consultation sorts that out: 30 minutes on a call, then a written proposal with a fixed price within two business days. Most owners with one obvious job can skip even that and describe the job in two paragraphs instead.