Startup builder · building Clienzo in public
Building SaaS.
Sharing the journey.
I'm Jonas. I look for opportunities worth building, then build the startups myself. Here I write down how it really goes — what shipped, what broke, and how I got past it — so you can skip a few of my mistakes.
- networks shipped in Clienzo
- 16
- build log entries
- 6
- articles
- 17
- tools in the stack
- 7
What you'll learn here
Notes from building a real product, not theory. Every article comes from something that actually happened.
Building a SaaS, part by part
The composer, publishing on time, retries, analytics, an API and an MCP server — how each piece of Clienzo works and why.
Getting past the gatekeepers
Meta App Review, YouTube verification, rate limits and paperwork: what each platform asked for, and what I would do first next time.
AI you can actually trust
Drafting posts with AI, then checking every price and date in code. Where AI helps, and where it needs a leash.
Finding the next idea
Opportunities I look at, the ones I say no to, and the questions that decide which ones are worth building.
Clienzo
Write a post once. Publish it to every network your business uses.
A social media scheduler for founders, freelancers and small agencies — with a public API and an MCP server, so posts can come from the app, a script or an AI assistant.
- Threads
- Bluesky
- Mastodon
- DEV
- Discord
- Telegram
- Viber
- Slack
- Tumblr
- Dribbble
- Dailymotion
- YouTube
a peek inside →Latest articles

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.

Three ideas I said no to, and the one I picked
Before building Autopilot I looked at a link-in-bio tool, an AI visibility tracker and SMS review requests. Why each one lost, and what made the winner different.

Platform reviews are part of the product
Building an integration takes days. Getting a platform to approve it can take weeks. What going through Meta, Google, Pinterest, Tumblr and others taught me about planning.
- The networks I chose not to support (yet)
- When the blocker is paperwork, not code
Shipped recently
Autopilot drafts next week's posts
Clienzo researches trends for your business, drafts a week of posts, checks the facts and waits for your approval.

Comments in the public API, and Dribbble
The API can list, read and reply to comments. Dribbble becomes the sixteenth network.

Meta approves comments and insights
Facebook, Instagram and Threads permissions for the inbox and analytics are approved. The Meta review is done.

YouTube verification is complete
Google's OAuth verification and API audit are both done, so anyone can connect a YouTube channel.

The stack behind it

Astro
Static-first web framework. This site and the Clienzo marketing site are built with it.

Brevo
Transactional email for Clienzo, and the newsletter provider behind this site.

Claude Code
AI coding agent in the terminal and editor. Much of Clienzo, and this site, was built with it.

Cloudflare
DNS, CDN and hosting. Clienzo's domains run through it, and this site is deployed on Cloudflare Pages.

Firebase
Authentication and Firestore for the Clienzo app.

Google Cloud Run
Runs Clienzo's API and its background jobs as containers.

