Debt Freedom From Loan Apps

A clear debt inventory solves that. It forces you to write down every loan you took, how much you still owe, and how much each app expects from you each month. Then the Monthly Capacity Model tells you what you can pay without collapsing your rent, food, transport, and basic survival. No guessing. No wishful thinking.

If you do this properly, you also remove the mental noise. Kelechi, a ride-hailing worker (24 years old), told herself she would “just pay whatever she can.” That worked for a week, then she started missing payments because her month wasn’t built for random amounts. When she mapped her debts and matched them to her real monthly cash flow, she stopped reacting and started executing. That’s the difference this chapter brings: control and a plan you can stick to.

How It Works

The core technique is the Debt Map + Monthly Capacity Model. You will create a table that lists every loan from OPay, PalmPay, Branch, and similar loan apps. Then you will calculate your monthly payment capacity using your real income and real expenses, so your repayment plan becomes doable.

1. List every active loan and its current balance (Debt Map). Open each app, go to your loan/repayment section, and write down the remaining amount you owe for that specific loan. Do not mix loans together. If an app shows multiple loans, record each one separately so you can target them correctly.

2. Add the repayment requirement you see in the app (minimum or due amount). For each loan, write the due date and the amount the app expects you to pay (minimum payment, instalment, or due total-use the figure shown in the app). This matters because your strategy must match what the app will do if you miss.

3. Calculate your real “Monthly Capacity” (what you can pay without panic). Use your last 4 weeks of income to estimate your average monthly income, then subtract your non-negotiable monthly expenses. Your leftover is your capacity. If you don’t have stable income, you base it on your lowest or most conservative weeks.

4. Pick a repayment order that reduces damage first (your strategy). Use your Debt Map to decide which balance to attack first. A practical order is: clear any loan that threatens immediate penalties or stops service first, then attack the loan with the highest monthly pressure, then the next highest. You are aiming to prevent emergency spirals while still making progress every month.

Here’s a concrete example of what your Debt Map looks like. Copy this structure into your notes app or spreadsheet:

| App | Loan label (from app) | Current amount owed | Due date | Amount due this cycle | Notes (penalties/charges shown) | |---|---|---:|---|---:|---| | OPay | Loan A | 150,000 | 12 May | 15,000 | Shows “late fee” if missed | | PalmPay | Loan B | 90,000 | 20 May | 9,000 | Instalment only | | Branch | Loan C | 60,000 | 28 May | 12,000 | “Service fee” added on next cycle |

Notice how this forces clarity. Instead of “I have debt everywhere,” you get “OPay Loan A needs 15,000 by 12 May, PalmPay needs 9,000 by 20 May,” and so on.

Now you match that with your Monthly Capacity Model. Use this simple formula:

Monthly Capacity = Average monthly income − Non-negotiable monthly expenses − Safety buffer

The safety buffer is important. If you set your capacity as “everything left,” one small problem (car fault, sickness, low ride days) will wipe you out and you’ll miss payments. A buffer can be a fixed amount you choose, like 10,000, 20,000, or whatever fits your situation, as long as you keep it realistic and consistent.

Putting It Into Practice

Let’s run Kelechi’s situation as a practical walkthrough. She rides-hails for income, and her pay changes week to week. She knows she cannot plan repayments based on “best week” money. So she builds her numbers from her real pattern.

Step 1: Build the Debt Map for every loan app you use Kelechi opens OPay, PalmPay, and Branch and records each active loan separately.

She writes these details for each loan: - current amount owed - due date - amount due this cycle (minimum/instalment/due total shown) - any notes about late fees or charges shown in the app

Expected outcome: You finish with a table that looks like the one above, filled with real figures from your apps.

Step 2: Calculate your Monthly Capacity using your last 4 weeks Kelechi checks her income records (even if it’s just her bank statements or the ride-hailing earnings she can track). She totals income for the last 4 weeks, then divides by 4 to get an average monthly income.

