HuhSpot*

Roast index / HubSpot Smart CRM

Smart CRM — 1,000 custom properties deep in the property swamp

Every object can grow 1,000 bespoke fields — until you hit the cap, then buy more. A data model is only 'customizable' before it becomes archaeology.

Bloat index 7/10

Custom properties are the CRM’s candy aisle. Need to track “churn_reason_v3_final” on contacts? A few clicks. Everyone makes some. Nobody deletes any. The cap arrives at 1,000 per object — and the catalog offers 500 more for $220/month, to a maximum of 3,000 per object.

A thousand bespoke fields is not flexibility. It is deferred maintenance that bills monthly.

The same story continues in custom objects (10 definitions; more with Operations Hub Enterprise), association limits (50,000 per association type per record, with a full page of exceptions, sub-caps, and “non-summable” enforcement rules), and migration consulting sold in precious-metal tiers — Bronze, Silver, Gold — because moving your own data out is, itself, a product.

The sign of a healthy CRM isn’t how many fields you can add. It’s how few you need to keep.

The property swamp is an archaeology project

Ask any veteran HubSpot admin: “How many of your contact properties would cause an incident if deleted?” The pause before the answer is the whole point. Fields accumulate because creation is frictionless and deletion requires institutional courage. Over time, the schema stops being a tool and becomes a risk register.

The job, done lean

SuperSuite takes the opposite bet: a shared, boring, documented entity grammar.

  • Account and User from GetAuth anchor everything.
  • Each app owns its domain entities — Feedback_Signal, Submission, Ticket, Roadmap_Item — with explicit, versioned metadata.
  • Cross-app data moves via APIs, so no app needs 1,000 fields of someone else’s context.
  • The whole schema lives in a knowledge catalog in the repo. Six months from now, an engineer can read it, not excavate it.

Boring schemas age well. Property swamps just age.

The use case fit

You need it to: understand your own database in six months, without a séance.

The lean alternative

honest tools, fairly priced

Shared entity schema

SuperSuite apps share one entity grammar — Account, User, and per-app domain entities like Signal, Ticket, Submission — each owning its own database. The schema is documented in a knowledge catalog you can actually read.

Shared entity schema →

Straight answers

How many custom properties can a HubSpot object have?

Up to 1,000 per object on paid plans. A Professional/Enterprise Limit Increase adds 500 more at $220/month, capped at 3,000. The free tools cap at 10.

Is a flexible CRM data model a good thing?

Moderate flexibility is. But 1,000 bespoke fields per object typically reflects a modeling failure: data with no owner, no schema review, and no retirement process. Constraints are the feature.

How does SuperSuite model customers vs HubSpot?

Each suite app owns its database but shares a documented entity grammar (Account, User, plus per-app entities). Apps exchange data via REST APIs with shared GetAuth identity — no shared tables, no property sprawl.

Answer blocks above are emitted as FAQPage structured data, because that is how information should travel now.