Data model
Bring your data model. Skip the custom build.
Every business keeps things no ready-made CRM or ERP knows about. Add them to SalexHub as records of their own, with the details you track, the links between them and the rules they keep, and change them as fast as your market does.
Create
No custom build
Add the kinds of record only your business keeps, with a name, an icon and a place in the menu. Each comes with its own list, record pages and properties. No developer, no project.
Adapt
Changes as fast as your market
Add a field on Monday, move a whole kind of record to another part of the menu on Wednesday. Ask the Agent to turn a text field into a number, and it shows what each value becomes before it does.
Use
Works like everything else
Your own records get the same tables, boards and calendars as contacts and deals, with reports beside your sales and money and automations that start when one changes.
Calculate
Numbers that fill themselves in
Days until a visit, a total across the records linked to one, a count of open jobs. Formulas and rollups work them out from the rest of the record, so nobody keeps a spreadsheet beside it.
Rules
One rule, every way in
Set a rule once, such as a technician on every booked visit, and it holds whether the record is typed in, written by the Agent, imported, or sent by an automation or your own systems.
Privacy
Private where it must be
Mark a detail personal or sensitive and it starts hidden from people who should not see it. Choose what AI may do with each one, and see who changed every value, and when.
The system you would have commissioned, set up in an afternoon.
When the software does not know your business, the usual answer is a project: a specification, developers and a release for every change. In SalexHub the same changes are settings, and they are yours to make.
| What you need | With a custom build | In SalexHub |
|---|---|---|
| A new kind of record | A specification, a database change, new screens and a release. | A name, an icon and the part of the business it belongs to. Its list, record pages and properties come with it. |
| A value worked out for you | Code, written and tested by a developer. | A formula over the record's other properties, from 24 functions, or a rollup that counts or adds up the records linked to it. |
| A link between two kinds of record | A join table, and every screen taught to show it. | Ask the Agent, such as a project and its suppliers. The link shows on every record of both kinds. |
| A rule the data must keep | The same check written into every screen and every import. | A record rule, written once and held on the screen, in the Agent, the API, an import and a workflow. |
| A change next quarter | Another project. | Add a property, move a record type to another part of the menu, or have the Agent change a property's type after it shows what each value becomes. |
Or describe it in a sentence.
Ask the Agent for a new kind of record, a property or a link between two kinds, in your own words, and it sets them up.
On every plan, and your own record types from Pro.
Properties, formulas, views, record rules and merging come with every plan, on the records SalexHub ships with. Record types of your own: Pro: up to 3; Business: up to 10; Enterprise: by contract.
Compare plansRun the business you have.
Start free with the records every business keeps, then add the ones only yours needs.