JMS320: Freelancing 101 – Part 1 – How to Find Problems People Will Pay You to Solve

This is the first installment of a 4-part tutorial series I’m doing, Freelancing 101: A Dead Simple Method to Get Your First Freelance Work. In this series, I’m walking you through the exact process I used to get my first freelance clients. The nice thing about this method is you get to start slow and simple, get your feet wet and grow at your own pace. Instead of trying to land and then deliver on $3,ooo or $5,ooo or $15,000 projects right off the bat.

That can be scary as hell.

What I’m going to show you isn’t. Yet, you can still make damn good money doing it.

But, with that said, lets jump into Part 1: How to Find Problems People Will Pay You to Solve. And, the key here is finding urgent problems you can solve for clients. The more urgent the problem, the easier it will be to get clients. So, here’s what to do:

Resources

Rate and Review the Podcast

If you leave a rating and review of the podcast, I’d really appreciate it. It’s the main way more people find out about it which allows me to bring even more value to you as a listener. I believe that so much I’ll even give you Module 1 of my PHP 101 course for FREE if you leave me an honest review. Get the details on that here: https://www.johnmorrisshow.com/start-here.

Related

2 Comments on “JMS320: Freelancing 101 – Part 1 – How to Find Problems People Will Pay You to Solve”

Dave C

April 18, 2018 at 5:35 am

John,

Thank you for putting together this series. My question is . Is there really that much business that I would be able to solve a couple of these problems a day? I’m skeptical. Sounds too good to be true.

I have learned a great deal from your podcasts–especially one like JMS320 (4/16/18). However, I have come to a time when I want to do Internet ad videos for web clients. How would I get involved in a business like this? By the way, my background includes designing, writing, and testing semiconductor wafer fab automation code in C. Even when I was working that job my passion was not writing the code, but making the code work for the customer. Thank you in advance for your answer.