CSCareerQuestions

4. this might just be me but the business side of things is a drag and takes a lot of time. Marketing, specing, client relations, it was too much for me as a one man shop, don’t discount how much time it takes.

It is! It's not just you. Running a business is a full time job on its own. When I finally accepted a corporate job, I was shocked to see that there were 15-20 person teams to do what I was doing all by myself.

The best option is to team up with someone else whose skills and passions are in marketing and client acquisition. Create a bidding template for them, like a rate card, and then unleash them. Split the cost of the projects with them. Don't forget to charge enough to make splitting worth it. Ideally this is an actual company, but another freelancer could work in this role too, if they're actually serious about building a business.

OP, making these contacts and setting this stuff up takes a lot of time. You can either make that your primary goal before starting, or you can just start trying to get jobs off job boards and hope you meet someone along the way. Eventually you'll get a marketing client and if you're good, they'll want to team up.

It's rough out there without a brand. There are a billion overseas "programmers" who will gladly work for $25 a day. They're going to be bidding on all the same jobs that you are. You really have to stress the value you bring in ease of communication. That is worth a ton. Companies and people value time and money. They will waste a lot of both working with a cheapo programmer.

You'll probably have to take some crappy, low paying jobs to start your portfolio. Don't rush those. Build them perfectly, and then proudly display them and the client testimonials in your portfolio. You'll eventually be able to charge more.

The guy above me already stated it, but it can't be overstated. A. Job. Will. Take. Longer. Than. You. Think. My strategy when I was freelancing was to break the project down into pieces, estimate everything using a chart I had for how long those steps took under ideal circumstances, add an hour for the time spent estimating, add 30% fluff, and then double it. That was usually pretty close to the actual time spent. You need to remember that all the time spent chasing the client down for images and answers, talking about what you've built, doing demos, and all that sort of stuff is time you need to be paid for. If you don't account for that then you'll hit the end of a year and realize that you just worked 52 weeks, 7 days a week, 15 hours a day, and made $17,500.

Best of luck! There are easier ways to make money with these skills, much easier, but few are as rewarding.

This makes a lot of sense. I'll have to see how I can apply this locally, but at least it's more information that I had before on how to approach this. I appreciate it, thank you.

I'll look into this and see if I can fill in the gaps. Thank you!

I have a degree in philosophy, which, as far as I can tell, is more of a "support" degree that says I like thinking and learning a lot. I've thought about going back and seeing what I can do, but I'm honestly so broke that it's not a viable option.

Related, but how much time per day did you put into learning practical skills? I put in a few hours each week, maybe somewhere between 5-10 hours, but it feels like I'm really low-balling the amount of time I should be coding and applying what I know.