Why I'm building Pythia

For years I led digital channels in government, and the hardest part of the job was rarely the writing. It was everything that happened after the writing was done. A message would be crafted, checked and signed off, and then the real effort began: getting that one approved message out across every channel without it going off course along the way.

I've since moved on from government, but that problem has stayed with me.

Agencies are publishing across more channels than ever, and the coordination load grows with every one they add. So I'm doing something about it. This is the story of why I'm building Pythia.

The work behind every announcement

Anyone who has worked in government communications will recognise the pattern. A media release goes through rounds of review before it is approved. Then social media needs a LinkedIn version, an Instagram caption and a Facebook post. Marketing wants it adapted for the newsletter. Media, engagement and comms each have a view on how it should land with their audiences.

Each of those versions means another draft, another check-in and, very often, another meeting. People who should be working in parallel end up waiting on each other, chasing approvals and reconciling edits made in different documents. By the time everything is ready, a surprising amount of skilled time has gone into moving the same message from one format to another.

None of this is anyone's fault. The people involved are talented and conscientious. The trouble is a process that relies on manual rewriting and constant coordination to do a job that should be far more straightforward.

When the message starts to drift

The time cost was frustrating, but what worried me more was what happened to the message itself. A carefully chosen policy term in the release would become something slightly different on Facebook, then something else again in the newsletter. Nobody set out to change it. Each person was simply adapting the words for their channel, and by the fourth or fifth rewrite the meaning had shifted.

In government, that drift matters. Terminology is often chosen deliberately, sometimes for legal or policy reasons, and the public relies on agencies to say the same thing wherever they encounter it. Inconsistent wording creates confusion, invites questions and can undermine trust in a message that was perfectly clear when it was signed off.

What I wanted instead

I kept coming back to a simple idea: create once, repurpose and publish everywhere. If a message has already been approved, the channel versions should flow from it, not be rebuilt by hand each time. That is what Pythia is designed to do.

You start with the content your team has already written and signed off. Pythia adapts it for each channel using content strategies set up for your organisation, so the rules about tone, length and terminology are applied consistently rather than reinvented by whoever is writing that day. Your team then reviews the versions side by side, gives feedback and regenerates until they are right. Once approved, they publish directly to your social channels.

Because it is built with government in mind, the details matter. Pythia has role-based access and an approval step before anything goes live. It handles embargoed content, deletes data once it has been published, and is NZ hosted, processed within Australia and New Zealand. It is not trying to replace the tools agencies already use, such as Microsoft Copilot.

The real goal is to give people their time back. Fewer coordination meetings and less rewriting means communicators can focus on the high-value work they were hired for: strategy, storytelling and genuinely engaging with the communities they serve.

Why the name Pythia

In ancient Greece, the Pythia was the oracle at Delphi, the voice people travelled to hear because what she said carried authority. The name felt right for a product about storytelling and truth-telling, and about making sure an organisation's voice is heard clearly wherever people are listening. It is an ancient name for a very modern problem, and I like that tension. Pythia is Paadia's flagship product, and it carries the mission I care about most: using technology responsibly to make people's working lives better.

Help shape what comes next

Pythia is coming soon, and I want it shaped by the people who will use it. If you work in government or public sector communications, I'd love to hear from you. You can book a demo to see how one approved message becomes repurposed, ready-to-publish versions for every channel, or join as an early adopter and help decide which features we build next.

Get in touch through paadiatech.com or send me a message on LinkedIn. If the problem I've described sounds familiar, I'd really value your perspective on it.