What does that look like in practice?
In software engineering, the work is already shifting from writing every line by hand to reviewing outputs, framing problems properly and catching what the machine misses. In finance and accounting, the same pattern is emerging: less manual preparation and routine analysis, more interpretation, orchestration and advisory work. My view is that organisations that are deliberate enough can hold both: stripping out the drudgery while protecting the conditions in which judgement develops.
Why do so many AI programmes still disappoint?
Because they add tools without redesigning the system around them. A pilot can make an individual task faster and still create almost no enterprise value if the workflow, incentives, accountability, and measures around it stay the same. The biggest multiplier is institutional rather than individual: culture, management discipline, decision rights, and workflow design determine whether AI becomes real operating leverage or just another layer of activity.
What does this mean for entry-level talent?
It means organisations need to think much harder about how people build judgement and experience early in their careers. If some of the routine work starts to disappear, the old apprenticeship model becomes less reliable on its own. So leaders need a clearer answer to how people learn, where they get exposure, and how they grow into more valuable roles over time.
How do you retrain at speed?
You do not start with a giant training catalogue. You start with the work changing fastest and the roles closest to value creation. The organisations moving quickest build a baseline level of AI fluency, then embed learning into live workflows. This is where Vertage can play a practical role: bringing knowledge, experience and oversight together so organisations can scale people's impact, while helping them steer an agentic AI workforce with clear guardrails, quality checks, and release models.
What does going fast on AI look like?
It means being able to zoom out, rethink the process, and move quickly on the use cases where reliability is good enough and the operating benefit is real. In practice, the strongest examples often come from small teams close to the business, with clear executive backing, strong guardrails and the authority to redesign how work gets done.