What it means
The category sits between two familiar ones. A CRM covers the customer relationship and largely stops at the sale. An ERP covers inventory, manufacturing and the general ledger, and is built for organisations with the staff to configure it. A business operations platform covers the work in between, from the first enquiry to the paid invoice and the support ticket after it.
It is not a set of separately bought products sold under one brand. The test is whether the modules share one set of records and one set of rules, or exchange data through connectors like any other stack.
Why it matters when you choose software
Many small and mid-sized companies run that work across five or more products: a CRM, a helpdesk, a project tool, a wiki and an invoicing tool, with automation joining them. Each is good at its job. The cost is in the joins: duplicated records, connectors to maintain, and reports that have to be exported before they agree.
One platform replaces the joins, not the jobs.
Questions to ask a vendor
- Which functions does it cover itself, and which rely on a partner product?
- Do all its modules share one data model and one permission model?
- Is every module included in the price, or sold separately?
- What does it deliberately not do, such as statutory accounting?
- How would we move our existing data in, and could we take all of it out again?
How Cyril approaches it
Cyril describes itself as a business operations platform: Sales, Projects, Support, Finance, Marketing and Automation, with Mail, Drive, Docs and Calendar as the everyday core, all on one schema, one permission model and one audit log. It handles invoicing, payments and expenses, but not statutory accounting such as the general ledger or tax filing at launch; it exports cleanly to your accountant’s tools instead. It is priced per seat, with every module included. Imports from CSV, Salesforce and Pipedrive come with rollback, and a full export is free at any time.