Pegasus
Dispatch Management & E-Invoicing System (B2B SaaS)
Professional Project | Company: Tradais Digital | My role: UX Designer
Project Overview
Pegasus is a B2B dispatch management and GST e-compliance platform built for Indian SMEs to create and track dispatches, invoices, IRN (e-Invoice), and e-Way Bills with structured workflows and audit-ready documentation. The product reduces manual Excel-based operations by enforcing validated inputs, role-based access, and compliance-driven UI patterns.
The Problem
SMEs handling logistics and compliance-heavy dispatch processes often face:
-
Fragmented workflows across Excel, WhatsApp, and multiple portals
-
High error rates due to manual entry (GSTIN formats, vehicle numbers, HSN/units)
-
Confusion around dependency flows (e.g., EWB only after IRN success)
-
Low traceability: hard to prove “who did what” during audits
-
Slow onboarding: users struggle to set up company details, GSTINs
Design Goals
-
Simplify complex GST workflows through guided UI
-
Reduce errors using validation-first design
-
Improve traceability with status-driven dashboards
-
Design scalable UI patterns for future modules
Users & Access Levels
Pegasus is a role-based system, and each role required a distinct experience:
-
Admin: Company setup, role management, module access
-
Dispatch Operator: Create dispatches, submit IRN/EWB
-
Accountant: Review invoices, GST summaries, reports
-
Transporter: View/download e-Way Bills
-
Auditor: Read-only access, logs, signed documents
Design implication: Navigation, visibility, and CTAs change dynamically based on role permissions.
Why This Matters
Onboarding acts as the foundation of data accuracy. A guided setup reduced dependency on support teams and ensured compliance readiness from day one.
1. Onboarding & Login Experience
Objective
Ensure users can set up company and user details correctly the first time, as incorrect setup leads to downstream IRN/EWB failures.
UX Approach
Step-based onboarding with progress indicators.
Inline validation for GST-critical fields.
Role-based user invitations and access setup.
Save-as-draft capability to reduce friction.
2. Dashboard Design (Operational Control Center)
Objective
Create a dashboard that helps users monitor, prioritize, and act without navigating deep into the system.
Key Design Decisions
Status-driven cards: Success/Failed/Pending/Draft.
Actionable widgets for failed or incomplete flows.
Table-first layout for operational clarity.
Smart defaults showing recent and critical dispatches.
UX Impact
The dashboard made it easy for users to quickly spot pending actions, failed IRN/EWB cases, and daily workload, reducing time spent searching and troubleshooting.
3. Tooltips, Toasts & Alert Cards (Micro-interactions)
Tooltips – Contextual Guidance
-
IRN prerequisites
-
Vehicle number formats
-
GST terminology
-
Status definitions
Used to explain:
Toasts – Action Feedback
Used for non-blocking confirmations:
-
Dispatch saved
-
IRN submitted
-
Token refreshed
-
EWB generated
Alert Cards – Critical States
Used for:
-
API failures
-
Token expiration
-
Missing mandatory fields
-
Duplicate invoice detection
Design Principle
Feedback intensity matched risk level—helping users act confidently without overwhelming them.
Design System & Patterns Applied
Status badges (success, failed, pending), Role-aware navigation, Sticky table headers, Empty and error states, Scalable components for future modules
Pegasus reflects my ability to simplify complex regulatory systems into clear, human-centered digital experiences balancing usability, compliance, and scalability.