crm-client-lifecycle
Design and optimize CRM systems and client lifecycle workflows for advisory firms, covering segmentation, household management, service tiers, and retention analytics. Use when the user asks about client segmentation models, building household structures, defining service tier SLAs, scheduling reviews, tracking lifecycle stages from prospect through estate, identifying at-risk clients, analyzing wallet share, consolidating held-away assets, or evaluating CRM platforms. Also trigger when users mention 'client segmentation', 'retention risk', 'at-risk clients', 'household linking', 'multi-generational', 'service tiers', 'Redtail', 'Wealthbox', 'Salesforce for advisors', 'referral tracking', or 'contact gap'.
What this skill does
# CRM & Client Lifecycle ## Purpose Guide the design, implementation, and optimization of client relationship management systems and lifecycle workflows for wealth management and advisory firms. This skill covers client segmentation models, household structure management, service tier frameworks with defined SLAs, review scheduling and preparation workflows, lifecycle stage tracking from prospect through estate succession, CRM data architecture and integration with portfolio management and custodial systems, and client engagement analytics including retention risk identification and wallet share analysis. It enables a user or agent to design CRM strategies, evaluate CRM platforms, build client service programs, and troubleshoot relationship management workflows that maximize client retention, deepen relationships, and ensure systematic service delivery across the entire book of business. ## Layer 10 — Advisory Practice (Front Office) ## Direction both ## When to Use - Designing or evaluating a client segmentation model for an RIA or broker-dealer - Building household structures that link individuals, accounts, trusts, and entities - Defining service tier frameworks with SLAs, review cadences, and service menus - Designing client review scheduling workflows and preparation checklists - Tracking client lifecycle stages from prospect through estate succession - Integrating CRM with portfolio management systems, custodians, and financial planning tools - Identifying at-risk clients using engagement analytics and retention scoring - Analyzing wallet share and held-away asset opportunities - Building referral tracking and client satisfaction measurement programs - Evaluating CRM platforms (Salesforce, Wealthbox, Redtail, Microsoft Dynamics) for advisory firms - Designing advisor assignment and team-based service models - Standardizing contact logging, activity tracking, and opportunity management workflows ## Core Concepts ### Client Segmentation Models Client segmentation assigns every household to a category that determines the level of service, contact frequency, review cadence, and resource allocation the firm provides. Without systematic segmentation, advisors default to reactive service — responding to whoever calls — rather than proactive, tiered engagement that matches effort to relationship value. **AUM-based segmentation** is the most common starting point. A typical three-tier model: | Tier | Household AUM | Typical Label | |------|--------------|---------------| | A | $2,000,000+ | Platinum | | B | $500,000 - $1,999,999 | Gold | | C | Under $500,000 | Silver | AUM-based segmentation is simple to implement because AUM data is readily available from the custodian or portfolio management system. However, AUM alone is an incomplete measure of relationship value. **Revenue-based segmentation** uses total annual fees generated by the household rather than asset levels. This captures value more accurately when fee schedules vary across clients, when some households pay financial planning fees in addition to AUM fees, or when clients have complex billing arrangements. Revenue data comes from the billing system and should be annualized to smooth quarterly fluctuations. **Multi-factor segmentation** combines quantitative and qualitative dimensions for a more complete picture: - Assets under management (current relationship size) - Revenue generated (actual economic value to the firm) - Growth potential (age, career trajectory, expected inheritances, held-away assets not yet consolidated) - Referral activity (clients who actively refer new prospects) - Relationship depth (number of services engaged — investment management, financial planning, tax planning, estate planning, insurance) - Strategic importance (centers of influence, professional advisors who refer, board members, community leaders) **Behavioral segmentation** classifies clients by engagement patterns rather than dollar amounts. Categories might include: highly engaged (frequent contact, attends events, uses the client portal), moderately engaged (responds to outreach, attends annual reviews), passively engaged (minimal contact, rarely initiates), and disengaged (does not respond to outreach, skips reviews). Behavioral segmentation identifies retention risk and helps advisors tailor their communication approach. **Segmentation review cadence.** Client segments should be re-evaluated at least annually, typically after year-end billing and performance reporting. Major life events (inheritance, business sale, divorce, retirement) can trigger an immediate re-segmentation. The CRM should flag households whose AUM or revenue has crossed a tier boundary so the advisor can adjust the service level. ### Household Management The household is the fundamental unit of relationship management in wealth advisory. A household groups related individuals, their accounts, and associated entities into a single relationship view that reflects how the family thinks about its finances. **Household composition** typically includes: - Primary client (the individual who is the main point of contact and decision-maker) - Spouse or partner - Dependent children (relevant for 529 plans, custodial accounts, and beneficiary designations) - Adult children who may be clients in their own right or future clients - Trusts (revocable, irrevocable, charitable) established by the primary client or spouse - Business entities (LLCs, S-Corps, partnerships) owned by household members - Family foundations or donor-advised funds **Account-to-household linking.** Every account in the portfolio management system and custodian must be linked to a household in the CRM. Account types within a household commonly include: individual taxable, joint taxable, traditional IRA, Roth IRA, SEP IRA, rollover IRA, inherited IRA, revocable trust, irrevocable trust, UTMA/UGMA custodial, 529 plan, entity accounts, and charitable accounts. Accurate linking is essential for household-level AUM aggregation, fee tier determination, consolidated reporting, and holistic financial planning. **Household AUM aggregation.** The CRM should display total household AUM by pulling position-level data from the portfolio management system or custodian feeds. Aggregation must handle: accounts at multiple custodians, held-away assets (employer retirement plans, outside brokerage accounts, bank accounts) that are tracked but not managed, and assets under advisement (where the firm provides guidance but does not have discretion). **Multi-generational relationships.** Wealth management relationships increasingly span generations. The CRM should support parent-child household linking so that when a client's adult child becomes a client, the advisor can see the full family relationship, track generational wealth transfer, and coordinate estate planning across generations. This is critical for client retention during the estimated $84 trillion intergenerational wealth transfer projected over the next two decades. **Primary and secondary advisor assignment.** Each household should have a designated primary advisor (responsible for the relationship and investment decisions) and optionally a secondary advisor or client service associate. The CRM should track these assignments and use them for routing service requests, scheduling reviews, and generating workload reports. When an advisor departs the firm, the CRM's advisor assignment data drives the client reassignment process. **Household data hygiene.** Common data quality issues include: orphaned accounts not linked to any household, duplicate household records for the same family, stale contact information (addresses, phone numbers, email), missing or incorrect beneficiary data in the CRM (which may differ from the custodian's records), and inconsistent naming conventions (e.g., "Robert Smith" in one record and "Bob Smith" in another). Quarterly data quality audits should identify and remediate these issue
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.