← All posts

When a system has no API, the software uses the screen

· Bob Ottley

Plenty of businesses run on a system nothing else can talk to: an old desktop package, a supplier portal, a government website. That used to be the end of the conversation. It is not any more.

115hours a year, example: half an hour a day in portals
4rules that make screen work safe
1stchoice is always the API

The problem

A modern system has an API: an official way for other software to read and write data reliably. Many systems do not. So someone logs in every morning, downloads a report, checks a status, uploads a document, and logs out again. Then does the same on the next portal.

Take three portals at ten minutes each, every working day. That is half an hour a day, around 115 hours a year, close to three working weeks spent clicking through screens that never change.

Example figures, based on 230 working days.

Working the way a person does

Where there is no API, software can now use the screen the way a person would. It logs in, finds the fields, enters the data and checks the result. Modern software can recognise a button by what it is, a "Save" or a "Submit", not just by exactly where it sits on the screen, which is what made older screen automation so fragile.

The four rules that make it safe

  • Use the API wherever one exists. The screen is the fallback, not the first choice. An API is faster, cheaper and more reliable.
  • Recognise change and record it. If "Save" becomes "Submit" after a supplier updates their site, it recognises the button and records that the screen changed, so we know before it matters.
  • Stop rather than guess. If it is not sure what it is looking at, it stops and asks. It never guesses with your data.
  • Check the result. After entering something, it reads it back to make sure it landed, the same way a careful person would.

When it is worth it, and when it is not

Worth itNot worth it
Daily or weekly, the same steps every timeOnce a month, different every time
A system that will be around for yearsA system being replaced next year
Data that then feeds something elseA one-off lookup a person can do in a minute
Errors that are costly when re-typedLow-stakes, easily corrected work

For a once-a-month task, a good checklist is usually cheaper than any software. We will tell you which side of the line you are on.

Have a job like this? Tell us in a few lines what gets copied, checked or chased by hand. We will come back with questions, not slides.

Book a call

Next: Is your business data used to train AI?