Questions people ask before they subscribe

EasyFlow is a subscription platform for lenders and banks. Applicants work in a customer portal, your team works in a back office, and dashboards sit on top of the same live loan book.

The engine is already built. What we shape around you is the part that makes it yours: your structure, your calculations, your rules, and the regulator you answer to.

• The three modules
• How a workspace is set up

Lenders and banks: origination, servicing, and collections, with the checks a credit file depends on. That is the product we build and support every day.

• The three modules
• How a workspace is set up

No. EasyFlow sits around the lending workflow: origination, servicing, and collections. Your ledger or core can stay where it is. We connect to the services the workflow actually depends on — identity, bank data, signatures, payments, screening — rather than asking you to rip anything out.

• What we connect to

The platform, hosting, support, and every update we ship. Configuring the standard modules to your structure, calculations, workflows, decisioning, and rules is part of onboarding and is covered by the same fee.

You can pay monthly or annually. The annual rate is lower.

• How you pay

We still build custom features when a standard module genuinely cannot cover the case. That work is scoped with you and quoted separately, before anything starts. Nothing is charged by surprise, and configuration of what already exists is never rebranded as a project.

• What is quoted separately
• Why we stopped selling custom builds

Monthly billing has no lock-in beyond the current period. Annual billing is a year, which is how the lower rate is priced. If you leave, you get your data back in open formats — we would rather keep you because the system earns its place than because walking away would hurt.

Onboarding is configuration, not a build, so most teams are working in the system in weeks rather than a financial year. The clock starts after a fit review: we map your workflows against the standard modules and say plainly what works as it stands, what will be configured, and whether anything genuinely needs to be built.

The fastest path is one product or one segment, end to end, rather than modelling the whole book before anyone logs in.

• The four steps
• Guide: moving off spreadsheets

Write to us with the workflow you want to automate and the volume you run today. If we are confident we can help, you will hear back with clear next steps. If we are not, we will say so rather than sell you a subscription.

• Tell us about the workflow

Usually yes. The integrations are built to be configured around the providers you already have, or the ones we recommend if you do not. Running a primary and a fallback is worth it once volumes justify it — that is a conversation for the fit review, not a surprise after you sign.

• The integrations
• Guide: choosing providers

You choose the region. Client records stay under the rules that apply in your country, and you can export all of it whenever you ask. We treat the audit trail as a by-product of doing the work, not a log file assembled afterwards — who decided what, on which evidence, and when.

• Privacy Policy
• What an audit trail has to survive

Yes. If you have historical outcomes, the model is trained on your definition of a bad loan, not someone else's. If you do not, we agree the criteria explicitly, start from those rules, and retrain as real outcomes accumulate. A score is a recommendation with a band for human review — not a verdict the system is forbidden to explain.

• How model training works
• What a score should decide

You ask, and you get the data back in open formats: cases, documents, the trail. There is no hostage clause. The same export is available while you are still subscribed, so you can check that the promise holds before you ever need it.

• Terms of Use