About
Technical content that still sounds like a person wrote it.
I write technical content that still sounds like a person wrote it.
I’m Gregory, and I’ve spent the last decade-plus inside real IT environments (IT service desk to infrastructure engineering). I’ve also spent the last few years translating technical subjects into writing that people can actually use.
Most of my work has been in SaaS, cybersecurity, and IT spheres. But I’m not precious about topics. If it’s complex, niche, high-stakes, or easy to get wrong, I’m interested. That could mean explaining a Linux workflow to a dev audience, breaking down a complex healthcare topic for everyday readers, or writing BOFU pages that don’t read like lukewarm marketing copy.
A lot of what I write is ghostwritten, so while the byline won’t always match, the work always does.
What I do
I write content that helps companies educate, rank, and convert, without sounding like a template.
SEO articles
SEO content that doesn’t read like loosely related and shoehorned keywords.
Technical how-tos
Linux, systems, infrastructure, product workflows, and practical guidance.
Developer & IT-facing guides
Deep, practical guides that are well-structured and KB-ready.
BOFU pages
Pages that answer real questions and address actual pain points.
TOFU content
Top-of-funnel content that doesn’t waste the reader’s time before the CTA.
Docs & newsletters
Wikis, knowledge bases, internal documentation, and newsletters written from experience.
Also
- Email newsletters written with passion from experience, not an LLM.
- Long-form essays that get the attention the topic deserves.
- Web copy, landing pages, product pages, and onboarding flows when needed.
Where I’m strongest
My lane is technical content, especially when the topic is complex or prone to oversimplification.
Core industries
- SaaS and B2B software
- Cybersecurity and remote access
- Developer tools and dev agencies
- Healthcare and health-adjacent products
- IT and infrastructure
- Energy transmission and distribution
That said, I’ve written plenty outside of these lanes, too. If you need someone who can switch from “here’s how to deploy it” to “here’s how to choose it” without losing credibility, that’s the job.
Background
I wasn’t always a copywriter. I actually started in IT.
Experience
- 12+ years across IT service desk, Wintel, sysadmin work, infrastructure engineering, and Linux.
- 5+ years writing professionally in-house, as a freelancer, and subcontractor.
- Native GB-English speaker (proficient in US and CA English as well).
Education & certs
- Bachelor of Health Science (Pharmaceutical Science)
- Advanced Diploma of IT (Networking)
- ITIL v3
- PRINCE2
Why it works
That combination (health + IT) has proved to be surprisingly useful. It means I can move between technical accuracy and reader clarity with almost any topic and any reference material.
A bit more human
Outside work, I write fiction and build small web apps in Python.
Both keep my writing sharp in different ways. Fiction reinforces pacing and voice. App dev keeps me current when I’m describing technical systems.
I’ve also spent a lot of time traveling, including parts of Eastern Europe and Central Asia, as well as the Middle East, Africa, Southeast Asia, and Oceania. I find it gives me a different read on how people work, communicate, and solve problems when all the assumptions I’m used to don’t apply.
I was born in Australia and have worked most of my life there. So I understand Western business expectations and the “how things are usually done” side of the world too.
How I work
Good copy doesn’t come from researching the top three search results and remixing.
If the reader can get the same answer anywhere, it’s not really worth publishing. Here’s the workflow I use to create better content for my clients.
1) Discovery
- What are we trying to achieve? Ranking, conversion, education, reducing support load?
- Who is the reader and what do they likely already know?
- What counts as a win when it’s done properly? Traffic, demo signups, retention?
2) Deep research (no SERP skimming)
- Vendor documentation and primary sources. No statistics aggregators.
- Standards, security notes, and technical references.
- Real-world constraints and edge cases.
- Forum questions on Reddit and Stack Overflow that nobody answers properly.
3) Structure and outlining
- Clear headings that match intent.
- Logical flow.
- A plan for examples, comparisons, and objections.
4) Drafting
I write with the assumption that readers are smart and busy. No filler. No robotic phrasing. No “in the ever-evolving landscape of…”
5) Revisions and polish
You’ll get clean revisions with markup, consistent voice, and copy that’s ready for publishing, technical review, or printing.
Ghostwriting and attribution
A large portion of my work is ghostwritten under subcontracting agreements. That’s normal in this industry, but it does mean the byline won’t always reflect authorship.
If you need proof for anything sensitive, I can provide:
- Tear sheets (PDFs).
- Role- or industry-specific sample bundles.
- References where appropriate.
Want to work together?
If you’re hiring for a writer who can handle technical depth, research properly, and still sound human, send me the role and what you need the content to do.