Every policy, from first enquiry to issued.
KRISPTS tracks commercial insurance business end to end: enquiries, quotes, approvals, policies, endorsements and renewals, with the documents read for you, the premium rated, the SLA clock running and every step on the record.
- 3database engines: MySQL, PostgreSQL, Oracle
- 7built-in reports with CSV, Excel and PDF export
- 216automated tests, run on three databases
- 1audit trail, tamper-evident and exportable
One record from the first email to the renewal.
Each stage has its own rules, owner and clock. Pick a stage to see what KRISPTS does there.
Everything an underwriting desk reaches for.
Tap or press any tile to flip it and see what sits behind the headline.
Drop the broker's documents. Get a filled-in enquiry.
KRISPTS reads slips, commercial registrations and statements, including scanned and Arabic ones, and fills the enquiry form. Every value carries a confidence score, and weak ones are flagged for a person to check.
Uploaded documents
Extracted enquiry Ready to review
Example values. Confidence below 70% shows in amber so a person confirms it before the enquiry goes on.
Know what is late before the broker calls.
The dashboard uses the same SLA rules as the alerts and the reports, so every screen tells the same story.
SLA compliance by stage
Sample data for illustration.
Open pipeline
Sample data for illustration.
Premium written
AED thousand per month. Sample data for illustration.
Try the rating engine
A simplified model with the same building blocks: rate on sum insured, claims-experience adjustment, minimum premium, fee and VAT. Real rates come from your own rate card.
Premium breakdown
Illustrative figures in AED. Broker commission is shown for the broker, not added to the customer's premium.
Let an assistant create the enquiry for you.
KRISPTS speaks MCP and a plain REST API. Hand an assistant the broker's documents and it creates the enquiry, then reads the quote back. API keys are scoped, can expire, and are shown once.
Built for data you would not post publicly.
Customer files, financials and personal details pass through an underwriting desk every day. The defaults assume that.
Your database, your storage, your AI choice.
Database
MySQL, PostgreSQL or Oracle behind one schema. Migrations are tracked and a backup restores across engines.
Document storage
Keep files on local disk or point an administrator-configured S3 bucket at them, with in-browser preview.
Document reading
Use a hosted model, a local Ollama model that never leaves your network, or plain rules with no model at all.
Deployment
Run from source or with the included Docker setup. Branding, colours and logo change from Settings, no rebuild.
Things people ask first.
See your own business in KRISPTS.
Tell us your lines of business and approval rules and we will walk you through the workflow on sample data. Reach us at support@builtbykris.com.
Email support@builtbykris.com