B2B Marketplace — Burket

C#.NET CoreAWS (Cognito, SES, S3)AzureSQL ServerJIRA

The Challenge

Burket was a Philippine B2B marketplace funded by the Department of Science and Technology (DOST), aimed at connecting local businesses with verified suppliers. The project started from scratch — no existing codebase, no established architecture — and needed to serve a diverse set of stakeholders: vendors, buyers, and platform administrators, each with distinct workflows and access requirements.

What I Built

System Architecture: Led requirements analysis with stakeholders and designed the entire system architecture from the ground up using a combination of Azure and AWS services. This was a full system analyst role — translating business needs into technical specifications, defining data models, and mapping out integration points.

Vendor Management System: Built the core vendor onboarding and management system. Vendors could register, manage their product catalogs, receive orders, and track fulfillment. The system included approval workflows to ensure only verified suppliers appeared on the platform.

Single Sign-On via AWS Cognito: Implemented centralized authentication using AWS Cognito, providing SSO across the marketplace. Buyers, vendors, and administrators all authenticated through a single identity provider with role-based access to their respective dashboards.

Notification System: Built transactional email notifications using AWS SES — order confirmations, vendor approvals, payment receipts, and system alerts. Each notification type was templated and configurable.

Project Delivery: Managed project delivery using JIRA for sprint planning and task tracking, coordinating across frontend developers, backend engineers, and business stakeholders to keep the build on schedule.

Impact

  • Delivered a working marketplace platform from concept to production within the DOST funding timeline
  • AWS Cognito SSO simplified the user experience across buyer and vendor portals
  • Vendor management workflows reduced manual approval processes for the platform team
  • JIRA-driven sprints kept a distributed team aligned and delivering consistently

What I Learned

This project was formative because it put me in a system analyst role alongside engineering. Gathering requirements from non-technical stakeholders, translating them into architecture decisions, and then building the system end-to-end — that full-cycle experience sharpened how I think about products, not just code.