They said 'you'll have 5 pages' at the start but now we're at 12 pages — why aren't they asking for more money?

bro i got from an agency like this too, they seemed great at first but ended up doing 8 pages instead of the estimated 3 then naturally i was happy, i'm calling them for references now.

edit: typed from phone, sorry for typos.

the agency being this flexible isn't for customer satisfaction. either they're bad at estimating (skill issue), or they plan to raise prices later (scammy).

Without arguing: get a list of pages at the end of each month or every 2 weeks. written list. say 'if this fits into the 5 pages we're good, if not can you let me know?'.

Since you got a good agency, you can see this as a positive. but say 'to continue from here, let's get these approved in writing' and take control.

this is the best case scenario accountant governance is all like this. no issue now but what if you run out of money later and the agency says 'that page wasnt in scope'?

Thanks for posting.

Don't miss this: Everyone rushing into scope creep gets stuck at the same point.

The answer above hits the nail on the head. The harder it is to reverse a decision, the slower you should make it.

Correct me if I'm wrong.

I have a question, don't want to go off-topic though. Implementing a change request process doesn't slow things down, it speeds them up.

I'm also curious if anyone does it differently.

Let me write how it's done in practice. Access credentials should be opened in the company's name, not personal accounts.

Proven by experience.

Let me share my experience. Most time waste accumulates in tasks waiting for approval.

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

Theres a part I dont understand. Any unwritten clause becomes a point of disagreement later as both sides remember it differently.

Proven by experience.

This thread is archived.

I've been dealing with this for a long time. If you don't write this down from the start, it leads to arguments later.

Proven by experience.

Sorry, but this doesn't apply in every case. Ask who prepared the quote and who will actually do the work.

Implementing a change request process doesn't slow things down, it speeds them up. Hope this helps.

Let's separate the concepts, they're getting mixed up. In legacy systems, the most expensive thing is unknown dependencies.

Let me summarize what's been said so far. If it's your first time, start small; scaling comes later.

Processes without records never improve, because you don't know what to fix. Good luck with that.