Translating the site into 3 languages, is it 3x the cost?

Saved. Solutions that work at a small scale collapse when you grow; I learned this late.

How did you solve this? If acceptance criteria aren't written, when the work is done is open to debate.

This is my opinion, I'm not claiming it's absolute truth.

let me write how it's done in practice. i mean the system lives on after delivery; maintenance is a separate line item.

everything goes well for the first three months; problems arise in the fourth then of course, it varies if your situation is different.

Saved.

If youre going this route sort this out first... honestly code without setup documentation isnt yours, even if you have it.

Just leaving this note, it might be useful.

Good call starting this thread.

I went through the same thing.

If you're going this route, sort this out first. In legacy systems, the most expensive thing is unknown dependencies.

Just leaving this note, it might be useful.

Thanks, this was very helpful. When making decisions, write down the worst-case scenario too, not just the best.

Just leaving this note, it might be useful.

Thanks for posting... tbh just because everyone does it doesnt mean its right.

Hope this helps.

I'll try it.

My perspective changed after experiencing that. The harder it is to reverse a decision, the slower you should make it.

It's rare to find an explanation this clear.

This is exactly what we experienced. Most time waste accumulates in tasks waiting for approval.

Any unwritten clause becomes a point of disagreement later, as both sides remember it differently.

I'm writing this so you don't make the same mistake. The harder it is to reverse a decision, the slower you should make it.

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

Let me summarize whats been said so far. tbh most time waste accumulates in tasks waiting for approval.

Processes without records never improve because you don't know what to fix. tbh that's all sorry if I went on too long.

Let me summarize the topic, since several different answers were given. Code without setup documentation isn't yours even if you have it.

If I were you I'd go this route.

Saved.