All works   Next →
Ramp BOA
Building consistency across enterprise digital products.



About

Ramp is a global financial technology company building infrastructure that connects the crypto economy with traditional financial systems. Since 2018, the company has focused on creating secure and compliant financial products that make access to web3 more reliable and accessible.

BOA (Back Office App) was Ramp’s internal operational backbone — the infrastructure and interface that enabled teams across the company to process thousands of daily transactions. It brought together multiple third-party services alongside custom-built internal tools into one coherent platform supporting AML/CFT (Anti-Money Laundering and Countering the Financing of Terrorism), compliance operations, customer support, and internal workflows.

As Ramp scaled globally, BOA became a critical piece of internal infrastructure: the system through which teams monitored transactions, resolved operational issues, managed compliance processes, and coordinated customer-facing support. It served as the operational layer connecting highly specialized teams while maintaining speed, accuracy, and regulatory standards.


The challenge

Designing BOA meant working with a highly specialized enterprise product with very few direct benchmarks in the industry. Because Ramp operated at the intersection of fintech, crypto, compliance, and payments infrastructure, many common standards or patterns used in enterprise software could not simply be applied. Success metrics and workflows often needed to be defined internally, in close collaboration with the teams using the platform every day.

A major challenge was the existence of a legacy system that was deeply embedded in daily operations. Many teams relied on it and had developed workflows around it over time. The system carried institutional knowledge and was trusted despite its limitations. Introducing a new internal platform required careful migration planning and strong stakeholder alignment to ensure continuity, reduce friction, and build confidence in the transition.

Another core challenge was designing around shared data used by multiple departments with very different needs. Finance, Compliance, Customer Support, and Development Support all relied on the same operational information, but each required different views, priorities, and workflows. Rather than forcing a single rigid interface, the product needed to support multiple ways of interacting with the same system while maintaining consistency and reducing operational complexity.



Goals

The project focused on building a scalable internal platform that could support Ramp’s growth while improving day-to-day operational efficiency across teams.

Key goals included:

  • Integrating multiple third-party services
    Centralizing external tools into one platform while gradually replacing selected services with in-house solutions.

  • Creating a unified operational overview
    Building a condensed and comprehensive view of Ramp’s back-office processes and establishing more consistent system behaviors across workflows.

  • Improving support operations
    Designing clearer workflows and more effective tooling to reduce support workload and improve response times.

  • Clarifying role management
    Introducing scalable permission structures and clearer operational accountability for a growing distributed workforce.

  • Reducing errors and improving service quality
    Minimizing operational mistakes through better system design while improving the reliability of customer-facing support.






My role

As a Senior Product Designer, I was responsible for the user experience of significant parts of Ramp’s core internal product. From prioritization through launch, I led design work across multiple streams, collaborating closely with product managers, engineers, compliance specialists, and operations teams.

The work required balancing regulatory requirements, business priorities, and complex internal workflows while advocating for both internal users and broader organizational needs. Because BOA sat at the center of daily operations, design decisions directly influenced how teams worked across departments.

Throughout the project I facilitated regular stakeholder meetings, interview sessions, and product discovery workshops to better understand workflows, identify friction points, and align teams around priorities.

During the early stages of the project, I also led the creation of the BOA Design System — a dedicated design system for Ramp’s internal applications that established shared UI patterns and improved consistency across the platform.






Approach

The product development process was inspired by Teresa Torres’s Continuous Discovery methodology.

The core team consisted of a Product Manager, Tech Lead, and myself as Design Lead. We worked closely in a focused product trio, combining business priorities, technical constraints, and user insights throughout the process.

Over the first months of development we mapped workflows, conducted interviews with internal stakeholders, identified operational pain points, and tested early hypotheses through wireframes and system maps. This iterative approach helped validate assumptions early and made it possible to design around real operational needs rather than theoretical requirements.

The process emphasized close collaboration with the teams using BOA every day, allowing the platform to evolve through continuous feedback while supporting long-term scalability.



Outcomes

The project delivered a stronger and more scalable internal infrastructure for Ramp’s operations.

Key outcomes included:

Attribute-based access control
Designed and implemented a permission model enabling secure and contextual access management for a distributed global workforce.

Faster customer support workflows
Reduced average support ticket resolution time within the first weeks of MVP implementation.

Improved operational response time
Helped decrease reaction time to technical issues through better internal visibility and workflow clarity.

Better internal collaboration
Introduced tagging and commenting systems that improved coordination and communication across teams.

Shorter onboarding time
Simplified workflows and improved system consistency, reducing training time for new customer support agents.