The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
A loan book with zero defaults is not a risk-free loan book.
Small cooperatives and new lenders often have no recorded defaults yet, so a standard model puts their risk at zero. Insurers, regulators and investors will not accept that number, and they are right not to.
For a 50-loan book with zero defaults, the 90% upper bound on probability of default sits between about 4.5% and 9%, depending on how correlated your borrowers are. The correlation assumption moves the answer more than the scorecard does.
I wrote this up as a short technical note with open, tested Python code, DOI 10.5281/zenodo.23864351.
If you run a small or young loan book and need a defensible PD, I can run the numbers for yours.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Project update: a safer way to move cards to "Paid" in a CRM
For a financial advisory firm, I built a feature in GoHighLevel that makes paying referral partners faster and harder to get wrong.
What it does: when a card is dragged to Paid, the system finds every other card due for the same partner and shows a checklist. The assistant ticks the cards to pay together and confirms once. With a single card, it asks a simple confirmation instead.
How I made it reliable: a small backend on Vercel re-checks every card before moving it (same partner, still due, only into Paid). A failed card is named in a message while the others still move. If the list can't be loaded, the plain question is asked, so nothing moves silently.
What I did: designed the flow, wrote the browser script and the backend, and tested the cases that go wrong, not only the happy path.
Tools: GoHighLevel, JavaScript, Node.js, Vercel, GitHub.:
Halden - Landing Page Concepts
Halden sells to grid operators, and there were two good ways to pitch it: tell them what's coming, or show them everything happening now. Rather than pick one on instinct, I designed the landing page as an A/B test so real traffic decides.
The two pages share one 12-column grid, the same section order, type system and components. Each variant changes only its message, its hero visual and its light color, so any difference in demo requests comes from the pitch and not the layout.
The work was building a system flexible enough to carry two different stories without either one feeling like the backup version.
Forecasting (act before demand spikes) vs metering (see and bill every kilowatt)
Primary metric: Demo requests from the hero CTA
4 voted
57%
3 voted
43%
7 votes
Closed
I'd pick Forecasting. "From meter reading to early action" tells a grid operator what they get in one line. Did you write both hero lines before designing the visuals?
Just shipped Sluice: a Framer template for open finance APIs.
Most fintech API sites open on a gradient and a promise. Sluice opens on a live console: a user picks a bank, approves access, and the accounts and webhooks arrive.
→ The consent moment plays out on a phone: pick a bank, share exactly what is needed
→ Every bank gets its own CMS page with ninety days of health, one bar per day
→ The Security page puts every grant on a consent ledger, and plays a revoke out live
→ Twelve endpoints, signed webhooks and code in Node, Python and cURL
17 pages, 6 CMS collections, 3 code components, a Start Here page in 13 steps and 6 Agent Skills.
$129, one-time. Remix link delivered instantly after checkout:
https://contra.com/products/VQDMPmng-sluice-framer-template-for-open-finance-ap-is
