Compare

Fashionly vs Joel Transport vs OrderEase

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
  • Both kinds of work: Web
  • Order: Joel Transport (Dec 2022 – May 2023) → OrderEase (2025 – 2026) → Fashionly (Apr 2026 – present)

Swipe sideways to compare ›

Fashionly ›

Your style, elevated: an AI stylist that starts with what you own

Joel Transport ›

Online booking platform on AWS

OrderEase ›

Branded online ordering for restaurants and retailers

At a glance

Role
Founder / Lead Engineer
When
Apr 2026 – present
Length
7 mo so far
Status
MVP
Type
AI, Mobile, Web
Role
Lead Engineer
When
Dec 2022 – May 2023
Length
6 mo
Status
Live
Type
Web, Platform
Role
Technical lead, Smart Kitchen Co
When
2025 – 2026
Length
1 yr
Status
Live
Type
Web, Platform

The problem

Fashion-commerce recommendations usually optimise for another purchase without understanding what the customer already owns.
Centralised the customer journey and operational data, reduced manual hand-offs and set up a documented AWS foundation.
Direct ordering and order management: menus, orders, payments and fulfilment, with automated order intake and status updates that cut merchants' operational overhead.

What was built

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.
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.
—

Stack

  • Next.js
  • Kotlin
  • Supabase
  • LangGraph
  • MongoDB
  • SSE
  • Python
  • AWS
  • Paystack
  • Sage
  • Zoho
  • Next.js
  • FastAPI
  • PostgreSQL
  • Redis

Highlights

  • 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
  • Python APIs and AWS deployment architecture
  • Paystack, Sage Accounting, Zoho Bigin and Zoho SalesIQ integrations
  • Fast, responsive ordering on Next.js
  • FastAPI services for menus, orders, payments and fulfilment

Infrastructure choices

  • Supabase with RLS
  • MongoDB checkpoints
  • SSE
  • AWS
—

Outcome

A working end-to-end MVP across web and Android: wardrobe management, catalogue discovery, conversational styling, saved looks and human-stylist booking.
Centralised the customer journey and key operational data, reduced manual hand-offs and established a documented AWS foundation for future development.
—