Should we write 'test acceptance criteria' when taking delivery of a website — what should be written?

You're right. The harder it is to reverse a decision, the slower you should make it.

Looking at it as a process, the picture changes. Just because everyone does it doesn't mean it's right.

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

Great work. If you get three different answers on a topic, the question was asked wrong.

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

I don't think this advice fits everyone. The cheapest quote is usually the least thought-out one.

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

We got stuck at the same point for a while. If you don't write this down from the start, it leads to arguments later.

Correct me if I'm wrong.

There's one point I'm curious about. If you get three different answers on a topic, the question was asked wrong.

When making decisions, write down the worst-case scenario too, not just the best. Correct me if I'm wrong.

We need to take it step by step. Every "we'll look at it later" in a meeting means unbilled work.

Absolutely. If I were to add anything: Hasty decisions become decisions you have to fix six months later.

I'm also curious if anyone does it differently.

heres how it went for us but if scope grows, either time or budgget must grow. there is no third option.

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

Let me clarify the technical side... tbh everything goes well for the first three months; problems arise in the fourth.

Don't hesitate to ask; those who don't ask always pay more. Just leaving this note, it might be useful.

We got stuck at the same point for a while. Just because everyone does it doesn't mean it's right.

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

ive been dealing with this for a long time and implementing a change request process doesnt slow things down it speeds them up.

correct me if I'm wrong.

Correct in theory but it doesn't work that way in practice. honestly if it's your first time start small; scaling comes later.

If you post the result here, it will help others too.

I'll try it.

I'm curious too. When you try to change everything at once, nothing settles.

If code ownership isn't in the contract you have no bargaining power when leaving... That's all, sorry if I went on too long.

If you're going this route, sort this out first. Any unwritten clause becomes a point of disagreement later as both sides remember it differently.

Proven by experience.

I didn't know that.

The answer above hits the nail on the head. If acceptance criteria aren't written, when the work is done is open to debate.

I'm also curious if anyone does it differently.