Quote:
Originally Posted by psili
Unless one is struggling hard to maintain paying bills, a support nightmare isn't worth it. Thus the key word "nightmare".
http://www.andyrutledge.com/calculating-hours.php
I'm not a designer, but the above article was helpful to try and calculate for development time pending the type of client. Maybe "designers" and "developers" aren't taking appropriate CYA approaches to projects, in regard to your question, and thus feel lame trying to branch out. |
The basic idea behind a support nightmare is that a certain client keeps needing more and more time. If you're committed to a single set price, that indeed becomes a nightmare.
On the other hand, when you do projects for larger companies, NGOs, the government, etc., you typically have a contract that specifies exactly what you're required to deliver.
Plan well, and you'll also have a maintenance contract that includes a set number of hours for support and upgrades, with additional billing for additional support and development.
And that's where the real money is. Not in single orders, but in long-term contracts.
Most designers who just sell single designs are extremely vulnerable. A busy month can mean they have to turn down work, and a slow month means their income grinds to a halt. It's hard to plan ahead that way - you'll never know how many orders you'll be getting in the next half year.
If you add service, maintenance, training and support agreements to the mix, you can build a constant stream of income. That makes it far easier to plan ahead and grow your business.