CQUELLE Boutique Software Development Company

Ask before the rewrite.
InsurTech software development.

CQUELLE has not shipped an insurance core system. The two systems below come from adjacent sectors, both a .NET API on PostgreSQL, built by two developers and by three, and they are where these four questions for any insurance software development vendor, us included, came from.

Book the 30 minutes Read the four questions
Hamburg, since 2019Contract under German law
Vendor questions

What should an insurer's CTO ask a vendor?

Each question separates insurtech software development vendors who built for audit from those who built screens.

  1. Claims

    Can the system show who changed what on a claim from last spring, step by step, or only where it stands today?

    Storing only the current state answers the second question and fails the first. Ask to see one record's history, not a dashboard.

  2. Policy administration

    If several brands or partners share one system, what stops a query from returning another partner's policies?

    Role settings hide records on a screen; they do not stop a query that forgets its filter. Ask whether the separation is enforced at the data layer.

  3. Underwriting

    When the model is unsure, does it hand the case to an underwriter, or pick the nearest answer?

    A model that may only propose from your rules or abstain demos worse and defends far better. Ask who signs off a case below the threshold.

  4. Regulatory reporting

    Is the report built from the records your operators work in, or from a copy?

    A copy can disagree with the operational data, and then someone reconciles the two by hand. Ask where last quarter's numbers came from.

Adjacent work

The two systems we can show you

Where you should hire someone else

You need a vendor that has shipped an insurance core system.
We have not shipped a policy, claims or billing core. Look for a vendor that can show one in production and let you speak to that insurer's operations team.
You want a packaged policy platform configured.
That is work for the platform's own implementation partners. We build where the package stops.
You expect a team that already knows your regulator's forms.
We would learn your reporting obligations from your people and documents, and that takes time to plan for.

What we get asked about insurance work

Has CQUELLE built insurance software?
Not an insurance core system. What we can show you is adjacent: an audit-trailed categorization platform for a US financial advisory firm and a multi-tenant donation platform for a blood-donation operator. Insurtech software development is where we would bring that work.
What carries over from financial and health platforms to insurance?
Audit trails with a person and a timestamp on every change, tenant separation at the data-access layer that fails safe, and models that propose from the client's own rules or abstain and route the case to a person.
Which questions should we ask an insurtech software development vendor?
Whether a claim's history can be rebuilt from the log, whether partner separation is enforced at the data layer, whether an underwriting model may abstain, and whether regulatory reports come from operational records or from a copy.
Which stack would an insurance project run on?
Both adjacent systems here run a .NET API on PostgreSQL, with React or Next.js front ends. On an existing system we would start from the stack you already run.
How does insurtech software development with CQUELLE start?
With thirty minutes with the founder. Bring one workflow, a claim, a policy change or an underwriting case, and you leave with a view on whether it needs custom work and whether we are the right team for it.
A first conversation

Start with the questions, not with us

Thirty minutes with the founder, and one workflow your current system handles badly is enough to fill them. If your shortlist should include a vendor with an insurance core in its record, these four questions still work on them.

Put the four questions to us

Or describe it in the form, and expect a reply inside 48 hours.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.