i pay 4000 lira a month for maintenance. Agency says: 'maintenance covers bug fixes only, no new pages.' But i thought i could get small pages made too.
Define the maintenance scope clearly in writing: 1) bug fixes (free) 2) feature updates (e.g. adding export to user list is paid), 3) hourly work (e.g. 5 hours/month included). If it's not in writing there will be disputes.
Let's separate the concepts they're getting mixed up. When you try to change everything at once nothing settles.
Of course, it varies if your situation is different.
If I understood correctly, you're saying: People defend habits not processes. Resistance comes from there.
If I were you, I'd go this route.
I can't fully agree with this. Hasty decisions become decisions you have to fix six months later.
Good luck with that.
The answer above hits the nail on the head. The cheapest quote is usually the least thought-out one.
Proven by experience.
I can't fully agree with this. In legacy systems, the most expensive thing is unknown dependencies.
If you post the result here, it will help others too.
Doki · Infrastructure migration · 2023
let me share my experience. like when you try to change everything at once nothing settles.
when we decide without measuring, we always end up in the same place and good luck with that.
I feel the same way. Any unwritten clause becomes a point of disagreement later, as both sides remember it differently.
Ask who prepared the quote and who will actually do the work. That's all, sorry if I went on too long.
Doki · Log management setup · 2025
I was thinking the same thing. Everyone rushing into what does the monthly maintenance fee cover gets stuck at the same point.
If code ownership isn't in the contract, you have no bargaining power when leaving. If you have questions, write them; I'll answer as best I can.
I'll try it. Everyone rushing into what does the monthly maintenance fee cover gets stuck at the same point.
Don't hesitate to ask; those who don't ask always pay more. I'm also curious if anyone does it differently.
Let me speak from the other side; I'm on the supplier side. The biggest time-waster for us was not knowing who had the final say.
There's a common mistake people make when doing this. People defend habits, not processes. Resistance comes from there.
Doki · Phishing awareness training · 2026
I'm a small business, let me explain from my side. If scope grows, either time or budget must grow. There is no third option.
Just leaving this note, it might be useful.
Let me summarize what's been said so far. When you try to change everything at once, nothing settles.
That's all, sorry if I went on too long.
Let me write how it's done in practice. Code without setup documentation isn't yours even if you have it.
I'm also curious if anyone does it differently.