Is it more sensible to refresh the current site or build from scratch?

A warning from a design perspective: "making it mobile-responsive" is a very broad term.

Some agencies just shrink it based on screen width. The result works on phones but is unusable because buttons are small, text is unreadable, and forms can't be filled out.

If the quote says "mobile-responsive," ask for screenshots of how it will look on a phone. Visual proof, not just words.

im in the same boat, following this. thx for asking.

Thanks a lot to both of you. I've written down my questions and will ask both providers on Monday.

When I asked the system question, the first provider hesitated a bit, while the second answered immediately. Honestly, that alone gave me some insight.

Sorry, but this doesn't apply in every case. Everything goes well for the first three months; problems arise in the fourth.

Ask who prepared the quote and who will actually do the work. I'm also curious if anyone does it differently.

I think differently. If you don't write this down from the start, it leads to arguments later.

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

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

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

quick summary for newcomers: When making decisions write down the worst-case scenario too, not just the best.

just leaving this note, it miight be useful.

Sorry, but this doesn't apply in every case. Access credentials should be opened in the company's name, not personal accounts.

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

There are three things to check when doing this. Just because everyone does it doesn't mean it's right.

If you get three different answers on a topic, the question was asked wrong. If you post the result here, it will help others too.

This thread is archived.

i cant fully agree with this. every "well look at it later" in a meeting means unbilled work.

hope this helps.

i'd appreciate it if you shared the outcome but code without setup documentation isn't yours even if you have it.

if code ownership isn't in the contract you have no bargaining power when leaving. correct me if I'm wrong.

This approach has a cost, which isn't discussed. The answer varies greatly by industry; there is no one-size-fits-all rule.

If you don't write this down from the start, it leads to arguments later. I'm also curious if anyone does it differently.

i'm in the same situation that's why I'm asking. weekly written progress reports are much more uesful than asking for dates.

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

Do you think this works at any scale? Hasty decisions become decisions you have to fix six months later.

Proven by experience.

The cheap-looking path usually ends up costing more later. People defend habits not processes. Resistance comes from there.

I'm also curious if anyone does it differently.

I agree, and Id like to emphasize that. I mean when we decide without measuring we always end up in the same place.

Thats all, sorry if I went on too long.

noted, thanks. payment schedules should be tied to project phases, not caendar dates.

if scope grows either time or budget must grow... there is no third option.