The most common way an automation programme underdelivers is structural rather than technical. A senior person scopes the engagement. A different, often junior, team builds it. Context leaks at every handover, and by the time delivery arrives the person who understood the process has moved to the next pursuit.
That pattern is not carelessness. It comes from a business model that needs its senior people selling rather than building, and it is very hard to avoid at scale.
We avoid it by not operating at that scale. The engineer on your first call designs the solution, leads the build, and stays through delivery and hypercare. No handover after scoping. No rotating faces mid-project.
The trade-off is real and worth stating: it means we take fewer engagements than a firm of comparable capability would, and we will occasionally tell you we are not the right people for a piece of work. It also means the estimate you receive was written by somebody who has to deliver against it.