Web, mobile, and IT advice for Australian SMBs from the GTS team.
Seventy posts across five sites in a week, and the more useful output was the audit that ran alongside them. 2,310 pages counted for the first time, 244 duplicates retired, and a publishing feature we assumed we had.
A shortened link hides where it goes, which is exactly what a phishing link does. We put the list on a page we own instead — and the difference is not aesthetic, it is whether a customer can check you independently.
We were approved for three affiliate programmes in twelve days. Two of them sell things we know nothing about, so they get no coverage. Here is the test we apply, and why refusing is the part worth writing down.
We automate a great deal, and there is a category we deliberately do not. The line is not about difficulty — it is about whether a wrong answer produces a signal, and who carries the consequence when it does not.
We wrote thirty posts to publish over a week and then discovered none of our five websites could schedule anything. Every one published on a flag, with no date comparison anywhere. Nobody had removed the feature — it was never built.
In one fortnight, three of our own tools reported something false — a record that said work did not exist, a check that could not fail, and a component that had silently lost a capability. None of them errored.
We publish these notes from a commit log rather than from memory, and the difference shows up in what gets reported. 180 commits across 20 repositories in eight days, and the three things that turned out to matter were not the three anyone would have named.
Australia recorded 1,205 notifiable breaches in 2025 and the average self-reported cost to a small business is $56,600. Here is the one page a small business owner actually needs, and the four things on it that matter.
We run four divisions and the honest answer to "which one do I need" is usually not the one a customer arrives asking for. Here is the question that sorts it, and the cases where the right answer is none of them.
Four WordPress plugins went out on the same day for one reason: a platform release that changed the editor underneath all of them. Preparing them surfaced a defect class our own repository could not see.
We run several brands from one office and answer all their email from one place, which is exactly what an invoice scam looks like. So we published the list: every domain, the ABN with a link to check it, and a line saying if it is not on this page it is not us.
Six of our domains route their mail to one Google Workspace account. Two of them have no website at all — an MX record and nothing else. Why that is a deliberate arrangement, what it costs, and the DNS check worth running on every domain you own.
Five websites meant five contact forms, five spam problems and five places a lead could go missing. Consolidating them onto one service took a day. The decision to do it took two years, and the arithmetic that finally settled it applies to most multi-site businesses.
171 commits across 20 repositories in the week to 26 September. A duplicate gate that passed everything because it read a file that is never written. A landscape screen that could never have rotated. A summary file for AI systems that said nothing. Three versions of the same failure.
295 commits across the group. A video frame specification stopped being something the renderer and the gates each assumed and started being a file both of them read. Substance gates landed for statistics scripts, and wave 1 and wave 2 of the social run shipped.
274 commits across 16 repositories. Having spent a fortnight finding checks that never ran, we spent this one making them run — and then two weeks discovering how many of them fired on things that were perfectly fine.
500 commits across 21 repositories. The recurring finding was not a missing safeguard — it was a safeguard that existed, was documented as existing, and had never once executed. We found nine of them in six codebases.
337 commits across 24 repositories in a fortnight. The dominant finding repeated itself in five separate codebases: the feature was built, shipped, and never actually appeared on the page.
169 commits across eight repositories in eight days. Most of it was not new features — it was discovering that several things we believed were working were not, and fixing them. Here is what shipped and what it cost.
A short round-up of what our sister brands shipped in the last two weeks — including a multi-tenant SaaS migration war story, a canonical-domain SEO incident, an og:image audit, a self-correcting content pipeline, and an adversarial code-review practice — with links to the full write-ups on each brand.
After three years of building across cloud infrastructure, mobile apps, AI systems, and web platforms, we faced a recurring problem: hard-won knowledge kept getting lost between projects. Here's how we built a systematic knowledge management system — and what changed when we did.
A strategic guide for Sydney SMBs on choosing the right combination of cloud services, web design, and mobile apps to build a digital stack that drives growth.
GTS digital solutions help Western Sydney businesses rank and grow — specialist web design, cloud IT, mobile apps, and content strategy under one roof.