steel-manning for fun: if its a master data governance tool then you could use it to load all systems master data and also extract all master data from those systems and reconcile it to ensure all rules are being followed. you may even use this info to trigger masterdata workflows..

there are so many bozos faking this precicley because a surface glance doesnt necicarily tell you they are full of shit.

A key indicator is do they dig into code?, do they look at data bases?, do they mock stuff up and prototype? do they reference company strategy and financial targets?.. they cant just talk the talk, they also have to walk the walk.

If someone said this to me then showed me a prototype integrated masterdata and business intellignence solution, how it would interface with busines governance, change management etc. i would be happy.. if they just had that triangle and wanted someone else to "do the technical stuff" then its another story :)

Or a cheeky way of looking at it.. does involving this person normally make things more or less clear? does the time to get value from work reduce or increase?