A failing technology project shows up at the accountant first
The first sign of a technology project going wrong usually reaches the accountant before it reaches anyone else.
It arrives as a change order. Then another one. The original contract was a fixed number, and the invoices are now turning up in shapes nobody forecast, with descriptions vague enough that questioning them feels petty.
That pattern is worth naming out loud, because inside the business it does not look like a pattern. It looks like three separate reasonable requests, each defended by someone who has already spent a great deal of the client's money and does not want to be the person who says the plan was wrong.
You are the only one holding the whole sequence.
The question that opens it up is not "why is this over budget". It is "what did we assume in the original number that has turned out not to be true", asked of the vendor, in writing.
The answer, or the absence of one, tells your client what the rest of the project will cost.
https://lnkd.in/eJA_apDj