Problems › Growing But Losing Money › Fintech
Growth that consumes cash is either an investment or a leak, and the arithmetic of take rate versus charge-off tells you which within one page. The version of this question that applies to fintech companies is not the generic one. Lending fixed the P&L and converts revenue worth a 7x multiple into revenue worth a 2x multiple — so an answer that ignores blended take rate will be confidently wrong. The analysis has to start from charge-off rate and contribution margin rather than from revenue.
Growth that consumes cash is either an investment or a leak, and the arithmetic of take rate versus charge-off tells you which within one page. The version of this question that applies to fintech companies is not the generic one. Lending fixed the P&L and converts revenue worth a 7x multiple into revenue worth a 2x multiple — so an answer that ignores blended take rate will be confidently wrong. The analysis has to start from charge-off rate and contribution margin rather than from revenue.
Growing TPV while posting losses is normal if each additional merchant eventually returns more in blended take rate than it costs after charge-offs. It is fatal if it does not, and the two look identical for as long as TPV continues to rise—which is why the failure is usually discovered when growth stops.
The test is per-merchant and it is simple: what does one more merchant cost to acquire by channel, what blended take rate does it generate after charge-offs, and over what period does contribution margin turn positive. If that is positive and the loss is fixed-cost absorption, growth solves it. If it is negative, growth accelerates the problem and every additional unit of TPV makes the position worse.
The second thing to check is warehouse facility draw. A business can show positive contribution margin per merchant and still run out of cash because advances or payouts leave weeks or months before settlement arrives—and the faster TPV grows, the wider that gap becomes.
These three together are the signature. One on its own usually points somewhere else.
✓ TPV rises while cash balance falls and the two movements are explained separately in the same review.
✓ Nobody can state contribution margin per merchant or per channel without launching a new project.
✓ Warehouse facility requests keep arriving earlier than the prior forecast assumed.
The move that usually makes it worse. Treating the loss as a scale problem when blended take rate net of charge-offs is already negative, which turns a fixable model into a larger one.
It is for you if you run or finance a fintech and revenue rises, cash falls, and the two are explained separately. It is the situation where the numbers are available but nobody has put them in an order that produces a decision.
It is not for you if Percision is the wrong tool if you already know the answer and only need execution capacity, or if the business is pre-revenue — then the constraint is evidence about the market, not analysis of your own figures. Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library. Also wrong if you need facilitation, politics, or someone to sit with a lender or buyer. Those are human jobs.
Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library.
Below is an excerpt from a real run of this analysis on a fintech. It is a sample profile rather than a customer, and it is unedited engine output — this is the format you get, on your own numbers.
The subject is Verrano Pay, a sample company profile used for testing rather than a customer — $84M net revenue, 28,000 merchants, $9.4B of payment volume.
Excerpt from a real Percision run · Cost Reduction & Efficiency · sample company profile
The move. Convert 18-24 month platform access into 30-36 month structural lock-in via exclusivity contracts and deeper API integration.
The leak it closes. Prevents 180-day exit clause activation that could remove 61% of new merchant flow overnight.
The assumption it rests on. Platform partners will accept 3-year exclusivity in exchange for deeper API features and revenue-share stability — the engine put the probability at 0.75.
| Investment required | $1.8-2.4M over 18 months |
| Expected return | 18-22× on $2.1M midpoint investment |
| Revenue, year 1 | $2-3M incremental from deeper integration (12-month lag) |
| Revenue, year 2 | $12-15M incremental from exclusivity-protected lending origination |
| Revenue, year 3 | $28-30M incremental from two new platform integrations |
| Exit criteria | Terminate if fewer than two platforms sign exclusivity by Month 18 OR if renegotiation windows do not materialize before December 31, 2026. Redirect resources to direct-acquisition diversification (Node 3) and lending covenant remediation. |
This is one move out of a full analysis. Read a complete report — every page, no email required.
This question routes to Proprietary EFF Methodology, one of 29 engagements the platform runs. For fintech companies it works through blended take rate, charge-off rate, contribution margin and CAC by channel, then produces the sequence rather than a list of options — which move first, what it funds, and the observation that would say the sequence is wrong.
You watch the analysis get built before paying anything. Read a complete report here if you would rather see the depth first.
Yes when the loss is fixed cost being absorbed and unit economics are positive. No when each additional customer loses money, which is a different situation wearing the same clothes.
Project the current unit economics at the volume you expect and see whether the line crosses. If it does not cross at a volume you can plausibly reach, growth is not the answer.
If unit economics are negative, yes and immediately. If they are positive and the constraint is working capital, the problem is financing rather than strategy and should be solved as such.
Materially, yes. Lending fixed the P&L and converts revenue worth a 7x multiple into revenue worth a 2x multiple — which changes both the diagnosis and the order of the fixes. The metrics that decide it here are blended take rate, charge-off rate, contribution margin, and an answer built on industry-general benchmarks will usually point at the wrong one first.
Less than most people expect. Your last twelve months of revenue and cost split the way you already split it, plus whatever you hold on blended take rate and charge-off rate. The analysis is explicit about what it is assuming where your data stops, which is more useful than waiting for numbers you may never have.
Percision is the wrong tool if you already know the answer and only need execution capacity, or if the business is pre-revenue — then the constraint is evidence about the market, not analysis of your own figures. Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library. Also wrong if you need facilitation, politics, or someone to sit with a lender or buyer. Those are human jobs.
Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library.
Describe the situation in your own words and we will tell you which analysis answers it — before you sign up for anything.
Describe my situation →Prefer to skip ahead? Go straight to the free diagnostic.
English · Español · Deutsch · Português · Français · Italiano · Nederlands · 日本語 · 한국어 · 中文 · Polski · Svenska · Türkçe · العربية · Tiếng Việt · ไทย · हिन्दी · עברית