Frontend
Blade and Tailwind CSS provide server-rendered screens with fast loading and maintainable UI patterns.
Back To Portfolio
Multi-Tenant Travel CRM and Operations Platform
Production Ready
Ornexa CRM
Ornexa CRM is designed to run the travel sales journey from first inquiry to final payment by connecting leads, follow-ups, quotations, bookings, payments, finance, customer communication and reporting in one SaaS platform.
My Role
Product designer, Laravel architect and full-stack developer
Purpose
CRM for travel agencies, Umrah operators, visa consultants, tour operators and study abroad consultants.
Business Problem
Why this product exists.
Travel agencies, Umrah operators, visa consultants, tour operators and study abroad consultants often manage inquiries, quotations, bookings, payments and follow-ups across spreadsheets, WhatsApp, notebooks and disconnected tools. This creates missed leads, slow responses, weak payment visibility and inconsistent owner reporting.
Objectives
What the system is designed to achieve.
Centralize travel agency sales, operations, finance and customer communication.
Support travel agencies, Umrah agencies, visa consultants, tour operators and study abroad consultants through focused modules.
Reduce missed follow-ups and manual tracking.
Improve quotation, booking, payment and document workflows.
Give owners clearer visibility into leads, bookings, collections and staff activity.
Provide Core and Pro editions without presenting the product as a generic ERP.
System Architecture
How the product is structured.
Backend
Laravel 12 handles routing, controllers, validation, business workflows and data persistence.
Authentication
Authenticated user access protects agency workspaces and admin areas.
Authorization
Roles and permissions separate super admin, agency admin and team responsibilities.
Database
MySQL stores agencies, users, leads, follow-ups, quotations, bookings, payments, documents, activity history, subscription records and finance data for Pro workflows.
Business Logic
CRM workflows are grouped around lead capture, follow-up discipline, quotation creation, booking operations, payments, finance and reporting.
API Layer
The architecture can support controlled integrations such as WhatsApp, customer portals, reporting tools and future mobile interfaces.
Technology Stack
Why each technology was selected.
Laravel 12
Selected for secure authentication patterns, validation, routing, migrations and long-term maintainability.
Blade
Selected because CRM screens benefit from fast server-rendered interfaces and tight Laravel integration.
Tailwind CSS
Selected for consistent UI systems, fast iteration and responsive enterprise layouts.
MySQL
Selected for relational business data, reporting queries and strong compatibility with Laravel hosting.
Database Design
Important entities and relationships.
Agencies own operational data and provide the basis for tenant separation.
Users belong to agencies and receive roles for controlled access.
Leads connect to follow-ups, quotations and eventual customers or bookings.
Quotations connect leads, packages, pricing details, approvals and booking conversion.
Bookings connect customers, travel services, documents, payments and operational status.
Payment and finance records support collections, supplier bills, expenses, invoices, commissions and reconciliation in Pro workflows.
Activity logs preserve operational history for accountability and auditability.
Subscription records support commercial SaaS management and super admin oversight.
Core Modules
Feature groups that define the product workflow.
Modules are grouped by business responsibility so the product remains understandable and easier to extend.
Agency Management
Lead Management
Follow Ups
Quotations
Bookings
Payments
Customers
Reports
Settings
Roles & Permissions
Subscription Management
Super Admin
Agency Portal
Multi-Tenancy
Finance Management
Supplier Bills
Customer Invoices
Commissions
Multi-Currency Exchange Rates
AI Sales Assistance
WhatsApp Integration
Customer Self-Service Portal
Security
Security decisions are part of the product design.
Authentication
User login protects internal CRM access.
Authorization
Role based permissions control what owners, managers and staff can view or manage.
Validation
Laravel form requests and server-side validation protect business workflows.
Data protection
Sensitive agency records, payments, customer documents and activity history are kept inside authenticated application areas.
Tenant isolation
Agency-owned data boundaries prevent one agency from accessing another agency workspace.
AI governance
AI-assisted sales and chatbot actions are treated as recommendations that require human review and approval.
Engineering Challenges
Problems that shaped the technical decisions.
Designing a CRM focused enough for travel, Umrah, visa, tour and study abroad workflows without becoming a generic ERP.
Keeping lead, quotation, booking, payment and finance data connected so reporting remains useful.
Separating super admin responsibilities from agency-level operations.
Adding AI-assisted workflows in a governed way so automation supports staff instead of silently changing customer or payment records.
Screenshots
Product interface evidence.
Technical Achievements
Designed a multi-tenant SaaS CRM foundation for travel agency operations.
Connected lead, follow-up, quotation, booking, payment and reporting workflows.
Separated Core CRM workflows from Pro finance, AI and customer portal capabilities.
Created a structure that supports super admin and agency portal responsibilities.
Built with Laravel conventions for maintainable long-term development.
Completed
Core CRM workflow structure.
Travel agency-focused operational model.
Lead, quotation, booking, payment and reporting module direction.
Multi-tenant agency management direction.
Future Roadmap
Advanced analytics dashboards for agency owners.
WhatsApp communication workflows.
Customer self-service portal expansion.
AI-assisted lead scoring, follow-up suggestions and chatbot workflows with human approval.
Finance workflows for expenses, supplier bills, invoices, receivables, commissions and reconciliation.
Project Discussion
Want to discuss a product with similar complexity?
Share your business problem and I will help identify the right architecture, workflow and delivery path.