IT, Security and Stories: Why One Family Runs All Three
People ask us how a single family ends up running IT consulting, cybersecurity, and a book publisher under one roof. On the surface they look like three different businesses that happen to share a surname. They are not. They are three answers to the same question.
The question is this. How do you build something you can trust when nobody has time to check the details themselves?
Three trades, one habit
Greg spent years in IT and cybersecurity. That work is mostly about one discipline practised relentlessly. You patch the system, you review the access, you write down how it all fits together, and you do it again next month. Most failures are not clever attacks. They are ordinary maintenance nobody got around to.
I have seen it hundreds of times. A company gets compromised and the root cause is a server that was never patched after the last admin left. Or a firewall rule that someone added for a temporary project and forgot to remove. The breach makes the news. The cause is boring.
Michelle came at it from publishing and writing. A book is the same discipline wearing different clothes. A manuscript becomes a finished book through a hundred unglamorous passes. The edit nobody sees, the proofread that catches the embarrassing mistake, the formatting that makes a page feel calm to read. Readers only notice when it is done badly.
She has seen the same pattern. A manuscript comes in with a brilliant story and inconsistent character names. Not because the writer is careless, but because they were focused on the story, not the spreadsheet. The fix is uninteresting. The result is a book that feels professional instead of self-published.
Put those two together and you get a single belief that runs through everything we do. The quality of a thing lives in the parts that do not show.
Why that connects rather than scatters
A security review and a manuscript edit feel unrelated until you watch how each one is done well. Both reward patience over flash. Both depend on someone caring about the detail when no one is watching. Both fall apart the moment someone decides the dull step can be skipped this once.
That is why the work sits together comfortably. The cybersecurity and advisory side protects what a business has already built. The managed IT platform keeps the lights on without drama. And the publishing side takes a writer’s work and finishes it to a standard they could not reach alone. Different outputs, identical instinct.
Why South Africa makes this sharper
Running this in South Africa adds something that might not exist in a more predictable market. Businesses here operate under real pressure. Margins are tight. Loadshedding, exchange rate swings, and skills shortages mean that every rand spent on IT or publishing has to justify itself. There is no budget for theatre.
That constraint has shaped how we work. We do not sell complexity. We do not build things that require a PhD to maintain. The IT platform has to be usable by someone who is also doing three other jobs. The security advice has to be implementable this week, not next quarter. The book production has to produce something a reader will actually buy, not just something that looks impressive on a proposal.
South African clients can smell padding. They have been oversold to by international vendors who do not understand the market. They want the thing that works, at a price that makes sense, delivered by someone who picks up the phone.
The family part is not decoration
Running this as a family is not a marketing line. It changes how the work gets done. When your name is on the door and the person beside you is the person you have dinner with, you cannot quietly let standards slip. There is no large organisation to hide inside. The accountability is total, and that is the point.
It also means the institutional knowledge does not walk out the door when a key employee resigns. The person who built the security assessment methodology is the same person who will refine it next year. The person who established the publishing workflow is the same person who will catch the regression in the next manuscript.
What we actually do with all of this
We started all of this because we kept seeing the same thing. Businesses and authors alike were being let down not by a lack of talent but by a lack of care in the unseen parts. We thought we could do those parts properly. That is the whole idea. Strategy, security, and stories, held to the same standard.
If you run a business in South Africa and want IT and security handled by people who will still be here next year, talk to us. If you have a manuscript and want it finished to a standard you would be proud to put your name on, same door.