The RIA Meeting Prep Workflow That Cuts 3 Hours to 15 Minutes

Manual meeting prep at an RIA averages 2 to 3 hours per client review.

That figure is not abstract. It is what you get when an advisor pulls account data from the custodian portal, reviews CRM notes from the last six months, checks open tasks and outstanding action items, reviews the most recent financial plan update, and writes talking points — one meeting at a time, without a structured workflow to assemble the inputs.

For an advisor with 120 households doing quarterly reviews, that is 240 to 360 hours of meeting prep per year. A full-time job inside the advisory practice, consuming work that does not require the advisor's judgment — just their time.

This guide walks through the 5-Input Meeting Brief framework: a specific meeting prep workflow with exact tool sources for each input, buildable inside the tools most RIA firms already own.

Why Meeting Prep Takes So Long

The time cost is not in the thinking — it is in the assembly. Advisors are not spending 3 hours forming views on a client's financial situation. They are spending 3 hours finding and compiling information from five different systems that do not share data automatically.

The systems involved in a typical prep session:

The CRM (Redtail or Wealthbox) holds client notes, action items, and relationship history
The custodian portal (Schwab Advisor Services or Fidelity Institutional) holds account data, balances, recent transactions, and pending activity
The portfolio management system (Orion, Black Diamond, or Tamarac) holds performance data and asset allocation vs. target
The financial planning software (eMoney or MoneyGuidePro) holds the current plan, plan assumptions, and any flagged changes
The meeting recap from the last appointment — often in the CRM, sometimes in a separate notes file, occasionally in the advisor's email inbox

None of these systems automatically produce a meeting brief. The advisor assembles it manually, every time, for every meeting. The 5-Input framework changes that.

The 5-Input Meeting Brief Framework

A well-designed meeting prep workflow assembles five specific inputs into a single brief an advisor can review in 90 seconds before walking into a meeting. Here is what each input contains, where it comes from, and how to automate its assembly.

Input 1: Account Summary

What it contains: Current portfolio value, asset allocation vs. target, account changes since last review (new accounts, closed accounts, balance changes exceeding a defined threshold), and any custodian-flagged pending activity.

Where it comes from: Schwab Advisor Services data feed or Fidelity Institutional Wealth Services data feed, routed through the portfolio management system.

How to automate: Set a meeting-triggered report in Orion, Black Diamond, or Tamarac that generates a client-level portfolio summary 24 hours before each scheduled meeting. The trigger is the calendar Activity in the CRM linked to the client record. Both Redtail and Wealthbox support activity-linked report triggers with portfolio management integrations — most firms have the integration active but have not configured the meeting trigger.

Input 2: Open Items from Last Meeting

What it contains: Every action item, follow-up task, and commitment logged in the CRM since the previous meeting — open, completed, and in-progress — with the responsible party for each.

Where it comes from: Redtail Activities or Wealthbox Tasks, filtered to the client record and time period since the last meeting recap.

How to automate: A CRM report or Workflow Template that generates a task list filtered by contact and date range, automatically linked to the upcoming meeting Activity in Redtail or the meeting Event in Wealthbox. This is a native feature in both platforms. Most firms pull this view manually rather than having it queue automatically as part of the pre-meeting task chain.

Input 3: Relationship Context

What it contains: Key client notes from the last 90 days, logged life events or circumstances (job change, health concern, upcoming retirement date, family situation), and any communication flagged for advisor attention.

Where it comes from: CRM contact record — notes, categories, and custom fields in Redtail or Wealthbox.

How to automate: A summary view or filtered report scoped to the contact record and the prior 90 days. In Redtail, the Activity History view scoped to Notes types surfaces this automatically. In Wealthbox, the Contact Timeline filtered by interaction type provides the same view. Neither requires custom configuration — the data is already there for firms where advisors and CSAs log consistently after client interactions.

Input 4: Plan Status

What it contains: Whether the financial plan is current, any open planning items, and whether plan assumptions have changed materially since the last review — income changes, insurance gaps, updated retirement timeline.

Where it comes from: eMoney or MoneyGuidePro, via CRM integration or via a pre-meeting report generated by the planning software.

How to automate: eMoney's Redtail and Salesforce integrations can push updated plan summary data to a CRM custom field when a plan is updated. MoneyGuidePro's CRM sync pushes key plan data fields on the same trigger. For firms without these integrations active, a structured CSA task 48 hours before each meeting — "review eMoney plan status for [client] and update CRM plan status field" — converts this from an advisor-time cost to a CSA-time cost and ensures the information is current before the meeting.

Input 5: One Proactive Concern

What it contains: A single item worth raising with the client that they are not expecting — a change in the account that warrants a conversation, a life event context that deserves follow-up, a planning gap that has opened since the last review.

