The whole business on one database, which is the point.
Operations is the function that pays for tool sprawl. Version X replaces the CRM, support desk, finance, contracts and HR tools with one system, so there is one integration surface, one permissions model and one export.
Today
- Five vendors, five renewal dates, five security reviews.
- Integrations between them break quietly and are found weeks later.
- Reporting means exporting everything and reconciling it by hand.
On Version X
- One vendor, one bill, one security review.
- Nothing to integrate between modules, because they are the same records.
- Reporting reads the database rather than five exports.
Who does this work
Not a tool you operate. Ori orchestrates, and the heads below do the work on your desk.
Head of Finance
Chases what is owed, reconciles what arrives, and watches the invoices that are going wrong.
Head of Knowledge
Answers from your actual process rather than a general model, and says when the documentation and the records have drifted apart.
Head of People
Holds employment records, onboarding and permissions on the same graph as the work itself.
Meet the rest of the team, and add specialists of your own wherever you need them.
The modules you will live in
Questions.
How many integrations do we need to maintain?
Between Version X modules, none: they are the same records rather than integrated systems. External integrations are capped at five on Launch and unlimited from Scale.
Can we export everything if we leave?
Yes. A complete export is possible precisely because the data is in one database rather than nine.