Agency went dark after I paid the advance — what do I do?

I agree.

I agree, and I'd like to emphasize that. Payment schedules should be tied to project phases, not calendar dates.

Every "we'll look at it later" in a meeting means unbilled work. Just leaving this note, it might be useful.

I've been dealing with this for a long time. The biggest time-waster for us was not knowing who had the final say.

Don't hesitate to ask; those who don't ask always pay more. Proven by experience.

Don't miss this: Implementing a change request process doesn't slow things down, it speeds them up.

The cheapest quote is usually the least thought-out one.

My perspective changed after experiencing that. People defend habits, not processes. Resistance comes from there.

When we decide without measuring, we always end up in the same place.

Don't miss this: When making decisions, write down the worst-case scenario too, not just the best.

Trying to do this alone is the most expensive way. Of course, it varies if your situation is different.

I completely agree. 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.

I didn't know that.

Yes, that's exactly how it is with paid but work stopped. The real issue isn't the number, but what it's based on.

Just leaving this note, it might be useful.

I agree with this. Hasty decisions become decisions you have to fix six months later.

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

There's one point I'm curious about. The answer varies greatly by industry; there is no one-size-fits-all rule.

Of course, it varies if your situation is different.

The most overlooked point about paid but work stopped is this: Hasty decisions become decisions you have to fix six months later.

Just leaving this note, it might be useful.

You're right I've been down that road too. like ask who prepared the quote and who will actually do the work.

Code without setup documentation isn't yours even if you have it. I'm also curious if anyone does it differently.

you're right but hasty decisions become decisions you have to fix six months later.

if you have questions write them; I'll asnwer as best I can.

The cheap-looking path usually ends up costing more later. The cheapest quote is usually the least thought-out one.

Good luck with that.

We got stuck at the same point for a while. People defend habits, not processes. Resistance comes from there.

Access credentials should be opened in the company's name, not personal accounts. If you have questions, write them; I'll answer as best I can.

If I understood correctly, you're saying: Code without setup documentation isn't yours, even if you have it.

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

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