Scroll Vertically -
Scroll Vertically -
Scroll Vertically -
Scroll Vertically -
Scroll Vertically -
Scroll Vertically -
Uga Station
A scalable operations platform for complex, multi-team work
overview
A real, built-and-shipped CRM used to manage leads, projects, tasks, invoices, and role-based access across teams.
Enterprise SaaS
RBAC
Real-time data
Google Studio
Firebase
Flutterflow
Design
Built
My Responsibilities
Product definition
UX & Information Architecture
Data modeling
Design → build → ship
Product type
Enterprise operations platform (CRM + Delivery + Billing)
Primary Users
Founders
Sales leads
Operations managers
Architects/Designers
Deliverable Teams
Product Scope | Core Modules
Dashboard
Sales
Projects
Tasks
Payments
Organisation
Healthy Ai
Non Goals | operational clarity first, extensibility later.
No advanced analytics
No custom reporting
No third-party integrations
THE CRITICAL PROBLEM
Sales data lived separately from delivery
Project status wasn’t tied to revenue
Access control was inconsistent
Founders lacked a real-time view
Each tool is functional on its own. However, they are not connected.
Goal: Companies Must scale from small teams to enterprise orgs
design principle
Visibility Over Control
Ownership over reporting
Early signals over late summaries
PRODUCT FLOW ARCHITECTURE
The product is structured around cause-and-effect, not isolated modules
sales
→
Delivery
→
Tasks
→
Payments
→
Roles
→
Health
design approach
Log In
User enters the product securely.
→
System verifies identity and authentication method.
→
User role and permissions are resolved.
→
User is routed to the correct starting page.
Q1. Why does the user start here?
To securely identify the user before any data or actions are exposed.
Q2. What decision does the system make here?
It determines who the user is and what they are allowed to access.
Q3. What is the outcome of this page?
The user is routed to the correct starting point with the right permissions.
Dashboard
Live activity across projects, quality, sales, and payments
→
Metrics summarised as signals (not reports)
→
Each signal exposes ownership + current state
→
Click takes you to the exact place where action is required
Q1. What question does the dashboard answer?
What needs attention right now.
Q2. Why are signals shown instead of raw data?
To help users understand status instantly without analysis.
Q3. What should the user do next from here?
Jump directly to the area that needs action.
Sales
View all deals
→
Track stage movement
→
Identify risks and priorities
→
Progress or close deals
Q1. What problem does the Sales page solve?
It shows how opportunities turn into real revenue.
Q2. Why track deal stages here?
To understand progress, risk, and conversion likelihood.
Q3. What action does this page drive?
Moving deals forward or closing them.
Projects
View all projects
→
Track progress and milestones
→
Detect risks early
→
Resolve issues
Q1. Why is this page critical post-sales?
Because delivery determines customer satisfaction and revenue realization.
Q2. What insight does this page provide?
How work is progressing and where it might fail.
Q3. What decision does it enable?
Where to intervene to keep delivery on track.
Tasks
View all tasks
→
See ownership and status
→
Spot delays
→
Update or complete work
Q1. Why is Payments part of the core flow?
Because completed work must translate into cash flow.
Q2. What risk does this page reduce?
Delayed or missed payments.
Q3. What outcome does it drive?
Faster and clearer revenue realization.
Healthy AI
System observes activity
→
Detects patterns
→
Explains insights
→
Guides action
Q1. Why introduce AI here?
To surface risks and insights humans might miss.
Q2. What does the AI analyze?
Patterns across sales, projects, tasks, and payments.
Q3. How does this help the user?
By guiding attention to what matters most.
Payments
View invoices and milestones
→
Check payment status
→
Identify revenue risk
→
Follow up to unlock payments
Q1. Why is Payments part of the core flow?
Because completed work must translate into cash flow.
Q2. What risk does this page reduce?
Delayed or missed payments.
Q3. What outcome does it drive?
Faster and clearer revenue realization.
Organisation
View org structure
→
Review permissions
→
Manage roles
→
Scale safely
Q1. Why does structure matter in this product?
Because access and responsibility must scale with growth.
Q2. What does this page control?
Roles, permissions, and team structure.
Q3. What failure does it prevent?
Unauthorized access and operational chaos.
Tablet Responsive Work In Progress 😎
Desktop recommended for the best experience.
This portfolio is optimized for large screens to clearly present complex systems and flows.
Desktop recommended for the best experience.
This portfolio is optimized for large screens to clearly present complex systems and flows.