Stop retyping details. Stop sending reminders.More time running your business.

I’m building a practical automation service for UK businesses. It starts with a conversation about the admin that quietly eats your week.

Get in touchSee example processes

Working remotely, across the UK.

One example: a supplier invoice

  1. Invoice received

    arrives by email, as usual

  2. Details checked

    supplier, reference and totals all present

  3. Details missing

    flagged for a person to decide, not lost

  4. Invoice filed

    no retyping, no reminders

An illustrative example, not a live system: routine invoices file themselves; anything incomplete waits for a person.

Processes I’m exploring

Examples owners and operations teams keep describing. If yours isn’t listed, it’s still worth raising.

  1. Moving information between systems

    Details arrive in one place and are needed in another: an inbox, a spreadsheet, an accounting package. A reliable handover between tools removes the retyping and the errors that follow.

  2. Following up on documents, updates and approvals

    A signature, an approval, a status update that never quite arrives. Timed follow-ups with a clear trail take the remembering and the reminding off someone’s desk.

  3. Preparing recurring operational reports

    Weekly figures assembled by hand from several systems, then tidied into a template. Assembling them automatically is usually the simplest improvement.

If one of these sounds like your week, tell me about it.

How I think about the work

  1. Understand the process

    Map the steps as they actually happen, workarounds included, and find where the time and the errors concentrate.

  2. Check existing software first

    Before building anything new, find out what the systems you already pay for can do when they’re set up properly.

  3. Decide whether it’s worth doing

    Some processes are better left alone. The outcome is an honest view: improve it, configure it, or leave it be.

Who you’d be talking to

Before this, I spent five years as a monitoring engineer at a managed service provider. The job was making sure the quiet things got noticed: whether last night’s backup completed, what happened when it didn’t. Monitoring is a discipline of visibility and exceptions, knowing what should have happened by now and dealing quickly with the thing that didn’t.

I’ve also programmed for long enough to be comfortable building and adapting things when it’s warranted, and sceptical about building when configuration would do.

That’s the mindset I bring to operations work: find where the time goes, check what the tools you already own can do, and make the handover something you can trust.

Tell me what’s eating your week

Send a short description of your business and one recurring admin problem: follow-ups, retyping, a report you rebuild by hand. I read everything myself and reply personally. If a call seems useful after that, we can arrange one remotely.

One process is plenty: what it involves, where it stalls, and roughly how often it repeats.

Used only to reply to this enquiry — no mailing lists, no sharing.

Prefer email? info@jwtechsupport.co.uk

  • The first conversation is exploratory and remote: how things work today, and where they snag.
  • No obligation, and no confidential documents or account access needed: a general description is plenty. Any paid work would be scoped and agreed separately.