No shared lifecycle model
Each vertical builds its own concept of "active," "lapsed," and "at risk." There is no cross-vertical signal when the same relationship is deteriorating across multiple touchpoints.
Aegis Retain
The continuity engine behind relationships that renew.
Retain powers the lifecycle layer for recurring relationships across the platform — memberships, renewals, onboarding, retention, reactivation, reimbursement-support workflows, and relationship analytics.
Cross-vertical lifecycle
Renewal & reactivation queues
Human-reviewed next actions
Packet & document state
AEGIS / RETAIN VIEW
In design
Lifecycle state
Active
Renewal queue
42 upcoming
At-risk relationships
9 flagged
Reactivation tasks
14 open
Packet / document state
18 ready
Next best action
Human review
The first transaction is the easy part.
Renewals discovered too late
Upcoming renewals, expiring agreements, and lapsing memberships surface reactively — after the relationship has already drifted. No queue, no cadence, no follow-up routing.
Packet and document state lost
Reimbursement packets, onboarding documents, and agreement state live in disconnected systems. No single view of what is ready, what is pending, and what is blocking a relationship from progressing.
The Retain model
Shared lifecycle infrastructure for every vertical.
Retain turns relationship lifecycle into shared platform infrastructure. Each vertical gets a common way to model stages, commitments, renewals, retention risk, reactivation, and packet state — without rebuilding that logic inside every product.
Lifecycle state tracking
Every relationship has a named stage and a set of lifecycle events. Retain tracks what happened, when, and what should happen next — across inquiry, agreement, onboarding, renewal, and reactivation.
Renewal and reactivation queues
Operators see what is coming due, what is at risk, what has lapsed, and what is ready for reactivation outreach — before the relationship disappears. Queues are actionable, not informational.
Operator-reviewed next actions
Retain surfaces signals — at-risk flags, follow-up tasks, packet readiness, next-best-action prompts — for operators to act on. Automation supports the workflow; humans confirm the decision.
Platform capability scope
What Retain powers.
Membership lifecycle
Model recurring memberships from inquiry through agreement, payment, onboarding, active membership, and renewal. Track stage, commitment, and continuity obligations in one place.
Renewal management
Surface upcoming renewals before they lapse. Track agreement expiry, renewal cadences, and operator-managed renewal queues without hardcoding any vertical's timeline.
Reactivation workflows
When a relationship lapses, Retain tracks the reactivation task queue, outreach state, and recovery momentum — so operators know what needs human follow-up today.
Retention signals
Flag at-risk relationships before they disengage. Retain tracks lifecycle signals — engagement gaps, payment anomalies, stage stalls — and surfaces them as operator-actionable alerts.
Packet and document state
Track reimbursement packets, onboarding documents, and agreement state without owning the document engine. Retain knows what is ready, pending, blocked, or waiting for human confirmation.
Lifecycle analytics
Emit relationship-lifecycle events to Sentinel. Track active, upcoming renewal, at-risk, renewed, lapsed, and reactivated cohorts. Lifecycle bottleneck reporting across verticals.
Payment and agreement continuity
Track the continuity state around payment and documentation workflows — what is active, due, delayed, or ready. Retain does not own payment processing; it tracks the continuity around it.
Human follow-up routing
Generate and route follow-up tasks to the right operator. Track task state, assignment, and outcome. Retain creates queues; operators work them.
Bridge workspace contribution
Contribute continuity workspaces, lifecycle queues, and relationship-level signals to Bridge — the operator cockpit. Operators see the Retain view alongside their other module-contributed workspaces.
Platform relationships
How Retain sits in the platform.
Retain is the continuity layer. It does not replace the document engine, the billing engine, or the analytics layer. It wraps around all of them to keep the relationship moving.
Retain + Bridge
Bridge is the operator cockpit.
Retain contributes the continuity workspaces, queues, lifecycle state, and relationship-level signals that operators act on. The renewal queue, the at-risk list, the reactivation tasks, and the packet-state panel all surface inside Bridge.
Bridge
Retain + Sentinel
Sentinel analyzes governed operational data.
Retain supplies relationship-lifecycle events and retention signals that Sentinel turns into analytics, risk scoring, and next-best-action intelligence. Retain emits; Sentinel interprets. AI suggestions remain operator-reviewed.
Sentinel
Retain + DocRadar
DocRadar moves the document work.
DocRadar moves document work through detection, classification, extraction, and human confirmation. Retain keeps the relationship-level lifecycle moving around that work: packet state, renewal state, follow-up state, and continuity obligations.
DocRadar detail
Retain + Public Intel
Public Intel keeps the governed canon current.
Public Intel keeps governed regulatory obligations current. Retain keeps the relationship-level lifecycle moving around compliance obligations: what is due, what is complete, what is blocking a renewal, and what needs human attention.
Public Intel detail
Applied and planned use cases
Cross-vertical continuity infrastructure.
From healthcare memberships to wine clubs, borrower journeys, operator plans, and recurring service relationships, Retain gives every Aegis vertical a shared way to understand lifecycle state, upcoming obligations, at-risk accounts, and renewal momentum.
Emprise Concierge
In Emprise Concierge, Retain keeps the membership relationship moving across inquiry, agreement, payment, onboarding, renewal, reimbursement packet state, and long-term retention. Retain does not own clinical workflow. It tracks the relationship around it.
PayDoc
PayDoc handles payment and documentation workflows. Retain tracks the continuity state around those workflows: what is active, due, delayed, ready, at risk, renewed, or ready for human follow-up.
Vinlio
Wine club memberships, allocation relationships, and recurring order plans all have lifecycle state. Retain can track the continuity of those relationships without owning the commerce or fulfillment engine.
Pro MLO
Borrower relationships have lifecycle stages too — from inquiry and pre-qualification through closing and long-term retention. Retain can model the borrower lifecycle alongside the mortgage workflow.
Snurpy
Snurpy operator plans are recurring relationships. Retain can track plan continuity, renewal state, onboarding progress, and at-risk operator signals across the Snurpy subscriber base.
Future recurring-service models
Any Aegis vertical with recurring relationships — agreements that renew, services that require continuity, and accounts that can lapse and reactivate — can use Retain without schema redesign.