Projects
Custom CRM & internal systems
Bespoke systems built around clients’ internal processes.
Work in this area is continuous. Because these are clients’ internal systems, no screenshots, client names or specific figures are shared.
The business problem
As a company grows, a process spreads across spreadsheets, email threads and several separate applications. The same data sits in three places with no way to tell which is right, and finding out whose approval it is waiting on means asking. Off-the-shelf platforms require bending the process to their logic — when the process is often the company’s own advantage.
The ORMUS role
ORMUS analyses the processes, builds the data model and the role matrix, develops the system and integrates it with the accounting software already in use, produces documentation and training, and then continues support.
User journey
A request is raised
An employee or a customer creates a task, an order or a query.
It is routed
By type and role matrix it reaches the person responsible.
It goes through approval
The approval chain is recorded step by step.
Execution is tracked
Status, deadline and owner are visible at any moment.
It reaches reporting
The outcome is collected into reporting automatically.
Key capabilities
- Bespoke CRM and request management
- Order and warehouse records
- Approval routing and document flow
- Role matrix and access control
- Integration with the accounting systems already in use
- Automated reporting and an audit trail
A substantial part of ORMUS’s work is internal systems that cannot be shown publicly: bespoke CRM, order and warehouse management, approval routing, internal portals and reporting systems. These are built around a specific client’s processes, so each one is unique and interface screens are not published.
Architectural approach
The process is modelled as a state machine: which status a document may move to, and who may move it, is constrained. Changes are not overwritten — every transition is kept as its own record, so “who changed what, and when” always has an answer. Integrations live in their own layer so that replacing an accounting package leaves the core logic untouched.
Security and privacy
Access is governed by the role matrix and every operation leaves an audit record. Where the data is stored is agreed with the client. Client names, screens, data structures and integration details are not published.
Scope of work
- Process analysis and the data model
- Role matrix and access control
- Integration with the accounting systems already in use
- Documentation, training and support
Technology direction
Web-based enterprise systems, an integration layer and a role model. Client names and screens are not disclosed.
This page contains only publicly disclosable information. Technical architecture, database structure and client processes are not published.
Related services
- SW-01
Custom Software Development
Rather than bending your process to a product, building the system around the process.
- SW-04
CRM, ERP and Business Automation
Sales, warehouse, orders, HR and production — in one system rather than separate spreadsheets.
- OP-03
Support, SLA and Dedicated Teams
The work after launch: response times, monitoring and planned development.
Need something similar?
Describe your situation briefly and we will work out together how a system like this would fit your processes.