Claims intake without a software project
A Policies folder, a Claims folder, and workflows between them — configured in the browser by the people who run the process, changed the day the process changes.
A claim, end to end
From incident to decision letter
The demo above is not a mock-up of someone else's product — it is the claim form this page describes, doing what claims do.
-
1 Intake
A public claim form collects the incident. Conditional fields keep it short; the engine computes an estimate from your rate bands as the server sees the answers.
-
2 Review
The claim lands in the Claims folder as Submitted, gets a reference number, and routing rules assign it. Reviewers see the computed estimate beside the submitted answers — two different things, stored separately.
-
3 Approval
Moving to Approved is a privilege-gated transition. The move generates the decision letter from your template, emails the policyholder, and can spawn a linked payout submission.
-
4 The record
Months later, the submission still carries the form version it was filled against, its audit trail, its documents and its figures. Disputes are settled by reading, not reconstructing.
The moving parts: the form builder, workflows and documents — each doing the same job it does for every other use case.
The broker channel
Partners raise business on your forms
A brokerage is not a login you hand out — it is an organisation of its own. Share the intake folder with each one and the whole channel works from the same forms, isolated by the database rather than by convention.
-
One intake, every brokerage
Publish a change once and every partner is on the new version at once — no emailed copies drifting out of date, no per-broker variants to reconcile.
-
Their book stays theirs
A brokerage submits through your form at submit level and its submissions belong to it; isolation is enforced by row-level security in PostgreSQL, and only you can change the form — cross-organisation edits are blocked by the database itself.
The full rules — access levels, what a recipient can and cannot do — are in the partner-sharing guide.
Questions
Insurance on Faldaro, plainly
Can policyholders submit claims without an account?
Yes — publish a public link for the claim form. The link is tokenised and revocable, throttled against runaway scripts, and never exposes your rating formulas or workflow to the person filling it in.
Can brokers or partner agencies use our forms?
Yes. Share a form or a whole folder with a partner organisation at submit level: they raise business through your forms, their submissions stay theirs, and only you can change the form.
What happens when a claim is disputed?
The record answers for itself: the submission keeps the exact form version it was filled against, every workflow move is in an append-only audit log, and every computed figure was produced by the server, not typed in.
Configure your claims process this week
No integration project, no vendor onboarding — a folder, a form and a workflow, built by the team that owns the process.
No card required.