Problemas › Necesitamos un plan de negocios para el banco › Fintech
Un prestamista warehouse no busca ambición. Busca si el caso negativo aún permite servir la facilidad. Para las empresas de fintech, esto aparece en un lugar particular. Los números que llevan la respuesta son el blended take rate y el charge-off rate, y la complicación específica de esta industria es que el lending fija el P&L y convierte ingresos que valen un múltiplo de 7x en ingresos que valen un múltiplo de 2x. La versión general de este problema y la que realmente tiene tienen diferentes primeros movimientos.
Un prestamista warehouse no busca ambición. Busca si el caso negativo aún permite servir la facilidad. Para las empresas de fintech, esto aparece en un lugar particular. Los números que llevan la respuesta son el blended take rate y el charge-off rate, y la complicación específica de esta industria es que el lending fija el P&L y convierte ingresos que valen un múltiplo de 7x en ingresos que valen un múltiplo de 2x. La versión general de este problema y la que realmente tiene tienen diferentes primeros movimientos.
Los planes escritos para prestamistas warehouse fallan en lo mismo: un caso único optimista sin aritmética visible que vincule el blended take rate y el charge-off rate con el reembolso de la facilidad. El lector intenta establecer si le pagan si las cosas van moderadamente mal, y un plan con solo un buen caso no le da nada que probar.
Lo que sobrevive al escrutinio es un caso base con supuestos declarados sobre take rate, TPV, charge-off rate y contribution margin, un caso negativo que sea realmente malo y no solo reducido con cortesía, y una línea clara desde el desempeño operativo hasta el servicio de la deuda en ambos. El caso positivo importa menos.
El segundo fallo es la inconsistencia: una línea de TPV que no cuadra con el número de comercios, o CAC por canal que no se mueve con el ingreso neto. Los prestamistas leen estos documentos por oficio y encuentran esas fallas rápido.
Estos tres juntos son la firma. Uno solo suele indicar otra cosa.
✓ Necesita el documento para una fecha límite fijada por el proveedor de la facilidad warehouse
✓ Las proyecciones existen en una hoja de cálculo que nadie fuera de la empresa ha sometido a prueba de estrés contra el movimiento del charge-off rate
✓ No hay caso negativo, o es el caso base con el contribution margin mantenido plano
La acción que suele empeorarlo. Escribir el plan para que sea persuasivo en lugar de verificable en la reconciliación de take rate y TPV, que es la forma más rápida de perder a un lector que revisa por oficio.
It is for you if you run or finance a fintech and you need the document by a deadline set by someone else. 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 una fintech. It is a sample profile rather than a customer, and it is engine output translated from English — 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 · Pricing Strategy · 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 Business Plan Studio, one of 29 engagements the platform runs. For empresas de fintech 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. Lee un informe completo aquí if you would rather see the depth first.
Lo suficientemente corto para leerse y lo suficientemente completo para probarse. Los estados financieros y los supuestos detrás de ellos deciden; la narrativa más allá de lo necesario para explicarlos añade riesgo en lugar de confianza.
Si el flujo de caja sirve a la deuda bajo un caso que no es el bueno, y si los números cuadran internamente. Casi todo lo demás es contexto para esas dos cosas.
Ajuste al plazo de la facilidad, mensual para el primer año. El detalle más allá del horizonte del préstamo indica desconocimiento más que rigor.
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 · ไทย · हिन्दी · עברית