5 ms·
A client that doesn't know what he wants is a bad client. Those kinds of people often have unrealistic expectations like "I want a website like Facebook for $50
by kjksf 9y ago
A client that doesn't know what he wants is a bad client. Those kinds of people often have unrealistic expectations like "I want a website like Facebook for $500". Don't work for such people.
That leaves people who do know what they want. So let's look at it from their perspective.
Let's say they need a Windows desktop app.
Two people apply for the job.
You say "I'm a great programmer, here's a website I wrote".
The other guy says: "I'm an experienced C# programmer. In the past I've developed 3 Windows desktop applications in C#/WinForms and I can do the same for you".
If you were hiring, who would get the job.
This is not about pushing C# technology but a best match between what the client wants and what your skills are.
It's also not about C#.
What the OP meant is that if you have a specific skillset, you should market that skillset specifically. Both ruby backend programmer and an iOS mobile programmers are programmers, but when a client is looking for iOS mobile programmer, he'll pick someone marketing his "iOS programming skills" over someone marketing his "programming skills".
- gk1 9y ago> A client that doesn't know what he wants is a bad client. I disagree completely. A prospect who doesn't know what they want is an opportunity for the freelancer to provide more value by finding a solution for them. You're conflating "unrealistic expectations" with "I know I have a problem but I don't know what the solution is." The former is something to avoid. The latter should make cash-register sounds in your head because it's an opportunity to provide more value and charge accordingly.
- inanutshellus 9y agoI believe his main point is that a client that doesn't know what he wants also doesn't know how much to spend, and sure doesn't want to over-spend. If you find someone that doesn't know what they want but is throwing cash around, sure, be the expert that leads them to digital nirvana. Generally though, if they don't know what they want, they don't realize how hard it is and so will be in for some serious shell-shock when you tell them the price tag. At which point you're either lowering your rate to still do the work or you've wasted a lot of time talking to them (which they generally don't expect to pay for unless your forte isn't writing code but "being the expert that tells you what you want").
- gk1 9y agoI think we’re talking about different classes of customers.
- HeyLaughingBoy 9y agoThis is where you quickly educate the customer. It's no different than you calling a plumber, only to find out that what you thought would be a $50 job is really a $500 job. If they seem like the type who doesn't understand the cost, you tell them "from your description you're already well into 5-figure development cost." Or "$500 is typically what you'd expect to pay for minor website content updates." This ballpark pricing shouldn't take more than a few minutes to figure out. And it puts the ball back in their court to do more research and figure out if they can really afford the going rates.
- mrhappyunhappy 9y agoThis times 1000.