Compare
Joel Transport vs Fashionly vs Multichoice installer payments
The problem, what was built, the stack and the outcome, next to each other.
Clear · Up to 3 at a time
In common
- Shared stack: none in common
- Order: Joel Transport (Dec 2022 – May 2023) → Fashionly (Apr 2026 – present)
Swipe sideways to compare ›
Joel Transport ›
Online booking platform on AWS
Fashionly ›
Your style, elevated: an AI stylist that starts with what you own
Multichoice installer payments ›
R5M+ paid to installers in the first six months
At a glance
- Role
- Lead Engineer
- When
- Dec 2022 – May 2023
- Length
- 6 mo
- Status
- Live
- Type
- Web, Platform
- Role
- Founder / Lead Engineer
- When
- Apr 2026 – present
- Length
- 7 mo so far
- Status
- MVP
- Type
- AI, Mobile, Web
- Role
- Integration engineer
- When
- Delivered
- Length
- —
- Status
- Delivered
- Type
- Platform
The problem
Centralised the customer journey and operational data, reduced manual hand-offs and set up a documented AWS foundation.
Fashion-commerce recommendations usually optimise for another purchase without understanding what the customer already owns.
Integrated the installer management system into Multichoice's payment process so installers are paid accurately and on time.
What was built
Led architecture and hands-on engineering for an online booking platform: Python APIs and the AWS deployment architecture, integrated with Paystack, Sage Accounting, Zoho Bigin and Zoho SalesIQ.
Fashionly grounds recommendations in the user's wardrobe, builds outfits from existing items and recommends products only where a genuine wardrobe gap exists. Khanya, a LangGraph stylist with about 15 typed tools, handles wardrobe access, catalogue search, saved looks and human-stylist bookings.
—
Stack
- Python
- AWS
- Paystack
- Sage
- Zoho
- Next.js
- Kotlin
- Supabase
- LangGraph
- MongoDB
- SSE
- Payments integration
Highlights
- Python APIs and AWS deployment architecture
- Paystack, Sage Accounting, Zoho Bigin and Zoho SalesIQ integrations
- Khanya: a LangGraph tool-calling stylist with about 15 typed tools
- MongoDB-checkpointed conversation memory and SSE streaming of tool progress and grounded product cards
- Request-scoped Supabase clients with row-level security on every request
- Processed over R5 million in installer payments within six months
Infrastructure choices
- AWS
- Supabase with RLS
- MongoDB checkpoints
- SSE
—
Outcome
Centralised the customer journey and key operational data, reduced manual hand-offs and established a documented AWS foundation for future development.
A working end-to-end MVP across web and Android: wardrobe management, catalogue discovery, conversational styling, saved looks and human-stylist booking.
Over R5 million in installer payments processed within six months.