Marketplace and product engineering
BirthTribes
Challenge
A birthday community is a simple idea. Making it a marketplace means the product has to hold consumers, merchants, gifting and commercial workflows across more than one market.
Approach
The engineering separates customer, merchant, catalogue, order, settlement and platform states, rather than treating the product as a set of pages. The live site currently shows the early-access consumer experience and the merchant application. It does not publish commercial results.
What was built
- An early-access consumer product: a reminder link, a tribe for people who share a calendar day, and reminders that stay opt-in.
- A wishlist that can be shared, including items brought in from other stores.
- A public merchant application for the United Kingdom and Nigeria. The page says applications still need admin approval before activation.
- Payments architecture is aimed at Stripe Connect for the UK and Paystack for Nigeria. That is a design direction, not a published transaction volume.
Scope
- Birthday communities
- Wishlists and gifting
- Merchant onboarding
- UK and Nigeria markets
Technologies
- Laravel 12
- Inertia
- React 19
- TypeScript
- Tailwind CSS 4
Named because they are in the verified engineering record. They are not partnership or certification claims.
What was delivered
The live product is an early-access birthday platform with a merchant path. Catalogue, order and settlement workflows sit in the engineering record. No revenue, merchant count or transaction figures are published here.
