Define your own record types with typed fields, create and link records like any built-in part of the CRM, then answer your own questions about them with a report builder that reaches six datasets — without exporting anything to a spreadsheet or paying a consultant to configure it.
You are storing the thing your whole business is about in a custom field called Notes.
It is that nobody has the hours, and the cost of skipping it never shows up as a line on any invoice.
The policy, the vehicle, the property, the animal — the thing every conversation is actually about — gets stuffed into a note or a custom field, where nothing can filter it, report on it or automate against it.
Someone asks how last quarter went by source and the answer is a CSV, a pivot table and an afternoon. Do that monthly and the reporting is always describing a business that has already moved on.
The enterprise CRMs will model anything you like, once you have paid for the licence, the partner and the implementation. The bill arrives long before the first useful report does.
Model
Name it, give it typed fields — text, number, date, boolean, select and more — and pick which field is its display label. No schema migration, no consultant, no ticket.
Use
Create, list and link records under /objects, workspace-scoped with the same row-level security as every other table, and validated by the same rules the server enforces so the errors read in plain language.
Report
Build reports from six datasets — contacts, deals, calls, messages, appointments and revenue — choosing dimensions, metrics, filters and a daily, weekly, monthly or total time bucket. Save the ones you will run again and share them with the workspace.
Automate
Custom objects get full API, MCP and Copilot access through the same capability registry as the rest of the product, so your integrations and your AI agents read and write them exactly like a contact.
These are not roadmap items. Each one is running in production today, described here in the same words the full product catalog uses.
Model the records your industry actually runs on, not just contacts and deals.
Define your own record types — properties, vehicles, policies, pets — with typed fields, then create, list, and link records under /objects like any built-in part of the CRM.
Answer your own questions about the business without exporting to a spreadsheet.
Build reports at /reports from six datasets — contacts, deals, calls, messages, appointments and revenue — choosing the dimensions, metrics, filters and time bucket yourself. Save the ones you'll run again and share them with the workspace.
One record per human, with everything they've ever done on it.
Inline-editable contact records with companies, business name, website, and address — plus your own custom fields for whatever your business actually tracks.
See the whole board and drag a deal to where it really is.
Drag-and-drop deal pipelines with stages you define — and stage changes that can trigger automations.
Define an audience once as rules and let it keep itself current.
Rule-based audiences over the contact record and everything attached to it, so “booked but never showed, and nobody has called them in two weeks” becomes a saved segment you send to — not a spreadsheet someone exports again every Monday.
Open Chirply and see what moved before you open a report.
A drag-and-resize dashboard combines pipeline, revenue, calls, contacts, tasks, live visitors, chat, and recent activity in the layout each workspace wants.
Your AI agents can drive Chirply directly.
The public REST action API, built-in MCP server, and in-app Copilot all read the same capability registry, so software can operate the same product people do.
This is the part of Chirply that solves custom objects & reporting. See the other 14 areas — CRM, scheduling, messaging, automations, funnels, commerce, reputation and the rest — all included in the same workspace.
You do not have to migrate anything to find out whether this works. Start the trial, set up the one thing you came here for, and judge it on that.
Your trial runs on Scale, the top plan, so nothing is locked while you evaluate. If custom objects & reporting is all you need afterwards, Scale at $97/mo carries it — switch down before the trial ends and keep the lower price.
Your order
$0 today. A card keeps the workspace running after the trial, and Scale renews at $97/month unless you change plans or cancel first.
Cancel any time before day 30 and nothing is charged. Calls, texts, emails and contacts are unlimited on every plan — you bring your own Twilio, Mailgun and model keys and pay those providers directly.
$0 today. Cancel before day 30 and you are never billed.
No contract, no setup fee, no cancellation call. The card only exists so a workspace you decide to keep does not stop working on day 31.
Scale, at $97 a month — the plan your free trial already runs on — along with unlimited custom fields and unlimited pipelines. The report builder itself starts lower, on Grow at $77.
Define the types your business needs. Records are workspace-scoped with row-level security like every other table, and the record form validates against exactly the rules the server enforces — so what you can save through the UI is what you can save through the API.
No. Reports run only through a declared catalog of datasets, dimensions and metrics, so a report can never reach data its dataset does not expose. Any result exports to CSV when you do want it in a spreadsheet.
Yes. They register in the same capability registry as everything else, which means the REST API, the built-in MCP server and the in-app Copilot can all read and write them under the same permanent action names.
A custom field describes a contact. A custom object is its own record you can create many of, link to contacts, and report on independently — one customer with four vehicles, or one household with three policies, without inventing field names like vehicle2_make.
Weighing it against something specific?
Chirply