What do you like best?
First and foremost, I love that it is available for the Salesforce platform. As Salesforce consultants and with the shortcomings we were experiencing with our previous PSA setup, Kimble PSA was a welcome addition to our organization's suite of tools. Not only did it speed up our internal business processes, but it allowed us to make customizations unique to our Salesforce environment using native Salesforce features.
Secondly, with delivery management, the ability to place controls around time entry for our consultants, to maintain and assign resources to our engagements in a seamless way, and to manage our projects from start-to-end with features such as risks, issues, and engagement statuses propelled our organization forward and made us more efficient. It gave us enhanced visibility into our engagements in ways that have benefitted us and, ultimately, our customers as well—more reporting, more control, and less mistakes!
Lastly, I absolutely love the Sales features of Proposals and Change Orders that work with native Salesforce Opportunities. With our recent upgrade to Kimble PSA Version 1.23, we have been taking full advantage of new Sales functionality and, like our Delivery Team, bringing some much needed control and streamlining to our pipeline management. Our Sales Team is now equipped to more efficiently collaborate and sell, spending more time on finding new business and less time having to manage the CRM side of the Sales equation.
What do you dislike?
At times, custom reporting using the Kimble PSA can be difficult. The application is comprised of many custom objects with multiple threading relationships which can definitely be hard to navigate, especially if you are trying to create custom report types and reports in Salesforce. For the most part, we are able to surpass this by analyzing the data model and tracing relationships, but it could be difficult for some admins or organizations. It would be helpful to have better documentation from Kimble on this, perhaps in the form of a Data Dictionary or Enterprise Relationship Diagrams (ERDs) in the future.
Application Roles—the main mechanism through which an organization's resources/users are given permissions within the Kimble PSA—can be problematic at times when interacting with native Salesforce permissions and user controls. Not a deal breaker at all, but it does require attention if an organization is trying to customize permissions to the PSA for their Users in some ways.
Recommendations to others considering the product
We all want to be more process oriented, efficient, and spend less time on the menial tasks that bog us down in our CRM. Kimble PSA allows you to spend less valuable time on tasks that can be automated and more time on the important things, delivering quality work or products to your customers.
What business problems are you solving with the product? What benefits have you realized?
- Efficient engagement selling with less time spent on CRM tasks during Sales Processes
- Tracking of collaboration on Sales Discovery through the use of Bid Teams
- Efficient Resource (Consultant) on-boarding, management, and assignment to engagement teams
- Enhancing visibility into engagement status, risks, and issues for reporting to Customers
- Controlling delivery engagement/consulting time burn through resource assignments, notifications, and available reports.
- Integrating financial reporting and invoice processing directly with delivery engagements, making it easier for admins/finance to process customer invoices for prompt collection.