The full catalog
Every workflow an insurer runs, in the order the company grows: the policy core first, then what feeds it, then what accounts for it, all on one foundation.
1 The policy core
Where a policy is written, kept, and kept lawful. The three products start here.
Underwriting & New Business
Should we take this risk, and on what terms? Value chain, starting with AiNOS Bind.
| Workflow | Today | AI-native |
|---|---|---|
| Submission intake | Applications, broker submissions and medical records arrive in mixed formats and are read and re-keyed by hand. | Every document is read and structured on arrival, with the missing facts listed before an underwriter opens the case. |
| Risk assessmentAiNOS Bind starts here | The underwriter assembles evidence from several systems and applies guidelines from memory and manuals. | An evidence-linked case workspace applies the approved guidelines, cites every material fact and surfaces conflicts, so the underwriter spends time on judgment. |
| Disclosure verification | Declared facts are taken at face value unless something looks wrong. | Declared facts are checked against available records, and discrepancies are shown with their source. |
| Referral and exception | Cases are referred up or to reinsurers with a note, and the reason is reconstructed later if asked. | Each referral carries the rule that triggered it and the evidence behind it, so the reviewer starts from the decision point. |
| Issuance QA | Contract wording and endorsements are checked by sampling after issue. | Every contract is checked against the approved terms and the underwriting decision before it is issued. |
| Guideline management | Rulebooks live in documents, are updated by committee and are applied differently by different underwriters. | Guidelines are versioned, testable logic. A change is tested against past cases before it is approved. |
Policy Servicing & In-force
Will the policy stay, and are we serving it right? Value chain, starting with AiNOS Keep.
| Workflow | Today | AI-native |
|---|---|---|
| Customer inquiries | Contact centre answers depend on which agent picks up and which screen they have open. | Answers are grounded in that customer's policy, its history and the rules that apply, with the source shown to the agent. |
| Policy transactions and notices | Changes, loans, surrenders and reinstatements are processed against rules the processor has to remember, including legally required notices. | Each transaction is checked against the contract and the notice obligations in force that day, and the notice is produced with the transaction. |
| Collection and lapse | Arrears are worked from a list, in order, after the grace period has started. | Lapse risk is scored as arrears begin, with the likely reason, so the outreach is specific and early. |
| Persistency and retentionAiNOS Keep starts here | Persistency is reported by cohort and channel. Deterioration is explained after the fact, and interventions are chosen by rule of thumb. | Deterioration is explained at the level of policy, agent and product, and candidate interventions are prioritized for a retention team to evaluate. |
| Customer lifetime value | Cross-sell is driven by campaigns rather than by what changed in the customer's life. | Changes in a customer's needs are detected from their own events, and any offer is checked for suitability before it is made. |
Risk, Compliance & Governance
Are we doing what the law and our own rules say, and can we show it? Control, starting with AiNOS Guard.
| Workflow | Today | AI-native |
|---|---|---|
| Regulatory change | Law and regulation changes are tracked in circulars and mapped to internal rules by hand. | Every version of every applicable law is kept, and a change is mapped to the internal rules and workflows it affects. |
| Internal rules and accountability map | Company rules drift from the law, and executive accountability maps are documents rather than something checked. | Internal rules are compiled against the law they implement, and each executive's duties are tracked against the controls that evidence them. |
| Sales conduct surveillanceAiNOS Guard starts here | Misconduct is found by sampling, complaints and regulator examinations, usually years after the sale. | Every contract and every agent is reviewed continuously against the rule in force at the time of sale, with each flag citing the clause and the evidence. |
| Advertising and material pre-review | Sales materials queue for a compliance reviewer and are checked against a checklist. | Materials are checked against the disclosure rules with each issue tied to the rule, and the reviewer decides. |
| Financial crime | Anti-money-laundering and sanctions alerts are high volume and low precision, and cases are built by hand. | Alerts arrive as cases with the linked evidence, and the analyst disposes of them with a recorded reason. |
| Complaints and consumer protection | Complaints are resolved one at a time and root causes are analysed quarterly, if at all. | Root causes are found across complaints as they arrive, and linked to the product, agent or process behind them. |
| Enterprise and model risk | Risk registers and model inventories are maintained in spreadsheets and reviewed on a cycle. | Operational and model risks are monitored from the systems that produce them, and the register updates from evidence. |
| Examination and reporting | A regulator's request triggers weeks of evidence gathering across departments. | The evidence packet for a request is assembled from the record, with each item traceable to its source and the rule it answers. |
| Internal audit | Audit tests a sample and extrapolates. | Audit tests the whole population continuously and spends its time on what the tests surface. |
| Third-party oversight | Outsourcing and agency partners are assessed annually by questionnaire. | Partner risk is assessed from their actual conduct, persistency and complaint record, continuously. |
2 What feeds it
The product a policy comes from, the channel that sells it, and the claim that tests it.
Distribution & Sales
Who sells it, and is it sold right the first time? Value chain.
| Workflow | Today | AI-native |
|---|---|---|
| Channel and partner management | Agency and partner performance is reviewed on volume, with operating risk and commission policy looked at separately or not at all. | Each channel partner has a live operating-risk and commission-policy profile built from its own contracts, persistency and complaint history. |
| Agent lifecycle | Appointment, licensing, training and termination checks run on paper and are hard to reconstruct later. | Every appointment, licence and termination decision carries its evidence, and gaps are flagged before the agent sells. |
| Needs analysis and proposal | Suitability depends on the individual agent's judgment and the product they know best. | Customer facts are matched to suitable products, with the reasons shown, so the agent recommends from the whole shelf. |
| Point-of-sale suitability | Replacement, comparison-notice and disclosure duties are checked after the sale, by sampling. | The duties are checked before the sale closes, against the customer's existing contracts and the rule in force that day. |
| Agent knowledge and support | Product and rule questions go to a help desk or to whoever the agent trusts. | Agents get answers that cite the product document or rule they came from, and the answer stays current as the documents change. |
| Incentive and compensation | Commission schemes are modelled once a year and their side effects on persistency and conduct show up later. | Commission and clawback scenarios are simulated against the actual book before a scheme changes. |
Product & Pricing
What should we sell, and at what price? Value chain.
| Workflow | Today | AI-native |
|---|---|---|
| Market and competitor sensing | Planners read competitor disclosures by hand and notice changes late, if at all. | Every competitor disclosure is diffed continuously, and each change is shown with the before and after wording and a view on what it means for our book. |
| Product design and basis documents | Terms, riders and policy wording are drafted in parallel and checked for consistency at the end, when it is expensive to fix. | Product rules are compiled into one structure, so wording, rider logic and basis documents are checked against each other as they are written. |
| Pricing and profit testing | Assumptions are set in spreadsheets with the supporting experience study attached somewhere else. | Every pricing assumption links to the experience evidence behind it, and a change in either is visible to the other. |
| Filing and regulatory approval | Filing packets are assembled by hand and regulator questions are answered from memory of past filings. | The packet is assembled against the current requirement corpus, and each regulator question is answered with the filing history and the rule it relates to. |
| Launch monitoring | Early sales mix and early experience are reviewed quarterly, after anti-selection has already happened. | Sales mix, early claims and early lapses are compared with the pricing assumptions from the first week, with the deviation explained. |
Claims
Is this covered, how much, and is it genuine? Value chain.
| Workflow | Today | AI-native |
|---|---|---|
| Intake and triage | Claims arrive with missing documents and are routed by queue, not by severity or complexity. | Completeness, severity and complexity are assessed on arrival, and the claim is routed with its missing-document list. |
| Coverage adjudication | The adjuster reads the policy, the claim file and the medical evidence separately and writes up the decision. | Claim facts are set against the policy terms in a cited decision brief, with the clauses, the evidence and the open questions in one place. |
| Fraud and investigation | Fraud is detected by rules and referred to investigators who rebuild the pattern by hand. | Patterns across claims, providers and agents are surfaced with the evidence that links them, and the investigator directs the inquiry. |
| Settlement and reserving | Payment accuracy, delay interest and case reserves are checked by sampling after the fact. | Every payment is checked against the decision and the contract, delay interest is computed from the record, and the case reserve updates with the file. |
| Disputes and appeals | Appeals, mediation and litigation responses are drafted from scratch each time. | The response is drafted from the claim file, the policy and prior comparable decisions, for a claims lawyer to finish. |
| Recovery | Subrogation and salvage opportunities are found when an adjuster happens to notice them. | Recovery opportunities are identified from the claim facts and tracked to closure. |
3 What accounts for it
Where every policy becomes a number the company has to stand behind.
Actuarial, Finance & Capital
Did the numbers do what we intended, and can we prove it? Balance sheet.
| Workflow | Today | AI-native |
|---|---|---|
| Experience studies and assumptions | Studies are run periodically and assumption changes are justified in a memo. | Each assumption carries a live trail to the experience behind it, and a change in experience shows which assumptions it touches. |
| Valuation and reserving | Movement analysis is produced after the close, and the explanation lives in an analyst's head. | Movements are explained step by step with the inputs that drove them, in a form an auditor can follow. |
| Capital and solvency | Capital scenarios are run on request and the narrative is written separately. | Scenarios and stress narratives are produced together, with the drivers of each capital movement shown. |
| Asset-liability management and hedging | Hedge effectiveness is reviewed at period end, and attribution is argued over. | Hedge results are attributed daily to the intended drivers, so the question is answered: did the hedge do what we meant it to? |
| Investments | Credit events and limit breaches are caught by periodic review. | Credit, concentration and limit monitoring runs continuously across the asset side with the evidence for each alert. |
| Reinsurance | Treaty structures are optimized at renewal and recoverables are reconciled by hand. | Treaty options are tested against the actual book, and recoverables are tracked claim by claim. |
| Planning and management reporting | KPIs are defined differently across teams, and an executive question takes a week of analyst time. | KPI definitions are compiled once and governed, and an executive question is answered from the governed data with its sources. |
AI-ready data foundation
Can the company read its own data, and can an AI act on it safely? Built as AiNOS One, by way of AiNOS Decode. How One works
| Workflow | Today | AI-native |
|---|---|---|
| Legacy data meaning recovery | Mainframe and legacy fields are understood by a few people, documented nowhere, and migrated by guesswork. | Field meaning is recovered from code, data patterns and expert interviews, with each recovered meaning tied to its evidence and a confidence level. |
| Insurance ontology | Each system has its own notion of policy, customer, agent, coverage and event, and reconciliation happens in spreadsheets. | One compiled model of the business: policies, parties, coverages, rules, events and decisions, with every instance resolved across systems and traced to its source row. |
| Versioned rules and law | Laws, regulations, internal rules and guidelines are documents in folders, and the version in force on a given date is reconstructed by hand. | Every source is captured from its original, compiled into controlling states and frozen per version, so any rule can be resolved as of any date. |
| Evidence linking | A number in a report cannot be traced to the row and the document that produced it without an analyst's week. | Every fact, flag and recommendation carries a link to the data row, the document page or the clause it came from. |
| Migration validation | Old and new systems are reconciled on totals, and the exceptions are negotiated at go-live. | Old and new are reconciled record by record, with each difference explained and classified before anyone signs off. |
| Institutional knowledge capture | Manuals, contracts and the judgment of experienced staff are scattered, outdated or about to walk out the door. | Manuals and contracts are compiled into queryable knowledge, and expert judgment is captured as rules and worked cases that can be tested. |
| AI governance | AI pilots run without a shared standard for what the model may see, do and claim, and nobody can audit a decision later. | Every AI workflow runs under the same controls: eligible evidence, applicable rules, allowed tools, validated outputs and human authorization, with a trace of each run. |
How the catalog stays clean
Each workflow has exactly one home. These rules decide it.
- The first line does the work. The second line watches it.
- Selling a policy belongs to Distribution. Reviewing how it was sold belongs to Risk, Compliance & Governance.
- Fraud lives in four places on purpose.
- Misrepresentation at application sits in Underwriting. Claims fraud sits in Claims. Sales misconduct and financial crime sit in Compliance.
- Complaints split by what they are about.
- Service inquiries sit in In-force. Claim disputes sit in Claims. Conduct complaints sit in Compliance.
- Pricing is Product. Valuation is Finance.
- Both are actuarial work, but they serve different decisions and different owners.
- Facultative referral is Underwriting. Treaty design is Finance.
- One is a decision about a risk. The other is a decision about the balance sheet.
- Data, technology and operations are drawn as the foundation.
- The eighth domain is what the other seven stand on, so it is drawn under them rather than beside them.