A CRM that fits your business beats a feature-rich one that does not. Nearly everything about how Spodus models your work is configuration you change yourself in the app: the fields on a record, the objects you keep, and the stages a deal moves through.
Custom fields
Every record type can carry fields beyond the defaults. Add the ones your workflow depends on: a license number for a contractor, a renewal date for a subscription, a referral source for a lead. Fields you add show up on records, in list views, and as columns you can map during an import.
Fourteen field types are available:
| Text | Numbers and dates | Choices | Links |
|---|---|---|---|
| Text, long text, email, URL, phone | Number, currency, date, rating | Select, multi-select, checkbox | Relation, person |
A relation field points at a record on another object, which is what puts a deal, its invoice and its ticket on the same customer. A person field points at someone in your workspace. Existing fields can also be renamed, reordered, and hidden without deleting the data underneath them.
Record types
Out of the box Spodus models the standard objects: contacts, companies, deals, tickets, invoices and the rest. If your business thinks in other terms — properties, matters, patients, jobs — you can create an object for them, with its own fields and its own relations to the objects you already have.
The defaults are not fixed furniture either: any object can be renamed, given a different icon, or removed if you do not use it. None of this is a code change or a support ticket.
Pipeline stages
Your pipeline should mirror your real process, not a generic template. Stages are the options on a select field, so you rename them, add and remove them, and reorder them the same way you would edit any other field. A deal's stage is just its value in that field, which is why moving a card between columns and editing the field do the same thing.
Teams running two genuinely different processes — new business and renewals, say — are usually better served by two boards than by one board with every stage from both. Each board carries its own stages.
After changing stages, rebuild any saved views that filtered on the old names.
When you need more than a field
Need a field that auto-populates, or a webhook when a deal closes? Workflows cover the first, and workflow webhooks, in and out, are on Growth and above. Because fields and objects are configuration rather than code, the shape of your data is something you change on a Tuesday afternoon rather than something you request.
