Web2022

Investor Marketplace

A full-stack investor marketplace built with ASP.NET MVC, C# and SQL Server: RESTful APIs for investor profiles, deal flow and startup onboarding, with role-based access control over a responsive UI. Built during my Web Development internship at Appuno IT Solutions.

User roles with distinct access
2
API architecture
REST
First production deployment
2022

The problem

Early-stage fundraising runs on introductions and asymmetry. Founders cannot see which investors are active in their space, and investors cannot see deal flow outside their own network. Both sides decide on partial information, and the matching that results has more to do with who you already know than with fit.

The approach

Put both sides in one structured system with role-based views. Startups list opportunities against a consistent schema, and investors discover, filter and track deals through the same data instead of through inbox forwarding. A shared schema is what makes the two sides comparable.

Early-stage fundraising is unnecessarily opaque. I wanted to build a clean, structured platform where the information asymmetry between founders and angels is reduced, making the matching process feel less like luck and more like informed decision-making.

Why I built it

Architecture

  1. 01

    Data layer

    SQL Server schema modelling investor profiles, startups and deal flow.

  2. 02

    API layer

    RESTful endpoints in ASP.NET MVC / C# for profiles, onboarding and deal management.

  3. 03

    Access control

    Role-based permissions separating founder and investor views over shared data.

  4. 04

    Interface

    Responsive UI for discovery, filtering and deal tracking.

Stack

Backend
ASP.NET MVC · C#
Database
SQL Server
Frontend
JavaScript · Bootstrap
  • ASP.NET MVC
  • C#
  • SQL Server
  • REST APIs
  • JavaScript
  • Bootstrap

Outcome

A working two-sided platform where startups list and investors discover, filter and track deals, with the matching grounded in a shared schema rather than in whose inbox a deck happened to reach. It was my first production engineering work.

NextML · Data Eng

Distributed EHR processing with 50K+ synthetic patient records.