I wanted to change the design color, agency said '1500 lira change fee' — is that right?

things to check for sure: 1) is it written in the contract or not 2) if written, what counts as a revision 3) is it an agency that can handle legal issues, or are they just dodging responsibility to get money

i had a similar situation. they said 'we're good' without a contract but the revision clause changed maybe 6 times. tbh in the end i paid the parameter but they weren't very willing.

legally speaking: if there is a contract and 'revision' is written, the agency has the right to enforce it. but if there's no contract, the agency is stuck. you can ask for a written document and negotiate in that case.

a CSS change is a 5-minute job, but if QA process is added it could be 30 minutes. the agency is billing for the latter, you're expecting the former. you need to define the written workflow.

i used to pay for things like this, then i said 'would you pay this amount if i started the site from scratch?' well that's how it goes what can you do

There is something to watch out for. Solutions that work at a small scale collapse when you grow; I learned this late.

I'm also curious if anyone does it differently.

Yes, that's exactly how it is with change request fee. When making a decision, first look at what data you have on hand.

Correct me if I'm wrong.

The opposite happened to me, that's why I'm writing. The system lives on after delivery; maintenance is a separate line item.

Most time waste accumulates in tasks waiting for approval. Proven by experience.

Let me summarize what's been said so far. When we decide without measuring, we always end up in the same place.

I'm also curious if anyone does it differently.

My questions are cleared up, thanks. When making decisions, write down the worst-case scenario too, not just the best.

I'm also curious if anyone does it differently.

Yes that's exactly how it is with change request fee. Ask who prepared the quote and who will actually do the work.

Good luck with that.

We need to take it step by step. Access credentials should be opened in the company's name, not personal accounts.

Of course, it varies if your situation is different.

Exactly and not many people know this. honestly when you try to change everything at once, nothing settles.

In legacy systems, the most expensive thing is unknown dependencies.

Timely topic.

I've been down this road, let me tell you. Weekly written progress reports are much more useful than asking for dates.

Hope this helps.

Don't miss this: When making a decision, first look at what data you have on hand.

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

Noted, thanks.

I think it's hard to be that definitive about change request fee. When you try to change everything at once, nothing settles.

People defend habits, not processes. Resistance comes from there. This is my opinion I'm not claiming it's absolute truth.