Skip to content
Jonas Nguyen, home

writing / building clienzo · part 1· · 2 min read

Why I'm building a social media scheduler in a crowded market

There are plenty of schedulers already. Here is the narrow bet that made me build another one, and who it is for.

Collage illustration: “Why another scheduler?”

Every list of “best social media tools” already has twenty entries. If you are building alone, entering that market needs a better reason than “mine will be nicer”.

This is the reason I settled on, and the first part of a series where I go through Clienzo one piece at a time.

Who it is for

I did not want to build for marketing teams with approval chains. Clienzo is for people who post for themselves or a handful of clients: a founder announcing a launch, a freelancer running three clients’ accounts, a small agency that wants each client kept separate.

Those people have one thing in common. Posting is not their job. It is the thing between them and their actual job.

The narrow bet

Most schedulers are built around their own composer. You open the app, write, pick accounts, schedule. That works, and Clienzo has it too.

The bet is that more and more writing does not start in a scheduler. It starts in a chat with an AI assistant, in a changelog, in a script that runs when a release is tagged. So Clienzo is built to be driven from outside:

  • A public REST API, so anything that can make an HTTP request can schedule a post.
  • An MCP server, so an assistant like Claude can create, schedule and retry posts from the same conversation where the post was written.
  • Chat apps as channels. Discord, Telegram, Slack and Viber are first-class destinations, next to Facebook, Instagram, Threads, LinkedIn and the rest.

Sixteen networks are live today. Each one turned out to have its own rules, quirks and review process — which is most of what this series is about.

What I want to be honest about

A scheduler is only useful if you can trust it. So two rules shaped the product early:

  1. Every network gets its own result. A post that went out on five networks and failed on one says exactly that, and lets you retry just the one.
  2. No made-up numbers. If a network does not report views for a post, the analytics show a blank, not an estimate.

Both rules cost more work than the alternative. Both come up again in later parts.

What comes next

Tomorrow: the composer, and why “write once, post everywhere” is really “write once, then satisfy sixteen different sets of rules”.