Investor Module

Opportunity & Context

As our investor base surpassed 20,000 on both internal and white-labeled platforms, the need for a dedicated system to manage investor data became critical. This module was designed to serve as the backbone for client servicing, compliance, and investor engagement — enabling teams to manage detailed records for both Individual and Organisation investors.

The Challenge

Key Issues with the Existing System

1. Scattered Investor Listings
   Investors are categorized across different tabs, requiring users to navigate multiple layers to find the relevant information. This fragmented structure makes searching for specific investors inefficient. The first change should be consolidating all investors into a single, searchable listing for streamlined access.
   
   The existing listing is separated out into 3 tabs in order to look for the specific investors:

   
   

   

   
   

   

   
   

2. Primary Investor Concept
   The system lacks clarity on which investors should have future privileges and features. Without a clear definition of primary investors, it becomes difficult to manage and track special privileges for specific investors over time especially for Organisation Investor
   
   

   

   
   

3. Limited User Access for Offline Investors
   Some investors are offline, posing a challenge in providing platform access. The system needs a solution for assigning user credentials and permissions to Investor Representatives, enabling them to manage these offline investors with appropriate access rights.
   The existing listing is separated out into 3 tabs in order to look for the specific investors:

   
   

4. Limited ability to create and update investor records
   Users were unable to create or edit investor profiles, which made it challenging to maintain accurate, up-to-date records. Managing both Individual and Organisation investor types, each with unique login accounts, representatives, and compliance data, required a more flexible solution. The lack of structured forms for data input and integration with other modules like KYC and Connected Profile led to errors and inefficiencies in workflows.

Contraints

To create Investor:
1. Investor cannot consist of more than one Investor Type (Individual or Organization)
2. Organization investor type may have multiple Investor Representative(s)
3. Organization investor type may only have one Primary Investor Representative set to the organization - (The Primary Investor Representative will have the authority to manage holdings and investments within the Investor account. )

Solution & Role

We introduced a new Investor Module within Atlas — designed to manage, edit, and surface detailed investor records efficiently.
This included:

• Profile creation and edit flows for both Individual and Organisation investors

• A centralised view of accreditation, KYC, and investment activity

• Integration with other modules such as Connected Profiles and Orders

• The ability to assign representatives and create login accounts

• Structured, user-friendly forms to minimise errors and enforce data consistency

This module now powers investor servicing across both internal teams and white-labeled clients.

Impact

✅ Enabled full creation and editing of investor records
🔒 Improved compliance with detailed audit logs and structured KYC data
⚡ Reduced manual workflows and data-related errors for internal users
🔗 Enhanced integration with downstream modules like Orders and Deals
🔄 Provided a scalable foundation for investor engagement — internally and through client platforms

This module now supports investor servicing for both internal teams and white-labeled clients. It has become a core component of Atlas and continues to grow in functionality as adoption increases.

What I Learned

Designing the Investor Module deepened my understanding of building tools that balance internal operational needs with regulatory compliance and client flexibility. I learned how to:

1. Design for complexity by mapping multiple user types (individuals, organizations, representatives) into one cohesive system

2. Collaborate cross-functionally with ops, legal, and engineering to align on regulatory requirements and data accuracy

3. Prioritize scalability from day one — ensuring the module could support both internal teams and white-label clients

4. Think in systems, not screens — connecting this module to orders, deals, login management, and more

5. Advocate for users by simplifying workflows that were previously manual, fragmented, or error-prone

6. This project strengthened my ability to lead end-to-end design for high-impact, high-complexity tools — and continues to shape how I approach modular, scalable design systems.