Home / Technology / Architecture
What your team needs before they will say yes.
Written for a CTO and a procurement function, not for a brochure. Where something is not built yet, it says so.
Nine layers
| Layer | Responsibility | Status |
|---|---|---|
| Device and capture | Handset telematics, location, permissions, offline fallback | Pilot |
| Identity and consent | Household identity, granular consent records, withdrawal | Pilot |
| Household data | Members, vehicles, property, travel, policies, documents | Pilot |
| Scoring | Driving Score, Protection Score, confidence separation | Pilot |
| Decisioning | Trigger events, renewal engine, reason codes, silence rules | In build |
| Broking | Quote rail, panel, sale, issuance, adjustment, renewal | In build |
| Fulfilment | Assistance dispatch, provider network, case management | Pilot |
| Partner surfaces | Lead queues, sales desk, case oversight, configuration | In build |
| Reporting | KPI framework, partner reporting, portfolio views | Planned |
Integration surface
- Quote rail. REST integration to the partner’s rating service or panel aggregator. Where no API exists, a rated-table fallback is supported for pilot only.
- Policy issuance. Bind, document generation and delivery, with the issued policy written back to the vault.
- Assistance dispatch. Case creation into the partner’s existing dispatch and provider network, with status callbacks.
- Identity and SSO. Where the partner already holds the customer relationship.
- Reporting export. Scheduled extracts against the KPI framework.
Sandbox environments with synthetic households are provided before contract for technical evaluation.
Typical integration timeline
Technical discovery and sandbox access: 2 weeks
Quote rail integration: 0–0 weeks
Dispatch integration: 0–0 weeks
Configuration, branding and content: 2–3 weeks
Timelines depend heavily on the partner’s own API maturity and are confirmed after discovery rather than promised beforehand.
Telematics
Capture is handset-based. There is no hardware dependency and no vendor lock-in at the device layer — a deliberate decision, since a telematics hardware commitment is difficult to reverse and constrains market entry economics.
Where a partner has an existing telematics programme, scores can be ingested rather than re-derived. Where it does not, the platform derives its own. In both cases the partner’s rights in the derived score are contractual and explicit.
Sandbox access before commitment.
Your engineers should evaluate the APIs before your commercial team negotiates against them.