Kadenzo
Kadenzo — The all-in-one social media scheduler for creators
Hey IH!
I'm Jan, one of two people building Kadenzo. First post here, so let me start with the why.
For a couple of years I kept watching the same thing: creators and small agencies paying for a scheduler, then a separate app just to read their comments, then something else for listening, and at the end of the month still copy-pasting numbers into a spreadsheet to build a report. Four subscriptions and a hundred open tabs to do one job.
That always felt backwards to me. Planning it, posting it, replying to people, seeing what worked, that's one workflow. So we're building one tool that does the whole loop instead of four that each do a slice of it.
Today Kadenzo schedules to ~12 networks from a single calendar, pulls every comment into one AI-triaged inbox, tracks brand keywords, and gives you analytics you can actually export. Nothing revolutionary on its own, the bet is that having it all in one place, at a price a solo creator can afford, is the thing.
The two parts I'm most into are less obvious:
DM automation for Instagram and Facebook — the "comment a keyword, get an auto-DM with the link" flow, built right into the tool you already schedule from. Rolling out now.
An API + an MCP server. I wanted Kadenzo to be scriptable, and honestly I wanted my own AI agent to be able to schedule posts. So there's a REST API, a CLI, and an MCP server you can drop into Claude or Cursor. That last one's been the most fun to build, and weirdly the thing that gets the most "oh, nice" reactions.
We're bootstrapped, two people, in Prague. No funding, no big launch, just shipping and talking to users. $19–$49/mo, 7-day trial, deliberately under the. Hootsuite/Sprout tier.
I know "social media tool" sounds like the most saturated space on earth. Probably is. But every time I show someone the one-tool-instead-of-five thing, or an agent scheduling a post over MCP, something clicks, so we keep going.
Happy to get into anything: stack, API design, how we think about a crowded market. And if you run social for yourself or clients, I'd genuinely love to hear what's in your current tool stack and what drives you nuts about it.
You can check it out at: https://kadenzo.app/
— Jan
1 Comment
I like that you're defining the product around the workflow rather than the feature set.
Scheduling, engagement, listening, and reporting all exist already. The harder question is whether users should have to think about them as separate jobs in the first place. Building around the complete workflow feels like a much stronger positioning than trying to win feature-by-feature.