Why a builder, not a reseller
Most IT companies are middlemen. They buy a product, mark it up, point you at a vendor's support line when it falls over, and move to the next ticket. There's nothing illegal about it; it's just thin. The person selling you the firewall has often never configured one in anger, and when the thing misbehaves at 2am the honest answer is "we'll raise it with the vendor."
I came up the other way. Eighteen years gets you across every corner of this field: building systems, securing them, keeping them alive when something fails at the worst possible time. You stop trusting brochures and start trusting what you've seen with your own hands. So my default isn't "what can I resell you," it's "what does this actually need, and can I run it myself." That single difference changes every piece of advice that follows. A reseller's incentive is to attach more product. A builder's incentive is to make the problem go away.
Why I run my own data centre
This is the line people raise an eyebrow at, so let me be plain about it. I run my own data centre because if I'm accountable for your systems, I want my hands on the infrastructure they live on. Not a tenancy in someone else's cloud where the real controls are three support tiers away: the actual hardware, the actual network, on a stack I designed.
Here's the unfashionable opinion: for a lot of small business, cloud-only is a worse deal than the marketing admits. You're renting capability by the month, the bill creeps every quarter, and the day something goes sideways you discover your "infrastructure" is a status page and a queue. Owning the gear flips that. The cost is predictable. The performance is mine to tune. And when something needs fixing I fix it at the root instead of opening a ticket and hoping. That doesn't make cloud wrong; I use it where it genuinely earns its place, for offsite backup and failover especially. It just means cloud is a tool I reach for on purpose, not the answer I default to because everyone else did. Own it, don't rent it isn't a slogan; it's how I keep control of the thing I've promised to keep running.
The "we do everything" thing is a feature, not a weakness
Plenty of providers specialise to one slice and refer the rest out. I do the opposite on purpose: networking, servers, phones, alarms, cameras, the websites, the backups, the lot. The industry treats that as a red flag, as if breadth must mean shallow. In practice it's the reverse. The reason your "phone problem" never gets fixed is that it's actually a network problem, and your phone vendor and your network vendor each insist it's the other one's fault. When the same person owns the whole stack, that finger-pointing has nowhere to go. Most messes I get called into aren't one broken thing; they're three half-installed things from three different suppliers that were never made to talk to each other. Breadth is how you stop being the customer caught in the middle of that.
What "done honestly" actually means
"Honest" is the most over-used word in this trade, so here's mine with the working shown. These are the principles I won't bend, and each one costs me money on purpose:
- Tell the truth, including "you don't need this." The fastest way to lose my trust in a provider is being sold the gold tier for a problem the free fix solves. I'll talk you out of spend more often than into it. Often the right answer is a setting, not a purchase: same as how, for most homes, a WiFi "booster" is usually a downgrade when the real issue was never coverage.
- Price from real cost, not from what the market will bear. I've spent years weighing power draw, resale value, and subscription-versus-own on real numbers, because I came up on a low budget and it taught me to. I price the same way I'd want to be priced. Constraint makes you a better engineer; it makes you a fairer one too.
- No lock-in, ever. If you want to leave, I'll hand over the keys clean. A client should stay because the work is good, not because the exit was booby-trapped. Lock-in is just a bet that your service can't survive a fair comparison; I'd rather it could.
- Speak plainly. If I can't explain it to you without jargon, I don't understand it well enough yet. Plain English isn't dumbing it down; it's proof I've actually got it.
The part I care about most: the bush
I've got a real soft spot for the businesses the big providers can't be bothered with: small operators, and rural and regional Australia. They get written off as too remote to support properly, which is both wrong and a bit lazy. Those businesses hold their towns together, and "too far away" hasn't been a genuine technical reason for years. With the right remote tooling, my own hosting, and a willingness to get on a plane when a job needs hands on site, geography stops being the wall it's made out to be. Out there, owning your stack matters even more, because the fixed line you're assuming is there often isn't. When 5G is the actual internet, not a backup, you design differently and you don't get to lean on someone else's data centre down the road.
Why any of this matters to you
You don't hire principles; you hire outcomes. But the principles are exactly why the outcomes are different. Because I build instead of resell, my advice points at the real cause instead of the nearest product. Because I own the infrastructure, I can fix things at the root and quote you a number that won't drift. Because I refuse lock-in, you can keep me honest by being free to leave. Same reason I'd rather run a company on a stubborn set of rules than chase the biggest invoice; it's slower, and it's the only way I know how to do work I'd actually stand behind.
That's the short version of who Angus Lewington is and why the shop runs the way it does: a builder who got tired of how the industry treats people, and decided to prove you can do this honestly and still do it well.