ClideyPolicies, claims and pricing that finally line up.
Underwriting, claims and finance each keep their own view of the policy. WhoDB connects policy and claims systems, models them once and keeps rating logic in functions your team can test.
1policy and claim model across teams
Testablerating and reserving logic
Every changedrafted and reviewed first
Privatedeployment inside your own cloud
IN THE PRODUCT
Rating logic, as a function you can check.
Pick a point on the left to see where it lives on the screen. Every screen shown here comes from the Clidey ERP demo project.
APP.WHODB.COM / APPS / CLAIMS-DESKDARK
HOW IT WORKS
From separate systems to one view of risk.
01
Connect policy and claimsConnect the policy admin, claims and billing systems in place.02
Model the policyDefine policy, claim and party entities with shared fields.03
Move rating into functionsRating and reserving rules live in code with reference cases.04
Give teams their toolsUnderwriters and claims handlers work in apps on the same records.RATING
Rating rules checked against known cases.
Reference cases sit next to the rating function, so every change is checked before it reaches a quote.
✓Reference cases kept with the logic✓Draft and promote for every change✓Output visible on every run
Reference checksRATING
CASEEXPECTEDRESULTSTATUS
Motor 001642.10642.10Pass
Motor 0021,105.801,105.80Pass
Home 001388.00388.00Pass
Home 002512.40512.40Pass
CLAIMS
Claims connected to the policy behind them.
Claims, policies and parties are related in the model, so a claim handler sees cover and history in one place.
✓Policy, claim and party entities✓Declared relationships between them✓Apps that read the shared model
Claims model5 NODES
ENTITY
ENTITY
ENTITY
FUNCTION
APP
What it changes for each team
UNDERWRITINGConsistent pricing.Every quote comes from the same tested rating logic.
CLAIMSCover at a glance.Policy terms and history beside every claim.
ACTUARIALData you can trust.Experience data traces back to the systems that produced it.
THE DETAILS
For the people who will ask.
The specifics your architects and security reviewers will want before a rollout.
SOURCESPolicy admin, claims, billing and files
LOGICPython functions with reference cases
MODELPolicy, claim and party entities
CHANGESDraft, review and promote
ACCESSProject members and roles
DEPLOYMENTManaged Private or WhoDB Cloud
EXAMPLE WORKFLOWOne
Rating function used by every channel.Brokers, direct and renewals all price from the same tested logic, so a rate change happens once.
Common questions
Yes. WhoDB connects to it in place and builds a shared model on top.
Keep exploring Industries
Industries overview →01Manufacturing→Testable pricing logic and quote records.02Retail→Allocation plans from your own rules.03Warehousing and distribution→Receiving, put away, picking and stock.04Banking→Customer, account and risk data in one model.05Accounting and finance→Close faster with reconciled, traceable numbers.06Logistics and transport→Shipments, fleet and capacity in one place.07Wholesale and trade→Orders from every channel in one model.08Energy and utilities→Assets, readings and work orders connected.09Healthcare operations→Capacity, supplies and staffing on shared data.