CASE STUDY // CRM · Business Systems
CRM OperatingSystem
Internal CRM and business-operations architecture designed for a multi-company structure spanning Veue and Onra.
- Role
- Designed the multi-company CRM architecture: instance separation, shared staff logic, currency handling, and reporting structure.
- Context
- Personal, internal business-systems architecture work built on Perfex CRM as the base platform — not a client engagement or formal employment.
- System Type
- Internal CRM / Business Systems Architecture
- Status
- Documented
- Priority
- Primary
- Stack
- Perfex CRM
Problem
Two related companies needed CRM and financial workflows that stay separate per entity (clients, projects, invoices, expenses) while sharing staff and rolling up to unified founder-level reporting.
Context
Personal, internal business-systems architecture work built on Perfex CRM as the base platform — not a client engagement or formal employment.
Role & Ownership
Designed the multi-company CRM architecture: instance separation, shared staff logic, currency handling, and reporting structure.
SCOPE CLARIFICATION
This is internal business-systems architecture work, not a client engagement or formal employment role. It maps how Veue and Onra could operate through separate CRM instances with shared staff, intercompany workflows, and founder-level reporting — built on Perfex CRM as the base platform.SYSTEM DESIGN
Architecture
Separate CRM instances per company with shared staff logic layered across them. PKR is the base currency, with foreign invoice handling and intercompany billing logic reconciling cross-entity transactions, plus payroll workflow logic feeding founder-level reporting.
SCOPE NOTE
Built as internal business-systems architecture rather than a customer-facing product.
KEY CAPABILITIES
What it does
Separate CRM instances per company with shared staff logic
Separate clients, projects, invoices, and expenses per entity
PKR base currency with foreign invoice handling
Intercompany billing logic
Payroll workflow logic
Founder-level reporting and CRM module planning
Business process mapping across entities
TECHNICAL STACK
Technologies used
CAPABILITY PROOF
What this proves
Systems thinking applied to real business/finance complexity — multi-entity architecture, currency handling, and cross-company operational logic — demonstrating the business-systems third of Musa's positioning.
CAPABILITY DOMAINS EVIDENCED
RELATED CASE STUDY
Founder Command Center
Founder Command Center
CAPABILITY LAYER
Want to see how this maps to the broader system?
Each case study connects to a capability domain. The full map shows how everything fits together.