The project went badly, I want to terminate the contract — will I get a refund?

Absolutely. If I were to add anything: Solutions that work at a small scale collapse when you grow; I learned this late.

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

I'll argue the opposite don't get mad. If code ownership isn't in the contract, you have no bargaining power when leaving.

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

I've been dealing with this for a long time. Ask who prepared the quote and who will actually do the work.

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

To get into the details: Every "we'll look at it later" in a meeting means unbilled work.

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

My question might sound amateurish sorry about that... The real issue isn't the number but what it's based on.

Just because everyone does it doesn't mean it's right. Correct me if I'm wrong.

Generally correct, but one part is missing. Ask who prepared the quote and who will actually do the work.

Good luck with that.

Following.

Good call starting this thread. Code without setup documentation isn't yours, even if you have it.

Just leaving this note, it might be useful.

There is something to watch out for. The system lives on after delivery; maintenance is a separate line item.

I agree.

We got stuck at the same point for a while. Hasty decisions become decisions you have to fix six months later.

Processes without records never improve, because you don't know what to fix. I'm also curious if anyone does it differently.

I'd say don't rush. Processes without records never improve, because you don't know what to fix.

I went through the same thing two years ago. Payment schedules should be tied to project phases, not calendar dates.

Let me share my experience. Access credentials should be opened in the company's name, not personal accounts.

Weekly written progress reports are much more useful than asking for dates. Hope this helps.

Correct.

I feel the same way. In legacy systems, the most expensive thing is unknown dependencies.

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

There's a trap here, let me mention it. When making decisions, write down the worst-case scenario too, not just the best.

I'm also curious if anyone does it differently.

Quick summary for newcomers: Ask who prepared the quote and who will actually do the work.

Correct me if I'm wrong.