Most organisations invest in AI or new systems without fully understanding their current processes, or how their people actually work. I bring 15 years of senior business analysis and change management into that gap. Whatever gets built — an AI solution, a new system, or a smarter use of what you already have — is the right thing, and your team will actually use it.
Organisations do not fail at transformation because they chose the wrong software. They fail because they did not understand their own processes well enough to define what they needed, and because nobody prepared their people for the change.
I am Frank Awuku. Over the past 15 years I have worked as a Senior Business Analyst and Senior Change Manager inside complex organisations, from financial services and government to fast-scaling retail. The first half of my career was rooted in analysis: mapping processes, documenting requirements, and designing solutions. The last seven years have been dominated by change management: helping organisations understand why new systems and ways of working do not stick, and what to do about it.
That combination is rare, and it is the foundation of Modus Flow. Most consultants can tell you what to build. Very few can tell you whether your organisation is ready to use it, and even fewer know how to close that gap. I have spent my career doing both, and I have built AI workflows and automation systems of my own, so when I make a recommendation, I understand exactly what it takes to deliver it.
None of these are failures. They are what happens when organisations grow faster than their processes, or invest in technology before the groundwork is laid. They are also entirely fixable.
Work gets done, but nobody has ever written down how. It lives in the heads of two or three people who have been there long enough to know. That is not a problem until someone leaves, the team grows, or you need to hand a process to a system. At that point, the undocumented knowledge becomes the bottleneck.
Knowledge DependencyThe platform was purchased with good intentions. The implementation happened. But three months later the team is still working the old way, the system is being used for a fraction of what it can do, and nobody is quite sure why it did not land. This is more common than most vendors will tell you.
Adoption GapThe pressure to do something with AI is real. But most organisations are not sure whether they need it, where it would actually help, or what would need to be true before a build makes sense. That uncertainty is not a weakness. It is the right instinct. The answer starts with understanding the current state first.
AI ReadinessMost engagements start with a solution already in mind. This one starts with a conversation about how your work actually flows today.
A proper working session, not a discovery call. We explore how your operations actually run today, where the friction is, what your team works around, and what has already been tried. By the end, we agree on the one process that would make the most meaningful difference to address first, and you will have a clearer picture of whether the answer is a process redesign, a better-configured existing system, an off-the-shelf product, or something involving AI. That agreement shapes everything that follows.
A deep-dive analysis of one agreed process, mapped end-to-end. I document how it works today, where the logic breaks down, what people do instead, and what a better version looks like. The output is a full Solution Design Document: a specification clear enough for any developer, vendor, or internal team to build from with confidence. It also tells you whether the right solution involves AI at all, and if it does, exactly what kind and why. One process. Done properly. Most consultancies would scope this as a multi-week engagement at day rates. This is a fixed fee with a defined output.
Once you have the blueprint, you have choices. The analysis may show that your existing systems, better configured, are enough. It may point to an off-the-shelf product that fits your situation. Or it may identify a genuine case for a custom AI workflow or automation that no existing tool covers. I can advise clearly on all three, help you evaluate the options, and where it makes sense, oversee or support the build directly. Critically, I also help you manage the change: preparing your people, planning adoption, and making sure what gets built actually gets used.
I work with service-based organisations where operational complexity is high and the cost of getting it wrong, whether that is a failed implementation or a team that reverts to old habits, is significant.
Consultants spending hours on CV formatting, manual CRM updates, and compliance paperwork instead of placing candidates. New systems get introduced but the team works around them within weeks because nobody addressed the adoption side. The process and the people both need attention.
Maintenance requests, compliance renewals, and contractor coordination all landing in the same inbox, handled manually by someone making individual judgement calls every time. The problem is not volume. It is the absence of a documented, repeatable process that anyone in the team can follow.
Senior professionals spending billable time on client onboarding, AML checks, and document chasing because the process was never properly designed. Technology has been purchased. It is underused. The real gap is that nobody mapped what the process should look like before the system was chosen.
If you are about to invest in AI, a new system, or a process redesign, and you want to make sure you are making the right call before any money is committed, the diagnostic is the right starting point. It costs nothing, takes 60 minutes, and will give you a clearer picture of what you actually need.
Book a Free Process Diagnostic60 minutes. No commitment. No pitch.
I take on a limited number of diagnostic sessions each month to maintain depth.
You will receive a confirmation with a short prep guide so we can make the most of the session.