Model your business, not someone else’s.
Most CRMs give you Contacts, Companies, and Deals, then ask you to bend a decade of domain knowledge into three tables. Unify Loop treats your objects as data: define Properties, Candidates, Policies, or Retainers, and the platform builds the rest around them.
- Objects per workspace
- Unlimited
- Field types
- 20+
- Schema change downtime
- None
- Developer required
- No
A new object is a definition, not a deployment
Adding an object in most systems means a schema change, a release, and a fight with whoever owns the roadmap. Here, an object is a row of metadata. The moment you save it, everything that reads objects generically picks it up at once — because none of those surfaces were written against a hardcoded table.
- List and table views with sorting, grouping, and saved filters
- A detail record with a timeline, related lists, and inline editing
- REST endpoints, CSV import with column mapping, and full-text search
- Workflow triggers, campaign segments, report dimensions, and AI tool access
Fields that carry meaning, not just strings
A field type is a contract. Currency knows its rounding and its display symbol. A relationship knows about both of its ends, so linking a Showing to a Property gives the Property a Showings list for free. Formula fields recompute when their inputs change rather than when someone remembers to refresh, and select options carry a stable internal value underneath their label — so relabelling “Deal” to “Matter” never breaks a workflow that referenced it.
Validation and permissions travel with the definition
Required-ness, uniqueness, allowed values, and who can read or write a given field live on the field itself. That means the same rules apply whether a record arrives from the UI, a CSV import, the public API, a workflow, or the AI copilot. There is no back door where a bad record slips in because a second code path forgot to check.
Custom objects, in detail.
Do I have to start from a blank slate?
No — and we don’t recommend it. Onboarding asks what your business sells and installs an industry pack with the objects, fields, pipelines, and workflows already modelled. You customise from a working starting point. A blank workspace is the escape hatch, not the default.
What happens to existing records if I change a field?
Widening a field (adding a select option, making a required field optional) applies immediately. Narrowing one — changing a type, or making a field required when some records are empty — shows you exactly how many records conflict before you confirm, so you never discover it afterwards.
Can I rename standard objects?
Yes. Display labels are per-workspace, so a law firm can call them Matters and an agency can call them Engagements. The underlying identifier stays stable, so renaming never breaks a workflow, saved view, or integration that referenced it.
Is there a limit on relationships between objects?
No. Objects can reference each other one-to-many or many-to-many, and every relationship is navigable from both sides without you defining it twice.
Try it on your own data.
Free workspace, an industry pack installed at setup, and every price published. No mandatory call.
Free trial · no card required · every price published