Add Membership to /crm menu [#3594115] | Drupal.org

Most CRM menus are built around what the software vendor thought you'd need — not what your business actually tracks.

A small but telling example: the Drupal CRM module is working through a change to add Membership as a top-level item in the /crm navigation. On the surface, that's a minor UI fix. But the fact that it requires a formal issue ticket, proposed resolutions, API changes, and data model updates just to surface a membership record in the right menu — that tells you everything about how these systems are built.

Nothing is obvious. Nothing is fast. Every gap between how your business works and how the software was designed becomes a project.

If you run a business where memberships, subscriptions, or recurring relationships are core to your model, you already know this pain. That data probably lives in a spreadsheet, a separate tool, or three clicks away from where your team actually works. And every time you ask your platform to surface it differently, you're back in a ticket queue or on a call with a consultant billing by the hour.

The platforms aren't broken — they're just not built for your specific business. That distinction matters when you're deciding whether to customize what you have or find something that starts from how you actually operate.

A menu item shouldn't require an engineering change request to add.

#CRM #SalesOps #MidMarket #CRMStrategy #BusinessOperations

Original Source

Add Membership to /crm menu · Problem/Motivation · Proposed resolution · Remaining tasks · User interface changes · API changes · Data model changes · Issue ...