Stackfusion
2025
B2B Smart parking management platform
Designing a scalable, role-based B2B SaaS platform that brought fragmented parking operations into one centralized system.
Overview
Turning fragmented parking operations into one scalable system
As Stackfusion's sole UX/UI designer, I led the end-to-end design of a responsive, role-based Smart Parking Management platform. The platform brought previously fragmented parking-management capabilities into one centralized system for site owners, managers, operators and other stakeholders. My ownership spanned the full product design lifecycle—from design and user research, requirements gathering and competitor analysis to information architecture, interaction design, prototyping, usability testing, documentation and developer handoff.
Because the product operated across both digital and physical parking environments, I worked proactively with founders, sales, developers, testers, support staff and on-ground parking teams throughout the project, bringing their requirements and constraints into the design process as they emerged. The result was a scalable platform designed to give clients greater control over their parking operations while reducing their dependency on support and development teams.
Problem & Research
The problem wasn't a lack of features. It was fragmented control.
Stackfusion already provided smart parking services to clients, but many functionalities were fragmented across tools or available only through support requests. This created several problems:
• Support teams spent significant time responding to repetitive client requests.
• Clients depended on support teams for routine operational tasks.
• Developers were repeatedly pulled into ad-hoc feature requests.
• Different tools and processes created inconsistent experiences.
• As the product grew, the existing approach became increasingly difficult to scale.
The goal was to move these recurring operations into a centralized product experience. The platform needed to:
• Integrate core parking-management functionality into one system.
• Reduce client dependency on support and developers for day-to-day tasks.
• Provide real-time visibility and control over parking operations.
• Support different parking-site configurations and user roles.
• Create a scalable foundation for future functionality.
Understanding the system before designing it
I approached the problem from multiple perspectives rather than treating it as a purely interface-design exercise. I worked with internal teams—including support, developers and client-success stakeholders—to understand recurring pain points and operational requirements.
I also reviewed historical client requests and support tickets to identify frequently requested functionality. Alongside this, I conducted competitor and design research to understand how comparable platforms handled data visibility, configuration and operational control. Throughout the process, I collaborated with stakeholders to create and discuss low-fidelity wireframes, using those early explorations to surface requirements and edge cases before moving into detailed design.
System design
Designing for complexity without exposing all of it at once
The platform had to support a wide range of functionality—from parking availability and dynamic pricing to subscriptions, reports, devices, gates, users and permissions. The complexity came from more than the number of features. Different users needed different levels of access, different parking sites had different configurations, and many workflows required detailed rules and conditions. This made information architecture and role-based access central to the design.
I structured the platform around key operational areas including:
• Parking availability
• Reports
• Dynamic pricing
• Pass plans & subscriptions
• User management
• Roles & permissions
• Gate activity
• Device management
• Coupon management
• Parking lot creation
• File centre
Rather than exposing the full complexity of the system to every user, the experience was structured around role, responsibility and context.
Role-based architecture
The platform served different stakeholders, including site owners, managers, operators and other users with different responsibilities. Each role required a different combination of visibility, control and permissions. The system therefore supported predefined permissions as well as customizable roles, allowing site owners to create access structures appropriate to their operational needs.
Progressive disclosure for complex configuration
Several workflows involved complex configuration—for example, dynamic pricing, pass plans, subscriptions and permissions. I used progressive disclosure to keep these workflows manageable, revealing relevant options as users moved through a task rather than presenting every configuration parameter at once. The objective was to preserve the flexibility required by an enterprise system without making the interface feel unnecessarily complex.
Design
From complex requirements to usable operational workflows
I designed the platform around the core jobs users needed to perform across a parking site's lifecycle. Rather than treating every feature as an isolated screen, I designed connected workflows that allowed users to monitor, configure and manage their parking operations from one system.
01 — Monitor Parking availability
Users can monitor live slot occupancy by vehicle type, company, parking lot or floor, with the ability to manually override availability for specific areas when required. Additionally they can access a wide range of report types to track site activity and generate insights.
02 — Manage Pass plans & subscriptions
The system supports flexible pass plans based on duration, number of visits or time slots. Users can create subscriptions for companies and manage individual vehicle passes within those subscriptions. The plan creation process is based on rule based structure (defined on the basis of user needs) with progressive disclosure to reduce cognitive load.
03 — Configure Dynamic pricing
Users can create pricing rules based on factors such as hours, days and vehicle type. These rules feed into ticketing and pass-plan logic.
04 — Control Users, permissions, gates & devices
The platform brings user management, custom roles, real-time gate activity and device monitoring into the same operational environment. Gate activity provides a live view of events from vehicle detection through exit, helping teams monitor operations and investigate issues.
Designing for operational visibility
Reports and data visualization were another important part of the platform. The system supported multiple report types—including ticket, gate, operator and dwell-time reports—allowing users to understand site activity and generate operational insights. A centralized file centre also provided a place to download reports and schedule automated reports for longer-term access and sharing.
Impact
Moving routine control closer to the client
The redesigned platform moved frequently requested operational tasks from support and development teams into the product itself. The project presentation reports a 90% reduction in recurring support queries and developer workload, enabled by giving clients direct control over workflows such as pass plans, coupons, reports and other day-to-day operations.
This changed the role of the product from a system that required frequent intervention into a platform where clients could independently manage more of their parking infrastructure. The platform also introduced advanced operational capabilities such as device alerts and event logs, which were not present in some competing products and helped strengthen Stackfusion's product offering.
Beyond efficiency
The platform also expanded what clients could manage directly. Capabilities such as real-time gate activity, device monitoring, flexible pricing, subscriptions and reporting created a broader operational control layer rather than a collection of disconnected administrative tools. The result was a more scalable foundation for Stackfusion's parking-management offering.
Reflection
Enterprise UX is the art of making complexity manageable
Designing Stackfusion's parking products taught me that enterprise UX isn't about making complex systems simple by removing capability.
It's about making complexity legible, contextual and manageable for the person using it.
01
Simplification matters as systems become more complex
In enterprise dashboards, summarized information, clear flows and contextual guidance can make large amounts of functionality easier to navigate.
02
Real-time visibility creates operational value
Live device and gate monitoring wasn't simply another dashboard feature. It gave users visibility into what was happening in the physical parking environment.
03
Customization needs boundaries
The system needed to accommodate different sites, configurations and roles without turning every workflow into an unrestricted configuration problem.
04
Complexity should follow the user's role
Users should encounter the level of system complexity relevant to their responsibilities rather than the complexity of the entire platform.
Where the platform could go next
The product also opened up opportunities for further expansion.
01 — Predictive analytics
Use historical data to forecast parking demand, detect anomalies in gate and device activity, and support more proactive decision-making for site managers.
02 — Floor-plan-based lot mapping
Use AutoCAD or floor-plan data to accelerate parking-structure configuration and enable visual mapping of live parking availability.
03 — B2C reservation
Extend the platform beyond B2B parking management by allowing individual users to reserve parking slots in advance.
