All work stories
Anonymized case studyFintech / Digital financial services

Connecting payments, deposits and credit in one digital finance model

An early-stage digital financial platform was planning rapid customer growth across everyday accounts, payment-led segments, a merchant proposition and later credit products. The forecast needed to show how acquisition became retained activity—and how that activity changed revenue, service cost, credit exposure and cash.

Launch, product expansion and funding planningFinancial model
Fictional neighborhood finance hub connecting customer onboarding, everyday payments, merchant activity and separate reserve and credit operations.
Original concept illustration. No client data shown.
CONFIDENTIAL BY DESIGNWhy you won’t see the client workbook

Financial models contain pricing, salaries, conversion assumptions, funding plans and other sensitive data. I do not publish client workbooks, identifiable screenshots or proprietary inputs—especially where an NDA applies. This page uses an anonymized summary and original concept art to explain the business decision and my modeling approach.

Acquire → retainCustomer engine

Paid, organic and referral growth passes through churn before it becomes active product use.

Segment × activityProduct economics

Each customer and merchant group keeps its own usage, revenue, cost and margin logic.

Book → recoverCredit discipline

Disbursement, repeat use, recovery, classification, provision and funding stay connected.

Growth ↔ capitalFunding view

Operations, cash, financing and ownership reach the same decision timeline.

WHY THIS WASN’T A TEMPLATE EXERCISE

The model had to respect
how the business actually moved.

The linked architecture turns acquisition into retained and active users, assigns segment-specific transaction behavior and economics, builds merchant and consumer-credit portfolios separately, and reconciles everything through unit economics, statements, capital and valuation views.

01

Account growth was not the same thing as useful activity

Marketing, organic discovery and referrals could all add customers, but churn, card adoption and active use determined whether those registrations developed into recurring economics.

02

One platform contained several customer businesses

Everyday users, independent workers, household-transfer users and payroll-linked accounts could create different payment behavior and revenue. A single blended revenue-per-account assumption would hide those differences.

03

Deposits connected product use to balance-sheet choices

Average customer balances, the investable share and timing of deployment affected income and available resources differently from transaction fees, so deposits needed their own operating logic.

04

Merchant distribution created both volume and exposure

Sales capacity and signup productivity could enlarge merchant coverage, transaction activity and deposit float. If merchants also used financing, the same acquisition engine changed the credit book and its funding burden.

05

Credit revenue arrived with a full risk lifecycle

New and repeat borrowing, recovery, overdue balances, classification, provisioning, funding and administration all influenced the economics behind interest and interchange income.

06

Operating capacity had to grow with the network

Card issuance, payment processing, user technology, customer support, engineering, launch spending and capital expenditure could move on different bases and at different times from revenue.

MODEL ARCHITECTURE

From operating activity
to a decision-ready view.

Each layer has one job. Together they keep the commercial story, unit economics and cash consequences on the same timeline.

01

Calendar and control panel

A common monthly timeline carries launch timing, customer growth, product assumptions, tax and reporting periods into the operating schedules.

02

Acquisition and retention

Marketing spend and acquisition cost build paid customers alongside organic and referral sources, after which churn converts cumulative signups into retained users.

03

Customer mix and activity

Retained users divide into several payment-led segments, then into active cards, transaction frequency, payment value, transfers, payroll activity and bill use.

04

Payments and deposits

Commission, interchange, bill-payment and deposit-yield revenue remain visible by mechanism instead of being combined into one top-line growth rate.

05

Acquisition and service costs

Marketing, referral incentives, card issuance, withdrawals, processing and tiered user-technology costs follow the activity that creates them.

06

Merchant operating engine

Sales capacity creates merchant cohorts whose transactions, balances and financing choices feed revenue, onboarding, payroll, administration, provisioning and borrowing costs.

07

Consumer-credit portfolio

Eligible customers, new and repeat borrowing, tenor, recovery, classification, write-off and provisions form a distinct loan-book schedule before net income is calculated.

08

People and launch investment

Role-based staffing, pre-launch work, recurring overhead and capital expenditure place the delivery organization on the same monthly forecast.

09

Statements, capital and decisions

The operating model flows into integrated statements, unit economics, customer-acquisition cost, cash burn, break-even, funding rounds, ownership and valuation views.

WHAT THE ANALYSIS SURFACED

Useful answers,
without exposing client data.

The takeaways are intentionally qualitative. Exact assumptions, calculations and outputs remain inside the confidential client model.

Reconstructed insight

Retention only became valuable when it led to activity

A retained account could produce very different economics depending on whether it was used for payments, transfers, payroll, bills, deposits or credit. Growth therefore had to be traced beyond registrations.

Generalized project pattern

Product mix mattered as much as user count

Two plans with the same retained population could create different contribution when segment participation, transaction frequency, customer balances and cost-to-serve changed.

Reconstructed insight

Merchant growth could accelerate the risk balance sheet

Adding sales capacity did more than increase merchant transactions. When financing adoption rose with distribution, it also expanded exposure, provisions and borrowing needs.

Generalized project pattern

The headline credit yield was not the credit margin

Recovery, portfolio migration, write-offs, provisions, funding, administration and issuance costs all sat between quoted customer pricing and net contribution.

Reconstructed insight

Funding and ownership belonged beside the operating plan

Keeping operating cash, financing rounds and diluted ownership on one timeline made it possible to test whether the intended product rollout was supportable before relying on valuation outputs.

MODELING APPROACH

The working system
behind the answer.

  • Paid, organic and referral customer-acquisition schedule
  • Customer retention, churn, card-adoption and active-use engine
  • Segment-level payment, transfer, payroll, bill and deposit forecast
  • Commission, interchange, deposit-yield and service-revenue schedules
  • Customer acquisition, card, processing and tiered servicing costs
  • Merchant sales-capacity, transaction, deposit and financing model
  • Consumer-credit disbursement, recovery and portfolio-risk schedule
  • Role-based staffing, pre-launch, fixed-cost and capital-expenditure plan
  • Integrated income statement, cash flow and balance sheet
  • Unit economics, burn, break-even, capitalization and valuation outputs

CASE CONFIDENTIALITY

This anonymized case explains the customer-growth, payment, deposit, merchant, credit-risk, staffing, financing and unit-economics logic without naming the client, company, people, partners, payment networks, software, regulators, locations or dates. Exact customer, activity, pricing, deposit, merchant, credit, recovery, cost, staffing, funding, ownership, forecast and valuation assumptions remain private because client work can be confidential or NDA-protected. No workbook screenshot, chart, formula, file name, logo, product name, testimonial or identifying interface is reproduced. The source review was not a financial-model audit or accuracy certification. The illustration is an original fictional neighborhood finance ecosystem rather than a real company, app, service point, merchant network, operating result or client deliverable.

CUSTOM PROJECTS START AT $2,500 USD

Need a financial model?
Or the complete business package?

The final fee reflects the agreed scope, complexity and deliverables. Combined packages are quoted individually.