Loading...
Answers
MenuHow can I find clients that pay $50-100/h for web/mobile development, while even with huge experience I always get $10-15/h?
Answers
The first thing you need to do is believe you can get those kinds of rates. You question is littered with reasons why you can't - but the first question you need to ask is "Is there anyone doing development living in Brazil getting paid $100+/hour for their work" - the answer is YES.
So, the better question to ask is "What are they doing different then me to get those rates?"
I know I've paid for remote developers + designers at the $100/hour range, and the thing that justified it was.
1) I had a budget and have paid that kind of rate in the past
2) They're past work, portfolio, online profile, and all interactions with them world spectacular
3) They had passion for their work, almost like craftman.
4) I felt I could trust that they could over deliver on my expectations
5) They were focused on doing one thing great (ex: Mobile Design, iOS Dev, Ruby Dev) - they didn't do it all.
6) Someone I trusted vouched for them.
You don't need all of them, maybe 2-3, but those are some of the things that come to mind.
"Still even after all those years I never managed to charge what I think I am worth. All my client projects run around from US$ 10 to 15/h. Every time that I try to charge more I lose the contract because there is always someone that offers smaller rates."
First things first, don't compete on rates. Ever. Someone can always go lower than you. It's an arms race you don't want to be a part of. Losing a client who prefers a cheaper option is not something you should lose sleep over.
Second, ask yourself: "If not rates, what I am competing with?" Ask yourself, "Why should someone hire me at $50-100 per hour instead of $10/15? What is it about what I do that makes it worth their investment?"
Avoid getting trapped in the weeds when you think about that. The correct answer to those kinds of questions is not really, "Cause I'm a good programmer." A lot of people are good programmers. A lot of them are cheap too. Whatever justifies your higher rate, it's gotta be more than just "I'm really good at code."
As well, whatever justifies a lower rate, it's gotta be more than "Cause I live in Brazil/India/whatever." People who are working with consultants in India/Brazil/etc because the rates are lower aren't the clients you want to attract. You need to attract people who want a consultant who knows what s/he's doing and doesn't care where in the world you are. But before you can get any clients like that, you need to know why it's worth paying you more... what do you bring to the table that others don't and who are you competing with?
Give that some thought... and best of luck!
I always use comparative pricing. don't get one contract at a time. Get 2 or 3. The second one gets priced higher as it requires overtime (effectively). So 15$/hr for the first project, 20$/hr for the second and 25/hr for the third. As time progresses, your rate naturally goes up if you are busy or if you are uncompromising.
Lately, I have been offered a lot to do some very specific jobs. I realised that I can't take one person's money and then offer the same for much less to others, so I have raised my overall rates and it is working really well.
If the client needs to compete for you, they will understand paying you more.
I just came across this question, and after briefly looking through the answers you have, I am not satisfied with the ideas/solutions they are proposing based on your situation.
I run a design studio, do a great deal of design and development work and hire many designers and developers as contractors around the world. I am 100% confident that I can help you position yourself to raise your rates regardless of where you live in the world.
Send me a message through Clarity and I'll schedule a quick call with you at no charge. I'm sure that in a few minutes I can provide you with a concrete, actionable strategy to reposition yourself in the market quickly.
The quote is derived from the 'efforts, time and value' matrix. Before you see what is the average quote in your country/region, see what value you are offering to your clients. If your service matches with a professional in the US, for quality, value and other such parameters, why the client would not pay you the same amount?
Now, the key is to explain the value that you bring to your client's vision, in layers. Make them understand how the quote of USD 15 per hour is different from USD 30 per hr and from USD 50 per hr. If the client wants the USD 40 per hour work for USD 15 per hour cost, he does not deserve you and you should not be working for such clients.
Related Questions
-
How can I manage my developers' performance if I don't understand IT?
Whenever you assign them a task, break down the task into small chunks. Make the chunks as small as you can (within reason, and to the extent that your knowledge allows), and tell your devs that if any chunks seem large, that they should further break those chunks down into bite size pieces. For instance, for the overall task of making a new webpage, _you_ might break it down as follows: 1) Set up a database 2) Make a form that takes user email, name, and phone number and adds them to database 3) Have our site send an email to everyone above the age of 50 each week When your devs take a look at it, _they_ might further break down the third step into: A) Set up an email service B) Connect it to the client database C) Figure out how to query the database for certain users D) Have it send emails to users over 50 You can keep using Asana, or you could use something like Trello which might make more sense for a small company, and might be easier to understand and track by yourself. In Trello you'd set up 4 columns titled, "To Do", "Doing", "Ready for Review", "Approved" (or combine the last two into "Done") You might want to tell them to only have tasks in the "Doing" column if they/re actually sitting at their desk working on it. For instance: not to leave a task in "Doing" overnight after work. That way you can actually see what they're working on and how long it takes, but that might be overly micro-manager-y At the end of each day / week when you review the tasks completed, look for ones that took a longer time than average (since, on average, all the tasks should be broken down into sub-tasks of approximately the same difficulty). Ask them about those tasks and why they took longer to do. It may be because they neglected to further break it down into chunks as you had asked (in which case you ask them to do that next time), or it may be that some unexpected snag came up, or it may be a hard task that can't be further broken down. In any case, listen to their explanation and you should be able to tell if it sounds reasonable, and if it sounds fishy, google the problem they say they encountered. You'll be able to get a better feel of their work ethic and honesty by how they answer the question, without worrying as much about what their actual words are. Make sure that when you ask for more details about why a task took longer, you don't do it in a probing way. Make sure they understand that you're doing it for your own learning and to help predict and properly plan future timelines.LV
-
How do you manage a developer who's slow, especially when you have a small budget and you don't feel like you'll get things done in time?
Usually Programmers are only slow when they don't know how to solve a particular problem. So they will spend a lot of time researching and a lot of trial & errors to solve a problem. It is important that before you engage a programmer on a project, you break down the entire project into simple, easy to understand modules. Let him give you an estimate of how many hours he will require to complete each of the modules. Example: a typical site will have a login module, registration, My account, profile etc. So let him estimate how much he will require to do the login. You can go even detail here. (e.g. how much extra time if you were to implement Facebook/Twitter Login?). Once he start developing, track his progress closely and make sure he is following his given timeline. If he goes over his budgeted time on a module, talk with him and see what went wrong. It is often seen that they may be wasting their time on something very insignificant that you may have asked him to implement, but you can totally go by without it too. So by understanding what is taking longer time, you will be able to prioritise things better. You definitely need some tools to get this done. Google Spreadsheet or Excel works just fine. But if you don't mind spending a few bucks there are many agile project management tools that you might look into. Here is a list, google them all and sign up for trials: * AgileZen * Agile Bench * Assembla * AssiTrack * Blossom * Basecamp * Breeze * DoneDone * Eidos * Fogbugz * GreenHopper * Jugggla * Kanbanpad * Pivotal Tracker Or the reason why he is slow can be purely non-technical. Sometime your developer may don't share the same level of enthusiasm as you about the idea that you are working on. They often don't often see the "bigger picture" (since you don't share everything with them explicitly). If you can somehow get them excited about what he is a part of, it will work like a drug :) He will work day and night without questioning you. But you need to work equally as hard as him. The moment he sees that you are the boss and he is just the guy doing work for you -- his mentality will shift from being part of something to being the low paid developer. Ultimately its all about motivation and making him a part of your venture. After all he deserves it, if he is really playing a crucial role in the entire development.SK
-
What learning path do I have to take to become a "full-stack" web developer?
If I was just starting out, I'd consider learning Meteor (https://www.meteor.com/). It's just entered version 1.0 and after working with it for a little less than a year I do have some issues with it but it still makes for a very solid framework that gets you up and running very fast. You would only need to learn Javascript, and you can slowly work your way towards nodejs from there (which Meteor is based on) if you want to, or you could get the basics down and focus on learning design if you prefer.KD
-
How much should I charge to develop a WordPress site?
Take the # of hours it takes you to do it and charge $50/hour. That's the price. Eventually you can charge $100/hour but that will require a bigger customer. If the customer is small < $1M in gross sales per year - charge $50/hour If the customer id medium < $1-5M / sales - charge $75 Over $5M - charge $100 The challenge you'll face is clearly defining the expectations and handoff so that you're not stuck doing stuff that you can charge for and always getting interrupted from past customers.DM
-
What's a reasonable profit margin on merchandise?
Are you the manufacturer or reseller? If you are the reseller, typically about 40-50% above cost. Use the MSRP as an indicator.ZR
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.