The team
Readiness takes more than one discipline.
Independent specialists, each deep in one readiness dimension, working client-side, never the vendor’s.
Fateh AlNaeb
Founder & Principal Advisor
Fateh AlNaeb
Founder & Principal Advisor
Since 2006, inside vendor organizations and alongside client teams, on one conviction: most failed implementations were never software problems, they were readiness problems.
I sit on the client side, map the processes, write the RFP, and keep vendors honest. No software to sell. No commissions.
Deanne Kelleher
Founder, KAOS Group
Deanne Kelleher
Founder, KAOS Group · Process Clarity & Organizational Ownership
Operations and process depth for businesses that have outgrown running on tribal knowledge.
Deanne is the operations specialist in the room. When discovery surfaces unclear processes, or a business that only works because the owner is in the middle of everything, that is Process Clarity and Organizational Ownership, and Deanne goes deep where a readiness review can only point. She documents how the work actually gets done and designs the process changes so the requirements are built on how the business should run, not just how it limps along today.
Kim Lafreniere
Founder, ProcurelyIQ
Kim Lafreniere
Founder, ProcurelyIQ · Data Integrity & Financial Realism
Inventory and procurement decision clarity for businesses where stock ties up the cash.
Kim is the inventory and supply-chain specialist. When discovery finds inventory numbers no one trusts, SKU bloat, or buying done on gut feel, that is Data Integrity and Financial Realism, and getting it right before requirements are written is what separates a clean go-live from a system that inherits years of bad habits. Kim fixes the thinking behind the inventory data so the requirements reflect reality.
Michael Gladstone
Founder, PinnacleBTM
Michael Gladstone
Founder, PinnacleBTM · System Debt
Technology and systems feasibility for decisions that go beyond what IT can fix.
Michael is the technology specialist. When discovery runs into a tangled systems landscape, brittle integrations, or system debt that nobody owns, that is the System Debt dimension, and Michael assesses what is really there. He helps translate business requirements into technical evaluation criteria so vendor claims can be tested rather than taken on faith, and so the shortlist is judged on what each platform can actually do. He does not own the selection decision, which stays with Metadata on the client's side, and within this network he is not the implementer either.