Playbooks

Simple guides for the finance and operations problems that slow cash.

Each guide shows what is going wrong, what to check first, and what small fix to test before the problem gets bigger.

what is going wrong what to check first best small fix

Start the intake Review proof

Start pointOne real payment or workflow case, not a broad rebuild.

First-review outputsSummary, payment path picture, checklist, and open-case queue.

Trust postureNo invented ROI. No fake logos. Private records stay out of the first step.

Start here first

Choose the first problem to fix.

If you only need one place to start, pick the guide that sounds most like the problem already delaying payment, close, or collection.

Fastest first move

Missing proof of payment

Use this when money moved but the proof is still scattered across screenshots, emails, or different systems.

Best when Proof lands later than the payment itself.

First thing to review The files or screenshots people are using as payment proof.

First decision Decide how one clean payment proof step should work first.

Review the playbook See sample work

Best for close-week friction

Reconciliation problems at close

Use this when the same mismatch keeps coming back at close and nobody can show what needs to be fixed first.

Best when Close keeps revisiting the same unresolved variance.

First thing to review A list of the mismatches that keep coming back.

First decision Choose who will clear the backlog first.

Review the playbook Start the intake

Best for aging queues

Old debt that keeps aging

Use this when old debt keeps aging because follow-up is happening, but nobody can show what is actually moving.

Best when Work keeps aging because nobody owns the queue shape.

First thing to review The list of old balances, blocked value, and next action.

First decision Keep the first fix to one debt queue and one team.

Review the playbook See market pages

What lands first

What each guide helps you decide.

Use these guides to decide what is broken, what to check first, and what small fix should happen next.

Output 01

Name the problem clearly

Each guide turns vague frustration into a clear summary with one problem, one next decision, and one first fix.

Output 02

Pull the right evidence

The guide tells you which file, report, or queue to check before opinions take over.

Output 03

Keep the first fix small

Each guide keeps the first fix small enough to prove before anyone asks for a bigger project.

Library

Browse the full guide library once you know where to start.

Once you know which problem comes first, use the rest of the page to compare the other guides without getting lost in equal-sounding options.

Payment guide

Missing proof of payment

See what proof should be accepted, who checks it, and where it usually gets lost.

Failure to start: disputed receipts, scattered confirmations, and leadership updates built on screenshots.

First thing to review: the payment files and screenshots people are using as proof.

Best market signal: Nigeria and Kenya teams where payment proof moves faster than the close file.

Close guide

Reconciliation problems at close

The three variances that should never escape the week unresolved.

Failure to start: recurring mismatches nobody owns long enough to close cleanly.

First thing to review: the mismatches that keep coming back, ranked by age and size.

Best market signal: Africa and Asia teams carrying multi-entity reconciliation pressure.

Debt guide

Old debt that keeps aging

See how old debt keeps aging when follow-up is happening but nobody can show what is really moving.

Failure to start: arrears queues that keep aging while cash forecasts stay optimistic.

First thing to review: the list of old balances, next actions, and blocked value.

Best market signal: UAE and Nigeria pages where leadership reporting and collections timing collide.

Leakage guide

Repeating revenue leakage

Why the same break across four sites is one system problem, not four local ones.

Failure to start: branch-by-branch exceptions treated as isolated noise instead of one repeating signal.

First thing to review: the list of branches, repeated losses, and where they keep showing up.

Best market signal: Lagos, Ibadan, and Latin America pages where location drift hides in volume.

Order-to-cash guide

Delivery done, cash still missing

See where delivery is done but the billing, proof, or follow-up step still breaks.

Failure to start: delivered work that outruns clean billing, confirmation, or follow-up.

First thing to review: the steps from delivery to payment, showing where proof and responsibility split.

Best market signal: Port Harcourt and Mexico pages where delivery and collection split across teams.

Approval guide

Approvals stuck in hidden queues

Why approval mess gets faster, not better, when you automate too early.

Failure to start: approval chains nobody can explain until leadership asks why cash is still waiting.

First thing to review: the approval rules, thresholds, and dead-end steps.

Best market signal: Middle East, Abuja, and Kano teams where escalation quality changes deal speed.

Language guide

Teams using different words for the same task

Where multilingual finance operations break proof and exception handling.

Failure to start: the same queue explained three ways across finance, field, and leadership language.

First thing to review: the bilingual handoff sheet and the labels people use for the same issue.

Best market signal: Kano, Asia, and multi-country pages where language drift changes the process itself.

Rollout guide

Rolling one process out across many countries

How to keep one control standard while local language and market pressure shift.

Failure to start: one region copies the policy while every local team runs a different exception path.

First thing to review: the rollout summary showing what stays global, what changes locally, and what gets checked first.

Best market signal: Africa, Latin America, and Asia pages where expansion makes responsibility blur.

Pre-diagnostic check

Before you start the 45-minute review intake, know these three things.

Come in knowing which missing proof, unclear owner, or local rule is already costing you the most. That makes the first review faster and more useful.

Check 01

What proof is missing?

Name the file, screenshot, or report that should settle the argument but never arrives cleanly.

Check 02

Who should act next?

Call out the step where work stalls because nobody is clearly responsible for the next action.

Check 03

What local rule makes this harder?

Note the language, tax, branch, or company-structure issue that will make the same problem harder if you ignore it.

Next step

See examples before the meeting.

Review the sample documents, then bring the one process that already feels slow, messy, or risky.

Review proof Start the intake

Proof

Sample documents

See what the summary, process notes, and next-step plan look like before you engage.

Open page

How it works

How the review works

See how one problem gets narrowed into the first measurable fix.

Open page

Use cases

See all problem guides

Jump straight into the guide that sounds closest to your current problem.

Open page