Workflow simplification replaced fragmented screens with a guided operating flow.
Problem
A CRM system used by customer service agents handling more than 200K calls per day had fragmented workflows, multiple system handoffs, and high cognitive load. That drove up average handling time, slowed onboarding, and increased support cost.
Why it was hard
The challenge was not just a UI redesign. The system sat inside a high-volume support operation where every extra step affected cost, training, and service consistency. Improvements had to land safely without disrupting active agent workflows.
What I did
Led the redesign of the CRM experience by introducing guided workflows, contextual data panels, and a widget-based dashboard. Partnered with backend teams to unify data access, reduce unnecessary navigation, and add enough observability to validate improvements safely.
Impact
Reduced average handling time by about 30 seconds across 200K+ daily calls.
Saved millions annually in operational cost.
Improved onboarding time for new agents.
Created a framework that was reused across other teams.
Unlocking High-Value Payments Through Compliance Architecture
Payment
→
Compliance
→
Flags
→
Approval
Compliance was inserted into the payment flow without adding rollout risk.
Problem
Payments above $3000 were blocked by regulatory requirements, creating lost revenue and a poor experience for high-value customers.
Why it was hard
This was a cross-platform compliance problem spanning web, Android, and iOS, with production risk, regulatory sensitivity, and multiple teams involved. It had to be coordinated without the safety net of a heavy program structure.
What I did
Led the cross-platform implementation to capture required compliance data without breaking the payment experience. Coordinated teams directly, used feature flags for controlled rollout, and added observability so transaction behavior could be monitored closely in production.
Impact
Recovered about $800K per week in transaction volume.
Enabled compliant processing for high-value transactions.
Contributed to 140% growth in transactions above $3000.
Rolled out without major production incidents.
Enterprise Dashboard Platform for Unified Data Access
Source Systems
→
GraphQL Layer
→
JSON UI
→
Frontend
Multiple enterprise systems were unified through GraphQL, then rendered through JSON-driven UI generation.
Problem
Sales and product teams relied on disconnected systems for identities, permissions, and internal resources, which created inefficiency and poor visibility across the organization.
Why it was hard
The hard part was not rendering dashboards. It was creating a reusable platform that could unify different backend systems, avoid repeated custom UI work, and stay flexible enough for teams with different needs.
What I did
Designed and built a metadata-driven UI platform where dynamic UI was generated from JSON schema definitions. Unified data from multiple backend systems through structured APIs and reusable frontend components so new views could be assembled faster.
Impact
Created a single interface for enterprise-wide data access.
Used dynamic UI generated from JSON to reduce repeated dashboard build work.
Reduced the need to rebuild custom dashboards repeatedly.
Adopted across multiple teams.
Reused the architecture for use cases beyond dashboards.
Perspective
What makes this work different
These projects were not greenfield builds.
They were delivered inside complex, high-scale systems with real constraints: legacy code, multiple teams, compliance requirements, and production risk.
The focus was not just building systems, but making them:
Easier to evolve.
Safer to operate.
Faster to deliver.
That is the difference between code and architecture.
Next step
If you're dealing with a system that feels hard to scale or evolve, I can help.