From policy wording to financial impact.
Explore how a synthetic prototype could combine a financial export, policy facts and a short risk questionnaire to illustrate modelled exposure, possible coverage questions and cash-flow impact. Production capabilities require pilot validation.
Built to help close the SME protection gap · All demo data is synthetic and clearly labelled
No install, no account, no upload · Precomputed synthetic scenarios · Fixture-supplied references.
Many SMEs struggle to connect exposure with policy wording
Small businesses may not have the time, data or specialist knowledge to connect their own numbers to their policy wording. So they don't know where an uninsured event — a cyber outage, a key supplier failing, property loss, or an interruption — would actually hurt, or how it would hit cash flow.
Built for the growing SME
The illustrative case is a synthetic Singapore digital-services SME (SGD) with two sites, a dominant cloud-hosting supplier and rising digital dependency — the kind of Southeast-Asian business that is exposed to cyber, supply-chain and business-interruption risk but has no in-house risk team. As it grows, its protection needs change; SBFinance re-runs the numbers whenever the data does.
Three inputs you already have
Financial export
The proposed protection workflow accepts CSV/XLSX inputs for revenue, expenses, cash, runway and supplier-concentration analysis.
Insurance policy PDF
The proposed workflow accepts a text-based policy and is designed to extract limits, sub-limits, deductibles and exclusions with source references. Extraction requires pilot validation.
Short risk questionnaire
A few fields (industry, digital dependency, key-supplier dependency, tolerable downtime, and any asset value you choose to enter).
Cyber, supply-chain, asset & business interruption
Cyber disruption
Cost of a selected outage = downtime × daily fixed-cost burden × activity affected + your recovery cost. No invented breach probabilities.
Supply-chain interruption
Spend-concentration signals plus an interruption scenario. We flag that high spend isn't automatically business-critical until you confirm it.
Asset / property loss
Uses the asset value you provide — never inferred from your expense transactions.
Business interruption
Days × daily revenue × contribution margin + unavoidable fixed costs, plus a user-set revenue-decline recovery window — shown against your cash buffer.
Review where complete-policy analysis may be needed
An illustrative example (synthetic Singapore SME, SGD). Statuses stay honest — under ambiguity we show a range, not a false number.
| Risk | Status | Modelled impact | Limit | Uncovered |
|---|---|---|---|---|
| Cyber | No matching text found | SGD 44,444 | Not found in reviewed text | Requires policy review |
| Supply-chain | No matching text found | SGD 48,944 | Not found in reviewed text | Requires policy review |
| Business interruption | Possible partial gap | SGD 54,444 | SGD 25,000 (sub-limit) | SGD 30,444 |
| Asset / property | Possible partial gap | SGD 250,000 | SGD 200,000 | SGD 52,500 |
No matching text is not a finding of zero coverage. Indicative only. Actual coverage depends on the full policy wording, endorsements, exclusions and the insurer's decision. Not a coverage determination.
How a loss hits your runway
The scenario engine provides precomputed synthetic results as you change downtime and the revenue-decline assumption, showing the selected scenario headline, runway and cash-gap date before and after the event. The risk-family matrix remains the labelled baseline assessment unless a selected scenario contains corresponding per-family results.
Review the inputs behind each result
The public fixture carries synthetic page and snippet references, but does not include the source policy, financial export or generator needed to verify extraction accuracy or derivations. A readiness index is withheld pending independent methodology review. Stated fixture fields and inferred interpretations remain separate.
Designed for local or private processing
The default desktop design processes supported files on-device or in an agreed private environment. Optional services may send data off-device and must be documented for each deployment. Document isolation, logging, redaction and deletion controls require validation for each build. This public demo is a synthetic, read-only illustration and does not upload financial exports or policy files.
What this is — and isn't
- Decision-support, not a broker, underwriter, claims handler or coverage determination.
- The proposed pilot is limited to text-based policy PDFs. Scanned-PDF detection and unreadable-document handling require validation before use.
- Loss figures are explicit user-selected "what-if" scenarios, not actuarial predictions or breach probabilities.
- Real-world extraction precision/recall is being measured on a first, synthetic benchmark; a broader real-policy corpus and SME/actuary review of the formulas are still to be done.
- No live insurer integration or protection-assessment API — a future pilot may evaluate a consent-gated, versioned JSON export.
- The proposed workflow should require a user-supplied exchange rate and date before combining currencies; this control requires pilot validation.
Seeking design partners to validate a proposed pilot workflow
A future pilot may validate a versioned protection-assessment JSON export, explicit consent, redaction options and an audit trail. These integration controls are proposed pilot scope, not a live insurer integration or production API. No insurer-specific endpoints are fabricated, and no affiliation with any insurer or programme is implied.
Frequently asked questions
Is this an insurance quote or a coverage decision?
No. It is indicative decision-support. Actual coverage depends on the full policy wording, endorsements, exclusions and the insurer's decision. Always verify with a qualified insurance professional.
Where does the analysis run?
The default desktop design uses on-device or agreed private processing. Optional services may send data off-device and must be documented for each deployment. This public browser demo is a synthetic, read-only illustration and does not accept file uploads.
What files are proposed for a pilot?
CSV/XLSX financial exports and text-based insurance-policy PDFs. Scanned-PDF detection and unreadable-document handling must be validated before use.
Do you estimate breach probabilities or asset values?
No. Loss scenarios are explicit "what if" calculations you control, and asset values are only ever the ones you enter — never inferred from your transactions.
Are the browser-demo numbers reproducible here?
The browser reads a versioned, precomputed synthetic fixture and does not calculate losses itself. The landing repository does not include the source export, policy or generator needed to independently regenerate that fixture.
Important notices
Results are indicative and for decision-support only. SBFinance is not a broker, underwriter, legal adviser, claims handler or authoritative coverage engine. Policy interpretation requires human verification; actual coverage depends on the full policy wording, endorsements, exclusions and the insurer's decision. Estimated losses are scenarios, not actuarial predictions. SBFinance does not recommend or sell a specific insurance product. Consult a qualified insurance professional before purchasing, changing or relying on coverage. All examples on this page use synthetic data and an illustrative policy.
Run the Protection Gap demo
The interactive browser demo loads a synthetic SME, an illustrative SGD policy and a risk profile, then shows the full assessment — with sliders to change the disruption scenario. It runs entirely in your browser and is driven by a precomputed synthetic fixture. Fixture generation is outside this public landing repository. For your own data, request a scoped private workflow.