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. UnifyLoop 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
- 10, with variants
- 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 board views with sorting, grouping, and saved filters
- A detail record with a timeline, related records, and inline editing
- CSV import with column mapping, CSV export, and full-text search
- Pipelines, automation triggers, segments, and AI summaries
- A public API with keys, so your own systems can read and write records Coming soon
Fields that carry meaning, not just strings
A field type is a contract. A currency field knows its display symbol. A record link knows about both of its ends, so a Showing linked to a Property shows up among that Property’s related records. Dropdown options carry a stable internal value underneath their label, so relabelling “Deal” to “Matter” never breaks an automation that referenced it.
- Text, number, currency, dropdown, multi-select, date, date and time, checkbox, email, phone, URL, user, and record link
- Formula, rollup, and lookup fields that recompute when their inputs change Coming soon
- File and address fields Coming soon
Rules travel with the definition
Required fields and allowed values live on the field itself, so the same rules apply whether a record arrives from the UI, a CSV import, or an automation. There is no back door where a bad record slips in because a second code path forgot to check. Record visibility is set by role (an agent sees their own records, a team lead sees their team’s, an admin sees everything), and it is enforced in the same place, for every surface.
- Required fields enforced on every path a record can arrive by
- Role-based record visibility, applied in the query engine
- Field-level read and write permissions Coming soon
Do I have to start from a blank slate?
No. Every workspace starts with Companies, Contacts, and Leads already set up, with a sales pipeline and a calling pipeline in place. Industry packs that install trade-specific objects (Properties and Showings for real estate, Candidates and Roles for recruiting) are coming soon. Until then, adding those objects yourself takes minutes.
What happens to existing records if I change a field?
Adding a field or a dropdown option applies immediately. A field you no longer need is archived rather than deleted, so the values already stored in it are not thrown away.
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 an automation or saved view that referenced it.
Does it catch duplicate records?
Yes. A duplicates screen finds likely matches on email, phone, website domain, and similar names, sorted by how confident the match is. You compare two records side by side, pick which values survive, and anything linked to the loser moves to the survivor. A merge is permanent, so the screen shows you exactly what will change before you confirm.
Step 2 of the customer journey.
Try it on your own data.
Free workspace, contacts and pipelines ready at signup, and every price published. No mandatory call.
Free plan · No credit card · Every price on the site