Flexible objects, explained: beyond contacts and deals
Why the rigid contacts-and-deals CRM breaks down, and how a flexible object model lets you model properties, projects, subscriptions or anything your business runs on.
Traditional CRMs ship with three nouns: companies, contacts and deals. That's fine if your business is exactly a B2B sales pipeline. If it isn't, you spend your life bending your reality to fit their schema.
The workaround tax
Sell subscriptions? You cram renewal dates into a deal's notes. Manage properties? You abuse the 'company' object. Run projects? You invent a naming convention nobody follows. Every workaround is data your reports can't see.
What a flexible object model gives you
A flexible CRM lets you define your own objects — Properties, Vehicles, Subscriptions, Applications, Courses — each with the fields, pipelines and relationships that actually describe it. A record can link to any other record. A pipeline is just a select field with stages, so anything can move through a board.
Computed fields do the arithmetic
Because everything shares one model, a field on one object can look up or calculate from another: a subscription's monthly value, a property's days-on-market, a deal's weighted forecast. You define it once; it resolves on read, always current.
Curious what to model? See 10 things to model with custom objects.