I'm transferring the old agency to another firm — what happens with data, source code, and access permissions?

If you're going this route, sort this out first. 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.

Quick summary for newcomers: If you don't write this down from the start, it leads to arguments later.

When you try to change everything at once, nothing settles. Good luck with that.

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

Hope this helps.

We need to make a distinction here. The real issue isn't the number, but what it's based on.

Everything goes well for the first three months; problems arise in the fourth. Correct me if I'm wrong.

Just a heads-up. Implementing a change request process doesn't slow things down it speeds them up.

Access credentials should be opened in the company's name not personal accounts. Hope this helps.

ive been down this road let me tell you... processes without records never improve, because you dont know what to fix.

of course, it varies if your situation is different.

We experienced almost the exact same thing last year. Weekly written progress reports are much more useful than asking for dates.

If you get three different answers on a topic, the question was asked wrong. Good luck with that.

Saved.

You're right, I've been down that road too. If you get three different answers on a topic, the question was asked wrong.

The system lives on after delivery; maintenance is a separate line item. Good luck with that.

i'm writing this so you don't make the same mistake. every "we'll look at it later" in a meeeting means unbilled work.

if I were you, I'd go this route.

i aggree and Id like to emphasize that and honestly payment schedules should be tied to project phases not calendar dates.

proven by experience.

correct... weekly written porgress reports are much more useful than asking for dates.

poven by experience.

Three different views emerged, they all complement each other. Taking notes for two weeks yields better results than a six-month estimate.

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

I went through the same thing two years ago. If it's your first time, start small; scaling comes later.

Let me summarize what's been said so far. Hasty decisions become decisions you have to fix six months later.

Of course, it varies if your situation is different.

Do you think this works at any scale? Implementing a change request process doesn't slow things down, it speeds them up.

The cheapest quote is usually the least thought-out one. I'm also curious if anyone does it differently.

My questions are cleared up, thanks.

My question might sound amateurish, sorry about that. If you get three different answers on a topic, the question was asked wrong.