01
Errand creation
Clients can describe the task they need completed and submit an errand through the platform.
Wanky flagship product
Errands, organised.Execution, connected.
ERS — the Errand Runner System — is a logistics marketplace designed to connect people who need errands completed with runners who can carry them out. We are building for the practical realities of getting things done in Lagos, Nigeria.
Product availability and individual capabilities may vary while release validation and testing continue.
ERS / WORKFLOW
From request to completion
01. Client posts an errand
The task enters the marketplace workflow.
02. Runner accepts
One active errand per runner.
03. Coordinate the task
In-app communication supports coordination.
04. Complete the errand
Completion and payment follow the implemented workflow.
Conceptual product workflow. This diagram is illustrative, not a live transaction or operational-status feed.
Product capabilities
Designed around the errand lifecycle.
ERS brings the key participants and steps of an errand into one product. The capabilities below describe the product design; individual features remain subject to implementation and release verification.
02
Runner workflow
Runners participate in the marketplace, with the operating rule that a runner can handle one active errand at a time.
03
In-app communication
The product is designed for client–runner communication through in-app chat and audio calling.
04
Payment and escrow
The payment flow is designed around holding funds through the errand lifecycle and releasing them according to the applicable completion rules.
Engineering foundation
Built in layers. Developed with intent.
ERS is being developed with a mobile client, a typed backend, managed identity and data services, and supporting infrastructure. The architecture is intended to keep product responsibilities clear as the marketplace evolves.
Security and access controls must be verified in the running product. Wanky Protect is the planned shared protection layer for the wider Wanky ecosystem.
Mobile application
Expo and React Native
API and business logic
Node.js, Express and TypeScript
Identity and data
Supabase and PostgreSQL
Payments
Paystack integration planned
Architecture overview, not a service-availability guarantee. Paystack integration is planned and should not be interpreted as confirmation that production payments are active.
The road ahead
Validate the core. Improve from real use.
The immediate priority is to validate the core marketplace on real devices, resolve release issues, and establish a dependable foundation before expanding the product scope.