Problem

Custom Objects currently only support list view. This makes them difficult to use for managing real operational workflows.

Teams that use Custom Objects for things like service orders, projects, or internal processes lack a visual way to track progress. This creates friction, reduces adoption, and forces teams to rely on external tools.

Proposed Solution

Allow Custom Objects to have a Kanban (pipeline-style) view with stages, similar to Opportunities.

Users should be able to:

Define stages for any Custom Object

View records in a Kanban board

Move records across stages using drag & drop

Automatically update status when moved

Example Use Case

A “Service Orders” Custom Object could have stages like:

Received

Diagnosis

In Progress

Waiting for Parts

Ready

Completed

This allows teams to manage operations visually instead of using static lists.

Key Clarification

This should not replace the sales pipeline.

Opportunities → Sales process

Custom Object Kanban → Operational workflows

Both should coexist independently.

Impact

Improves usability and adoption

Provides real-time operational visibility

Reduces dependency on external tools (like spreadsheets)

Enables better workflow management inside GHL

Conclusion

Custom Objects today act mostly as data storage.

With a Kanban view, they become a true operational management tool, making GHL significantly more powerful for real-world use cases.