Compare
Joel Transport vs Pairly vs WDDNG
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) → WDDNG (Jan 2026 – present) → Pairly (Jul 2026 – present)
Swipe sideways to compare ›
Joel Transport ›
Online booking platform on AWS
Pairly ›
An AI-native operating system for founder-led teams
WDDNG ›
South Africa's wedding marketplace, with two apps on Google Play
At a glance
- Role
- Lead Engineer
- When
- Dec 2022 – May 2023
- Length
- 6 mo
- Status
- Live
- Type
- Web, Platform
- Role
- Founder / Lead Engineer
- When
- Jul 2026 – present
- Length
- 4 mo so far
- Status
- In progress
- Type
- AI, Web, Platform
- Role
- Founder / Full-stack & Mobile Engineer
- When
- Jan 2026 – present
- Length
- 10 mo so far
- Status
- Live
- Type
- AI, Mobile, Web
The problem
Centralised the customer journey and operational data, reduced manual hand-offs and set up a documented AWS foundation.
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.
South African couples plan across fragmented directories, WhatsApp messages and opaque “price on request” listings, while many international tools don't support local multi-ceremony wedding journeys.
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.
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.
A Next.js and Supabase marketplace with two Kotlin / Jetpack Compose Android apps on Google Play: one for couples, one for vendors. Thuli, the AI planner, is a LangGraph supervisor coordinating 16 specialist agents.
Stack
- Python
- AWS
- Paystack
- Sage
- Zoho
- Python
- FastAPI
- PostgreSQL
- Redis
- Next.js
- React
- Azure
- LangChain
- Docker
- Next.js
- Supabase
- PostgreSQL
- Kotlin
- Jetpack Compose
- LangGraph
- Zod
- Paystack
- Azure
- LangSmith
Highlights
- Python APIs and AWS deployment architecture
- Paystack, Sage Accounting, Zoho Bigin and Zoho SalesIQ integrations
- 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
- Two Kotlin / Jetpack Compose Android apps published on Google Play
- Thuli: a LangGraph supervisor coordinating 16 specialist agents through Zod-typed handoff tools
- Per-agent model selection, token metering and LangSmith tracing
- SSE streaming that renders vendor cards and progress during an answer
Infrastructure choices
- AWS
- PostgreSQL
- Supabase with PostgreSQL RLS
Outcome
Centralised the customer journey and key operational data, reduced manual hand-offs and established a documented AWS foundation for future development.
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.
The marketplace runs across web and two production Android apps, giving couples structured planning tools and vendors better-qualified enquiries with date, budget and guest-count context.