Why we built Creator:P.A.T.
Creator:P.A.T. started with a simple frustration: publishing one piece of content should not mean repeating the same job across four different platforms.
The problem we wanted to solve
For a creator making short-form video, the creative part is only half the job. Once the video is ready, there is still the repetitive work of opening Instagram, Facebook, TikTok and YouTube, uploading the same file, copying captions, adjusting titles and hashtags, checking visibility, and then repeating the process again.
That is manageable for one post. It becomes a chore when you are publishing regularly, and it gets even harder when each platform needs slightly different wording or settings.
We wanted a workflow that felt much more natural: create once, choose where it should go, make any platform-specific changes, review everything, and publish.
From a useful tool to a real product
The first idea was intentionally small. Could we upload a video once and deliver it reliably to one social platform? YouTube became the first working destination, giving us a safe way to prove the connection, authentication, upload and delivery process.
From there the idea quickly became broader. A useful creator tool needed connected accounts, draft recovery, safe test publishing, per-platform settings, delivery history, support, and eventually scheduling, analytics and creator-focused automation.
That changed the question from “can we automate an upload?” to “what would a creator actually want to use every time they publish?” That question has shaped the product ever since.
Before Creator:P.A.T., there was just PAT
Long before we had a public product name, this was simply a pet project. Like most pet projects, it needed something to call it while we experimented, built screens, broke things and worked out whether the idea was actually useful.
We called it PAT.
There was no carefully constructed brand strategy behind it at that point. PAT was the informal name of the little publishing project we were building. But because we used the name constantly throughout development, it started to acquire a personality of its own. Instead of saying “the publishing application”, we talked about what PAT should do next, what PAT had successfully delivered, and what we needed to teach PAT to do better.
PAT stopped feeling like a temporary project name and started feeling like the product.
That mattered more than we expected when the time came to give the application a proper identity.
Trying to choose the “real” name
Once the project was clearly becoming more than an experiment, we did what you are supposed to do: we started looking for a serious product name.
We explored various naming options around creators, posting and multi-platform publishing. There were plenty of names that described what the product did, but every time we compared them with the name we had already been using throughout the build, we kept coming back to PAT.
The more alternatives we considered, the more obvious something became: we did not really want to let PAT go.
So instead of asking “what should replace PAT?”, we changed the question to “can PAT actually mean something?” If this was going to become the real product name, the letters needed to describe the product rather than simply preserve our pet-project name.
Giving P.A.T. a meaning
We worked backwards from what the product was actually trying to achieve. It was about publishing. It was designed to get content anywhere a creator's audience might be. And we did not want it to become a single-purpose uploader; the longer-term ambition was a toolkit around the whole publishing workflow.
That gave the pet-project name its proper meaning: P.A.T. — Publish Anywhere Toolkit.
Adding Creator made the audience explicit, and Creator:P.A.T. became the identity we had been looking for without throwing away the name that had been with the product from the beginning.
It also gives us room to grow. Publishing is the starting point, but the toolkit can expand into covers, reusable branding, scheduling, analytics, optimisation and other jobs that sit around the creator publishing process.
The principle behind the product
We keep coming back to one idea: One video. Everywhere.
That does not mean every platform should receive an identical post. Creator:P.A.T. should make the repetitive work disappear while still giving the creator control. A master post provides the starting point; Instagram can have one caption, YouTube another title, Facebook another setting, and the creator should still be able to see exactly what will be published before anything goes live.
That balance between speed and control is central to the way we are building the product.
Built in public, improved by real use
Creator:P.A.T. is being developed iteratively rather than designed behind closed doors and revealed as a finished product. Features are being added, used with real creator accounts, tested, questioned and refined.
That has already changed the product several times. Draft recovery became important because browser sessions fail. Test Mode exists because publishing mistakes matter. Per-platform review exists because creators do not always want identical copy everywhere. Even small details such as connected-account avatars and drag-and-drop uploads matter because this is a tool intended to be used repeatedly.
The goal is not simply to connect four APIs. The goal is to remove friction from the publishing process without taking control away from the creator.