Then she lists her non-negotiable expenses for the month: - food - rent or accommodation - transport to work - airtime/data you must pay - utilities or any fixed commitments - school fees (if any)

She subtracts these from her average monthly income.

Finally, she adds a safety buffer so she doesn’t get trapped. She decides a buffer she can keep even in a rough month.

Expected outcome: She gets a number she can pay without stress. Example structure (replace with your real numbers):

• Average monthly income: 220,000 - Non-negotiable expenses: 160,000 - Safety buffer: 15,000 - Monthly Capacity = 45,000

Step 3: Translate your capacity into a repayment plan for the next 30 days Now Kelechi compares her monthly capacity to the total due across all apps in the next cycle dates.

She checks her Debt Map and totals the amounts due within the next month. If her total due is higher than her capacity, she does not panic. She adjusts the order and payment allocation, but she stays within capacity.

A practical approach: - Pay enough to avoid immediate penalties on the most urgent due dates. - After that, put extra payments to reduce the biggest pressure loan first.

Expected outcome: You choose a payment schedule that fits your capacity and stops the “miss one payment, then everything becomes worse” pattern.

Step 4: Set “payment targets” per app and per cycle Kelechi writes a simple target list for the next month: 1) OPay due date payment amount 2) PalmPay due date payment amount 3) Branch due date payment amount 4) Any extra amount she will add to the loan she wants to clear first

If she has capacity for 45,000 and the due totals are, say, 36,000 across the month, she uses the remaining 9,000 as extra to the loan with the highest pressure or the earliest follow-up cycle.

Expected outcome: You know exactly what to pay on each due date, not “I will try.”

Step 5: Track one thing only: “Did I pay the target?” Kelechi doesn’t track 10 things. She tracks payment execution: - Did I pay the amount I planned on that due date? - Did the app show my balance reduced after payment? - Did any loan charge extra because of missed deadlines?

Expected outcome: You catch problems early, before they multiply.

Quick checklist - Write every active loan from OPay, PalmPay, Branch into your Debt Map with current balance and due date. - Record the amount due this cycle exactly as the app shows it. - Calculate Monthly Capacity using average income minus non-negotiable expenses minus a safety buffer. - Total the next 30 days due amounts and build a schedule that fits your capacity. - Pay on the due dates with a clear target per loan. - After payment, confirm the balance changed in the app.

One more thing: if your apps show different cycle dates, you still plan using the next 30 days. You don’t need perfect calendars. You need a realistic window you can control.

What to Watch For

Mixing loans and losing track If you combine balances like “OPay debt 240,000” without separating Loan A and Loan B, you will struggle to follow your repayment order. You might pay what looks like progress, but you could be reducing the wrong loan first. Do this: Record each loan separately in your Debt Map, including its due date and the amount due this cycle. Not this: Write one total for the whole app and assume any payment reduces the loan you want.

Setting Monthly Capacity too high Many people calculate capacity as “income minus expenses” and then forget that transport repairs, fuel changes, and low ride days happen. If you plan to pay everything you can, you will miss payments when life hits you. Missing payments then triggers extra charges and makes the plan harder. Do this: Add a safety buffer and base your income average on the last 4 weeks, not your best week. Not this: Use your highest earning week as your monthly income and pay the full leftover amount every month.

Ignoring due date pressure and paying the “easy” loan first Some loans feel smaller, so you pay them first. Meanwhile, another loan may be the one that triggers late fees, blocks new borrowing, or forces urgent instalments. That mistake makes you feel like you’re working, but you’re still losing the fight on the most dangerous balance. Do this: Use your Debt Map to prioritize urgent due dates and immediate pressure first, then attack the next highest pressure loan. Not this: Pay the smallest balance first if it has a later due date while another loan due sooner piles up charges.

When you finish your Debt Map + Monthly Capacity Model, you won’t just “know your debt.” You will control it. Next, you’ll use this same inventory to choose a repayment strategy that matches your real cash flow and prevents you from slipping back into the same cycle.

End of chapter one. 4 more chapters and about 8,961 words in the full book.