Make the request the organising object.
I built the dashboard around pending, accepted and declined partnerships.
PRODUCT DESIGN CASE STUDY

MY ROLE · Research, information architecture and end-to-end partnership UX/UI
I designed Synqit to make business partnerships feel more structured than scattered cold messages. A request could be reviewed, accepted or declined, with both sides knowing where the relationship stood.
I interviewed founders, Web3 teams and investors, mapped the three roles and designed profiles, requests and messaging. Testing with businesses helped refine the trust signals in those flows.
I built the dashboard around pending, accepted and declined partnerships.
I unlocked messaging after acceptance rather than making an unsolicited message the first step.
I used business details, expertise and partnership history to support the decision before a request is accepted.
The screens below show how those decisions came together.




The existing case study documents the MVP and business testing, with the design presentation and pitch deck available as supporting work. I would next examine request acceptance and whether founders and investors need different dashboard priorities.