The record stays in Core. The work happens here.

Quote, rate, bind, manage clients and handle claims in an interface built for the people doing the work. Every transaction writes through to IHQ Core, your system of record. Your own instance, your own database, nothing shared with anyone else.

Book a walkthrough

Why this exists

Core was built to hold the record.
Not to run your Tuesday.

IHQ Core is where every policy, premium and payment is recorded, and that is exactly what it should be. The work around those records is a different job.

An underwriter pricing a risk, an operations lead moving a claim along, an account handler updating a client. None of them need the full depth of a core system to get through the day. Workbench is that day, running over the top of it.

Built and running today

What your team can do in it

Quote, rate and bind

Price new business and bind it. The policy writes to Core as a single transaction. It lands in both places or neither.

Client management

Client records sync both ways with Core. Update in either place and see it in both.

Product builder

Policy classes and lines of business sync from Core, so what you can sell matches what Core already knows.

Claims

Log, assess and progress claims, with claims data held in Workbench.

Accounting and ledgers

Trial balance, GL enquiry, AR and AP ledgers, without going back to Core to read them.

Documents and assistants

Generate policy documents. An underwriting assistant and a document summariser sit beside the work, not in a separate tool.

How it is run

Your data is not sitting in a shared database

Every Workbench customer gets their own application and their own database. Not one shared system with your records partitioned off inside it. Yours, on its own.

Nothing that happens in another insurer's data can reach yours, because there is no shared backend between customers for it to travel through. When your compliance team asks who else is in the database, the answer is nobody.

The obvious question

"We already have Core. Why do we need this?"

You are not adding a second system of record. Core keeps that job. Every financial and policy transaction still lands there and is still reconciled there. Workbench holds the screens your team works in, then hands the result to Core.

If you switched Workbench off tomorrow, your record would be intact and unaffected.

IHQ Core

Holds the record

Policies, premium, payments, reconciliation, trust accounting. The financial source of truth, unchanged.

Workbench

Holds the work

Quoting, binding and client updates, written back to Core. Claims handling and ledger views, worked on here.

Not built yet

What you cannot do in it

Endorsements, renewals and cancellations. In development, not shipped. Handle them in Core today.
Broker and client self-service portals. Prototypes, not production.
Payments integration. Not active.

We would rather you knew this before the demo than found it after.

Core holds the record. Workbench is where your team works in it.

Thirty minutes, your lines of business, a real quote bound through to Core.