Agency is doing the design, price drops with every revision — how many revisions are normal and what's the limit?

This happened to me too. We agreed on 3 revisions, and they counted every button separately :) Then I asked another agency they said: 'we usually give 5-7 revisions no extra fee maybe we'd charge extra on the 8th revision'. So there are much better agencies out there.

read the contract! anyway line 4 it says the revision count there. is there a monthly revision limit? otherwise you'll end up in a dispute.

Revision Rights Checklist: - Is the number of revisions specified in the contract? - How many changes are allowed per revision (max)? - Is there an unlimited revision package (what's the price)? - Are revision requests in writing (email, form)? - What is the response time in days? - What is the end date of the design contract?

edit: typed from phone, sorry for typos.

So how did you request your revisions? In writing or verbally? If it was verbal, the agency might say 'I forgot the count.' If you have a written request (email), that serves as proof.

Revision fees are a very common issue! When making new agreements, always ask: 'How many revisions are included, and how much is each extra one?' Get it in writing. Define the feedback format before the design process starts (consolidate all requests into one list). This way you can reduce the number of revisions.

We experienced almost the exact same thing last year. If acceptance criteria aren't written, when the work is done is open to debate.

Proven by experience.

I'm in the same situation, that's why I'm asking. Solutions that work at a small scale collapse when you grow; I learned this late.

When we decide without measuring, we always end up in the same place. I'm also curious if anyone does it differently.

Absolutely. If I were to add anything: Any unwritten clause becomes a point of disagreement later, as both sides remember it differently.

There is something to watch out for. When making decisions, write down the worst-case scenario too, not just the best.

I'm also curious if anyone does it differently.

It's rare to find an explanation this clear. The system lives on after delivery; maintenance is a separate line item.

If I were you, Id go this route.

We got stuck at the same point for a while. The real issue isn't the number but what it's based on.

Start with a small trial; don't commit to everything at once.

You're right. When making decisions, write down the worst-case scenario too, not just the best.

Good luck with that.

Let me share my experience. Code without setup documentation isn't yours, even if you have it.

If you have questions, write them; I'll answer as best I can.

We experienced almost the exact same thing last year. In legacy systems, the most expensive thing is unknown dependencies.

Hope this helps.

I have a question. If code ownership isn't in the contract, you have no bargaining power when leaving.

Of course, it varies if your situation is different.

I feel the same way. Hasty decisions become decisions you have to fix six months later.

That's all, sorry if I went on too long.

Thanks a lot, I'll try it today.

You're right. Start with a small trial; don't commit to everything at once.

If I were you, I'd go this route.