Work in progress
Hey, I just started building my new app, hoping it won't end up like the rest of my projects. But here's more about the project itself, PostSider. It's an app for publishing and scheduling content on social media. I know, very romantic.
But why is this even needed? Pretty simple. Imagine having all your social media accounts in one place, and instead of posting to each one separately, you can plan and push to several channels at once.
Second thing: scheduling. You plan your posts for the whole week.
And the most important part: API access. That means your whole automation/AI agent setup (Hermes, Open Claw) can plug right in. You can draft a post in Claude Code/Codex, send it over to PostSider, and it'll publish whenever you want, without fighting with the Meta Graph API or setting up developer accounts on every platform.
The thing I'd be careful with is that the product already seems to have multiple candidates for the main reason to exist.
Social scheduling is one story.
Cross-platform publishing is another.
The API layer for AI agents is a third.
The risk is not building the wrong feature. The risk is that early users understand the product in completely different ways, which makes feedback harder to trust.
That feels like the decision I'd pressure-test before building much further.
Really good point, and you're right that I listed three stories when I should lead with one.
The core thesis is the API layer for AI agents. Scheduling and cross-posting are table stakes, they have to exist, but they're not why someone would pick PostSider over Buffer. The bet is that more and more content is drafted by agents (Claude Code, custom n8n setups, etc.), and those agents need a dead-simple publishing endpoint that isn't "go register a Meta developer app."
So the positioning I'm testing: PostSider is the publishing API for AI workflows, with a normal scheduling UI on top for the human in the loop.
Appreciate the push, this is exactly the kind of thing that's cheaper to fix now than after launch.
That's exactly why I'd be careful here.
A lot of products end up with the right thesis but the wrong first users, which creates confusing feedback before launch.
The useful part is making the actual positioning call before the market makes it for you.
If you'd like the tighter version, drop your email and I'll put it together properly rather than trying to unpack it in a thread.