Firm: [RIA or BD firm name] Prepared for: [CCO name] Date: [Date]
Advisor Prep Hero is a local-first AI workspace for professional client work. It is a desktop application. Every conversation and AI output is saved as a plain text file in a folder the advisor controls on their own machine. Advisor Prep Hero does not maintain a cloud database of client information. The tool's servers handle only licensing and product delivery, not client data.
Advisor Prep Hero supports two AI paths:
Local model (Ollama): The AI model runs on the advisor's machine. Client information never leaves the machine. There is no network transmission of client data. This path has no service-provider footprint under Reg S-P.
Cloud API key: The advisor's prompts go directly from their machine to the AI provider (Anthropic, OpenAI, or Google) under the advisor's own API key. Advisor Prep Hero's servers are not in the data path. The network call is from the advisor's machine to the AI provider, not through any Advisor Prep Hero intermediary.
Reg S-P Rule 30 (as amended 2024) requires firms to oversee service providers that handle customer information. Advisor Prep Hero itself is not a service provider in the data path for client information. It is local software running on the advisor's machine, comparable in structure to a word processor or spreadsheet application.
Local model path: There is no service provider to diligence. Nothing leaves the machine.
Cloud API key path: The AI provider (Anthropic, OpenAI, or Google) is the relevant service provider under Reg S-P, not Advisor Prep Hero. The firm should evaluate the chosen AI provider's API data-processing terms, incident notification commitments, and data-handling controls as part of its standard service-provider due-diligence process. Each of the major providers offers enterprise API agreements with appropriate data-handling terms for financial services firms.
Every Advisor Prep Hero output is a plain file retained under the firm's existing file-retention schedule. The Advisor Prep Hero audit log records each AI action (timestamp, model, files included, output produced) at the per-client level and supports Rule 204-2 documentation requirements. The advisor can export a per-client AI activity log on request.
This document describes the data-path architecture of Advisor Prep Hero as used by an advisor at this firm. It does not constitute a Written Information Security Program (WISP), a Reg S-P risk assessment, or legal or compliance advice. Firms should have their compliance consultant review Advisor Prep Hero's role within the full Reg S-P program, including any required updates to the firm's service-provider due-diligence log and incident-response plan.
The most common AI tool in this category is Jump (meetjump.com), used by more than 27,000 advisors for automated meeting notes and CRM sync. Jump is a cloud SaaS tool with a contractual no-training policy, and it genuinely wins at automating post-meeting admin. It also holds SOC 2 Type II certification and can satisfy a standard signed-DPA requirement, which Advisor Prep Hero cannot today. If the firm's priority is meeting transcription and automatic CRM updates, Jump is a proven choice.
The architectural difference that matters for this review: Jump routes meeting data through Jump's servers. Under Reg S-P, Jump is a service provider in the data path and requires documentation and monitoring accordingly. Advisor Prep Hero is not a service provider in that path. With a local model, Advisor Prep Hero runs entirely on the advisor's machine and there is no AI vendor to vet or monitor. With a cloud API key, the relevant service provider is the AI provider (Anthropic, OpenAI, or Google) directly, not Advisor Prep Hero. For a CCO whose goal is minimizing the vendor surface that touches client data, that is a meaningfully different posture, not a better meeting-notes tool.
Advisor Prep Hero does not have SOC 2 or a signed DPA, and does not record or transcribe meetings. Firms that need meeting-notes automation and cloud-vendor credentialing should use Jump for that function. The question for this review is whether an advisor's drafting and analysis workspace a separate layer from meeting notes needs to add another cloud vendor to the service-provider inventory at all.