Site looks terrible on phone — no responsive design?

Looking at it as a process the picture changes. The biggest time-waster for us was not knowing who had the final say.

Good luck with that.

We experienced almost the exact same thing last year. btw people defend habits not processes. Resistance comes from there.

If youre going this route sort this out first... I mean when you try to change everything at once nothing settles.

Correct me if I'm wrong.

We've heard this a lot, but it never happened like that for us. Just because everyone does it doesn't mean it's right.

When you try to change everything at once, nothing settles. If you have questions, write them; I'll answer as best I can.

Exactly like that. Don't hesitate to ask; those who don't ask always pay more.

Start with a small trial; don't commit to everything at once.

I felt relieved reading this answer so it's not just me. If you don't write this down from the start it leads to arguments later.

I'm also curious if anyone does it differently.

There's a trap here, let me mention it. The real issue isn't the number, but what it's based on.

Just because everyone does it doesn't mean it's right. If you post the result here, it will help others too.

Following. The system lives on after delivery; maintenance is a separate line item.

The harder it is to reverse a decision, the slower you should make it. If you have questions, write them; I'll answer as best I can.

I was thinking the same thing. When making decisions, write down the worst-case scenario too, not just the best.

There's a trap here, let me mention it. Code without setup documentation isn't yours even if you have it.

Proven by experience.

we need to take it step by step then the biggest time-waster for us was not knowing who had the final say.

any unwritten clause becomes a point of disagreement later, as both sides remember it differently and anyway if you post the result here, it will help others too.

there are three things to check when doing this and anyway most time wase accumulates in tasks waiting for approval.

that's all sorry if I went on too long.

If you're going this route, sort this out first. The cheapest quote is usually the least thought-out one.

Three different views emerged, they all complement each other. People defend habits not processes. Resistance comes from there.

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

If I understood correctly, you're saying: 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 answer varies greatly by industry; there is no one-size-fits-all rule.

Proven by experience.

Thanks for writing this, that's the right way. The system lives on after delivery; maintenance is a separate line item.

I'm also curious if anyone does it differently.

I completely agree. The biggest time-waster for us was not knowing who had the final say.

Proven by experience.