>>1010259 (OP)Just don't leave room for revisions?
When I was working with clients, after every day of work, I'd send the client a few renders or screenshots of what I finished that day and a description of what I was tackling next. Obviously if it was small shit I'd hold off a bit before sending, but I'd generally try to have something sent to the client consistently.
Including the client in on the creative process means they've got a direct line for changes they need BEFORE it becomes a hassle to make them, helps them see the big picture, and covers your ass if all the way down the line if they say it's not what they wanted ("my nigga, you've been giving me the OK for weeks").
Sometimes you'll get clients that are like "wow cool" or "looks good" and won't offer much except a vague response that says you're going in the right direction, but sometimes you'll have clients that are useful to bounce ideas off of and actually make meaningful suggestions that improve the work as a whole.
Of course doing this approach means that you need to know when to reign things in a bit for those enthusiastic clients, otherwise the project can start going way out of scope, but it's a fun way to work and build relationships that create repeating clients.
Those clients that mesh well can make for really fun projects though, and if I'm enjoying myself I do sometimes let loose and let things run a little wild if it means a better end product that I'M happy with as well as the client.
To me, best way to avoid revisions that require a rework of an entire project after you've kept the client in the dark the entire time, is just to not do that. Don't get a job, go dark for a few weeks and just send them a final product.