Simply double your hourly rate.
...wrong
Many developers are quick to say $'x' for a 'y'-page website based on what is the "going rate." There...
For further actions, you may consider blocking this person and/or reporting abuse
Good 👍 Article.
I don't do freelancing but code on front-end as well as on back-end and nowadays digging more of MongoDB.
As suggested value-based approach is effective than others, so if a code crashes during that year then how to handle that?
As the client is giving you some % of the profit then how one should charge?
There's a guy on YouTube called Fox Web School who also hammers home this philosophy. I have personally found that it absolutely works and more freelancers should adopt this approach. Thanks for sharing Guy!
Thanks Luke for suggesting this channel
This is a revolutionary approach that can help both businesses and developers to grow.
Pleasure is all mine Luke!
Thanks for sharing these valuable information.
Excuse me, I'm new front end developer can you explain to me how a developer can increase a website sales ?!
I'd be grateful for that 😃
First of all welcome to the club(FRONT END DEVELOPERS)🎉. and thanks for the idea stay tuned, I'm a writing a whole post for you on "How to increase a website sales!".
Pleasure is all mine Gad
Great 🤩
Thank you very much
I too want to know this
@ntare_guy Points made are well taken but It is never easy to predict how many sales a website will make and even if it is this should not be folllowed blindly as the calculated price can drive potential customers away.
Lets say a local Ferrari dealear comes to you for an improved presentational website of latest ferrari models. The cheapest Ferrari I believe is above $250K. Lets assume the dealer is able to sell 1 extra Ferrari per month after website improvements. You can not blindly charge $250K for improving a presentational website unless you are going to deliver some miraculous improvements. The owner would probably get 2-3 different offers and if you are the one with extrordinarily high price you are probably never going to hear from them again.
My personal approach over the years would be to have a set hourly rate in mind and estimate the time it would take me for the project and weight in some unforseen delays and revisions (+30% to %100 extra hours) and give the customer a fixed price based on the hours but without telling hours or hourly rate. Over the years or over the course of the same year (if you feel comfident) you can raise that hourly rate but it should come with your experience which can be delivered to the client without them realizing.
In some rare cases I would use my calculated price as lower bound and the potential sales improvements as upper bound price limit before arriving to my final offer ;-)
My 2 cents
I couldn't disagree more with the conclusion. Cards on the table: I bill clients hourly, invoice monthly (no deposit), and have been doing so for the majority of the last 10 years. My work needs to continually justify the rate I bill, which is incentive to work hard on every project and always look for ways to get better and more efficient.
The result? I get paid in a timely manner, reliably. Clients come back to me for new projects, and when stakeholders leave, they sell me in on projects at their new companies. I have the flexibility to turn down projects I'm not interested in or steer the tech stack that gets used. And very little of my time is spent on contracts, marketing, or sales. I don't even have a real website, just a kludgy template on Persona.
The reality is that concerns about capped hourly earnings are moot if you're billing at a competitive rate and revising it periodically. Freelancers routinely out-earn their peers doing full-time work while having more flexibility—if they couldn't most wouldn't be taking on the additional risk.
Thanks for sharing. I am a full-stack web developer, recently joining here on DEV. I prefer to calculate the hour and then multiple the hourly rate. Most importantly, I analyze and document the requirements with an EDD and let the client approve this. So, we are on the same page and do the design and development by items in an agile method.
Once the Client approves the item/s, then I close that as done.
Thanks,
Sanjoy
skpaul.me
DevsStation.com
Thanks so much for these tips! I usually charge a flat fee up front based on a certain number of hours and revisions. After that I start charging by the hour or request.
That's not bad(charging a flat fee) but it's not consistent, as i said don't sell HOURS , sell potential RESULTS. Trust me Sarah you'll grow irrevocably.
Thank you Sarah, pleasure is all mine
Thanks for the advice.