Creative work is hard enough. Running it shouldn't be.
If your team spends too much time chasing updates, repeating tasks or figuring out what happens next, I can help you build a clearer way of working. With automation and AI where they genuinely make a difference.
What could your team do with a little more time?
Those little repetitive tasks add up. See how much time you might free up by making one workflow easier.
For example, renaming and uploading assets, copying information or chasing an approval.
Count repetitions across everyone involved. If three people each do it eight times, enter 24.
An assumption you can adjust, not a guaranteed automation result. Some work will always need a person.
A little less admin. A little more room to work.
2.4 hrs
110 hrs
And what could you do with that time?
For perspective, that's roughly equivalent to…
Not suggesting you spend all that time drinking coffee. But having the choice would be nice.
Illustrative team-wide savings based on 46 working weeks per year. These are time equivalents, not promised outcomes, extra time off or a financial-return forecast.
The work is moving. Until it isn't.
A project starts with a good brief and capable people. Then the changes begin. Feedback arrives in a different conversation. Someone works from an older version. An asset is ready, but nobody is quite sure whether it has final approval.
Meanwhile, somebody is checking messages, updating spreadsheets, copying information between tools and reminding people what needs to happen next.
Nothing dramatic has to go wrong for all of this to become expensive. A little time disappears at every handoff. As the workload grows, so does the coordination.
The problem isn't necessarily the people or the software. Often, it's the way the work moves between them.
MANUAL HANDOFFS; SCATTERED APPROVALS; UNCLEAR OWNERSHIP; VERSION CONFUSION; REPEATED DERIVATIVES; FRAGILE AUTOMATION; MANUAL PUBLISHING. The diagram includes lost and unclear handoffs.
- MANUAL HANDOFFS to SCATTERED APPROVALS
- SCATTERED APPROVALS to UNCLEAR OWNERSHIP — problem handoff: LOST
- UNCLEAR OWNERSHIP to VERSION CONFUSION (controlled state)
- VERSION CONFUSION (controlled state) to REPEATED DERIVATIVES — problem handoff: UNCLEAR
- REPEATED DERIVATIVES to FRAGILE AUTOMATION
- FRAGILE AUTOMATION to MANUAL PUBLISHING
Make the next step obvious.
Imagine opening a project and knowing exactly where it stands. Which version is current. Who needs to approve it. What happens once it's approved. And whether anything needs your attention.
That's what a well-designed workflow makes possible.
I start by understanding how your team already works. Then I help make the important steps, decisions and responsibilities visible. Repetitive handoffs can happen automatically, while creative and commercial decisions stay with the people responsible for them.
You spend less time reconstructing what's happened and more time moving the work forward.
A workflow system is simply the structure that makes this possible — connecting the work, the people and the tools around a recurring process.
KNOW WHERE THINGS STAND
See the current status, version and next step without chasing updates.
KNOW WHO'S RESPONSIBLE
Make ownership and approval decisions clear.
SPEND LESS TIME COORDINATING
Reduce repetitive copying, checking and handoffs.
KEEP PEOPLE IN CONTROL
Use automation for repeatable tasks, not as a replacement for meaningful judgement.
You probably don't need to replace your tools.
Your team already has ways of getting things done. Maybe briefs live in Google Drive, feedback arrives through email or Slack, and production happens in Adobe applications or other specialist software.
Those tools may be perfectly good at their individual jobs. The problem is often what happens between them.
Imagine someone approves a piece of content. Instead of another person copying files, sending messages and updating a spreadsheet, the workflow can take care of the appropriate next steps — while keeping the approval and responsibility clear.
Sometimes a few connections make a big difference. Sometimes an existing tool just needs better configuration. And sometimes a small custom component is worth building.
I work with what makes sense for your team, not with a predetermined collection of technologies.
SAME TOOLS. CLEARER OWNERSHIP, VERSIONS AND NEXT STEPS.
The system should fit the work — not force the work to fit the system.
First, get clear on what needs to change.
Before spending money on a new system, it's worth understanding why the current process gets stuck.
That's what the Workflow Systems Blueprint is for.
It's a paid, focused engagement where we take one recurring workflow and look at how it actually operates. Where does work wait? Which decisions are unclear? What keeps getting repeated? Which tools are already doing their job well?
From there, I design a clearer way for the work to move and recommend what should happen next.
You leave with a practical direction: what to improve, what to keep, what might be automated and whether anything needs to be built.
What the Blueprint gives you
UNDERSTAND
- CURRENT STATE
- FRICTION & RISK
DESIGN
- FUTURE STATE
- HUMAN / AUTOMATION BOUNDARY
- TOOLS & IMPLEMENTATION OPTIONS
DECIDE
- SUCCESS MEASURES
- PHASED PATH
Not every problem needs new software.
Sometimes a clearer way of working is enough.
Different work. The same attention to how things run.
The systems I build come from practical experience with content production, website operations, client delivery and creative projects. Each has different needs, but the same kinds of handoff, ownership and coordination problems appear again and again.
From a rough idea to published content — and what happens next.
Imagine you want to publish useful content regularly across several platforms.
Ideas come from different places: articles worth sharing, blog posts, project notes, source material and things you've learned through your own work. Content Engine brings that material into one editorial process.
It helps develop posts, checks drafts for quality and repeated angles, and prepares content for different destinations. A post might need an image. Another might work better as a carousel or video. Different platforms and languages call for different formats and publishing schedules.
People still make the important editorial and approval decisions. Behind those decisions, the system coordinates the repetitive work, keeps track of what's ready and records what happens when content is published.
That means the next decision can be informed by what has already been done, instead of starting from memory every time.
This is a working production system, not a collection of disconnected automations. It has also been improved through real operational problems — including duplicate execution, interrupted workflows and the need to recover incomplete work.
View full case study- People decide what is worth publishing.
- Writing and visual formats suit the destination.
- Interrupted work can be identified and recovered.
- Published work stays visible for later review.
More work, in different contexts.
02—04 / OTHER WORKWebsite Operator
A website keeps producing useful signals after launch, but they're easy to miss across different reporting services. Website Operator collects that information twice monthly and brings it into one reporting view, making it easier for me to review changes and decide what deserves attention next.
Recurring collection / human reviewClient Operations
When an enquiry comes in, ChatGPT helps me organise information, clarify the brief and prepare next steps. Google Sheets maintains a structured project record, while important commitments and approvals remain under my control.
In use / founder-supervisedCreative production
Before developing workflow systems, and still today, I work professionally in video production, editing, motion graphics and advertising content. That experience helps me understand the realities behind briefs, changes, deadlines, approvals and delivery.
Professional creative-production experience