Chief Martech Officer's Founder, Nicole Pereira was recently featured in Template Monster's blog 'How Many Revisions on Projects Do You Offer? Devs and Designers Shared Their Personal Stories [+Survey].'
The amount of project revisions allowed seems to be a touchy subject. Some allow for a limited number and some don’t limit them at all. In this article, developers and designers were asked to share their opinions.
The Number Of Project Revisions Allowed Seems Controversial
After doing some of our own research on this topic, it seems a little all over the place.
On one hand, you want to make your clients happy and produce an end product that you are proud of. On the other hand, some clients take advantage of their developers and designers and have endless revision requests - costing you time and eventually more money.
So what's the solution?
Well some options are below:
- Include an exact number of revisions allowed in the contract before the project starts
- Set up milestones within the project time frame, so the client knows exactly when they can give feedback and how many times
- Allow for an unlimited amount of revisions within a specific period of time
- Allow for an unlimited amount of revisions within a specific period of time and then anything after that is out of scope and costs more
- Allow for an unlimited amount of revisions for an unlimited amount of time
If you aren't sure of which direction to go, choose the one you are most comfortable with and see what happens. If the project seems to run smoothly and the client is ok with the revision expectations you've come up with, then you should be good to go.
Ultimately, this could differ with the various clients you end up working with, as some will have more design and development experience than others.
To learn more and read the full article click the button below: