Weekly retail audits. Check every store’s shelf, price and stock each week — with photo proof from every visit.
See the solutionSet it once, it runs on your schedule. Recurring verified work — capped, and every run is yours to approve.
Loops
- Weekly retail auditEvery Mon
- Vendor re-verifyMonthly
- Rider checksPaused
Loops / Weekly retail audit
Weekly retail audit
ActiveBudget cap · this month₦180k / ₦500k
Next run · proposedMon 12 Aug · ₦42k of your cap
Approve- Mon 5 Aug Verified
- Mon 29 Jul Verified
- Mon 22 Jul Verified
The problem
Staying up to date takes a full-time team. Hire the people, plan every round, chase the results — then do it all over again, with no end in sight.
Every check is the same grind — find and train people, plan the trips, and pull together what comes back. The work never stops, and neither does the cost.
Skip a round to save money and you’re flying blind — a shop closes, a rider quits, a vendor stops following the rules — and you find out too late.
Keep it current — without keeping a team. A Loop wires recurring verified checks into the systems and compliance files you already run — on your schedule.
You set it once
- Every Monday · 9:00
- Budget cap · ₦500k / month
- Every run you approve
hannu runs it, verified
- Week 32 Verified
- Week 31 Verified
- Week 30 Verified
on the ground · on schedule
Your systems stay current
- Compliance fileupdated
- Live dashboardsynced
- You’re alertedon any slip
Fits your compliance. Every run comes back as a signed record your auditors accept.
A live picture of your sector. You catch a change the week it happens, not at the next audit.
No team to run. No field staff to hire, no money moving without you.
Arm a Loop from your own stack. Set a cadence over the API and hannu drafts each run for your approval, dispatches verified operators on the ground, and posts the signed result straight back to your systems — every cadence, propose-only.
One governed loop, wired into your stack. On your cadence, the Loop drafts a run and waits for your approval; hannu dispatches verified operators, the hub checks and signs, and the result is posted straight back to your systems — then it repeats.
Scheduleevery Mon · 9:00
AOYaba · store 12on the groundBELekki · store 7on the groundCNIkeja · store 3on the groundDUV.I. · store 9on the ground
- Draft
- Approve
- Verify
- Sign
Your systemswebhook · notified
repeats every cadenceCapped, scheduled, and yours to stop. A Loop is a governed programme, not an autopilot — you stay in control of the money, the cadence, and every single run.
A budget cap you set.
Choose a cap and the Loop can never spend past it. You see what a run would cost before you approve.
Every run proposed first.
A Loop drafts each run and waits for your yes — nothing is funded or sent until you approve it.
Yours to pause or stop.
Change the cadence, hold the next run, or end it whenever you like — with a record of every decision.
Made for the checks you run again and again. Set each one up once as a Loop, then let it report back on your schedule.
Monthly vendor re-verification. Re-confirm your merchants still trade where they say, every month — not just once at sign-up.
See the solutionRecurring rider checks. Keep rider and bike checks up to date as your fleet changes, on the schedule you pick.
See the solutionOngoing field data. Collect the same prices, stock or sentiment on repeat — returned as one clean, comparable series.
See the solutionFrequently asked questions
Everything you need before you set up your first Loop.
No. A Loop drafts each run and proposes it to you — nothing is funded or dispatched until you approve. Loops run propose-only today, so a person is always in the loop before any money moves.
Every Loop carries a budget cap you set. Before you approve, you see the cap and exactly how much of it a proposed run would use — the Loop can never spend past it.
A workflow is one verified outcome, run once. A Loop wraps that same workflow in a schedule and a budget cap so it repeats on your cadence — the same checks, the same signed report, every run. See how workflows work for the building block.
Yes. A Loop is yours to pause or stop at any time. Pausing holds the next proposal; stopping ends the programme. Nothing is ever queued behind your back.
Never. Funds are escrow-locked with licensed partners only when you approve a run, and hannu custodies ₦0 — our records simply track every movement. Between runs, nothing of yours is held. See how escrow works for the full money story.
More resources
Docs
Set up a Loop over the API
Create and arm a Loop from the systems you already run — propose-only, no money moves without you.
GuideHow proof verification works
The full checklist behind every signed Verified report — and how to re-check it.
GuideHow escrow protects you
Your money waits safely in escrow and moves only when you approve a run.
Ready to get started?
Tell us the programme you need to run on repeat, and we’ll set up the Loop with you — capped, scheduled, and yours to approve. Start today, or talk to our team.