JCOCredit Decision Engine Book a call

Credit policy as rules, not a spreadsheet.

Your written policy, running as rules your credit team edits. Every decision logged with its inputs, tuned each month by a CFA and FRM.

Book a 30-minute call Per month$2,500
  • Runs in your own Google Cloud
  • Your credit team edits the rules
  • Cancel any month
Scroll

Built for lenders like yours

Real engagements, anonymized. The same patterns this engine is built from.

Underwriting rules the board approved.

Outcome$5M funded
Built asPolicy as rules
New lender, inside its risk appetite framework

Cutoffs the credit team edits as CRM fields.

OutcomeBands and cutoffs
Built asConfig-driven scoring
Weighted score per offering, parameters in the CRM

Bureau file and bank data read into one score.

OutcomeBureau and bank feeds
Built asStructured intake
Equifax XML and Flinks JSON parsed, not retyped

The engine moved into the lender's own cloud.

OutcomeClient-owned project
Built asGCP migration
Risk model and intake in the client's own tenancy

The funded book checked, file by file.

OutcomeLoan tape analysis
Built asDefault analysis
Funded-to-revenue and payment-to-revenue per file

Threshold changes made under control.

OutcomeDated changes
Built asChange control
Thresholds in config, each change reviewed and recorded

Risk-based pricing inside the same policy.

OutcomePriced by band
Built asPricing engine
Rate and term set from the score, not by hand

Your policy, written.
Our engine, running it.

Month one runs in shadow mode beside your underwriters, on last month's files. From month two it runs unattended in your own project, tuned once a month.

Book a 30-minute call
Johnny Chen
Johnny Chen, CFA, FRM
CEO and Founder of JCO. Our team brings over a decade in finance and data, most of it in specialty finance.
Month one, then every month
  1. Hand us the written policy Your part The policy, the scorecard, one input: CRM, bureau or bank data. Week 1
  2. Policy becomes versioned rules Decision, band, reasons and a log ID on the CRM record. Week 2
  3. Replay last month's files Approved and declined re-run. Each disagreement explained. Week 3
  4. Shadow mode, then sign-off Your part Your underwriters decide, the engine logs its answer. You sign off. Week 4
  5. One parameter cycle a month Replay report, one credit-lead session, a dated config note. Monthly

What it takes

One policy
Written, single input
$2,500
A month, cancel any month
Your cloud
Runs in your Google Cloud

What the engine decides

Auto-approve in band
Decline reason codes
Offer size by revenue
Debt service floors
Balance and NSF rules
Exception routing
Monthly replay report
Decision log per file

Bring your policy.

Thirty minutes with our team. We work out whether your policy and data fit a rules engine. If they do not, you will hear that on the call.

Book a 30-minute call