Compare
Pairly 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: Fashionly (Apr 2026 – present) → Pairly (Jul 2026 – present)
Swipe sideways to compare ›
Pairly ›
An AI-native operating system for founder-led teams
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
- Founder / Lead Engineer
- When
- Jul 2026 – present
- Length
- 4 mo so far
- Status
- In progress
- Type
- AI, 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
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.
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
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.
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
- FastAPI
- PostgreSQL
- Redis
- Next.js
- React
- Azure
- LangChain
- Docker
- Next.js
- Kotlin
- Supabase
- LangGraph
- MongoDB
- SSE
- Payments integration
Highlights
- 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
- 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
- PostgreSQL
- Supabase with RLS
- MongoDB checkpoints
- SSE
—
Outcome
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.
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.