In-force CRM is the frame for teams whose primary workflow is tracking the active book of policies, contracts, or subscriptions: insurance agencies tracking policies in force, financial advisors tracking active accounts, SaaS teams tracking active subscriptions, service firms tracking active retainers. Strkr ships in-force primitives - active policy or contract tracking, renewal cadence Flows, retention risk scoring, service queue management, and commission reconciliation on the in-force book.
The in-force CRM frame comes up in a set of buyer contexts: insurance agencies where the policy book is the primary asset, financial services firms where the AUM book is the primary asset, SaaS teams where the subscription book is the primary asset, and services firms where the retainer book is the primary asset. The common CRM options optimise for new business pipeline (which deals are moving through stages) and miss on the in-force book management (which active policies need service, which active accounts face renewal risk, which active subscriptions are at churn risk, which active retainers need the next check-in). The pain points below show up on every in-force-focused CRM buyer conversation.
The common CRMs ship pipeline-first views: opportunities, stages, forecast. The in-force book (active policies, active contracts, active subscriptions) often lives on a secondary surface or in a separate tool entirely. The team spends time on new business visibility while the real asset (the in-force book) sits in a different dashboard.
The common CRMs lack native renewal cadence on the in-force book. The agent or account manager tracks policy X-dates in a spreadsheet, contract renewals in a calendar, and subscription renewal in a billing system. The renewal window gets missed on 15 to 20 percent of the book because the cadence lives outside the CRM.
The in-force book carries churn risk patterns: policies with coverage gaps, accounts with low engagement, subscriptions with declining usage, retainers with missed cadence. The common CRMs do not surface the risk patterns, so the retention team runs reactive save motions instead of proactive protection.
The in-force book generates service requests (coverage questions, policy changes, account inquiries, subscription support). The common CRMs do not model service queue management, so the service team runs on email folders with no SLA tracking, no routing, and no retention risk escalation.
The in-force book generates recurring commission (annual renewal commission on policies, trailing commission on subscriptions, override commission on retainers). The common CRMs do not reconcile the expected commission flow against the carrier or vendor statement, so the discrepancy lives in a parallel spreadsheet.
The in-force book carries metrics that matter beyond the new business pipeline: book composition by product/segment, concentration risk by top accounts, value trends over time, retention rate by cohort, net revenue retention. The common CRM reporting layer surfaces pipeline reports natively and in-force book reports as export-to-Excel exercises.
Strkr ships the in-force book as a first-class surface alongside the new business pipeline. The in-force dashboard shows active policies, active contracts, or active subscriptions with renewal cadence, retention risk, service queue, and commission flow all visible on one surface. The pattern below covers the primitives.
The in-force dashboard shows the active book composition (by product line, segment, carrier, or vendor), concentration risk (top-decile accounts drive what percentage of the book), value trends over time (book value growth, retention rate, net revenue retention), and renewal pipeline (what is coming up at 30, 60, 90, 120 days out).
The renewal cadence Flow fires at 120, 90, 60, and 30 days before each in-force asset renewal (policy X-date, contract renewal, subscription renewal, retainer term end). The Flow sends the renewal review email, creates the review task, surfaces the renewal on the retention dashboard, and tracks the renewal outcome (renewed, non-renewed, replaced).
The retention risk score runs per in-force asset with signals from service history (ticket volume, resolution time, sentiment), engagement history (email engagement, meeting cadence, product usage), coverage or scope changes (reductions, downgrades), and competitor signals (RFP activity, inbound competitor inquiries). The dashboard surfaces the highest-risk assets for proactive outreach.
The service queue surface routes inbound service requests to the right team member (per account, per product line, per service tier) with configurable SLA timers, escalation Flows for breach, and retention risk escalation when a service pattern indicates churn risk. The service team runs on a managed queue instead of email folders.
The commission reconciliation surface ingests carrier commission statements (per-carrier for insurance, per-custodian for financial services, per-vendor for SaaS reselling) with Strkr AI matching each statement line to the in-force asset record. The reconciliation surfaces discrepancies with the recommended dispute reason, fires the dispute Flow for gaps above threshold, and tracks the dispute resolution.
The book-level reporting surface runs on native dashboards covering book composition (by product, segment, carrier), concentration risk (top-decile and bottom-decile analysis), retention rate (by cohort, by product, by segment), net revenue retention, premium or ACV growth trends, and churn attribution. The dashboards replace the common export-to-Excel pattern.
The single largest driver of retention performance on the in-force book is renewal cadence discipline. The team that touches the account at 120 days out, follows up at 90, reviews at 60, and signs at 30 retains at a materially higher rate than the team that lets the renewal date arrive without proactive outreach. Strkr ships the renewal cadence as a native Flow with configurable triggers per in-force asset type.
At 120 days out, the retention Flow fires an internal review (what has the account done this term, what are the signals of risk and opportunity, what is the retention game plan) and schedules the client-facing conversation. The pattern starts the retention motion with sufficient lead time to address material concerns before the renewal window closes.
At 90 days out, the Flow fires the renewal recommendation preparation (coverage review, pricing analysis, competitive positioning) with Strkr AI drafting the recommendation document. The pattern gives the account manager time to collect approvals and iterate before the client-facing conversation.
At 60 days out, the Flow fires the client-facing renewal conversation with the recommendation presented, the pricing documented, and the next-step commitments captured. The pattern ensures the renewal conversation happens with sufficient time for alternative scenarios (if the client wants changes, the account manager has time to iterate).
At 30 days out, the Flow fires the signature push with the executed renewal documents and the escalation sequence for any outstanding commitments. The pattern closes the signature window before the renewal date instead of letting the signature fall into the renewal week.
After the renewal signs, the Flow fires the welcome-back communication, the first-term success check-in at 30 and 90 days, and the next-renewal cadence setup for the following cycle. The pattern treats the renewal as the start of the next term, not the end of the current one.
For non-renewals, the workflow captures the reason (price, service, competitor, business change, no longer needed), runs a recovery sequence for recoverable cases, and feeds the churn reason data to the retention risk scoring model for future cohort improvement. The pattern turns the non-renewal into learning rather than loss.
The in-force book generates service requests at a scale the new business team never sees: policy changes, coverage questions, account inquiries, billing issues, subscription support, retainer check-ins. The common CRM pattern is email folders with no routing, no SLA tracking, and no retention risk escalation. Strkr ships the service queue as a native surface with routing, SLA, and retention integration.
Service request routing runs on configurable rules: per-account assignment (named account service team), per-product-line specialist (life insurance questions to the life team), per-tier escalation (platinum accounts to senior CSMs), round-robin for unassigned, and overflow routing for capacity caps. The pattern replaces the email folder with a managed queue.
Service SLA tracking runs per request with configurable response time (first response within 2 hours, 4 hours, 24 hours) and resolution time (resolution within 24 hours, 48 hours, 5 days) by request type or account tier. SLA breach triggers escalation to the manager with the breach context and the retention risk impact.
Service request patterns feed the retention risk score: high ticket volume (relative to account baseline), long resolution time, negative sentiment, repeat-issue patterns, service downgrades. The pattern surfaces at-risk accounts early so the account manager can intervene before the renewal window.
Strkr AI drafts the first service response based on the request context, the account history, and the common resolution patterns for the request type. The service team reviews and sends in one tap, which compresses the response time without reducing message quality.
When the renewal review runs, the service history for the renewal period is visible on the review surface. The account manager walks into the renewal conversation knowing the full service pattern (ticket volume, resolution outcomes, outstanding issues) instead of discovering the frustrations during the renewal call.
Service satisfaction tracking runs per request with configurable satisfaction capture (micro-survey, resolution confirmation, longer survey for high-stakes requests). The satisfaction data correlates with retention outcomes to surface the service patterns that drive renewal versus the patterns that drive churn.
The in-force book carries metrics the pipeline reports do not surface. Book composition (how the book splits by product, segment, carrier), concentration risk (what percentage of the book sits in the top decile of accounts), retention rate (what percentage renews each term), net revenue retention (how much the renewing book grows or shrinks), and growth trends over time. Strkr ships the book-level reporting natively alongside the pipeline reporting.
The book composition dashboard shows the active book split by product line, segment, carrier or vendor, and vintage (acquisition cohort). The pattern surfaces concentration patterns, growth areas, and strategic shifts in the book over time.
The concentration risk dashboard shows what percentage of the book value lives in the top-decile accounts (concentration risk), the bottom-decile accounts (long-tail profitability), and the middle (sustainable base). The pattern informs the retention investment allocation.
The retention rate dashboard shows logo retention (percentage of accounts that renew), revenue retention (percentage of revenue that renews, including any contraction), and net revenue retention (percentage of revenue that renews including expansion). The cohort view surfaces retention trends over time by acquisition period, segment, and product line.
The churn attribution dashboard shows the churn reasons (price, service, competitor, business change, no longer needed) with correlation to acquisition patterns (which acquisition channels produce retained accounts vs churned accounts). The pattern informs the new business motion by showing which top-of-funnel sources produce the best in-force book.
The growth dashboard shows the in-force book changes over time: accounts that grew (expansion), accounts that stayed flat (steady state), accounts that contracted (downgrades), accounts that churned (full loss). The pattern surfaces the expansion opportunity on the existing book, which is often more cost-effective than new business acquisition.
The commission forecast runs 90 days forward based on the in-force book and the per-asset commission schedule. The forecast split by carrier or vendor, by product line, and by period gives the team cash-flow visibility that most in-force-focused teams never had.
The common pipeline-focused CRMs optimise for new business visibility and miss on in-force book management. Strkr ships the in-force book as a first-class surface alongside the pipeline with renewal cadence, retention scoring, service queue, and book-level reporting all native.
| Feature | Strkr | Pipeline-focused CRM |
|---|---|---|
| In-force dashboard | First-class surface | Secondary view |
| Renewal cadence Flows | Native 120/90/60/30 day triggers | Manual spreadsheet tracking |
| Retention risk scoring | Native signal-based scoring | Not available |
| Service queue | Native with routing and SLA | Email folders or add-on |
| Commission reconciliation | Native per-carrier matching | Parallel spreadsheet |
| Book composition reporting | Native dashboards | Export to Excel |
| Concentration risk analysis | Native top/bottom decile | Not available |
| Retention rate by cohort | Logo + revenue + net revenue | Basic retention metric |
| Churn attribution | Native with acquisition correlation | Not available |
| Commission forecast | Recurring commission 90 days forward | One-time commission only |
| Request-to-renewal visibility | Service history on renewal review | Cross-system lookup |
| Strkr AI on in-force | Drafting + retention risk signals | Not available |
The patterns below show up on teams that framed the CRM buy around the in-force book management problem.
A 15-producer insurance agency with 2,000 in-force policies runs Strkr with the X-date renewal cascade (120/90/60/30 days), retention risk scoring on signal patterns, service queue routing by carrier and account tier, and commission reconciliation across eight carriers. Policy book composition dashboard shows carrier concentration, line of business mix, and vintage trends.
An independent financial advisor with 180 households runs Strkr with the quarterly review Flow, AUM-based trailing commission forecast, retention risk scoring on engagement patterns, service queue for client inquiries, and book composition reporting (AUM by segment, concentration by top-decile households, net revenue retention over time).
A 50-person SaaS team with 400 active subscriptions runs Strkr with the subscription renewal cadence (120/90/60/30 days), churn risk scoring on usage and engagement signals, service queue for customer support, net revenue retention dashboard with expansion attribution, and commission reconciliation on the CSM compensation structure.
A 25-person creative agency with a $4M annual retainer book runs Strkr with the quarterly retainer review Flow, scope tracking per retainer, utilisation data feeding retention risk scoring, service queue for client requests, and book-level reporting on retainer composition, concentration, and renewal trends.
A 40-person managed services provider with 150 active multi-year contracts runs Strkr with contract renewal cadence (6 months out for strategic review, 90 days out for renewal commitment), trailing commission tracking across the contract term, service queue for support tickets, and book-level reporting on ARR composition and retention cohorts.
Start a 14-day trial with the full in-force stack enabled: in-force dashboard, renewal cadence Flows at 120/90/60/30 days, retention risk scoring, service queue with SLA, commission reconciliation on the recurring book, and book-level reporting on composition, concentration, retention, and growth.
The renewal cadence runs on native Flows with configurable triggers per in-force asset type (policy, contract, subscription, retainer). The default cadence fires at 120, 90, 60, and 30 days before the renewal date with the actions tunable per asset type. At 120 days out, the retention review Flow fires with the internal review and the game plan definition. At 90 days out, the recommendation preparation Flow fires with Strkr AI drafting the renewal recommendation document. At 60 days out, the client-facing conversation Flow fires with the renewal meeting booked and the recommendation presented. At 30 days out, the signature push Flow fires with the executed renewal documents and the escalation sequence. After the renewal signs, the welcome-back and first-term check-in Flows fire. For non-renewals, the recovery sequence runs for recoverable cases and the churn reason feeds the retention risk scoring model. The pattern turns the renewal cadence from a manual spreadsheet discipline into a native workflow.
The retention risk score runs per in-force asset with signals from multiple sources: service history (ticket volume relative to the account baseline, resolution time, sentiment, repeat-issue patterns, service downgrades), engagement history (email engagement, meeting cadence, product usage decline for SaaS, policy service inactivity for insurance), coverage or scope changes (reductions, downgrades, line removals), competitor signals (RFP activity, inbound competitor inquiries, mentions in meeting notes), and tenure patterns (certain account vintages have higher churn risk). The score weights are configurable in the admin UI based on which signals correlate with churn on the tenant's specific motion. The dashboard surfaces the highest-risk assets for proactive outreach with Strkr AI drafting the retention conversation based on the risk signals present. The pattern replaces the common reactive save motion with proactive protection before the renewal window.
The service queue surface routes inbound service requests to the right team member with configurable rules: per-account assignment (named account service team), per-product-line specialist (life insurance questions to the life team), per-tier escalation (platinum accounts to senior CSMs), round-robin for unassigned, and overflow routing for capacity caps. SLA tracking runs per request with configurable response time and resolution time by request type or account tier, and SLA breach triggers escalation to the manager. The service patterns feed the retention risk scoring so high-volume or negative-sentiment service history flags the account for proactive renewal preparation. Strkr AI drafts the first service response based on the request context and the common resolution patterns, which compresses the response time without reducing message quality. The service history is visible on the renewal review so the account manager walks into the renewal conversation knowing the full service pattern instead of discovering frustrations during the call.
The commission reconciliation surface ingests recurring commission statements from carriers (for insurance in-force policies), custodians (for financial services AUM), or vendors (for SaaS reselling trailing commission). Strkr AI matches each statement line to the in-force asset record on identifier, named insured or account, and effective date. The reconciliation runs the expected commission (based on the asset value and the commission schedule configured for the carrier or vendor) against the actual commission paid. The discrepancy report surfaces the gaps per asset with the recommended dispute reason (missed commission, incorrect split, reversal error, chargeback on cancellation). For discrepancies above a configurable threshold, the dispute Flow fires with the carrier or vendor contact, the asset reference, and the supporting evidence pre-assembled. The commission forecast runs 90 days forward based on the in-force book and the per-asset commission schedule, giving the team cash-flow visibility that most in-force-focused teams never had before the Strkr pattern.
Yes. The in-force book model supports multiple asset types on one tenant: policies (insurance), accounts (financial services), subscriptions (SaaS), contracts (services), retainers (agencies). Each asset type carries its own schema (the vertical field library), its own renewal cadence configuration, its own commission structure, and its own retention risk weights. The book-level dashboard rolls up across asset types for the aggregate view (total book value, aggregate retention rate, aggregate renewal pipeline) and drills down into one asset type for the type-specific review. For professional services firms serving multiple industries (an advisor managing both insurance clients and financial services clients, a consultancy with both SaaS and services retainer books), the multi-type pattern avoids running separate CRM tenants.
Pipeline reporting answers questions about new business (which deals are moving, what the forecast looks like, where the pipeline is stuck). Book-level reporting answers questions about the in-force book (what percentage of the book sits in the top-decile accounts, what the retention rate looks like by cohort, how net revenue retention is trending, which product lines are growing and which are contracting, which acquisition channels produced the retained book). The Strkr book-level reporting runs on native dashboards covering: book composition by product line, segment, carrier, and vintage; concentration risk with top-decile and bottom-decile analysis; retention rate split into logo retention, revenue retention, and net revenue retention; churn attribution with correlation to acquisition patterns; growth and expansion tracking; and commission forecast. The dashboards replace the common export-to-Excel pattern that defines in-force reporting on most CRM options.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
