Most organisations run a ledger here, a staff list there, a course register in a spreadsheet and a website nobody can edit. Backbone holds them as one set of records, so a correction made once is a correction everywhere.
A person hired through Recruitment becomes an employment record in People without being typed again.
What somebody may see is decided once, by role, and applies to the ledger, the course register and the website alike.
Finance, people, training and the public site are the same console, not four logins.
Pick the modules that match how the organisation actually works. The rest stays out of the way until it is wanted.
Choose an industry and the vocabulary follows it, so the screens use the words the people in that trade already use.
Logo, palette, letterhead, numbering, approvals and who may do what are all settings rather than code.
Every plan includes a sandbox: a copy of the live system that sends no email and takes no payment, for training and for trying a change first.
Supplies, contracting, manufacturing and services: quotations, projects, invoices, stock and payroll against one ledger.
Programmes, cohorts, facilitators, attendance, marking, certificates and the fees that go with them.
Programmes, beneficiaries, grants and reporting, with the audit trail a funder asks for already in place.
Several organisations under one roof, each with its own database, its own branding and its own people.
Every organisation on Backbone holds its own database rather than a partition of somebody else's. Your data has a boundary you can point at, a backup you can take, and an export you can leave with.
A tenant's records live in a database of their own, so the boundary is a boundary rather than a filter somebody has to get right.
A walk through the modules that matter to your organisation, using your own vocabulary.
Bring your chart of accounts, your staff list and your course register across.
Questions about modules, pricing, hosting or the mobile application.