Where it comes from: This input requires synthesis. It cannot be fully automated — but it can be prompted. A structured pre-meeting checklist item in the CRM prompts the advisor with three questions: Has anything material changed in the account? Is there a logged life event requiring follow-up? Is the client approaching a plan milestone?

The advisor answers these three questions based on Inputs 1 through 4. The result is a single proactive concern worth raising — not generated by the system, but surfaced by a consistent process that ensures the question is always asked.

What the Assembled Brief Looks Like

A complete 5-Input Meeting Brief for a 90-minute client review looks like this in practice:

Account Summary: Portfolio at $1.24M, allocation 62/38 vs. 65/35 target, one RMD processed last week pending confirmation
Open Items: 3 open tasks from last meeting — beneficiary update (CSA in progress), Roth conversion analysis (advisor), 30-day check-in call (completed)
Relationship Context: Client mentioned retirement date moving up 18 months in last CRM note; daughter starting college this fall — flagged in CRM
Plan Status: eMoney plan current as of 3 months ago; income projection not updated since job change logged in February
Proactive Concern: Income assumption in eMoney not updated for new salary; worth discussing whether to accelerate retirement contributions now

Total reading time: 90 seconds. Total advisor time in assembly: 0 minutes for Inputs 1 through 3, 10 to 15 minutes for Inputs 4 and 5.

The change from manual to structured prep is not a reduction in quality. It is an improvement in consistency. The advisor who reads this brief before the fifth meeting of the day arrives with the same quality of preparation as the first.

Building the Workflow

The meeting prep workflow described above requires four configuration steps:

Step 1: Activate the portfolio management integration in your CRM. In Redtail, this is the Orion, Black Diamond, or Tamarac integration in the Apps section. In Wealthbox, the same integrations are available in the Integrations settings. Once active, account-level summary data pulls automatically to the CRM contact record and is available for the meeting trigger.

Step 2: Standardize note-logging. The relationship context input is only as good as what is in the CRM. Establish a practice-wide standard for what CSAs and advisors log after every client interaction — at minimum: any life event mentioned, any open question, and the outcome of any outstanding action item.

Step 3: Build the pre-meeting task chain. In Redtail, a Workflow Template fires 48 hours before each scheduled meeting Activity, queuing: plan status review (CSA), account summary report generation (automated), open items review (advisor). In Wealthbox, the same chain is built as a Workflow Template triggered by a meeting Event type. The 48-hour trigger gives the CSA time to complete their steps before the advisor reads the brief.

Step 4: Add the proactive concern prompt. A single checklist item at the top of the advisor's pre-meeting task — "Identify one proactive concern to raise" with the three trigger questions — converts an informal habit into a consistent practice that runs at every meeting, regardless of what the rest of the day looks like.

Frequently Asked Questions

What is the right time window to pull relationship context from the CRM?

90 days is the practical standard for quarterly reviews. For annual reviews or clients with complex, evolving situations, extend the window to 180 days. Shorter windows (30 days) miss context that is directly relevant to the meeting agenda — particularly for clients where the last significant note predates the prior quarter.

Do we need a separate meeting prep tool, or can this run in Redtail or Wealthbox?

For most RIA firms under 200 households, the 5-Input workflow runs entirely within Redtail or Wealthbox plus the existing portfolio management system. A separate meeting prep tool adds a vendor, a login, and an integration project without meaningfully improving the output for firms where the core CRM is configured correctly.

How do we handle same-day meeting prep when a meeting is scheduled with less than 48 hours of lead time?

The 48-hour trigger still fires — it queues closer to the meeting. For truly last-minute meetings (under 4 hours), the pre-meeting task chain should include a CSA step that manually pulls the account summary and flags open items, with the advisor receiving a 30-minute brief. This edge case warrants a specific named workflow rather than depending on the standard chain to run fast enough.

Key Takeaways

Manual meeting prep at 2 to 3 hours per review is an assembly problem, not a judgment problem — the advisor's time is spent finding information, not forming views
The 5-Input Meeting Brief framework: Account Summary (portfolio system + custodian feed), Open Items (CRM task list), Relationship Context (CRM notes), Plan Status (planning software), and one Proactive Concern (advisor synthesis)
All five inputs are buildable within tools most RIA firms already own — Redtail or Wealthbox plus the existing portfolio management integration
The pre-meeting task chain triggered 48 hours before each meeting converts 3 hours of advisor assembly time to 15 minutes of advisor review time
Floor quality is the key outcome: the fifth meeting of the day gets the same preparation depth as the first

If you want to map your current meeting prep workflow against the 5-Input framework and identify where your assembly time is going, book a discovery call with Systemaic.