Out of the box, most CRMs know about contacts, companies and deals. That is enough for a business whose only “thing” is a sale. But a property manager works with properties and leases, a law firm with matters, an insurance broker with policies, and a garage with vehicles. Forcing those into notes fields or deal names makes them impossible to search, report on or keep accurate. Custom objects solve that.
How custom objects work
A custom object behaves like a built-in record type:
- It has fields. You choose the name and type of each one: text, number, date, a pick list, a checkbox, an email or phone number, a link, or a lookup to another record.
- It links to other records. A lookup field connects a lease to a tenant, a vehicle to its owner, or a matter to a client company.
- It gets its own lists. You can search, filter, sort, save views and export the records.
- It has a page layout. You decide which fields show first and how they are grouped.
Examples by industry
| Business | Custom object | Typical fields |
|---|---|---|
| Real estate agency | Listings | Address, list price, status, bedrooms, listed date |
| Law firm | Matters | Matter number, client, practice area, status, responsible partner |
| Insurance broker | Policies | Policy number, carrier, premium, renewal date, status |
| Recruiter | Requisitions | Role, client, salary range, openings, status |
| Garage or dealer | Vehicles | Make, model, year, registration, owner |
| Nonprofit | Grants | Funder, amount, deadline, stage |
When you need one, and when you do not
Create a custom object when the thing you are tracking has its own lifecycle and several facts of its own, and especially when one customer can have many of them. A tenant can have several leases; a client can have several matters.
Do not create one for a single extra fact. If you just need to know a customer’s preferred contact time, that is a field on the person, not a new object.
Mistakes to avoid
- Designing everything up front. Start with the two or three objects you use daily and add fields as real questions come up.
- Free text where a pick list belongs. Status, type and category fields should be selections, or your reports will count “Active”, “active” and “Actve” separately.
- Duplicating built-in records. Do not create a “Clients” object if clients are simply companies or persons; link to the built-in records instead.
- Forgetting the lookup. An object that is not linked to the customer it belongs to becomes an island.
How GuardenerAI handles it
- GuardenerAI CRM lets admins add custom objects with no cap on how many objects or fields you create.
- Field types cover text, number, date, date and time, select, multi-select, checkbox, email, phone, URL and lookup, each with optional validation such as lengths, patterns, number ranges and date ranges.
- Admins set page layouts and saved list views, and records can be imported and exported as CSV.
- Starter templates add ready-made objects, for example Listings for real estate, Matters for professional services and Policies for insurance brokers. Everything a template adds stays editable.
- Custom objects use table views; board views are for opportunities, tasks and cases. Save-time validation and enrichment rules run on the built-in records rather than on custom objects, so per-field validation is how you keep custom records tidy.