Add on

The work nobody should be doing by hand.

Onboarding, offboarding, provisioning, licences, reporting. The repetitive work that eats a day a week in a brokerage and never appears on anyone’s job description. We automate it, and then it happens whether anyone remembers or not.

0Automated tasks run each month across our clients

0Automations deployed and running in production

0Platforms integrated, so the work crosses systems

The problem

Three jobs that eat a day a week.

Onboarding an AR takes a fortnight

Six platforms, a ticket for each, and a new starter sitting at a desk on day one with a laptop and access to nothing that matters.

Offboarding is the one that shows up in an audit

And it is the one that slips. Somebody leaves in March. Their access is still live in June, and nobody notices until an auditor asks who had it.

The same report, rebuilt by hand, every month

Export, paste, format, send. Half a day gone, and it is identical to last month’s except for the numbers.

What's included

What we automate.

Starter automation across every platform. Mailbox, Teams, SharePoint, broking system login and licences, from one entry.
Leaver automation in reverse. Access removed the day it should be, with the record written as it happens rather than reconstructed later.
Microsoft 365 licence assignment and reclamation. So you stop paying for people who left.
Ticket triage and routing. The right person sees it first, instead of everything landing in one queue.
Monthly reporting, produced rather than assembled. Generated from the data instead of exported and pasted.
Custom workflows. For the processes that are specific to how your brokerage actually runs.

In practice

An AR starts on Monday.

FRIDAY, 4PM
Somebody enters the new starter. Once.
Name, role, start date, and which authorisations they need. That is the entire task, and it takes about ninety seconds.
OVER THE WEEKEND
Nothing needs a person.
The mailbox is created. Teams and SharePoint access is granted. The broking platform login is built. Licences are assigned from the pool you already pay for. No tickets are raised, because there is nothing for anyone to do.
MONDAY, 8:30AM
They sit down and everything works.
Email, Teams, the shared drive, the broking system. Not a morning of someone in your office chasing access while a new employee reads the staff handbook for the third time.
AND WHEN THEY LEAVE
The same sequence runs backwards.
Access is gone on the day it should be, across all of it. The record of exactly what was removed and when is written at the time — which is the version an auditor will accept, and the reconstructed one is not.

How it is charged

Quoted as a project.

A build has a scope and an end date

Automation is one of only two things that sit outside the monthly plan, because each build is a defined piece of work rather than an ongoing service. We scope it, quote it, build it and hand it over.

Common questions

What people ask about automation.

What can actually be automated in a brokerage?

Anything that follows the same steps every time and touches more than one system. Starters and leavers are the obvious ones. After that it is usually licence management, report generation, and whatever your team currently does with a checklist and a spreadsheet.

How long does a build take?

It depends on how many systems it has to touch and how much of your process is written down versus in someone’s head. A workflow inside one system is quick. Onboarding that spans your broking platform, Microsoft 365 and two portals is not. Either way the scoping happens first, so you get a timeframe with the quote rather than after you have committed.

What happens when one of the platforms changes?

We maintain them. Vendors change interfaces and APIs, and an automation that nobody looks after quietly stops working — usually without telling anyone. Ours are monitored, and a failure raises a ticket with us rather than surfacing as a new starter with no email.

Do we have to change how we work?

Usually a little, and only where your current process has steps that exist because a person was doing it. We would rather automate the way you actually work than sell you someone else’s process.

Is this only for larger brokerages?

No. The smaller you are, the more the repetitive work lands on someone who has another job. What decides it is not your headcount, it is how often the task runs. Something one person does every fortnight is usually worth automating. Something done twice a year usually is not, and we will tell you that rather than quote it.

The rest of it

The other four services.

Managed IT & Microsoft 365In the plan Cyber & ComplianceIn the plan Broking SystemsIn the plan Websites & HostingAdd on

Doing it by hand? Let’s talk.

Thirty minutes to work out which of your repetitive jobs is worth automating first, and which is not worth touching.