In most small businesses the IT person is whoever’s good with computers, doing it on top of their real job. The setup grew one problem at a time, nobody has the whole picture, and every new question means another vendor with another product to sell.
I’m someone to ask and someone to sort it. I’ll look at the whole setup, tell you plainly what matters and what doesn’t, and fix what needs fixing.
I spent eight years at IT support companies, looking after businesses from a few people up to companies with sites across the country, and the systems they all run on.
What you have, what’s costing you time, and what’s worth changing. Written down, in order, so you can do it all at once or bit by bit.
Email, shared files, calendars and accounts that make sense, or tidied up after years of patching. Old accounts closed and licences matched to what you use.
Your domain in your name, and email that arrives instead of landing in spam.
Backups you’ve seen restored, not a setting someone switched on once, and an alert when a backup job fails, instead of finding out on the day you need it.
Multi-factor sign-in, a password manager, updates that actually happen, and a clear list of who has access to what.
Laptops enrolled and configured through Microsoft Intune: the same apps and settings on every machine, the junk removed, and a new starter’s computer ready without a day of fiddling.
The machine in the cupboard, moved to something you don’t have to keep alive, with the files and permissions intact.
When something breaks, I come and fix it: the computer that won’t start, the printer nobody can find, the account that’s locked out.
I’ll make the calls and speak their language, so you don’t spend an afternoon on hold.
A free chat about what’s going on.
A visit to see the setup: the computers, the accounts, the network, and how you use them.
A written list of what I found and what I’d do, with a quote.
The work, and a handover: what’s where, who has access, and what to check if something changes.
A network of medical practices
16 websites on one shared server had been compromised, one after another. I cleaned out the backdoors and rebuilt the server so every site is walled off from the rest, with the whole setup kept in version control.
A network of medical practices
A booking system other developers built years earlier, still running a network of practices every day. I took it over, found and fixed its security problems, and got its source building again, without breaking anything people relied on.
Leahy & Co’s own
A free, open-source web console for Windows Deployment Services: images, devices and drivers in a browser, and a live view of every network install. Published on GitHub.
Leahy & Co’s own
Every BuiltSite website runs on a hosting platform I built and run: changes go live in minutes, the servers are locked down, and nothing is open to the internet.
A Perth roofing business
A roofing business moved from a personal Hotmail address to email on its own domain, set up so it gets delivered and can’t easily be spoofed, with the website’s quote form sending through it.
A team of about ten
A self-hosted password manager for a small team who share logins for customers’ sites and servers, opened with the Google Workspace accounts they already use.
No. I work in projects and one-off jobs. When something needs doing, you get in touch and I quote it. Nothing ticks over in the background.
Yes. If something’s broken, I’ll come and fix it. Bigger changes get a written quote first.
Yes. I can give a second opinion, or take on a project they don’t cover.
No. Most setups have a few things that matter and a lot that are fine. I’ll tell you which is which.
Once I’ve seen the setup, plenty can be done remotely: Microsoft 365 changes, account problems, most software. Hardware and networks need a visit.
A free chat about the problem, then a written quote before any work starts.
