Compare
Pairly vs Joel Transport 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: Web, Platform
- Order: Joel Transport (Dec 2022 – May 2023) → ParcelNow (2025 – 2026) → Pairly (Jul 2026 – present)
Swipe sideways to compare ›
Pairly ›
An AI-native operating system for founder-led teams
Joel Transport ›
Online booking platform on AWS
ParcelNow ›
On-demand parcel delivery with real-time tracking
At a glance
- Role
- Founder / Lead Engineer
- When
- Jul 2026 – present
- Length
- 4 mo so far
- Status
- In progress
- Type
- AI, Web, Platform
- Role
- Lead Engineer
- When
- Dec 2022 – May 2023
- Length
- 6 mo
- Status
- Live
- Type
- Web, Platform
- Role
- Technical lead, Smart Kitchen Co
- When
- 2025 – 2026
- Length
- 1 yr
- Status
- Delivered
- Type
- Web, 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.
Centralised the customer journey and operational data, reduced manual hand-offs and set up a documented AWS foundation.
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.
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.
—
Stack
- Python
- FastAPI
- PostgreSQL
- Redis
- Next.js
- React
- Azure
- LangChain
- Docker
- Python
- AWS
- Paystack
- Sage
- Zoho
- Next.js
- FastAPI
- PostgreSQL
- Redis
- Docker
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
- Python APIs and AWS deployment architecture
- Paystack, Sage Accounting, Zoho Bigin and Zoho SalesIQ integrations
- Next.js dashboards over FastAPI services
- Live delivery updates through logistics and messaging integrations
Infrastructure choices
- PostgreSQL
- AWS
- 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.
Centralised the customer journey and key operational data, reduced manual hand-offs and established a documented AWS foundation for future development.
—