New errand
Pick up, confirm, deliver.
Yaba run01 / 04
Loading next workflow0%
Collect printed signage from Yaba by 2:00 PM.
Budget
N18,000
Deadline
Today
Required: proof of collection, live ETA, payment released after completion.
Operations, but calmer
Local errands,
without the messy follow-up.
Errands gives taskers and gofers one clear place to post work, track movement, protect payouts, and close the loop without turning every handoff into a flood of messages.
- Outcome
- 1 thread
- Outcome
- 0 guesswork
- Outcome
- Fast setup
for request, updates, and completion
when someone asks where things stand
for taskers, gofers, and repeat errands
Live movement
Every update stays visible.
- Task posted with location and deadline
- Gofer accepted and shared ETA
- Proof of completion attached before payout
Scenario loading
Protected payout
Release funds when the work is actually done.
Verification, ratings, and disputes stay in the same flow.
Why Errands
Built for teams that are tired of coordinating work in fragments.
The product is intentionally simple on the surface, but it handles the parts that usually create friction: unclear ownership, missing proof, payment anxiety, and too much back-and-forth.
What changes
Less checking in.
Taskers spend less time asking for updates. Gofers spend less time repeating themselves. Everyone spends less time guessing.
One place for the handoff
Post the brief, confirm who picked it up, and see what happened next without searching through chats.
Clear movement, not vague status
ETAs, completion proof, and live updates give everyone the same picture in real time.
Trust built into the workflow
Verification, payment release, ratings, and disputes work as part of the product instead of side conversations.
Workflow
Three moves from request to done.
Errands is designed around the actual handoff: assign the work, follow the movement, and close payment only when the task is complete.
Step 01
Post the task once
Add the brief, destination, deadline, and payout so the right person can move with context.
No more split instructions across chat, voice notes, and calls.
Step 02
Watch the handoff live
See who accepted, where the work is, and what has been confirmed without chasing updates.
Status changes, proof, and chat stay tied to the same errand thread.
Step 03
Close with confidence
Complete the task, release payout, leave ratings, and keep the history for the next repeat request.
Trust signals and record-keeping happen as part of the finish line.
Shared visibility
One errand thread replaces the usual pile of follow-up messages.
The result feels calmer because the product removes ambiguity. Each participant sees the same status, the same proof, and the same next step.
Trust Layer
The parts that usually break trust are built in.
Errands is not just a nicer request form. It also supports the safety, accountability, and record-keeping that make repeat local work actually scalable.
Identity and verification
Know who is taking the job before the handoff begins.
Protected payment release
Tie payout to progress and completion instead of a separate promise.
Native task chat
Keep decisions, clarifications, and proof attached to the errand itself.
Ratings after completion
Build a trust layer over time so repeat errands get easier.
FAQ
Questions teams usually ask before they switch.
Start with one errand
Replace scattered coordination with one clean workflow this week.
Create the request, track the handoff, protect the payout, and keep the record. That is the whole point.