client-onboarding
Design and implement end-to-end client onboarding workflows from prospect intake through funded account, covering KYC verification, document collection, e-signature, and custodian submission. Use when the user asks about building a digital onboarding flow, integrating identity verification or CIP checks, reducing NIGO rejection rates, opening complex account types like trusts or entities, connecting to custodian APIs, designing suitability questionnaires, or comparing advisor-assisted vs self-service models. Also trigger when users mention 'new account opening', 'onboarding bottleneck', 'KYC integration', 'beneficial ownership', 'OFAC screening', 'account funding', or 'onboarding automation'.
What this skill does
# Client Onboarding ## Purpose Guide the design and implementation of client onboarding workflows for wealth management and advisory firms. This skill covers the end-to-end process from prospect intake through funded account — including digital identity verification, suitability data collection, account type selection, document generation, e-signature, custodian submission, and initial investment. It enables a user or agent to design, evaluate, or troubleshoot onboarding systems that satisfy regulatory requirements while minimizing friction for advisors and clients. ## Layer 10 — Advisory Practice (Front Office) ## Direction prospective ## When to Use - Designing or redesigning a digital client onboarding workflow - Evaluating onboarding platforms or technology vendors - Integrating KYC/CIP verification into account opening processes - Building document collection and generation pipelines for new accounts - Implementing e-signature workflows for account opening forms - Connecting onboarding systems to custodian APIs (Schwab, Fidelity, Pershing) - Troubleshooting high NIGO (Not In Good Order) rejection rates - Designing suitability and risk profiling questionnaires for new clients - Determining which compliance checkpoints to embed in onboarding flows - Opening complex account types (trusts, entities, estates) that require additional documentation - Comparing advisor-assisted vs self-service (digital-direct) onboarding models - Measuring onboarding efficiency and identifying workflow bottlenecks ## Core Concepts ### Onboarding Workflow Architecture Client onboarding is an orchestrated, multi-stage process that transforms a prospect into a funded, investable account. The canonical stages are: 1. **Prospect intake** — capture contact information, establish CRM record, assign advisor 2. **Identity verification** — CIP/KYC checks (name, DOB, address, SSN/TIN, government ID) 3. **Suitability data collection** — investment objectives, risk tolerance, time horizon, financial situation 4. **Account type selection** — individual, joint, trust, IRA, entity, or other structure 5. **Document generation** — assemble the required document package based on account type and features 6. **E-signature** — execute new account forms, agreements, and disclosures electronically 7. **Custodian submission** — transmit the completed application to the custodian for account creation 8. **Funding** — ACH, wire, ACAT transfer, or check deposit to fund the new account 9. **Initial investment** — assign the funded account to a model portfolio or execute the initial trade The two primary flow models are **advisor-assisted** and **self-service (digital-direct)**. In advisor-assisted onboarding, the advisor guides the client through each step, often in a meeting or screen-share, with the onboarding platform pre-populating data from the CRM. In self-service onboarding, the client completes a guided digital workflow independently, with the advisor reviewing and approving the completed application. Most firms support a hybrid model where self-service handles simple account types and advisor-assisted handles complex ones. The onboarding platform acts as an orchestrator across multiple downstream systems: CRM (client master), KYC/AML vendor (identity verification), custodian (account opening API), document management (storage and retrieval), and portfolio management system (model assignment). The platform must manage state transitions, handle errors at each stage, and provide visibility to both the advisor and compliance. ### Digital Identity Verification Identity verification during onboarding must satisfy CIP requirements under USA PATRIOT Act Section 326 and, for legal entities, the FinCEN CDD Rule (31 CFR 1010.230). The onboarding workflow collects the following minimum identifying information: - **Individuals:** Full legal name, date of birth, residential address, Social Security Number (or TIN for non-citizens) - **Entities:** Legal name, formation date, principal place of business, EIN/TIN, formation documents **Verification methods integrated into digital onboarding:** - **Database verification** — real-time API calls to identity verification vendors (LexisNexis Risk Solutions, Equifax, TransUnion, Alloy) that cross-reference provided data against credit bureau, public records, and government databases. This is the most common method for digital onboarding because it requires no document handling and provides a pass/fail result in seconds. - **Document verification** — the client uploads a photo of a government-issued ID (driver's license, passport), and optionally a selfie for facial comparison. OCR extracts data fields; liveness detection prevents spoofing. Used as a fallback when database verification is inconclusive or as a primary method for non-US persons. - **Knowledge-based authentication (KBA)** — the client answers challenge questions generated from their credit file (e.g., "Which of the following addresses have you lived at?"). KBA is declining in use due to data breach exposure but remains a supplementary method. - **Biometric verification** — fingerprint or facial recognition, typically used in mobile onboarding flows. **OFAC and sanctions screening** is a mandatory gate before account opening. The onboarding platform must screen all individuals associated with the account (account holders, authorized signers, beneficial owners, trustees) against the OFAC SDN list, FinCEN 314(a) lists, and any firm-specific restricted lists. A match or potential match must halt the onboarding flow and route to compliance for manual review. **Beneficial ownership collection for entity accounts** requires identification of every individual who directly or indirectly owns 25% or more of the equity interests in the legal entity, plus at least one individual with significant managerial control (the control person). The onboarding workflow must dynamically present beneficial ownership forms when the account type is an entity (LLC, corporation, partnership, certain trusts). **Enhanced due diligence triggers** that the onboarding system should detect and flag: politically exposed persons (PEPs), connections to high-risk jurisdictions (per FinCEN advisories and FATF guidance), complex multi-layered ownership structures, and negative news screening results. When EDD is triggered, the onboarding flow should pause and escalate to the compliance team before proceeding. ### Suitability and Risk Profiling Onboarding is the primary data collection event for investment suitability. Before any investment recommendation can be made, the firm must gather sufficient information to satisfy FINRA Rule 2111 (suitability) for broker-dealers and Regulation Best Interest for BD recommendations, or the fiduciary duty of care for registered investment advisers. **Required data elements:** - Investment objectives (capital preservation, income, growth, aggressive growth, speculation) - Time horizon (short-term under 3 years, intermediate 3-10 years, long-term over 10 years) - Risk tolerance (conservative, moderate, aggressive — and the behavioral willingness to endure volatility) - Liquidity needs (anticipated withdrawals, major expenses, emergency reserves) - Annual income and net worth (including liquid net worth) - Investment experience (years of experience, asset classes traded, knowledge level) - Tax status (marginal tax bracket, tax-sensitive vs tax-exempt accounts) - Special circumstances (concentrated stock positions, employer restrictions, ESG preferences) **Risk questionnaire design** follows two approaches: - **Psychometric questionnaires** measure the client's emotional and behavioral relationship with risk — willingness to accept losses, reaction to market downturns, comfort with uncertainty. These are better at capturing true risk tolerance but can be subjective. - **Knowledge-based questionnaires** assess the client's understanding of investment concepts and their objective fin
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.