Solutions
Start with all of it. Add a vertical only if you need one.
Most of what a business does is the same everywhere — conversations, contacts, follow-up — and the generic build gives you every bit of that with nothing switched off. Some trades also carry records the core CRM genuinely cannot hold. That is what an industry module is for.
Generic
The whole platform, with nothing switched off
The default, and what most businesses run: every core capability, with no industry module narrowing it to one trade.
- Every core capability, nothing held back
- The generic bookings module, which industry accounts don't get
- Pipelines, fields and tags named the way your team talks
- Add an industry module later if you ever need one
Aesthetics clinics
The diary, the record and the money, in one place
A full clinic module — appointments, patient records, treatments, invoicing and doctor commissions — sitting on top of the messaging platform your patients already use.
- A diary the database will not let you double-book
- Patient records with the conversation attached
- Invoices that freeze on issue, commissions that never recalculate
- A Doctor role with its own workspace and its own visibility
Study abroad consultancies
Every case, every deadline, and who you're waiting on
Cases and tracks for admissions and visas, checklists with a real gate, branch scoping, and two separate billing systems — one for students, one for university commission.
- Admission and visa tracks under one student case
- Checklists gated by the database, overridable on the record
- 'Waiting on' tracked per step, so worklists show real work
- Student fees and university commission billed separately
How it works
No module, or exactly one — and it owns its own ground
Most accounts run none
No module is the default, not a lesser tier — every core capability is there either way, plus the generic bookings module that industry accounts don't get. You can add a module later if your business turns out to need one.
Adding one goes one way
An account runs at most one module, and once it is set it is frozen. That is deliberate: a module owns real records — patients, cases, invoices — so moving between verticals is a migration rather than a preference.
A module replaces, it doesn't sit beside
Where a module owns something, core stands down — a clinic gets the clinic diary and generic bookings disappears entirely, so two calendars never disagree about the same afternoon. Everything else is untouched.
Not on this list?
If your business has records and money the core CRM can't quite hold, tell us what they look like. New modules get built when a real business needs one.