Back to blog
Founder Build Log12 min read

How I Built Baakas

A founder-level breakdown of building Baakas from idea to marketplace: validating the opportunity, designing buyer and seller workflows, launching the app, onboarding sellers, and learning what it takes to operate a real product with real users.

Baakas mobile marketplace poster showing the buyer app home screen

Case study draft

Overview

Baakas is the project that best represents the difference between building an app and building a business. The technical work mattered, but the bigger challenge was designing a marketplace that could support buyers, sellers, products, orders, and operations without becoming too complex to manage. This article will document the product decisions, architecture decisions, and founder lessons behind that process.

Planned Structure

Part 1

Why a multi-vendor fashion marketplace made sense for Nepali consumers

This section will turn the topic into practical, founder-level documentation with clear decisions, constraints, implementation notes, and lessons that can be reused in future products.

Part 2

How the buyer app, seller app, and admin dashboard fit together

This section will turn the topic into practical, founder-level documentation with clear decisions, constraints, implementation notes, and lessons that can be reused in future products.

Part 3

The marketplace operations behind seller onboarding, orders, catalog quality, and user support

This section will turn the topic into practical, founder-level documentation with clear decisions, constraints, implementation notes, and lessons that can be reused in future products.

Part 4

What changed after reaching 5,000+ downloads, 2,000+ users, and 50+ sellers

This section will turn the topic into practical, founder-level documentation with clear decisions, constraints, implementation notes, and lessons that can be reused in future products.

Publishing Goal

The goal for this article is to show how I think, build, make tradeoffs, and learn from real execution. It should help clients, collaborators, and hiring teams understand the quality of my product thinking, not just the tools I can use.