For the complete documentation index, see llms.txt

TwitterShots $500 MRR

5 min read

"twittershots trusted by Stripe"

I open-sourced this product's revenue on trustmrr.

Today is the day — TwitterShots hits $500 MRR.

A small milestone, but one that took me a year to reach.

I Almost Gave Up

TwitterShots is my first product as a solo founder.

Honestly, I made many mistakes, there were a few weeks where I thought about just stopping.

Traffic was coming in, signups were happening. But barely anyone was paying. I wasn't sure if any of this was worth it.

TwitterShots it has been free to use for a long time. I made a decision: switched to a limited quota instead.

The people who actually needed the tool paid for it. The people who were just "trying it out" disappeared — and that turned out to be exactly the signal I needed.

The quota change wasn't pushing users away. It was helping me find the right ones, after that, MRR actually started moving.

What I Learned

Earn The Trust

Nothing is given, everything is earned.

Earn trust through no excuse, the system broken, the API do not render right, just apology and repair quick.

Earn trust with feedback and quick support, I read every tickets and feedback and get back to them.

Earn trust through authenticity & openness.

Real feedback, real testimonial, real revenue, I don't want to win traffic and applause through fake data.

Trusted by 10544+ real content creators.

The number is select count from TwitterShots database.

TwitterShots hits $500 MRR.

The number is from Stripe MRR, In fact, I've made this product's revenue public.

On users: Go find real feedback, don't wait for it

Staring at your dashboard won't tell you what users actually think.

I started reaching out — sending emails, replying to every tweet, asking questions in communities.

Every customers got directly founder's responses.

Yes, I read and write every emails to the paid customers.

A lot of features I thought people would love? actually nobody cared.

The gap between what you think users want and what they actually want is huge more than I thought.

On SEO: Write about their problems, not your story

When I first started writing content, I wrote about myself — What I wrote reflects what I want to express.

I’m thinking about how users would search for and use my product.

What actually brought in traffic was writing from the user's point of view.

What are they typing into Google? What problem are they stuck on? I started answering those questions instead.

Not my experience — but user experience.

That one shift brought more traffic than before.

On building: Validate first, code later

For a while I got completely stuck trying to make the code perfect.

Better folder structure, cleaner architecture, reusable components — I was having fun writing it, but nobody was really care about your stack.

My rule now is simple: validate first, code later. Make sure someone actually wants the thing before you build it.

Don't spend time polishing something nobody asked for.

What's Next

TwitterShots isn't going anywhere.

This is just the start.

I want to keep building more tools around tweets and social content. I'm also seriously thinking about enhancing API — so developers and teams even AI agent can plug screenshot generation directly into their own workflows.

I want to sincerely say thank you, from the bottom of my heart.

Thanks to everyone who has visited my site, those who shared design feedback, and those who sent kind emails and encouragement.

Thank you to everyone who has paid for a plan. You're not just paying for a tool — you're telling me this is worth continuing. That means more to me than the $500 number itself.

Sign up to TwitterShots

Start Creating Professional Tweet Screenshots

Join the group who trust TwitterShots for their content. From tweet threads to Instagram carousels, create stunning screenshots in seconds.

  • Turn Tweets into Image
  • Custom Branding & Themes
  • Bulk Twitter Screenshot
  • X Post API

© 2026 TwitterShots. All rights reserved.