Compare
Joel Transport vs Fashionly vs Pairly
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) → Fashionly (Apr 2026 – present) → Pairly (Jul 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
Pairly ›
An AI-native operating system for founder-led teams
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
- Founder / Lead Engineer
- When
- Jul 2026 – present
- Length
- 4 mo so far
- Status
- In progress
- Type
- AI, Web, 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.
Small teams stitch together disconnected tools for websites, customer communication, content, analytics and operations, while generic AI assistants lack safe access to business context and actions.
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.
Pairly gives each business one governed platform where specialised agents can work across those functions. It combines tenant-scoped AI agents, websites and CMS, CRM and communications, newsletters, analytics, integrations and a skills marketplace.
Stack
- Python
- AWS
- Paystack
- Sage
- Zoho
- Next.js
- Kotlin
- Supabase
- LangGraph
- MongoDB
- SSE
- Python
- FastAPI
- PostgreSQL
- Redis
- Next.js
- React
- Azure
- LangChain
- Docker
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
- Tenant-scoped agent runtime with durable memory, model routing, typed tools and permission ceilings
- Streaming agent UX with human approval gates, audit events and token budgets
- Installable skills marketplace with automated validation and human publication review
- End-to-end features spanning API, CMS, renderer, email and PDF output
Infrastructure choices
- AWS
- Supabase with RLS
- MongoDB checkpoints
- SSE
- PostgreSQL
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.
A broad working platform with multi-tenant permissions, real-time agent execution, publishing and revision workflows, provider integrations and installable skills, with approval gates, audit events and human review for consequential AI actions.