Insurance domain architecture
Translating projects, pooled capital, isolated risk pockets, premiums, cover, professional roles, claims, and lifecycle states into a coherent model.
Insurance technology · 0 → 1
Building the programmable foundation for insurance to behave like software.
Product and platform engineering across customer journeys, insurance operations, serverless APIs, cloud infrastructure, and smart-contract execution.
- Client
- Nimblr
- Stage
- 0 → 1
- Status
- Completed
- Engagement
- March 2022 → May 2023
01 / Programmable insurance
Turning insurance workflows into product primitives.
Nimblr set out to rethink insurance as a connected software system—one where cover, risk capital, and claims could move through configurable workflows instead of disconnected paperwork and manual operations.
From March 2022 to May 2023, Incub8 helped translate that ambition into a coherent platform spanning insurance domain architecture, customer journeys, operational tools, versioned serverless APIs, cloud infrastructure, and programmable execution on Algorand.
02 / What we built
One engineering partner across product, platform, and protocol.
The engagement crossed the boundaries between an insurance product, a customer-facing financial experience, an operational platform, and a programmable transaction system.
Backend & API platform
Building versioned serverless services, schema validation, queryable operational records, network orchestration, and scheduled lifecycle jobs.
Smart-contract engineering
Implementing and evolving Algorand contracts for registries, projects, pools, pockets, cover, staking, rewards, and settlement operations.
Customer product journeys
Helping build wallet-connected flows for buying cover, allocating capital, monitoring positions, participating in claims, and receiving payouts.
Operations & administration
Creating tools to configure insurance products, review applications, manage claims, and inspect contracts, balances, and network state.
Cloud & delivery systems
Establishing environment-aware AWS infrastructure, authentication, storage, secrets, scheduled processing, CI/CD, and release workflows.
Platform evolution
Moving from the initial risk-pool architecture to a more modular v1.1 model without treating the first system design as permanent.
Verifiable certificates
Generating cover and stake certificates, anchoring their metadata, and coordinating transfer through customer-authorized wallet flows.
03 / The system boundaries
One action crossed insurance, capital, customer, and network state.
Buying cover, allocating capital, or receiving a claim payout was never a single transaction. Each journey crossed insurance rules, capital constraints, customer authorization, network confirmation, operational records, and a product experience that still had to feel understandable.
Those layers needed to agree even when a wallet signature was rejected, a network transaction was delayed, a cover expired, or the underlying insurance model changed. The difficult work lived in the seams between them.
Insurance rolesWallet authorizationOn-chain guaranteesOperational dataCapital constraintsLifecycle states
04 / Engineering judgment
Make the complexity explicit inside the system—not inside the experience.
Design the domain before the screens
Projects, pools, pockets, cover, stakes, and insurance roles remained explicit so multiple customer and operational experiences could share the same rules.
Split intent, signature, and confirmation
The platform prepared transactions, authorization stayed in the customer’s wallet, and completion was recorded only after the network confirmed the signed result.
Use the chain for guarantees, not every query
Smart-contract state was paired with a queryable operational model so product and administration screens did not need to reconstruct every view from network history.
Version the model instead of freezing it
The platform supported v1.0 and v1.1 while moving toward a modular registry, project, pool, pocket, cover, and stake architecture.
05 / Product system
Customers, operators, capital, and contracts in one platform.
The work connected human insurance workflows to programmable execution through a set of product, operational, platform, data, and delivery layers.
01Customer experience
Buy coverStake & earnPositionsClaimsWallet
02Insurance operations
ProductsApplicationsTermsProfessional rolesAssessmentsPayouts
03Platform services
Versioned APIsSchema validationAuthenticationTransaction orchestration
04Operational data
Queryable recordsAttachmentsStatus historiesGenerated certificates
05Programmable execution
RegistryProjectsPoolsRisk pocketsCoverStakes & rewards
06Cloud & delivery
AWS LambdaCognitoDocumentDBS3SecretsScheduled jobsCI/CD
06 / Product evolution
A foundation built for a product that kept evolving.
The result was more than a decentralized application. It was an extensible insurance product system connecting customers, operators, capital, contracts, and claims across several distinct product surfaces.
Nimblr has since evolved toward an AI-led experience for underwriting and claims. That later generation sits outside the engagement documented here, while many of the programmable insurance concepts established during our work remain visible in the product’s current direction.
EngagementMar 2022 → May 2023
Stage0 → 1
RelationshipProduct & platform partnership
Start a conversation / 05
Bring us the
hard part.
Tell us what you are trying to prove, build, or untangle. We will respond with useful questions—not a generic sales deck.
Discuss your producthello@incub8labs.com ↗