The kind of work we are called in for
These are typical situations, not client case studies. We have deliberately not dressed them up as named customers with invented numbers — when we have client stories we are allowed to publish, they will appear here with the client's name on them.
Moving office
The situation. A lease ends and the whole company has to be working in a new building on the Monday. Internet, phones, network points, the server, the printers and thirty people's desks all have to arrive at once.
What we do. We plan the move backwards from the first working morning: order the connection early because that is what slips, map what plugs in where, move and test the server out of hours, and be on site while people arrive.
What changes. The business loses hours rather than days, and someone other than the owner is holding the list.
The server nobody has looked at
The situation. A machine in a cupboard runs the accounts system. It was set up years ago by someone who has left, nobody knows the passwords, and the backup light has been amber for a while.
What we do. Document what it actually does, get administrative access back under the company's control, check the disks and the backup, and test a restore before deciding whether to repair, replace or move the workload to the cloud.
What changes. The business knows what it depends on, and can survive that machine dying.
A new starter on Monday
The situation. Someone joins and nobody has ordered a laptop, created an account or worked out what they need access to. This repeats every time.
What we do. Agree a standard build and a starter checklist: device, Microsoft 365 account, licences, group membership, the applications for that role, and a leaver process that mirrors it.
What changes. New people work from day one, and leavers stop keeping access they should not have.
Suspicious email
The situation. An invoice arrives that looks like a supplier's but the bank details have changed, or a member of staff enters their password on a page that was not really Microsoft.
What we do. Contain first: reset credentials, check what the account did while it was accessible, look for forwarding rules quietly added to the mailbox. Then close the gap — multi-factor authentication, domain records, filtering.
What changes. The incident stops there rather than becoming a payment to a criminal.
Growing out of ad-hoc IT
The situation. The business ran on a friend who is good with computers. There are now twenty people, and it takes days to get anything fixed.
What we do. Start with an IT health check to find out what exists, then take on the day-to-day: monitoring, patching, backups, a place for staff to ask for help.
What changes. Problems get found before they stop work, and the friend gets their weekends back.
Paying for licences nobody uses
The situation. The Microsoft 365 bill has grown every year and nobody can say who each licence belongs to.
What we do. Reconcile licences against people who actually work for you, remove leavers, and right-size plans to what each role needs.
What changes. A smaller monthly bill and an account nobody has to guess about.
Why there are no case studies here yet
Our business IT work paused during the pandemic while the company concentrated elsewhere, so we would rather show you honestly described situations than dress up old jobs as fresh success stories or publish testimonials with no name against them. If you want to know whether we can handle something specific, ask us directly — we will tell you plainly, including when the answer is no.