This is pretty far removed from how I price jobs, specifically web apps.
To me, web apps are not comprised of "screens" or "templates". They're comprised of components, flows, and interactions.
The concept of "revisions" never made much sense to me either, especially building them into your pricing. When designing, I exhaust all the options that I think have merit, then present the option that works best. I also explain how I arrived at that conclusion and discuss my thoughts. If someone thinks of a potentially better approach, then we can explore that option too, at extra cost.
I rarely deliver PSDs. If I'm not building the front-end myself, I usually deliver some mocks, plus a CSS based UI kit (not production ready), plus some CSS transitions/animations (not production ready), plus maybe some Google Docs with extra thoughts.
The pricing is higher than I usually charge. $8k - $12k for 30-50 hours work on a web app seems very high to me. Please don't tell me I'm under charging?
I also don't price that way (I always priced by time personally).
But I wanted to give readers an idea of the amount of work involved in each project. Maybe using actual, real-world projects as examples would be a better way to do it?
And regarding pricing, the “expert” category is intended to be the upper bound of pricing. So it makes sense that most people would fall somewhere below it.
It can be tricky for freelancers to know how much they should charge, or for clients to know how much they should budget.
So I've been working on a set of very general pricing tables to use as a starting point for discussions.
Would love to have some feedback: are the prices too low? too high? what would you do differently?
This is great. Pricing is definitely hard. How do most people determine their pricing? What's your biggest challenge with it?
Thank you, this is a great idea. It's something that I've been looking/waiting for due to my lack of a) knowledge on pricing and b) mentors.
The one thing I will say is that it may be nice to expand the print section to some smaller pieces (rather than just a logo or a full brand set). I have had requests for tiny jobs (1 brochure, business card design, etc.) before. When you're just starting out, it's hard to understand how much to charge for something so small.
Just thought that may be something that can help out the 'junior' category' people, as they may be likely to get those small jobs when they start freelancing. Wouldn't be much help to the other categories, as they're probably not taking on jobs that small. May help to keep the juniors from low-balling and undercutting their pay though.
Good point. I'm doing this for Folyo, which usually only features medium/large projects, so for now I'm focusing on those. But a real survey should definitely include more categories.
The midline prices are good benchmarks from my experience, but there shouldn't be a cap to how much something can cost. Projects for different clients are worth variable amounts which each designer needs to take into consideration from the start.
Another thing I disagree with as a web developer and designer is the suggested cost reduction for a redesign. In all of my projects I take time to assess the content I'm working with and to structure it (IA) as I and the client see best fit. Even if we don't use my proposal, I still spent time working on it and understanding the content so I still need to be paid for it. Assuming the rest of the project is visual or coding, it ends up being at least the same amount of work as a new design.
Agreed, I'll remove the redesign option.
I like how you give an example of the scope of the work to help frame things. Other things that may factor price are complexity of pages on apps especially. Modules and components of some target areas could take days rather than hours to develop, prototype and refine.
Sometimes I think designers (especially product designers) had a similar system like architects have for projects. They often think in $/sq. ft. Which helps generate an estimate of budget based on area and how much the owner wants to put into the house/space.
In our case, whether it's pages or screens, you could come up with some average rate of complexity based on the apps scope and vision.
Really great work but I find the coding prices for many of the items completely off base. Coding an iOS app takes much longer than designing it usually.
"Coding" was supposed to be front-end coding. I added it to the mobile app table by mistake actually.