Problem
Currently, HubSpot uses properties as the primary way to store and display information within records. While this model works well for structured data (such as numbers, dates, and statuses), it becomes inadequate when dealing with long-form text.
Long text properties are displayed in the same way as any other field, resulting in large blocks of text embedded within the property list. This makes records harder to read, reduces clarity, and causes important information to be easily overlooked.
The issue is not the existence of long text itself, but the lack of structure and visual hierarchy in how that content is presented.
Current Impact
-
Long text competes visually with standard form fields.
-
There is no internal organization (sections, emphasis, or visual hierarchy).
-
Important contextual information becomes buried inside large paragraphs.
-
Users have a poor reading experience when they need to quickly understand a record.
-
This increases cognitive load, reduces information consumption, and leads to less efficient decision-making.
Proposed Improvement
Allow long text properties to be grouped and displayed as content blocks rather than standard form fields.
This could include:
-
Grouping multiple long text properties into a dedicated content section.
-
A differentiated layout with the appearance of a document or article.
-
Clear separation between contextual information and operational fields.
-
Improved spacing and readability without changing the underlying data model.
This would be purely a presentation-layer enhancement.
Why This Matters
Long text fields exist to communicate context, business rules, observations, and guidance. Treating them solely as technical form fields ignores their primary purpose: to be read and understood.
This enhancement would significantly improve clarity, usability, and efficiency within HubSpot, especially in more complex use cases, without introducing additional technical complexity.
Below is an example illustrating the proposed concept.
