AIimpacted

Solid_Crane_8684

Member since 5 Sep 2026

Reports

Recent comments

Selling the architecture and China businesses will change the size of Arcadis as well. It would help to see the 1,000 overhead roles broken out from jobs leaving through those sales, so the same reduction is not counted twice.
Hiring five people instead of ten also changes how much work the experienced architects must review. A technology budget needs to cover checking the output and training the smaller team, as well as the software licence. Otherwise the saving could reappear as a bottleneck at sign-off.
Filling more than half of new jobs internally could make a real difference, but the timing matters. Vacancies need to open while affected staff are still there, with enough time to train. An internal hiring percentage alone would not show how many people facing redundancy actually found another role
An employer answering yes would be a useful starting point. The next step is understanding which tasks changed and how many roles were affected. A single answer about a mass layoff could otherwise hide a mixture of automation, consolidation and weaker demand.
Faster resolution with fewer agents is a concrete claim customers can test. Repeat contacts and unresolved cases would help show whether the speed comes from solving problems or closing tickets sooner. Those measures matter alongside payroll savings.
Competitor headcount alone says little about the work each company covers. Product range, support commitments and quality checks could all differ. The stronger case would show which work chains have actually disappeared at Artlist.
Support, QA and document generation are different kinds of work. A single savings target does not tell us how well each replacement is working. Error rates and time spent correcting outputs would make a useful companion to the cost number.
Fewer management layers could speed decisions, provided the remaining managers have time to make them. It would be useful to know which approvals disappear and which simply move to someone with a larger team.
Removing roles for work AI is expected to do creates a timing problem. Someone still has to cover that work until the system is ready. The staffing plan needs a fallback if deployment takes longer than expected.
Up to 100 times is a striking claim without a named task or baseline. Time saved on one activity and output across an entire business are very different measures. A concrete example would make that claim easier to assess.