Small lenders and microfinance teams win on consistency more than on cleverness. The notes below are written for supervisors and operators who need steps they can teach, not slogans.
Price and fee rules that survive contact with reality
A ₱10,000 product can anchor a young book if the term, fees, and repayment cadence fit the borrower’s cash cycle. Price for sustainability, not only for marketing slogans.
When something fails, prefer a reversible correction with a note over a silent edit. Future you is part of the audit committee.
Practical checklist: name the owner, set the cutoff time, define the system of record, and decide what gets escalated versus fixed locally.
Fee configuration should be explicit: processing fees, late fees, penalty interest, and when each applies. Ambiguous fee rules create support tickets and borrower distrust.
Align branch managers and back-office on the same definitions of due, overdue, and written off. Shared language prevents fake urgency.
Store the policy where people work — beside the LMS screens — not only in a shared drive folder nobody opens during peak hours.
Pilot one product in one branch before you invent a catalog. Complexity multiplies support cost faster than it multiplies revenue for a small team.
If you use PesoLend or similar operational software, configure products and roles to mirror these policies so the screen matches the playbook.
Measure one leading indicator (same-day posting rate, KYC completeness before disbursement, or till variance) and one lagging indicator (PAR movement or ticket volume).
Leave spreadsheet debt before volume forces you
Startup lenders often outgrow spreadsheets at the worst moment: right when volume spikes and hiring is still messy. Plan the exit from spreadsheet debt before the spike, not during it.
Align branch managers and back-office on the same definitions of due, overdue, and written off. Shared language prevents fake urgency.
Write three examples: a clean repayment, a partial payment, and a reversal. If your process cannot handle those three, field staff will invent workarounds.
Pick day-one LMS features that match your actual volume: disbursement, repayment posting, basic arrears, and user roles. Advanced modules can wait until the core loop is clean.
If you use PesoLend or similar operational software, configure products and roles to mirror these policies so the screen matches the playbook.
Practical checklist: name the owner, set the cutoff time, define the system of record, and decide what gets escalated versus fixed locally.
Fundraising stories get stronger when you can show operational discipline — clean PAR trends, consistent receipting, and a month-end close that finishes on schedule. Investors notice process as much as growth charts.
Do not wait for a perfect data migration. Clean the next hundred accounts well, then expand the standard.
Store the policy where people work — beside the LMS screens — not only in a shared drive folder nobody opens during peak hours.
Report what supervisors can act on this week
Weekly reporting should answer three questions: are we collecting what we planned, where is risk rising, and which branches need help. Anything beyond that can wait for month-end unless a regulator or funder asks.
If you use PesoLend or similar operational software, configure products and roles to mirror these policies so the screen matches the playbook.
Measure one leading indicator (same-day posting rate, KYC completeness before disbursement, or till variance) and one lagging indicator (PAR movement or ticket volume).
PAR and arrears buckets only help if the definitions are stable. Decide whether interest and fees sit inside the overdue amount, how grace days work, and when a reschedule resets aging. Document those choices so two analysts cannot invent two truths.
Do not wait for a perfect data migration. Clean the next hundred accounts well, then expand the standard.
Write three examples: a clean repayment, a partial payment, and a reversal. If your process cannot handle those three, field staff will invent workarounds.
Controllers care about cash movement and liability accuracy. Loan officers care about who to visit. Build two views from the same ledger rather than two separate books. Parallel ledgers are how small teams lose weeks.
Applied to “How startup MFIs should price a ₱10k product,” this means writing the rule so a new hire can follow it without pinging the founder on chat.
Practical checklist: name the owner, set the cutoff time, define the system of record, and decide what gets escalated versus fixed locally.
Put the loan system inside the daily workflow
Loan management software for a small lender should reduce retyping, not create a second job of feeding the system. If officers update the LMS only at week’s end, the LMS is not yet part of the work.
Do not wait for a perfect data migration. Clean the next hundred accounts well, then expand the standard.
Store the policy where people work — beside the LMS screens — not only in a shared drive folder nobody opens during peak hours.
Role-based access, approval trails, and immutable receipt numbers matter more than fancy dashboards in the first year. Security basics protect both the institution and the people handling cash.
Applied to “How startup MFIs should price a ₱10k product,” this means writing the rule so a new hire can follow it without pinging the founder on chat.
Measure one leading indicator (same-day posting rate, KYC completeness before disbursement, or till variance) and one lagging indicator (PAR movement or ticket volume).
Train officers in the order of real work
Teach new loan officers the system in the same order they will work: onboard a borrower, book a loan, post a repayment, print a statement, escalate an exception. Abstract menu tours do not stick.
Applied to “How startup MFIs should price a ₱10k product,” this means writing the rule so a new hire can follow it without pinging the founder on chat.
Practical checklist: name the owner, set the cutoff time, define the system of record, and decide what gets escalated versus fixed locally.
One-week onboarding works when each day has a live task with a supervisor check. Shadowing alone is not enough; supervised doing is.
Teams searching for guidance on how startup mfis should price a ₱10k product usually need fewer tools and clearer ownership, not another dashboard nobody opens.
Store the policy where people work — beside the LMS screens — not only in a shared drive folder nobody opens during peak hours.
A week-one implementation sketch
Day 1–2: map how “How startup MFIs should price a ₱10k product” shows up in your current branch. Interview one cashier, one loan officer, and one supervisor. List the three moments where numbers disagree.
Day 3: pick a single system of record for that workflow. Freeze parallel spreadsheet updates for the pilot group even if the rest of the company still uses the old path.
Day 4: configure products, fees, roles, and receipt templates to match the written policy. Run five dry-run transactions with deliberate mistakes to test reversals.
Day 5: go live for a limited book. End the day with a till count, an aging export, and a short note on what confused people. Schedule coaching for Monday based on those notes.
Throughout the week, refuse scope creep. You are proving a rhythm, not launching every module you might need next year.
If you already use PesoLend, mirror the week-one sketch inside your sandbox or pilot branch settings so training screens match production habits.
Common failure modes to avoid
Definitions that change mid-month because someone wanted a prettier PAR chart. Change definitions on period boundaries with a written note.
Training that stops at login. Officers need supervised posting of ugly, real cases — partial pays, wrong borrower selected, then corrected.
Ignoring cashier feedback. Tellers see friction first; their notes are early warning for borrower experience problems.
Buying complexity to impress a funder. Show discipline with clean basics; sophistication can follow once the basics are dull and reliable.
Shadow systems that reopen the day after you “go live.” Assign an owner to shut them down and verify with a sample of accounts.
Closing thoughts
If your team can explain how cash, approvals, and arrears work without opening five files, you are ahead of most peers at a similar size. Keep documenting as you grow.
Keep this page handy when you next revisit How startup MFIs should price a ₱10k product. Re-read it after a month of real volume and strike anything that did not help. Living playbooks beat perfect documents that nobody updates.