Configured to your operation, not rebuilt for it
Products, rate tables, workflow rules, document templates, commission structures and roles are configuration on Regure rather than code. That is what lets two operations that look nothing like each other run on the same platform, and what turns a commission change or a new product from a development project into an operating request.
- RateBase rate · per $1,000 TIV0.3800.400
- DocSchedule template · clause 7rev 3rev 4
- RuleReferral threshold · limit$10.0M$12.5M
Every insurance buyer has been burned by the word “configurable”
It usually means one of two things, and both are expensive. Either the platform is genuinely rigid and every deviation from the vendor's model becomes a change request, a quote and a release cycle. Or it is so open that configuring it is really programming it, and the work lands on a systems integrator for a year.
The question worth asking a vendor is not whether the platform is configurable. It is: when our commission terms change in March, what exactly happens, who does it, and how long does it take?
On Regure the answer is that it is a configuration change: no new code, no release, no migration, and no deployment window to wait for.
Walk through your operating model
Bring the parts of your operation that no vendor has been able to fit — the commission structure, the tax treatment, the product that is not like the others. We will tell you which are configuration and which are not.
The things most platforms hardcode
None of the following is written into the platform. All of it is set up per operation, which is why a specialty programme can go live without a bespoke build sitting behind it.
Products and programmes
What you write, what each product asks for, what coverages and limits it carries, and which rules apply to it. Adding a product does not mean extending the data model.
Rating and rate tables
Rate tables are configured per product and versioned, so a rate change in March does not silently rewrite what a January quote was priced on. Regression tests run against captured rating baselines, so a rate change that moves an unrelated product is caught rather than discovered.
Workflow rules
Rules are trigger, condition and action. A trigger is an event on the record; conditions compare fields with the operators you would expect, including ranges, set membership and pattern matches; actions assign, change status, notify or annotate. Rules carry a priority and can be turned off without being deleted.
Documents and templates
Policy documents, slips, notes, closings and correspondence carry your layout and branding, in the languages the operation actually works in.
Commission and money terms
Commission structures, brokerage, tax treatment and invoicing terms follow the way your agreements are written rather than a fixed model you map onto.
Roles and authority
What each role can see and do, and the authority limits applied at the point of decision. Portal access for brokers and policyholders sits in the same model.
Changes that move at the speed of the business
Everything above is configured without changing application code. That configuration is managed as part of the Regure implementation and operating process, so a change is a request that gets actioned rather than a development project that gets scheduled.
No release, no migration
Products, rate tables, workflow rules, document templates, commission terms and roles all change without a deployment window. That is what keeps the operation inside the platform instead of drifting into spreadsheets the moment something needs to move quickly.
Configured with you, then supported
Our implementation team sets your configuration up alongside your operation and stays with it afterwards. When commission terms change in March or a new product launches in June, that is an operating request rather than a change-control exercise.
Your administrators run the day to day
Account, locale, display and organisation settings sit with your own administrators in the product, so routine operational control does not route through us.
| Change | Requires new application code? | How it is made |
|---|---|---|
| Account, locale, display and organisation settings | No | In the product, by your administrators |
| Rate table values and versions | No | Configuration, as part of the operating process |
| A new product or programme | No | Configuration, as part of the operating process |
| Workflow rules, authority limits, routing | No | Configuration, as part of the operating process |
| Document and correspondence templates | No | Configuration, as part of the operating process |
| Commission, brokerage and tax terms | No | Configuration, as part of the operating process |
| Enabling a module for your operation | No | Configuration, as part of the operating process |
| An integration to a system you run | Sometimes | Configured per deployment, scoped against the system and version you run |
Configuration changes carry the same audit trail as any other action — who changed a rate, a rule or an authority limit, and when — and sit behind role permissions. See audit trails and evidence.
Where configurability actually shows up in the work
Reinsurance broking
No lines of business, currencies, cedants, markets, commission rates or tax rules written into the platform, which is why two broking operations with opposite shapes run on the same code. See reinsurance operations.
MGAs and coverholders
Multi-capacity bordereaux templates, dual delegated-authority limits, and separate claims and underwriting authority modelled per operation. See MGA and coverholder software.
Specialty programmes
A programme whose product does not resemble anything else you write is a configuration exercise rather than a reason to be told the platform is not a fit. See policy administration.
What buyers ask about configuration
Does changing a workflow on Regure require developers?
No. Workflow rules are configuration — a trigger, a set of conditions comparing fields on the record, and actions that assign, change status, notify or annotate. Rules carry a priority and can be disabled without being deleted. No new code, no release and no migration is involved. Today our implementation team makes the change with you rather than you making it in the product yourself.
How are configuration changes made?
Account, locale, display and organisation settings are managed in the product by your own administrators. Products, rate tables, workflow rules, document templates and commission terms are configured without changing application code, and that configuration is managed as part of the Regure implementation and operating process — our team sets it up with you and maintains it alongside your operation, so a change is a request that gets actioned rather than a development project that gets scheduled.
How are rate changes handled?
Rate tables are configured per product and versioned, so a change does not rewrite the basis of quotes already written — a quote can be explained months later against the rates in force when it was priced. Rating regression tests run against captured baselines, so a change that moves an unrelated product is caught rather than discovered in production.
What is the difference between configuration and customisation here?
Configuration changes behaviour without new code, a release or a migration, and it covers products, rating, rules, documents, commissions, roles and templates — which is the great majority of what an operation needs to make the platform fit. Anything beyond that is scoped and quoted as product work, with a clear answer up front rather than a workaround.
Are configuration changes audited?
Yes. A change to a rate, a rule or an authority limit is recorded like any other action, with who made it and when, and configuration sits behind role permissions. In a configurable system a careless change reaches production faster than one that needed a release, which is exactly why it belongs on the audit trail.
Walk through your operating model
Bring the parts of your operation that no vendor has been able to fit. In a working session we will tell you which are configuration, which are integration and which are product work — before anyone writes a proposal.