LifeStudio and LifeWorks · design and run
The people who own the process design the change. The platform runs it.
E-App
Why journeys
Every business outcome is a journey.
A journey is the approved sequence of people, decisions, information and systems required to complete an insurance outcome. It connects the people, information and capabilities required to deliver it.
An annuity application does not end at issue. Suitability and funding come before it. The first commission, anniversaries and retention all come after.
01
Recognize the need
An advisor, agent, partner or customer initiates.
02
Make the decision
Product, illustration, needs analysis or suitability, and application.
03
Issue and administer
Policy, billing, commissions and downstream systems.
04
Service and evolve
Service, changes, anniversary events and claims.
Design and run
Two components, one versioned definition.
Design · part of the platform
LifeStudio
Process and screen design
Lay out what happens, what people see, where it branches and where it waits. Promote through draft, test and production.
DRAFT → SIT → UAT → PRODUCTION
Run · part of the platform
LifeWorks
Governed runtime
Run the published version step by step. Call LifeBridge or carrier systems. Pause on an outside event and resume.
- START
- FORMApplication
- APILicense & appointment
- IGO?NEW
- RULESSuitability review
- EMAILNIGO requirements to producer
Experience steps
Form · Email · Messaging · Portal
System steps
API · Policy admin · Claims · CRM · Payments · Legacy
Logic steps
Rules · Decision
AI steps
Prompt · Agent
Drag a step in, and the journey is versioned, tested and effective-dated before it runs.
Approved now. Reaching the next person who starts.
The next person to begin the process gets the new version. Work in flight finishes on the version it started on, and rollback is re-approving the previous one.
AI inside the journey
The hard part is not the model. It is knowing where to put it.
Most carriers can reach a capable model. Far fewer can put one where the work actually happens. The process runs across systems the carrier does not control, each with its own runtime, and each now shipping its own agents and its own models. Embedding AI becomes a matter of asking every vendor for permission and accepting whatever each one provides.
In LifeStudio, AI is a step type in your journey, not a feature of someone else’s product. Drop it anywhere in the journey above, alongside the form, the API call and the rule.
Prompt node
A bounded question at one step. Summarise the submitted document, classify the request, pull the missing field. The answer is written to the case.
Agent node
A task with a defined scope and a defined set of tools. The agent works the step; the journey decides what it may touch and where a person takes over.
Model and agent agnostic
Choose the model or agent framework behind the step. Change it later without redesigning the journey around it.
An AI step is versioned, tested and approved like every other step, and it leaves the same evidence behind.
The process and the screens
The screens aren’t built. They’re rendered.
Most platforms model the process and leave the screens to a front-end team. Here the screens live inside the same versioned definition, and at every step, the portal renders the screen this person’s situation calls for. A process change is not a portal release. A new variation is not a new portal.
Sarah
Independent advisor · RILA · in good order
- FORMProduct detail: RILA terms
- FORMRider selection
- FORMReview & e-signature
● STRAIGHT THROUGH
David
Bank channel · FIA · suitability review
- FORMSuitability questionnaire
- FORMBest-interest comparison
- FORMPending review: what happens next
◆ ROUTED FOR REVIEW
The channel, the product and the state of the case decide the screens. The definition carries them all. Nobody built a bank-channel portal.
Authored once
The definition carries the screens: which components appear, in what order, with which labels, rules and behaviours, designed by the people who own the process.
Rendered per person
At each step, the portal asks the running journey what to show. Same version, different situation, different screen. No parallel portals, no wizard sprawl.
Changed by promotion
An approved change reaches the next person who starts, with no portal release. Rollback is re-approving the previous version.
Scenario-aware journeys
One journey. The right path for every scenario.
An address change looks simple until authority, admissibility, verification and jurisdiction each have a say. Rules decide which steps, evidence and referrals apply. Define the variation once instead of maintaining a separate journey for every combination.
| Step | OwnerTerm · same state | OwnerFIA · cross-state | LTC · representativeCross-state · care facility |
|---|---|---|---|
| 01 · STEPChange requested | Requested by the owner | Requested by the owner | Requested by the representative |
| 02 · RULEAuthority | Owner authenticated | Owner authenticated | Representative on file |
| 03 · RULEAdmissibility | Address admissible | Address admissible | Care facility flagged |
| 04 · RULEVerification tier | Standard tier | Elevated tier | Elevated tier |
| 05 · RULEJurisdiction impact | No change | State change applies | Reciprocity review |
| 06 · STEPComplete | Straight through | Completed with evidence | Referred |
| Outcome | STRAIGHT THROUGHAuthority is satisfied by authentication alone. The move stays in-state, so no additional evidence and no referral. | EVIDENCE REQUIREDThe cross-state move raised the verification tier and re-evaluated withholding and premium-tax parameters before completion. | REFERREDAuthority evidence is required for the representative, and LTC Partnership reciprocity referred the case to compliance. |
- 01 · STEPChange requestedRequested by the owner
- 02 · RULEAuthorityOwner authenticated
- 03 · RULEAdmissibilityAddress admissible
- 04 · RULEVerification tierStandard tier
- 05 · RULEJurisdiction impactNo change
- 06 · STEPCompleteStraight through
Outcome
STRAIGHT THROUGH
Authority is satisfied by authentication alone. The move stays in-state, so no additional evidence and no referral.
- Owner, Term · same state. 01 STEP Change requested: Requested by the owner. 02 RULE Authority: Owner authenticated. 03 RULE Admissibility: Address admissible. 04 RULE Verification tier: Standard tier. 05 RULE Jurisdiction impact: No change. 06 STEP Complete: Straight through. Outcome: Straight through. Authority is satisfied by authentication alone. The move stays in-state, so no additional evidence and no referral.
- Owner, FIA · cross-state. 01 STEP Change requested: Requested by the owner. 02 RULE Authority: Owner authenticated. 03 RULE Admissibility: Address admissible. 04 RULE Verification tier: Elevated tier. 05 RULE Jurisdiction impact: State change applies. 06 STEP Complete: Completed with evidence. Outcome: Evidence required. The cross-state move raised the verification tier and re-evaluated withholding and premium-tax parameters before completion.
- LTC · representative, Cross-state · care facility. 01 STEP Change requested: Requested by the representative. 02 RULE Authority: Representative on file. 03 RULE Admissibility: Care facility flagged. 04 RULE Verification tier: Elevated tier. 05 RULE Jurisdiction impact: Reciprocity review. 06 STEP Complete: Referred. Outcome: Referred. Authority evidence is required for the representative, and LTC Partnership reciprocity referred the case to compliance.
Three combinations shown. Requesting party, product, move type and destination jurisdiction each vary; every other combination runs on this same definition.
Design it with us
Bring one change you need to ship.
Go deeper: follow one journey the whole way · see the three experiences