Editorial Policy
How we decide what to publish, who writes it, and what we will not say. Written before we published a single article, so it describes a standard we have to meet rather than one reverse-engineered from what we already did.
Who writes this material
Everything on this website is written by the Geeks360 team — the technicians and consultants who do this work for Sydney businesses. Nothing is outsourced to a content agency, and nothing is bought from a syndicated library of MSP articles.
That matters more than it sounds. Most managed IT websites run identical articles, because a handful of marketing services resell the same content to hundreds of providers. If a page could have been written by someone who has never seen your industry, it usually was.
Who we write for
The reader we have in mind is the person who has to make the decision and pay for it — an owner, a practice manager, an office manager, a partner. Not an IT department, and not another technician.
So the test for every page is whether a capable non-technical reader finishes it understanding what the problem is, what it would cost them to ignore it, and what to do next. Jargon that survives that test stays; jargon that only demonstrates expertise gets cut.
What we will not publish
This list is short, specific, and enforced:
- Partnership or certification claims we cannot evidence
- Uptime percentages, response times or resolution times we have not measured
- Client numbers, years in business or team sizes stated for effect
- Testimonials, reviews or case studies that are not real and not permitted for use
- Statistics without a source we have actually checked
- Compliance obligations described as more onerous than they are, to create urgency
- Anything implying we provide legal, financial or insurance advice
If a claim cannot be verified, it does not go on the site. That rule is why several things a competitor would display are simply absent here.
Fear as a sales technique
Cyber security content is unusually prone to manufactured alarm — a frightening statistic, an implied deadline, a threat described as though it is already inside your network.
We describe risk in proportion to what we actually see, including when the honest answer is that something is unlikely to affect a business of your size. A reader who acts because they understood the risk makes better decisions than one who acts because they were frightened, and stays a client longer.
Commercial independence
We recommend products we work with, and we say so plainly when we do. We do not publish paid placements, sponsored articles or affiliate links, and no vendor pays to appear on this website or to be described favourably.
Where we name a product, it is because we support it and have an opinion about it — including, sometimes, that it is more than a particular business needs.
Corrections
If something here is wrong, tell us at hello@geeks360.com.au and we will correct it. Where a correction changes the substance of a page rather than fixing a typo, we note what changed and when.
We would rather be corrected than be wrong quietly. A technical website that never issues a correction is not more accurate than one that does — it is less honest about it.