← All articles
10 things to model with custom objects
Ten real-world examples of custom CRM objects — properties, subscriptions, vehicles, courses, tickets and more — and the fields and relationships that make each one useful.
If your CRM only has contacts and deals, half your business lives in the notes field. Here are ten things worth promoting to real objects — each with the relationship that makes it click.
- Properties — status pipeline, price, days-on-market; linked to buyers and sellers.
- Subscriptions — plan, renewal date, MRR; linked to the account, with a formula for lifetime value.
- Vehicles — VIN, service history; linked to owner and workshop.
- Courses / cohorts — start date, capacity; linked to enrolled students.
- Applications — a stage pipeline from received to decision; linked to the applicant.
- Support tickets — priority, status; linked to the customer and the deal.
- Projects — phase, budget; linked to client and team member.
- Events — date, venue, capacity; linked to attendees.
- Assets / inventory — quantity, location; linked to supplier.
- Partners / vendors — tier, agreement dates; linked to the accounts they touch.
The pattern is always the same: give the thing its own fields, its own pipeline if it moves through stages, and a link to the records it relates to. Computed fields then read across those links for free — the idea behind flexible objects.