How I Reverse Engineer Businesses from X Posts
Every time someone interesting shows up on my X feed, I end up with the same questions. How do they actually make money? What's the real business model? And if I wanted to build something similar, what would the blueprint look like?
Answering that by hand takes a lot of research, and sometimes I don't even know how to research it. So I built reverse-engineer-success, a free Claude Code skill that does this research whenever someone sparks my interest.
Key Takeaways
- People rarely spell out their whole business online, but they share plenty of pieces in their posts.
- reverse-engineer-success rebuilds the likely business model from those pieces and labels how well each claim holds up.
- The goal is to learn strategies and apply them with your own twist, not to copy someone's product.
Why I study people I look up to
I picked this up from self-improvement books, and I think Atomic Habits was one of them. James Clear argues that lasting change starts with identity, and that we tend to imitate people we admire. So when you're trying to change who you are, it helps to have a role model and mimic what they do, because that's who you're trying to become.
That stuck with me. If I want to become a better builder, I need to understand how the builders I admire actually operate, not just see their wins.
The answers are rarely in one place
It can be hard to crack what someone does to generate their income. Many people keep their apps or SaaS off social media so others don't copy them, and I completely understand why.
But they still share a lot of bits and pieces. A reply explains a tool they use. A screenshot shows a number. A follow-up post admits what went wrong. Put enough of those together and you can start to see how the whole operation works.
What the skill does
You give it an X profile or post, and here's roughly how it works:
- It asks a few questions about your goals.
- It reads that person's posts and replies, then follows public links to their products.
- It checks live evidence, such as pricing pages and sitemaps.
- It looks for competitors and people who tried the same thing and failed.
- It stress-tests the story: do the numbers add up, and who benefits from it being believed?
You get a Markdown report and a shareable page with all the source links. They cover:
- What the business really is
- A step-by-step blueprint
- The key numbers
- What to copy and what to avoid
- Whether something similar is worth pursuing for you
Every claim gets a label, such as Confirmed, Self-reported or Unknown, so you know how far to trust it. You can see the format in this made-up sample report.
The skill is free, but a full run takes a while and uses a lot of Claude tokens. It also works best with a browser logged in to X, because much of the evidence is in replies.
Spotting stories that don't add up
Some people are making it, and some are mostly making it look that way. The skill can't settle which is which, but it shows you where a story doesn't add up.
In my first full test run, an article's itemized costs came to more than double what its opening claimed. The same person had also described their business four different ways in under a year.
That doesn't prove anyone is lying. The skill can't see private revenue, so an unverified claim simply stays unverified. But it tells you when a story deserves more skepticism before you build your plans around it.
Copy the strategy, not the product
I don't use this to clone anyone's product or service. I use it to understand their strategy and how they run things, then apply that to my own ideas, or to similar ideas with my own twist.
After learning how people run automated SEO blog pipelines, I immediately wanted to try the same thing in my own industry. Their apps and niches didn't matter to me. The process did. It's the same reason I think you should do the job yourself before you launch: you learn the most by seeing how the work really gets done.
Try the skill
The skill is free and open source on GitHub. Once it's installed, point it at someone:
/reverse-engineer-success https://x.com/<handle>
It's still new, so please open an issue when it gets something wrong. If you're deciding whether it belongs in your setup, here's how I evaluate AI agent tools.
I'm a software engineer who loves building and learning. You can read more about me or find me on X at @imdeadcode.
I hope this helps you learn more about the people you look up to. Have fun with it!