Two years of independent development experience Programmers tell us the experience of making money (listen to the masters who really make money)

Going it alone and building your software product can pay big dividends, but there are caveats on the road to success.

Like almost all software engineers, I've always longed for the idea of ​​building a software company, and in 2020 I started a conquest where I'll be making five software products in two years, three of which fail and one gains insignificantsuccess, while others are reaching $300 a month in revenue.

Making money with your software is easier than you think
Seriously, we think too much.

As a software engineer, it's easy to want to build more features or fix a small bug that doesn't affect anything or get our code to 100% test coverage.In reality, it's just a waste of time, and your users probably don't care about it.

Every product I've launched that can charge users has had at least 3 sales.

One of the best is WallStreetTexts.A simple project I built in 4 days, had 35 paid members in two weeks, and didn't have a single test case or fancy UI on the site.

The project failed due to cost and the client's decision not to pay more than $8 for the service.

Everything the landing page contains is an input field, an image, a logo my friend cobbled together in 30 minutes, a button to the Stripe checkout form, and a fully cobbled together MVP (Minimum Viableproduct).

Lessons: Just start it!Build a simple version of your product in no more than two weeks, charge, and see what happens.Making money with your software is a lot easier than it first seems.

Make sure you do everything you can to make your project work

In retrospect, I made a big mistake with WallStreetTexts.I didn't analyze how to improve the product to increase its value or figure out how to make it profitable.

I just looked at the numbers and didn't stop to see how to improve them.

Furthermore, its MRR is around $280, which is profitable