I'm building an open source social media scheduler to hit $10K MRR and quit my job
For years I had the same embarrassing pattern. I would commit to posting content consistently, keep it up for a week or two, then quietly disappear. Every product I shipped had the same hole underneath it. I could build the thing just fine. I just could not show up and market it day after day.
At some point it clicked that scheduling was never my actual problem. There are a hundred tools that will queue a post for Tuesday at 9am. My problem came earlier than that. It was staring at an empty box with nothing to say, every single day. None of the tools touched that part.
So I built TryPost.
On the surface it is an open source social media scheduler. It lines up posts across 10 networks. But the part I actually care about is that it helps you create the content with AI, and the whole goal is for none of it to read like AI wrote it. Clean, structured, human.
I made it open source on purpose, not as a sticker on the readme. If you run real volume, like an agency juggling dozens of accounts, you can self host the whole thing and post as much as you want. No per seat pricing, no limits, the code is yours to run however you like.
The cloud version at trypost.it is how I keep the lights on, and I am not going to pretend otherwise. People who would rather not manage infra subscribe, and that money is exactly what lets me keep shipping features instead of letting this rot into one more dead repo.
Now the real reason I am writing this.
I am building Trypost to reach $10K MRR. It is not a vanity number. $10K is the line where I can quit my job and work on my own product full time. That is the thing I want more than anything right now, and I am done being quiet about it.
So I am building it in the open, revenue and all. You can watch the MRR move in real time here:
https://trustmrr.com/startup/trypost-it
Whatever it shows today is the truth. And if it ever hits 10k, you will have watched the exact moment I got to walk away from the day job and bet on my own thing.
If you have already made that jump to full time on something you built, I would really like to know one thing: how did you know your number was actually enough?
Github: https://github.com/trypostit/trypost
Site: https://trypost.it
Thanks for sharing your experience
👊
The industry is quite over-saturated. Wishing you the best mate.
Yeah i know, i'm trying do something different.
Thank you!
This is a much stronger angle than “open source social scheduler.”
The real pain is not scheduling. It is the gap before scheduling: knowing what to say consistently without turning content into another exhausting founder task. That is the part most tools skip, and it is the part that makes TryPost more interesting than another queueing app.
I’d make that clearer everywhere: TryPost is not just helping founders post later. It is helping them keep a publishing engine alive when they are tired, busy, or still figuring out their message.
One thing I’d pressure-test early is the name. TryPost is simple and friendly, but it may keep the product feeling like a lightweight posting tool. If your real goal is to build a serious open-source content workflow layer for founders, creators, and agencies, the brand may need more room than “post.”
Xevoa .com would fit that broader direction better because it feels more like a workflow system than a single-purpose scheduler. The product can stay founder-friendly and open source, but the name should help it feel durable enough to carry AI drafting, scheduling, self-hosting, agency volume, and eventually the $10K MRR story.
The positioning is already bigger than scheduling. I’d make sure the name does not make people shrink it back down.
🫠
The part that resonated with me wasn't the scheduler itself, it was the observation that scheduling isn't actually the problem.
Most creator tools seem obsessed with distribution mechanics, while the real bottleneck is consistently generating ideas worth publishing. That feels like a much deeper problem space.
I'm also curious whether open source is primarily a trust mechanism for you, or a distribution channel. In crowded markets, it sometimes feels like open source is becoming the new content marketing , people discover the project through the codebase long before they become paying users.
Absolutely love the design Paulo, congrats!
Yeah, this hits. The blank-box problem is real, and most scheduling tools just skip right over it. I ran into the same thing with marketing content, it wasn’t that I had no ideas, it was that typing felt way too formal for what I actually wanted to say. What helped was dictating posts out loud like I was talking to a friend. Sounds obvious, but it gets past that editor-brain that shows up the second you see a cursor. I built DictaFlow (dictaflow.io) partly for exactly this, hold a key, talk, let go, and the text is there. The first draft is garbage, sure, but at least it exists. Editing something messy is so much easier than staring at a blank page. Good luck with the launch, the open source angle is smart for volume users.
I'm user of wisprflow, it's game changer, try use it on TryPost, it's really helpful!
"Scheduling was never my actual problem. My problem came earlier than that. It was staring at an empty box with nothing to say."
This is the insight most social media tools miss completely. They solve the logistics of posting but not the blank page problem. You're building for the right pain.
The $10K MRR goal is ambitious but the problem is real and common enough. Consistency is the hardest part of content for most founders. If you can crack that, the scheduling piece is just infrastructure.
How are you helping users with the ideation side specifically?
What's your current MRR and how long until you hit your quit number? Asking because I'm building towards the same goal from a different angle (AI bots, not scheduler).
I launched it few weeks ago, MRR it's ~ $400.
$400 in a few weeks with an open-source angle is solid traction. Are most signups from organic GitHub discovery or from places like IndieHackers/X? Curious which channel actually moved the needle.