Why I built planpo.st

Lukas
@lukcombinatorI am an IT consultant by day and I build small SaaS apps the rest of the time. Several at once, which is its own problem.
Posting for all of them was the part I kept putting off. The same idea retyped into a different tab for every network, a different aspect ratio every time, and at the end of the month I still could not tell you which post did anything. Likes went up. Nothing in Stripe explained why.
So I built the thing I wanted. Write the post once, send it to every network in the right format, and put the actual revenue next to the post that earned it, straight from Stripe, Shopify or RevenueCat.
Then I added the part I use most. I spend my day in Claude Code, and opening a browser tab to fill in a form felt like a step backwards, so planpo.st ships an MCP server. I ask my agent to plan the week, and it comes back later with what those posts made.
11accounts of my own on it
900+posts published
I run my own accounts on it. As of November 2026 that is 11 accounts and more than 900 published posts, most of them written and scheduled by an agent. It is also how I found the bugs: TikTok videos that went nowhere because nobody had picked a visibility, and a post marked published when one network had failed. Both are now caught when the post is created, and a post that reached two of three networks says so.
Questions people ask
- Which social networks can I schedule posts to?
- Instagram, Facebook, X (Twitter), LinkedIn, Threads, YouTube and TikTok. You write the post once and each network gets its own version with the right format, aspect ratio and character limit, so an Instagram Reel, a LinkedIn company post and an X thread can all come out of the same draft.
- Can an AI agent post for me?
- Yes. Planpo.st runs an MCP server, so Claude Code, Claude Desktop, Cursor, the OpenAI Codex CLI, Gemini CLI, ChatGPT and any other MCP client can plan and schedule your posts by talking to the same API the dashboard uses. The agent can draft a week, queue it, check what published and read back the revenue each post earned.
- How does revenue attribution actually work?
- Every link you post can be wrapped in a tracked redirect. When someone clicks it and later pays, the payment is matched back to the exact post that sent them. Planpo.st connects to Stripe, Shopify and RevenueCat, so the number next to a post is real money from your own payment data rather than an engagement score.
- Is this a social media scheduler or an analytics tool?
- Both, and that is the point. Scheduling without revenue data tells you what you posted. Analytics without scheduling tells you what happened after somebody else posted it. Planpo.st publishes the post and then reports what that post earned, in one place.
- Do I need to be technical to use the AI agent features?
- No. The dashboard works on its own and most people never touch the agent side. If you already use Claude or Cursor, connecting them takes one link and then you can schedule by asking in plain language.
- What does it cost?
- There is a free plan with no card: 2 accounts, 30 posts a month and 200 agent calls. X needs a paid plan. Creator is $24 a month and Pro is $49 a month, with a 7-day free trial on both. Both plans track revenue: totals, MRR and transactions from Stripe and RevenueCat. Attributing revenue to individual posts, advanced analytics and brand voice are Pro features.
- Can I schedule Instagram Reels, Stories and carousels?
- Yes. Instagram supports feed posts, Reels, Stories and carousels. Facebook covers Page posts and Reels (not Stories), YouTube handles videos and Shorts, and TikTok handles video posts.
- Can I approve posts before they go out?
- Yes. Turn on approval when you connect an agent, or any time on the Agent page, and the posts it creates wait in Posts, under In review, until you approve them. Approval starts off, so until you turn it on an agent's posts go out at the time it sets. The agent cannot change the setting itself.
Still deciding? Compare planpo.st with the tool you use now, or read how revenue attribution works.
