Hyperqube Ionic – Deal Sourcing & Investor Intelligence Platform

PROJECT

Hyperqube Ionic – Deal Sourcing & Investor Intelligence Platform

Due to confidentiality and NDA restrictions, detailed product visuals and business information cannot be shared. This case study focuses on my design process and contributions.

Product

Hyperqube Ionic

ROLE

Product Designer

TIMELINE

2 Months

( 8 weeks )

MY RESPONSIBILITY

I was responsible for designing the Referral Management experience within Hyperqube Ionic, including referral workflows, Inbound Referrals, Outbound Referrals, Permissions, and supporting user journeys.

My work involved understanding complex investment workflows, creating wireframes, designing user flows, aligning with the existing design system, and translating product requirements into scalable experiences.

What Exactly?

Deal Sourcing & Investor Intelligence Platform

Hyperqube Ionic helps investors discover opportunities, evaluate companies, manage referrals, track relationships, and organize investment decisions within a structured workflow.

The platform includes:

Deal Pipeline

Referrals

Relationship Management

Watchlists

Permissions & Access Control

Investment Tracking

Decision Workflows

Company & Investor Profiles

more

But First

Before designing referrals, I had to understand how investment teams actually work.

Briefly studying:

Deal sourcing workflows

Investment decision processes

Referral networks

Relationship-driven investing

User permissions and access control

Pipeline management

Alongside this, I reviewed existing investment platforms and CRM workflows to understand how referral and relationship systems are structured.

Questions I Got Everyday

How does a referral actually begin?

How should inbound and outbound referrals differ?

How do users track referral outcomes?

How much information is necessary at each stage?

How should permissions affect visibility?

How can we reduce complexity without removing context?

How do referrals connect back to the deal pipeline?

How should relationship tracking fit into the workflow?

Due to project confidentiality, only limited previews of the designs are displayed.

Things I Figured Out

About Designing Investment Workflows

Referrals are not standalone features—they are connected to deals, relationships, and decisions.

( Permissions influence nearly every interaction )

Tracking status and ownership becomes critical as workflows grow.

Consistency matters more than introducing new UI patterns.

Designing within an established design system often means solving problems through structure rather than visual redesign.

Through Wireframes, Iterations & Reviews

A large part of the process involved:

Understanding business logic

Mapping referral journeys

Designing multiple workflow states

Testing information hierarchy

Iterating based on stakeholder feedback

Due to project confidentiality, only limited previews of the designs are displayed.

Key Areas I Designed

Referral Dashboard

Inbound Referrals

Outbound Referrals

Permissions

Referral Detail Views

Referral Status Tracking

Supporting Referral Flows

Takeaway

Designing Hyperqube Ionic taught me how deeply interconnected enterprise workflows can be.

A referral isn't just a referral—it is connected to a deal, a relationship, permissions, ownership, and eventually an investment decision.

The challenge wasn't creating screens.

It was creating clarity.

Due to project confidentiality, only limited previews of the designs are displayed.

Note