Compare
Multichoice installer payments vs CaseNotes vs Fashionly
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: CaseNotes (Feb 2026 – present) → Fashionly (Apr 2026 – present)
Swipe sideways to compare ›
Multichoice installer payments ›
R5M+ paid to installers in the first six months
CaseNotes ›
South African legal research, e-discovery and learning, powered by AI
Fashionly ›
Your style, elevated: an AI stylist that starts with what you own
At a glance
- Role
- Integration engineer
- When
- Delivered
- Length
- —
- Status
- Delivered
- Type
- Platform
- Role
- Founder / Lead Engineer
- When
- Feb 2026 – present
- Length
- 9 mo so far
- Status
- Live
- Type
- AI, Web, Mobile
- Role
- Founder / Lead Engineer
- When
- Apr 2026 – present
- Length
- 7 mo so far
- Status
- MVP
- Type
- AI, Mobile, Web
The problem
Integrated the installer management system into Multichoice's payment process so installers are paid accurately and on time.
South African legal information is scattered across portals with limited keyword search, while international e-discovery platforms are often priced beyond the local market.
Fashion-commerce recommendations usually optimise for another purchase without understanding what the customer already owns.
What was built
—
An integrated research, e-discovery and learning platform: hybrid semantic search across more than 10,000 judgments, a precedent citation graph, structured document extraction, AI-assisted discovery and stateful research workflows.
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
- Payments integration
- Next.js
- FastAPI
- PostgreSQL
- pgvector
- Neo4j
- Redis/ARQ
- Azure OpenAI
- LangChain
- LangGraph
- Next.js
- Kotlin
- Supabase
- LangGraph
- MongoDB
- SSE
Highlights
- Processed over R5 million in installer payments within six months
- Five-stage Graph RAG pipeline in LangGraph
- Hybrid pgvector and Neo4j retrieval, and a TAR active-learning loop
- Human-in-the-loop tool-calling chat with PostgreSQL checkpoints
- MCP server for case search and drafting
- 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
Infrastructure choices
—
- pgvector + Neo4j
- Redis / ARQ workers
- LangGraph with PostgreSQL checkpoints
- Supabase with RLS
- MongoDB checkpoints
- SSE
Outcome
Over R5 million in installer payments processed within six months.
An integrated research and review platform grounded in more than 10,000 judgments, with a structured learning bank of 1,624 rubric-scored questions. The architecture supports resumable jobs, traceable sources and human review.
A working end-to-end MVP across web and Android: wardrobe management, catalogue discovery, conversational styling, saved looks and human-stylist booking.