Operational data modelling
Designing one schema that holds a whole company: customers, money, contracts and people, with the relationships between them intact rather than inferred at report time.
About
One question about a customer should not need five systems.
A company of 5 to 100 people typically runs a CRM, a support tool, a finance tool, a contracts tool and an HR tool. Every one of them bills per seat. At least two of them put real costs somewhere other than the pricing page. And none of them can answer the question that actually matters, which is whether the customer who is unhappy in support is the same one who is late paying and quiet in meetings.
That question is unanswerable not because the software is bad but because the link between those records does not exist anywhere. It only exists inside one database. That is the whole idea, and everything else in Version X follows from it.
What we will not do
Charge for onboarding
Migration is done by Ori and included from the Scale tier. A services team charging separately to map fields by hand is exactly the cost we are trying to remove.
Claim certifications we do not hold
ISO 27001 and SOC 2 are a roadmap goal. Until an auditor has signed something, this site says so.
Pretend we win every comparison
HubSpot’s marketing automation is better than ours. Salesforce scales past where we stop. Our comparison pages say that before they say anything else.
Let AI write silently
Anything Ori does that touches more than one record runs through an approval gate. An AI with real permissions and no gates is a liability, not a feature.
What we are good at.
AI that is allowed to act
Agents with real permissions, real approval gates and a real audit trail. The engineering problem is not the model, it is deciding what it may do without asking.
Migration without a services bill
Getting a company off five systems and onto one, with the field mapping proposed automatically and approved by a human rather than billed by the hour.