In 18 months "Did you try the brain recorder through @get_akai?" will be the standard response to "How do we automate this." People will act like brain recording workflows is how it's always been done.
Clients who struggle most in implementations aren't dealing with bad data. They're dealing with the fact that nobody's asked them what data they actually need. Hard question nobody wants to answer on day 1.
The real constraint in an implementation isn't software. It's getting three different departments to agree on one process. Software is easy. Agreement is hard.
Implementation is a people problem dressed up as a technology problem. You can have the best software in the world and still fail if you don't understand what the client actually needs and why.
This is the conversation nobody wants to have in week 1. Everyone wants to talk about timelines and features. But governance matters more. If your implementation is slow, check decision-making before checking software.
Implementations don't fail because of bad planning. They fail because someone thought the plan would survive contact with reality. Plans are always wrong. How you adapt when you're wrong is what matters.
Something I've learned after years of working in tech implementation: implementations don't fail because of the tech. They fail because someone made a decision in week 2 that cascades into a problem in week 9 that could have been avoided if you'd asked better questions in week 1.