One Mortgage System (OMS): broker software review

One Mortgage System, usually shortened to OMS, is a UK mortgage technology platform for intermediaries and lenders. Its public messaging concentrates on two things: reducing the amount of information that has to be entered more than once, and connecting to third-party services so that work happens in one place. It also emphasises support for a wider range of lending than standard residential — buy to let, bridging and second charge among them.

That combination makes it best reviewed as a workflow and integration platform rather than as a CRM in the narrow sense.

The problem it is built around

A single mortgage case can require the same client details to be presented to a sourcing tool, a criteria checker, an identity provider, a credit reference service, a valuation process, a lender portal and a protection quote engine. Every one of those is a small task. Collectively they are a job.

Rekeying is not just slow. It produces disagreement between records, which is the thing that actually causes trouble: a figure entered once as gross and once as net, an address that differs by a postcode, a date of birth typed from memory. Cleaning that up later costs more than entering it carefully would have.

A platform organised around entering data once is aiming squarely at that. Whether it succeeds for your firm depends entirely on which connections exist for the tools you use.

How to test an integration claim

Integration is the word doing the heaviest lifting in this category, and it hides a lot of variation. Do not accept the list; test one.

Pick the integration that would save you the most time and ask to watch it work on a live case, end to end, including what happens when the third party returns an error or nothing at all. Ask whether it is available today or planned, whether it costs extra, whether it requires your own account with that provider, and which side maintains it.

Then ask for the name of a customer using that specific connection in production, and ring them. Integration lists are compiled by marketing departments; production behaviour is known only to people relying on it on a Friday afternoon.

Specialist lending is the differentiator to probe

If your firm handles bridging, second charge, complex buy to let or portfolio landlords, spend most of the demo there. Those cases are where general-purpose broker software tends to strain: the data model assumes a residential purchase, the fields do not fit, and advisers end up using the notes box as a workaround.

Ask to see a bridging case and a second charge case captured properly, including the fields that only matter for those products, the documents they require and how the case is reported alongside your residential pipeline. If your specialist work is a meaningful share of revenue, this single test is worth more than the rest of the evaluation.

What else to have demonstrated

• Client and application data capture, and exactly how much is entered once.
• Case status, task ownership and what a stalled case looks like on a dashboard.
• Document handling and client communication.
• Customisation available for your own process, and who performs it.
• Reporting for managers and for compliance review.
• A real case moving through the system rather than a sequence of individual screens.

Counting what you would actually save

Before the commercial conversation, spend an hour producing your own number. Take five recent cases and mark, for each, every field a person typed that already existed somewhere else in your systems. Note roughly how long each round of entry took, including the checking afterwards.

That gives you a per-case figure. Multiply it by your monthly volume and you have the size of the prize, in your firm, for your case mix. It will usually be smaller than a vendor's illustration and larger than you assumed when you started counting.

Do the same exercise again three months after go-live. It is the only honest way to know whether the platform delivered, and it protects you from judging a decision on how the software felt rather than what it changed.

Who it tends to suit

Firms whose honest description of their main cost is repeated data entry across too many systems. Firms with a varied product mix that includes specialist lending. Teams that want a central workflow connected outwards to many providers rather than a closed environment.

It suits less well a firm whose priority is a polished consumer-facing journey, or one that has already standardised on a single supplier's ecosystem and is content there.

Practical checks

Ask how OMS sits alongside your network's requirements if you are an appointed representative, and alongside any packager or club relationships you rely on. Ask about submission routes to the lenders you use most, because that is where an integration gap is felt most sharply.

Confirm pricing, package contents, contract length and data export terms with OMS directly. Ask about implementation effort, migration of existing cases and what support looks like once you are live.

Bottom line

OMS is a strong shortlist option where duplicated data entry across multiple mortgage systems is the firm's central complaint, and particularly where specialist lending is part of the business. Its value stands or falls on whether the specific connections you need are live and dependable for the products you actually write. Test one of them properly before you sign anything.