About Infer

Direct, by design.

Infer Analytics was built to solve financial risk problems by merging software engineering with risk management expertise. The people who scope the work are the people who do it. There is no delivery layer between you and the person writing the model or the code, and no account manager relaying your question to somebody you never meet.

The founder

Built from both sides of the problem.

Nathan Mwande

An engineer by training. His career began in software development and data analytics, building software designed specifically for analytics, and it was there that the idea behind the Infer platform started. He moved into clearing and settlement, working as a risk analyst at a tier two broker that had formerly operated as a prime brokerage, and then into credit risk underwriting and model development at the world’s largest commodities trading firm.

Software

Built and maintained in house, with configuration handled directly rather than through a change queue.

Risk services

Scoped and delivered into your environment or ours, on the tools your people already know.

Access

Direct. The person who answers the question is the person who built the answer.

Why we exist

The credit view and the commercial one shouldn’t be separate jobs.

Risk and relationship management spend too much of their time reconciling versions of the same counterparty: re-keying deposits between systems, working out chase dates by hand, and arguing about who is in arrears before they can discuss what to do about it. The fix is structural. Put the prospect, the client, the exposure, the deposit and the contact history on one record, automate the arithmetic between them, and enforce who can see what at the database rather than in the interface. Where a firm wants the method without the platform, that stands on its own too.

One record, not two lists

Everything we build is aimed at closing the gap between credit risk and relationship management: fewer hand-offs, less reconciliation, one shared picture of the counterparty.

Decided, not just displayed

A dashboard that shows a deficit is less useful than one that has already worked out the business days, the jurisdiction’s holidays, and who is due a chase today.

Tailored, not templated

Every deployment is scoped to the client’s desks, jurisdictions and systems, and configured around how their teams work, including the words they use for it.

Want to see how Infer fits your desk?

Book a walkthrough against your own counterparty workflow.