Compare
WhatsApp platforms vs Pairly vs ParcelNow
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: Platform
- Order: WhatsApp platforms (2018 – 2022) → ParcelNow (2025 – 2026) → Pairly (Jul 2026 – present)
Swipe sideways to compare ›
WhatsApp platforms ›
Altur, Harambee and eButler on the WhatsApp Business API
Pairly ›
An AI-native operating system for founder-led teams
ParcelNow ›
On-demand parcel delivery with real-time tracking
At a glance
- Role
- Lead engineer, Mmogo Media
- When
- 2018 – 2022
- Length
- 4 yr
- Status
- Delivered
- Type
- Platform, AI
- Role
- Founder / Lead Engineer
- When
- Jul 2026 – present
- Length
- 4 mo so far
- Status
- In progress
- Type
- AI, Web, Platform
- Role
- Technical lead, Smart Kitchen Co
- When
- 2025 – 2026
- Length
- 1 yr
- Status
- Delivered
- Type
- Web, Platform
The problem
A WhatsApp-based job platform (Altur), Harambee Youth Accelerator's move from a mobisite to WhatsApp, and eButler's WhatsApp ordering with payments through Flash.
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.
Customer and operations dashboards with backend services for parcel lifecycles, tracking events and notifications, built for high-throughput transactional workflows.
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.
—
Stack
- Python
- Django
- WhatsApp Business API
- Infobip
- Twilio
- Python
- FastAPI
- PostgreSQL
- Redis
- Next.js
- React
- Azure
- LangChain
- Docker
- Next.js
- FastAPI
- PostgreSQL
- Redis
- Docker
Highlights
- Conversational journeys on the WhatsApp Business API
- Payments via Flash, Paystack and MTN MoMo
- 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
- Next.js dashboards over FastAPI services
- Live delivery updates through logistics and messaging integrations
Infrastructure choices
—
- PostgreSQL
- Docker-based development and deployment standards
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.
—