Accessibility shouldn't be an extra, it should be a delivery requirement

You're right and i'll admit, we also listed it as a separate line item for a long time.

Now it's part of our standard delivery terms. It didn't increase the cost for the client because it's not extra work when done from the start. The only thing that changed is that it's no longer forgotten.

Theres also a measurement aspect to this. Mistakes made on the design side are usually reversible but expensive.

Proven by experience.

I don't think this advice fits everyone. Payment schedules should be tied to project phases, not calendar dates.

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

i was thinking the same thing but in legacy systems the most expensive thhing is unknown dependencies.

if code ownership isn't in the contract you have no bargaining power when leaving. proven by experience.

To get into the details: Any unwritten clause becomes a point of disagreement later as both sides remember it differently.

Solutions that work at a small scale collapse when you grow; I learned this late. Correct me if Im wrong.

I'd say don't rush. The cheapest quote is usually the least thought-out one.

Good luck with that.

let me summarize the topic, since several different answers were given but solutions that work at a small sale collapse when you grow; I learned this late.

payment schedules should be tied to project phases, not calendar dates but just leaving this note, it might be useful.

Correct. Access credentials should be opened in the company's name, not personal accounts.

Proven by experience.

We got stuck at the same point for a while. When we decide without measuring, we always end up in the same place.

If you have questions, write them; I'll answer as best I can.

You're right.

Saved. If it's your first time, start small; scaling comes later.

Trying to do this alone is the most expensive way.

I feel the same way. btw if you get three different answers on a topic the question was asked wrong.

That's all, sorry if I went on too long.

Let me write how it's done in practice. The biggest time-waster for us was not knowing who had the final say.

If you don't write this down from the start, it leads to arguments later. If you have questions, write them; I'll answer as best I can.

Exactly like that. Mistakes made on the design side are usually reversible but expensive.

Proven by experience.

I agree and I'd like to emphasize that. Implementing a change request process doesn't slow things down, it speeds them up.

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

I was thinking the same thing. Every "we'll look at it later" in a meeting means unbilled work.

If you have questions, write them; I'll answer as best I can.

let me share my experience and the biggest time-waster for us was not knowing who had the final say.

just levaing this note it might be useful.

There's a trap here, let me mention it. Don't hesitate to ask; those who don't ask always pay more.