Spoom vs. Vertify

It is well suited when you have several sources of data.

I would recommend it, as VertifyData exactly fit our use case. I can't speak for all use cases and all connectors - naturally - but the ones we are using and have explored so far, work perfectly well. Also, being a person myself that is not fluent in SQL or JSON or API language in general, I was still able to create all workflows our company needed myself. Which I consider a huge benefit.

• Easy to use
• Focus on analyzing and not on finding and loading data
• "One version of the truth"

• Communication.
• Follow up.
• They're constantly trying to improve.

• I would like to have more modules. Eg. : supply chain tool.

• Automated error trouble-shooting is not always clear/helpful
• Clearly distinguishing internal errors vs. external errors
• Perhaps a blog where users can interact with questions + solutions

Creating a mapping between source and target while also using lookups and transformations is not trivial. And VertifyData solved this reasonably well, at least all users in my organization understood it pretty quickly.

It is not the easiest user interface to read/understand. However, once you understand how it works, then using it is not that bad. It's hard to remember what feature is listed under what tab (Manage vs. Define). A suggestion would be to get all call to actions on the same page

Cognos is very expensive and needs heavy IT-team to implement it.

Vertify offered more flexibility and was presented as a simple solution. In reality, it is more complex that we envisioned and we have never fully utilized our tools due to the lack of ability to configure things properly.

Incentivized

• Independently, teams are able to carry out their process with less communication and at a higher level of accuracy.
• VertifyData is actively taking into consideration, consulting, and supporting our plans to build out the business