Why I started Alien IT Solutions
Hi, I'm Angus. I started Alien IT because IT support shouldn't feel alien, and after the better part of two decades in this industry I'd watched too many small businesses get treated like they didn't matter. This is the short version of why I built something different, then the detail.
I came to IT from the tools, not from a textbook
Before IT, I worked in the trades. I came up on building sites, where the job is simple to describe and hard to do well: understand the real problem, then build the thing properly so it lasts and nobody has to come back and redo it. You can't bluff a wall into standing up. It either holds or it doesn't, and everyone can see which.
That mindset never left me, and it turns out to be exactly what most IT is missing. A lot of the industry is built on selling you the product first and working out your problem later, if at all. I do it the other way around. I want to know what you are actually trying to run, where it hurts, and what "done" looks like for you. Then I build to that. Same as a good build: measure first, cut once, and don't leave a mess for the next person.
Around eighteen years of watching how it shouldn't be done
I've spent roughly eighteen years in IT now, building, securing and supporting technology for businesses of every size. That's long enough to see the same pattern on repeat. The big providers keep their best people and their straight answers for their biggest accounts. Everyone else gets a ticket number, a different account manager every few months, and an invoice full of words chosen to be hard to understand.
Two things about that always bothered me. The first is the lock-in. You sign up, and slowly your domains, your email, your data and your licences all end up sitting behind a login only your provider controls. Leaving becomes a threat rather than a right, so you stay whether they're any good or not. The second is the jargon. Half the time the complicated language isn't there to inform you. It's there to make you feel like you couldn't possibly understand, so you stop asking and keep paying. Small businesses cop the worst of both, and they're the ones who can least afford it. I kept thinking the same thing on job after job: it doesn't have to be like this. Eventually I stopped thinking it and built the alternative.
What "built properly" actually means to me
Built properly means the thing does the job, keeps doing it, and doesn't quietly turn into a trap. It means I'd be happy to hand you the keys and explain exactly how it works, because there's nothing in there I'd be embarrassed to show you. No dependency I bolted on so you'd need me forever. No shortcut that saves me an hour today and costs you a weekend in a year.
It also means matching the solution to the real need instead of the shelf. Plenty of providers have one product and every customer somehow turns out to need exactly that product. I'd rather start from your problem. Sometimes the honest answer is a simple, cheap fix and I'll tell you so, even when a bigger sale was sitting right there. I'd take a customer who trusts me for ten years over a quick invoice that leaves a bad taste. That's not charity. It's just how you build something that lasts, whether it's a wall or a business.
And built properly means it's built to be handed over. On a good site you leave the job clean, you label the switchboard, and the next tradie who opens it can follow what you did. Good IT is the same. I document what I set up and I keep it tidy, so if you ever bring in someone else, or take a piece of it in-house, they can pick it up without starting from scratch. A setup nobody but me can understand isn't clever. It's just another form of lock-in wearing a different hat.
Why I run my own infrastructure
Alien IT is, deliberately, a hands-on operation. I run my own on-premise infrastructure, my own data centre, rather than reselling someone else's stack and hoping for the best. That matters more than it sounds. When your website, email and systems live on gear I actually control, I can answer for them. If something breaks, I'm not opening a ticket with a faceless supplier and waiting my turn behind ten thousand other resellers. I go and fix it.
Owning the stack also means I understand it end to end, because I built and maintain it myself. There's no layer of the setup that's a mystery to me, which means there's no layer that has to be a mystery to you either. Own it, don't rent your dependence on it. That principle runs through everything, and I hold my own operation to it before I ever ask a client to trust it.
The promise, in plain English
- Honest. Straight answers, real pricing, and "you don't need that" when it's true.
- Plain English. No jargon used to make you feel small or to pad an invoice. If I can't explain it simply, I don't understand it well enough yet.
- No lock-in. Your domains, your data, your licences stay yours. You can walk out the door whenever you like and take everything with you. Most people stay anyway, because they want to.
- One human to call. You get me and my team, not a queue and a stranger who has to read your history before they can help.
- Product-first, not sales-first. I solve the problem in front of us. If the right answer is small, the invoice is small.
Who I'm for
I'm for the small and medium businesses who've been made to feel like an afterthought by their current provider. The ones who've been burned by lock-in, talked down to, or billed for things they never understood and probably never needed. If you want your technology explained like you're a capable adult, set up so it actually works, and kept honest, we'll get on well.
I care about the businesses further from the city too. The rule seems to be that the more remote you are, the worse your IT support gets, written off as too far, too small, too much trouble. I think that's backwards. Those businesses keep towns running and deserve the same standard as anyone on a city block. Between remote tooling, my own hosting, and getting on the road when a job genuinely needs someone on the ground, distance stopped being a good excuse a long time ago.
The alien, since you're wondering
Yes, there's a little green pilot on the logo, and yes, the alien jokes are free and frequent. The mascot is a reminder of the whole point: technology should feel approachable, not intimidating. We come in peace, there's no probing, and we genuinely enjoy the work. Good IT and being pleasant to deal with were never meant to be a trade-off, and I've never understood why so much of the industry treats them like one.
If any of this sounds like the kind of people you'd want looking after your tech, tell me what's slowing you down and I'll tell you straight whether I can help. Book a free consult 🛸