From one post a week to several a day

Item: Upload-Post
Author: Daniel Hanson Music

A musician who built his own front end so an evergreen content pool keeps publishing itself.

danielhansonmusic.com

Daniel Hanson recording vocals in his studio — Daniel Hanson in his studio

Several/day

publishing cadence, up from one a week

5h+

of productive utility per week

Before Upload-Post

Posting happened by hand from mobile apps or their desktop versions, at roughly one post a week across a few platforms.

Older content that had performed well was almost never recycled. There was no time for it, and no budget for a team to do it instead.

How it works now

Daniel and a friend built a custom front end, and he still builds it with Claude. It is a private website with a scheduling engine: everything runs through it, not through the Upload-Post dashboard.

Video files live in remote storage and are referenced from Notion. The engine turns that Notion data into a set of queues and hands the storage links to the Upload-Post API, which publishes them to each platform as needed.

Data flows back the other way. Upload-Post status drives Discord notifications for upcoming, successful and failed posts, and the live URL of each post is stored in Notion next to performance data pulled from the platforms.

From the front end he can see and edit the schedule and preview upcoming posts. He loads up the content pool now and then; his own involvement is down to occasional tweaks and check-ins.

Schedule board of Daniel Hanson’s custom front end, with posting queues per account and a post preview — The schedule board of Daniel’s own front end, built with Claude

What changed

Publishing moved from about once a week to several times a day, across more platforms.
A Threads presence that had been, in his word, "crickets".
Performance and staleness are tracked per post over time, and that decides which content gets reposted, which gets pruned and what to produce next.
At least five hours a week of productive utility, spent on work he could not otherwise have taken on.

It's less that it's saved me time, and more that it's enabled me to do things I would never have had the time to do.

Daniel Hanson

Music producer and vocalist

In their own words

“If you want a clean and reliable way to automate your posting schedule programmatically, this is it.”

“We looked hard for the right fit and came back to Upload-Post every time. For the price and feature set, it's the clear winner.”

“I can load up the content pool once in a while, and then let my Upload-Post API integration do the heavy lifting and decision-making.”

“All through my custom frontend. However, I used (and continue to use) Claude to build it. It's a continually-evolving project.”

Publish everywhere with one API call

Free tier, Python and JS SDKs, no credit card required.

Start free All stories