You're starting from a position of what do I have (software dev skill) and trying to backfit a need onto it.
The right mentality is to think hard about your buyer: What are you selling, why would someone buy it, and how would they find you? Ideally it should be some kind of business need, like "I want to stop using Expedia at my hotel and transition to get more direct bookings" or "I need a very high-value, complex system migrated from one thing to another". The more risk/difficulty/P&L impact/fewer people can do it, the more you can charge.
What you don't want to do is come in and just be a coder. Those are a dime a dozen. Even though developer skill varies dramatically, there's no way to really bill for that. Most business buyers are going to see "C# developer" and want to pay the lowest rate they can. It is outrageous how little the pay difference (even at software companies) is between high and low performers. It's like 2x, it should probably be like, 10x (no company outside finance would ever tolerate this kind of pay difference). You will never win charging 2x when the other guy is charging 1x for what, on paper, looks like the same skill (a relationship/reputation can offset this partially).
Don't become a "consultant" unless you want to do sales and marketing full-time, as that is the end-state of a successful consulting career. If that isn't your cup of tea, either find a better dev job (if you want to keep coding professionally) or find a company like 10x who will place you with good clients and do the grunt work for you of selling, where you can simply come in and provide value as a high-skilled technical person (which has its benefits, including decent pay, work from anywhere, put up with less of the posturing/BS of typical office life).
Source: did this. Wasted a lot of time doing bottom-of-the-barrel dev work before I realized probably 95% of the software that gets written in the world is boring, not particularly well paid, and has no real career trajectory in front of it.
Comments
This whole thread is misguided.
You're starting from a position of what do I have (software dev skill) and trying to backfit a need onto it.
The right mentality is to think hard about your buyer: What are you selling, why would someone buy it, and how would they find you? Ideally it should be some kind of business need, like "I want to stop using Expedia at my hotel and transition to get more direct bookings" or "I need a very high-value, complex system migrated from one thing to another". The more risk/difficulty/P&L impact/fewer people can do it, the more you can charge.
What you don't want to do is come in and just be a coder. Those are a dime a dozen. Even though developer skill varies dramatically, there's no way to really bill for that. Most business buyers are going to see "C# developer" and want to pay the lowest rate they can. It is outrageous how little the pay difference (even at software companies) is between high and low performers. It's like 2x, it should probably be like, 10x (no company outside finance would ever tolerate this kind of pay difference). You will never win charging 2x when the other guy is charging 1x for what, on paper, looks like the same skill (a relationship/reputation can offset this partially).
Don't become a "consultant" unless you want to do sales and marketing full-time, as that is the end-state of a successful consulting career. If that isn't your cup of tea, either find a better dev job (if you want to keep coding professionally) or find a company like 10x who will place you with good clients and do the grunt work for you of selling, where you can simply come in and provide value as a high-skilled technical person (which has its benefits, including decent pay, work from anywhere, put up with less of the posturing/BS of typical office life).
Source: did this. Wasted a lot of time doing bottom-of-the-barrel dev work before I realized probably 95% of the software that gets written in the world is boring, not particularly well paid, and has no real career trajectory in front of it.
I worked as a contractor early in my career, on a team made up of contractors.
It's just temp work. It wasn't how I wanted to run my career, but I wouldn't knock anyone for doing it.