How Capcells works

One definition. Pricing, compliance, and every offer that follows.

Most lenders keep the math in one place, the rules in another, and the offer in a third. Capcells holds all three in a single product definition, so pricing, checks, and proposals cannot drift apart.

Image placeholderProduct overview: a lending product open in Capcells, with its schedule, its checks, and a drafted proposal side by side.

What Capcells does

Everything from one definition. Compute, check, and advise, in one place.

One definition feeds all threeCompliance built inAI assistant
01Compute

The exact cost of every loan, the same every time.

Capcells reads a product definition and produces the full schedule: principal, interest, fees, and taxes, down to the effective rate, with its working shown. No spreadsheet to reconcile, no rounding that drifts between systems.

  • Schedule, interest, fees, and taxes from one definition
  • Effective cost computed the way each market measures it
  • Every number traceable back to its input
02Check

Every product tested against the rules it has to follow.

Each market's rate caps, effective-cost method, and disclosure requirements are encoded once and checked on every product. A problem shows up as a failed check while you are still designing, not as a complaint months after launch.

  • Market rules encoded next to the product
  • Checks run on every change
  • Each result traced to its source in the regulation
03Advise

Better terms proposed, with a person always deciding.

The assistant reads your catalog and the rules, drafts a proposal, and shows the reasoning behind it. A person reviews, approves or rejects, and the system records who decided and why.

  • Proposals drafted from your catalog and the rules
  • The reasoning shown, never hidden
  • A person approves, and the decision is logged

Compliance, built in

Compliance is part of the product, not a review bolted on at the end.

Every definition is checked against the rules of the market it runs in, while you build it. A problem shows up as a failed check, not a complaint months later.

Checked against each market’s rules
The rules a product must follow are encoded next to the product, so the check runs on every change.
  • Per-market rate caps
  • The effective-cost method each market requires
  • Mandatory disclosures, in the form each market asks for
An audit trail of every check
Every check and every change is recorded, so you can show exactly what was tested, against which rule, and when.
Rules kept as versions
When a market moves a cap or a tax, you update that rule once and every product re-checks against the new version.

Data is handled under GDPR from Barcelona. We mark anything in progress as in progress, and claim no certification we have not earned.

The details, handled. So the work stays on the product, not the plumbing.

Versioned definitions

Every change becomes a new version, and the one before it stays exactly as it was.

What-if scenarios

Try a different rate or fee against real numbers before anything reaches a borrower.

Market rule updates

When a market changes a cap, update it in one place and every product re-checks.

Exportable offers

Hand your risk team an offer document with its schedule and working attached.

The AI assistant

Ask about one product or the whole catalog, and read the reasoning behind the answer.

Audit trail

See what was computed, what was checked, and who approved it, at any point in time.

Questions before you build

Each market's rules are encoded separately from your products, so a new country is a rule set we add, not a rebuild. Tell us where you operate and we will confirm coverage.

For the people who run lending.

If you run a lending business, build the systems behind one, or back companies this early, we want to hear from you.

Book a demo