I had the site built by an agency (30k TL) been using it for 2 months. Suddenly some pages started throwing errors, we asked the agency and they said 'this isn't covered by the maintenance agreement'.
Apparently I need to pay separately for maintenance. The agency wanted '500 TL/month for maintenance'. The site is like 10 pages, how much can bug fixes cost?
Maintenance is 6k TL a year, I paid 30k for the whole site. Doesn't make sense. What happens if I don't have a maintenance agreement?
Maintenance agreement covers: 1) Server monitoring, 2) Bug fixes, 3) Security updates, 4) Database backups, 5) Small feature requests.
Not covered: design changes, adding new pages, big features.
500 TL/month is reasonable (for a 10-page site). Without a maintenance agreement: site will run on outdated plugins, there will be security vulnerabilities.
we didnt get a maintenance agreement after having the site built. 3 months later malware got into the site. anyway then 10k TL in costs.
Correction: I misremembered the figure, it was a bit lower.
How many 'revisions' are included in the maintenance agreement? How many simple tasks like text changes are free?
Doki · Incident response support · 2023
i compare the site to a car: production price 30k, maintenance 500/month. not doing maintenance = letting the car go to waste.
Doki · Phishing awareness training · 2026
Let me summarize the topic, since several different answers were given. Every "we'll look at it later" in a meeting means unbilled work.
Thanks a lot, I'll try it today. Hasty decisions become decisions you have to fix six months later.
Don't hesitate to ask; those who don't ask always pay more.
How did you solve this? Taking notes for two weeks yields better results than a six-month estimate.
Thanks for writing this, that's the right way. Weekly written progress reports are much more useful than asking for dates.
Everyone rushing into maintenance agreement gets stuck at the same point. I'm also curious if anyone does it differently.
There's also a measurement aspect to this. If it's your first time, start small; scaling comes later.
This is my opinion, I'm not claiming it's absolute truth.
Generally correct, but one part is missing. In legacy systems the most expensive thing is unknown dependencies.
The answer varies greatly by industry; there is no one-size-fits-all rule. Of course, it varies if your situation is different.
I'll argue the opposite, don't get mad. Everything goes well for the first three months; problems arise in the fourth.
If I were you, I'd go this route.
We experienced almost the exact same thing last year. People defend habits, not processes. Resistance comes from there.
Correct me if I'm wrong.
I agree with this. btw when making a decision first look at what data you have on hand.
Just leaving this note it might be useful.