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: trypost.it
This is a strong angle because you are not just building another scheduler. The real pain is the part before scheduling: consistently turning blank-page pressure into usable, human-sounding content.
That is a much better wedge than “post to 10 networks.” For agencies and serious creators, the value is not only queueing posts. It is keeping the content engine moving without making everything feel automated or generic.
One thing I’d pressure-test early is the brand frame. TryPost is clear and practical, but it may make the product sound like a simple posting tool, while the bigger direction is closer to an AI-assisted content workflow platform for founders, creators, and agencies.
Xevoa .com would fit that broader direction better because it gives the product more room to grow beyond scheduling into content creation, approvals, agency workflows, analytics, and multi-channel operations.
The open-source angle is already strong. The main risk is that people mentally place TryPost in the crowded scheduler bucket before they understand the bigger content workflow promise. Naming can help prevent that before more users, GitHub stars, and customer memory lock around the current frame.