It's a question that comes up regularly when a lender is expanding — into a new geography, a new credit segment, a new vertical. You have an existing model. You're launching something new. Does the model come with you, or do you need to build something fresh? The honest answer, as with most modeling questions, is: it depends. But the dependencies are specific enough to be useful, and there's a logical path through them. What "New Product" Actually Means Before getting into th

A founder’s guide to the paths, tradeoffs, and decision points that matter There’s more than one way to launch a credit card. If you’re a fintech founder or early product lead exploring how to offer a credit product, you’ve likely discovered this already: there’s no single blueprint. Just a handful of viable paths each with their own infrastructure choices, regulatory implications, cost profiles, and long-term consequences. This post breaks down the core approaches, the real-

There are numerous benefits to owning your own UX infrastructure as a credit card lender. You have total control. You can test things without involving vendors — meaning you move on your own timeline. You can fully customize user flows and features, creating a truly differentiated product. If money were no object, we’d recommend it to just about everybody. But, of course, building your own UX infrastructure takes time and money. Lots of it. A white-label solution is faster an

We recently worked with a fintech trying to increase the profitability of their loan product. The obvious lever: price. Lower the interest rate, increase uptake. Raise the interest rate, increase the interest income, but volume takes a hit. Econ 101. So, this lender ran tests: increasing or decreasing the interest rate 100 bps for different groups. The results were underwhelming, with customers barely responding to the new interest rates. This puts the lender in a frustrating