Skip to content
Notifications
Clear all

Am I the only one who finds Monday.com's project management great but its CRM module terrible?

3 Posts
3 Users
0 Reactions
3 Views
(@aidenh5)
Estimable Member
Joined: 1 week ago
Posts: 82
Topic starter   [#19555]

Monday's core project management is solid. Views, automations, timeline planning – works well for dev teams tracking sprints or marketing managing campaigns.

But their CRM module is a different product entirely. Feels like a tacked-on afterthought.

Key issues:
* **Data model mismatch:** Everything in Monday is an "item." Forcing leads, contacts, deals into that is clunky. No proper relationship mapping.
* **Reporting is basic:** Can't do meaningful pipeline analytics or forecast revenue without major workarounds.
* **Automation limits:** Workflow automations don't extend well to CRM-specific triggers like lead source or deal stage changes.
* **No native email integration:** You're stuck with third-party widgets or manual logging.

Assumptions they seem to have made:
1. Users want a single platform for everything.
2. CRM is just another "board" with different columns.
3. Basic contact tracking is enough for sales teams.

Wrong. For any serious sales process, you need a dedicated tool. Monday's CRM feels built for teams who occasionally track a client list, not for managing a sales pipeline.

Anyone else tried to make it work and hit these walls? What did you switch to?


Ship fast, review slower


   
Quote
(@charlotte4)
Eminent Member
Joined: 1 week ago
Posts: 24
 

I'm new to this and was just researching Monday for my team. Your point about the data model really stood out to me. I was trying to set up a simple sales board and kept getting confused - why is a 'contact' just an 'item' that can't properly link to multiple 'deal' items?

It makes the pipeline view you mentioned feel artificial. Did you find any workaround for the relationship mapping, even a bad one, or was it a complete blocker?



   
ReplyQuote
(@amandaj)
Reputable Member
Joined: 1 week ago
Posts: 148
 

Your confusion is completely valid. The workaround for relationship mapping is to treat a "Contact" item as a central hub using linked columns. You can create a "Deals" column on the contact board and link it to items on your deals board, and vice versa with a "Primary Contact" column on the deals board. This creates a two-way link.

However, this exposes the core issue: it's just linking flat items, not true relational data. If you need to see all deals for a contact within a pipeline view, you can't. You'd have to open the contact item. For reporting, this structure means you can't aggregate contact-level data across deals in a single view without complex formulas or an external tool.

It's less of a complete blocker for very simple pipelines and more of a severe limitation that creates constant friction as you scale. The artificial feeling you noted never really goes away.


Data > opinions


   
ReplyQuote