What do you dislike about Kantata Professional Services Automation (formerly Mavenlink+ Kimble)?
Several core workflows require heavy administrative support because the platform has limited automation, fragmented permissions, reporting constraints, and significant dependency on clean setup data.
Kantata has not kept pace with AI advancements, and Huge is pulling data into self-designed interfaces that are more modern and user friendly than the Kantata UI.
Reporting Suite lacks flexibility. Changing time frames often requires creating separate reports rather than adjusting a single view. Users also cannot save common filtered views, such as their own Practice or set of Projects.
Reports are slow and cumbersome to use. Users often need to load a report, apply filters, and wait for it to reload, which reduces adoption.
Historical trend reporting is limited. The current reporting suite does not make it easy to view how metrics change over time.
The permissions model is limited and fragmented. Kantata has multiple permission models, and available controls are not granular enough for some common operational needs.
The skills functionality is not advanced enough for our needs.
Overall, the price is exceptionally high compared to the value we receive. Review collected by and hosted on G2.com.