Skip to content

Built for Canadian credit unions and lenders

Approve the borrowers a credit score misses.

Farmers, gig workers, newcomers and seasonal businesses look risky on a credit score. Berry reads their cash flow, explains every decision in plain language, and runs the loan through funding, collections and reconciliation.

Try the live demo

A portfolio project with fictional lenders. The live demo needs no sign-up and runs on synthetic data.

ONE APPLICANT · THREE RULEBOOKS

Hollis Family Farm

Grain farm, Saskatchewan · asking for a seasonal operating line

Deposits, last 12 months
Each reason is written twice: once for the borrower, once for the lending team.
Aspen BankPolicy-driven

Declined

No offer

Income CV 0.96 exceeds policy maximum 0.35.

KiteAutomated

$8,000

Business line of credit

Limit reduced to $8,000 from $60,000: 2x median monthly net cash flow.

Northgate Credit UnionRelationship

$60,000

Seasonal operating line

Seasonal: 65% of income in September to November. Peak-season surplus $189,035 covers the line 3.15x (minimum 1.15x). Assessed on annual cash flow.

Northgate, Kite and Aspen are sample rulebooks. Each lender's policy runs as settings, not code.Try 13 more applicants in the demo →

Four tools. One loan record.

Use them together, or start with the one that fixes the biggest bottleneck.

One system from application to ledger.

Replace the hand-offs between an origination tool, a payments file and a spreadsheet. Berry takes the loan from consent to the last reconciled payment.

Step 03 of 07

Three lenders read the same cash flow.

Each lender applies its own rules and explains the result in words a borrower can follow, along with what would change the answer.

What a lending team would work in every day.

Cash flow, the decision, its reasons and who needs to sign off, on one screen.

berry / workbench / hollis-family-farm

Hollis Family Farm

Grain farm · Saskatchewan · Business

Most income arrives at harvest, input costs land in spring, and the months between are quiet.

Income pattern
Seasonal
Months of history
12
Returned payments, 12 mo
0
Member since
2004
Products held
4
Cash flow, last 12 monthsInOut
Northgate decisionApproved

$60,000

Seasonal operating line · interest-only, repaid after peak season

  1. Most of your income arrives September to November. We've set the line up so you draw on it in quieter months and repay it from those sales.
  2. You've been a member for 22 years and hold 4 products with us.
  3. None of your payments bounced in the last year.
Needs branch manager sign-off. Above the lending officer's $50,000 authority.
Compare all three lenders

Nothing waits in an inbox.

Reviews, referrals, missed payments and reconciliation breaks each become a task with an owner and a deadline. The back office sees what's late before a member does.

Work queuesFeb 4, 2027, 09:05 (simulated) · 3 open · sorted by SLA
  • Fennick Hardware: returned PAD not appliedBreachedReconciliation breaks · M. Tran
  • Quillfeather Plumbing & Heating: stopped or refused debit2 business days leftCollections outreach · J. Okafor
  • Petalwick Florals: approve a 3-month deferral3 business days leftHardship approvals · R. Bisset
You prepared this override, so you can't approve it. A second person has to sign off. Your attempt is in the audit trail.

Time to funding, by rail

Simulated medians across 30 funded loans

AFT batch
23 hours
e-Transfer
20 minutes
Real-Time Rail (simulated)
10 seconds

The dashboard also tracks cure rate, delinquency, SLA attainment and cost per loan.

  • Maker-checker. Overrides and hardship approvals always need a second person.
  • Policy changes with a preview. “This change would have approved 4 more of the 51 applications in the demo.”
  • An audit trail you can't edit. Every decision, override and action, logged and exportable.
See the console in the demo
Concept

How it would plug in

Berry would sit between a lender's core banking system and its payments provider. It wouldn't replace either one, and the lender's team would keep the final say on every decision.

Core banking
Would take member and account data in and send booked loans out, by API or nightly file.
Applications
Could use Berry’s application flow, or take files from the origination tool a lender already has.
Bank data
Would start with uploaded statements, then use consent-based data feeds as the open banking framework goes live.
Payments
Would produce CPA 005 files for a lender’s clearing provider, plus Interac e-Transfer.
Sign-in
Could use single sign-on with a lender’s identity provider, with roles that match its approval authority.

Built for Canadian rules and rails.

Designed to cut custom work for compliance and payments teams. Each item links to the rule it follows and its current status.

Regulatory status, as of October 2026 →

Decisions you can check.

Rules, not guesses. Limits, prices and approvals come from tested code. The same file gets the same answer every time.

Blind to who you are. Name, age, gender, nationality and postal code are never used. A test shuffles them on every build to prove it.

AI drafts the memo. The engine and a human make the decision. Every figure in the draft is checked against the engine before anyone sees it.

Tested in public. Every release runs against a set of applicants with known right answers. See the results, including the misses →

How it's built

  • Synthetic data onlyYes
  • No personal data sent to AIYes
  • Append-only, hash-chained audit trailYes
  • Maker-checker on overrides and sign-offsYes
  • Deterministic, tested decisionsYes
  • Rate-limited AI routeYes
How decisions are made →
Concept

Find the good borrowers you're turning away. First findings in a week.

Berry is a portfolio project. This is how I'd run a pilot with a lender.

A 30-day shadow pilot on one product. No borrower is affected, and you finish with a go or no-go.

  1. Week 1Load your rulesYour limits, thresholds and approval authority, plus last year's declined and referred applications for one product.
  2. Week 2Find the missed approvalsRe-run those files on cash flow. See who your policy declined that could likely have repaid: seasonal businesses, gig workers, newcomers with thin files.
  3. Week 3Run in the shadowBerry decides alongside your team on new applications. Your staff still make every decision; nothing reaches the borrower.
  4. Week 4Decide with evidenceA short readout: approvals you're missing, the risk behind them, time saved per file, and a go or no-go for a live trial.

Common questions

About this project

Berry is a portfolio project by Joshua Osunbor: fictional lenders and synthetic data, with real, tested rules, ledger and operations console. Questions about how it works, or how it would run with a real lender? I'm happy to talk it through.