Skip to content
Notifications
Clear all

Thoughts on the new Freshworks CRM update?

6 Posts
6 Users
0 Reactions
73 Views
(@connork)
Reputable Member
Joined: 4 months ago
Posts: 216
Topic starter   [#27426]

Hey everyone, just saw the announcement for the Freshworks CRM update. I'm currently evaluating a few options for our small team's sales pipeline.

The new "Unified Customer View" looks interesting, but I'm curious about the practical side. For anyone who's tried it:

* How does the new project tracking integration actually work? Does it sync tasks from tools like Trello or Asana, or is it something built-in?
* They mentioned improvements to user onboarding. Was it easier to set up automations or custom fields compared to before?

I'm coming from mostly spreadsheets, so any comparisons to simpler setups would be super helpful. What's the learning curve like now?



   
Quote
(@danm)
Honorable Member
Joined: 4 months ago
Posts: 452
 

The project tracking is more of a built-in feature now, not a direct sync. I found it a bit limited compared to dedicated tools like Jira. It might feel clunky if you're used to Trello's flexibility.

For onboarding, yes, setting up automations and custom fields is definitely easier than their old interface. The new flow is quite visual, which is a big help coming from spreadsheets. The initial learning curve isn't too bad, but mastering the advanced workflow rules takes some tinkering.



   
ReplyQuote
(@hannahw)
Reputable Member
Joined: 4 months ago
Posts: 234
 

If you're coming from spreadsheets, the unified view will feel like a big step up - way better than hunting across tabs. The onboarding flow is smoother now, I'll agree with user556 on that.

Just watch the pricing, they've restructured packages around some of these new features. Make sure you're comparing the TCO over 12 months with your other options. The built-in project tools are nice, but if you outgrow them you might need pricier integrations later.

Good luck with the eval!



   
ReplyQuote
(@gardener42)
Reputable Member
Joined: 4 months ago
Posts: 391
 

I agree the unified view is a significant improvement for spreadsheet users. However, the data modeling behind that view is a critical factor for long term usability. If the underlying schema is too rigid, the "unified" front end can become a constraint when you need to adapt to new sales processes.

Regarding your point on comparing TCO, I'd add that you should also account for the cost of data migration and cleanup. Moving from spreadsheets often reveals inconsistencies that require manual resolution before a system like this can be truly effective. The smoother onboarding might mask that initial data preparation work, which is a hidden time cost.

The pricing restructure around features is a common move, but it often locks basic automation behind higher tiers. You should verify exactly which workflow rules and custom field types are available in the package you're considering, not just the presence of the features.



   
ReplyQuote
(@devops_shift_lead)
Honorable Member
Joined: 8 months ago
Posts: 443
 

Spot on about hidden migration costs. Everyone fixates on the subscription fee, but I've seen teams burn 40-60 hours just cleaning CSV data for import. The slick UI makes you think it's plug and play, but it's not.

Your point on the rigid schema is the real risk. If you can't add a custom object or modify relationships without a consultant, you're locked in. That's when teams start running shadow spreadsheets again, defeating the whole purpose.

Check the API limits and webhook support on the tier you're buying. If basic automation is gated, you'll hit a wall when you need to connect to your billing system or a data warehouse. The vendor's idea of "integration" is often just a pre-built connector that needs custom work anyway.


shift left or go home


   
ReplyQuote
(@davidm78)
Reputable Member
Joined: 4 months ago
Posts: 351
 

Coming from spreadsheets, the biggest win for you will be having a single source of truth. No more merging tabs or version control headaches.

The onboarding is indeed more visual now. For basic automations, like sending a welcome email after a deal stage change, you can set it up in minutes. Custom fields are easy, but think about what you'll need in 6 months. Adding a field later can sometimes break existing reports, so map them out first.

The learning curve feels gentle at first, but gets steeper when you need to connect data to other systems. Plan for that.


Data doesn't lie, but dashboards sometimes do.


   
ReplyQuote