You’re tracking a spreadsheet of client birthdays. Every October, someone on your team filters for everyone turning 73 this year, pulls their IRA balances from the custodian portal, calculates the RMD using the IRS table, and emails a reminder. By mid-December, you’re chasing stragglers who forgot or ignored the first note. The IRS doesn’t care that your client was traveling. The penalty is 25 percent of the shortfall, and you’re the one fielding the angry call in January.

This is manual work that doesn’t scale. When your book sits at 50 households, one person can handle it in a few afternoons. At 150 households, you’re burning a week of staff time every quarter just to stay ahead of RMD season. At 300, you’ve hired someone whose job description includes “RMD coordinator” because the volume overwhelms your existing team.

The dollar cost is straightforward. A paraplanner running RMD tracking spends 10 to 15 hours per month during the busy season. That’s $4,000 to $6,000 in fully loaded cost for work that adds zero advice value. Multiply that across the year, and you’re looking at $20,000 to $30,000 in recurring expense. For larger firms with multiple advisers, the number climbs past $70,000 annually when you include the time advisers spend answering client questions, following up on missed distributions, and fixing errors that slipped through.

The real damage isn’t the payroll line. It’s the opportunity cost. Every hour your team spends calculating RMDs is an hour they’re not preparing for client reviews, building financial plans, or onboarding new relationships. You’re paying skilled people to do arithmetic the IRS publishes in a table.

What RMD Tracking Actually Involves

Let’s walk through the steps your team repeats every year. First, someone identifies which clients hit the age trigger. The SECURE 2.0 Act moved the starting age to 73 for anyone born in 1951 or later, so you can’t rely on the old 70½ or 72 rules. You filter your CRM or pull a birthday report, then cross-reference against account types to exclude Roth IRAs and accounts that don’t require distributions.

Next, you need the prior year-end balance for every traditional IRA, SEP, SIMPLE, and inherited IRA. If your custodian is Schwab, Fidelity, or TD, you log into the portal and export a CSV. If you have clients across three custodians, you repeat the process three times. If a client consolidated accounts mid-year, you adjust the balance manually.

Then comes the calculation. You look up the client’s age as of December 31, find the corresponding life expectancy factor in IRS Publication 590-B, and divide the balance by that factor. For inherited IRAs, the rules diverge depending on whether the original owner died before or after their required beginning date, and whether the beneficiary is a spouse, minor child, or non-eligible designated beneficiary. You’re now reading 40 pages of IRS guidance to get one number right.

Once you have the RMD figure, you draft an email or letter. You explain the amount, the deadline, the penalty for missing it, and the withholding options. You send it in September or October, hoping the client acts before Thanksgiving. Then you wait. In December, you pull another custodian report to see who actually took the distribution. You send a second reminder to the ones who didn’t. A few clients call to ask if they can take it from their taxable account instead (no), or whether they can donate it to charity (yes, if it’s a QCD and they meet the other rules). You answer the same questions a dozen times.

Finally, you document everything. Compliance wants a record that you notified the client, calculated the amount correctly, and followed up. You save the emails, update the CRM notes, and file a copy of the calculation in the client folder. If the client missed the deadline anyway, you write a file note explaining that you sent two reminders and the client chose not to act. You’re building a paper trail in case the IRS or your compliance auditor asks questions three years from now.

This process runs from September through December. For a firm with 80 clients subject to RMDs, it’s 60 to 80 hours of work spread across four months. That’s two full weeks of someone’s calendar. And next year, you do it again.

Why Spreadsheets and Calendar Reminders Break Down

Most firms start with a shared spreadsheet. Column A is the client name, column B is the birthdate, column C is the IRA balance, column D is the life expectancy factor, column E is the RMD amount. Someone updates it once a year. It works until it doesn’t.

The first failure mode is version control. Two people open the file at the same time. One person updates the balance for client A, the other updates the balance for client B, and when they both save, one set of changes disappears. You don’t notice until a client calls in January asking why their RMD letter showed the wrong amount.

The second failure mode is formula drift. Someone copies a row, forgets to update the cell reference, and now 15 clients are calculating their RMD using the same life expectancy factor. The error is invisible until you spot-check the math.

The third failure mode is scope creep. A client has three IRAs. Do you calculate three separate RMDs, or aggregate them? The IRS says you can aggregate across IRAs but not across inherited IRAs. Your spreadsheet doesn’t enforce that rule. Someone on your team aggregates everything, and now the client is under-distributing from the inherited account.

Calendar reminders don’t solve the problem. You set a recurring task for October 1: “Run RMD calculations.” The task pops up, you assign it to someone, they do the work, and you mark it complete. But the task doesn’t tell you which clients are new this year, which ones turned 73 since last October, or which ones rolled over an inherited IRA in March. You’re still manually filtering your CRM and cross-referencing custodian data.

The firms that scale past 200 households usually build a database or buy RMD-specific software. The database approach works if you have someone on staff who can write SQL queries and maintain the schema. The software approach works if the vendor integrates with your custodian and your CRM. Both options cost money and require someone to own the system. And both still require human review of every calculation before it goes to the client.

What an AI Agent Does Instead

An AI agent doesn’t replace the IRS rules. It automates the repetitive work of applying those rules to your client base. Here’s what that looks like in practice.

The agent connects to your CRM and your custodian feeds. Every week, it scans for clients whose age or account structure changed. A client turns 73 in November. The agent flags them in August and adds them to the RMD workflow. A client inherits an IRA in June. The agent reads the beneficiary designation, determines whether the 10-year rule applies, and sets a reminder to calculate the first required distribution.

In September, the agent pulls the prior year-end balance for every IRA subject to RMD. It looks up the correct life expectancy factor based on the client’s age and the account type. It runs the calculation and generates a draft notification. The draft includes the RMD amount, the deadline, the withholding options, and a link to schedule a call if the client has questions. The agent queues the notification for your review.

You open the queue and see 60 draft emails. You spot-check five of them. The math is correct, the tone matches your firm’s voice, and the withholding language is accurate. You approve the batch. The agent sends the emails and logs the activity in your CRM.

In November, the agent checks the custodian feed again. It identifies which clients took their distribution and which ones didn’t. For the clients who didn’t, it drafts a follow-up email. The follow-up is shorter and more urgent. You review it, approve it, and the agent sends it. The agent also flags any client who’s still outstanding in mid-December so you can call them directly.

In January, the agent generates a summary report. It shows how many clients were subject to RMD, how many took their distribution on time, how many needed a follow-up, and how many missed the deadline despite two reminders. You file the report with your compliance documentation. If a client calls in February asking why they owe a penalty, you pull up the CRM notes and show them the two emails you sent in September and November.

The agent doesn’t make judgment calls. It doesn’t decide whether a client should take the RMD in cash or reinvest it. It doesn’t advise on QCDs or Roth conversions. It handles the mechanical work of identifying who needs to take a distribution, calculating the amount, and sending the reminders. You still own the client relationship and the advice.

This is what we call an Advice Document Agent in the Omni ops framework. It drafts compliance-sensitive communications from structured data and firm templates. The same agent that writes SOAs and ROAs can write RMD notifications, beneficiary update letters, and annual review summaries. You train it once on your firm’s style and compliance requirements, and it applies that training across every document type.

The Workflow in Detail

Let’s zoom in on what happens month by month.

January through March: The agent monitors account activity. A client rolls over a 401(k) to an IRA. The agent updates their profile and notes that they’ll be subject to RMD once they turn 73. Another client’s spouse passes away, and they inherit an IRA. The agent reads the beneficiary designation, determines the distribution rules, and sets a flag to calculate the first RMD next year.

April through June: The agent pulls year-end IRA balances from the custodian. It reconciles any discrepancies between the custodian data and your CRM. If a balance looks wrong (a client had $500,000 last year and $50,000 this year), the agent flags it for manual review. You investigate, discover the client moved the account to a different custodian, and update the CRM. The agent re-pulls the correct balance.

July through August: The agent generates a preliminary RMD list. It includes every client who will be 73 or older by December 31, plus every client with an inherited IRA subject to annual distributions. It calculates the RMD for each account and queues the notifications. You review the list in early August, make any adjustments (a client is planning to retire in October and will take a large distribution then), and approve the batch.

September: The agent sends the first round of notifications. Each email is personalized with the client’s name, the specific IRA accounts, the RMD amount, and the deadline. The email includes a calendar link to book a call if the client has questions. The agent logs every email in the CRM and sets a follow-up task for November.

October through November: The agent monitors custodian activity. As clients take their distributions, the agent marks them complete and removes them from the follow-up queue. For clients who haven’t acted by early November, the agent drafts a second email. You review and approve it. The agent sends it and logs the activity.

December: The agent flags any client who’s still outstanding two weeks before year-end. You call them directly. Most take the distribution in the final week. A few don’t. The agent documents the outcome in the CRM.

Year-end: The agent generates a compliance report. It lists every client subject to RMD, the amount calculated, the dates you sent notifications, and whether the client took the distribution. You file the report with your annual compliance documentation.

The entire workflow runs with minimal human input. You review the preliminary list in August, approve the email batches in September and November, and make phone calls in December. The agent handles everything else. Your paraplanner isn’t spending 15 hours a month on RMD tracking. They’re spending two hours reviewing the agent’s work.

What This Unlocks for Your Firm

The immediate win is time. You’re reclaiming 60 to 80 hours per year that your team was spending on RMD calculations. That’s a week and a half of capacity. You can onboard three more clients, prepare for six more reviews, or give your team a week off in December.

The second win is consistency. The agent applies the same calculation method to every client. It doesn’t forget to adjust for inherited IRAs. It doesn’t mix up the life expectancy tables. It doesn’t send a notification to a client whose IRA is already empty. The error rate drops to near zero.

The third win is proactive service. Clients receive their RMD notice in September, not November. They have time to plan the distribution, decide on withholding, and coordinate with their CPA. You’re not chasing them in December when they’re traveling or distracted by the holidays. The clients who want to do a QCD have time to work with their custodian. The clients who want to reinvest the distribution have time to review their portfolio allocation.

The fourth win is compliance confidence. Every notification is logged. Every follow-up is documented. If a client misses the deadline and blames you, you pull up the CRM notes and show them two emails and a phone call. If your compliance auditor asks how you manage RMD tracking, you show them the agent workflow and the year-end report. You’re not relying on someone’s memory or a spreadsheet that might have been updated.

The dollar impact scales with your client base. A firm with 80 clients subject to RMD saves $20,000 to $30,000 per year in staff time. A firm with 200 clients saves $50,000 to $70,000. A firm with 400 clients saves over $100,000. That’s recurring savings every year, because RMD season never goes away.

But the bigger impact is strategic. You’re no longer constrained by the manual work of RMD tracking. You can take on more clients without hiring another paraplanner. You can grow your book from 150 households to 250 without adding headcount. The agent scales with you. See Omni for financial advisory firms to understand how this fits into the broader automation picture.

How This Connects to the Rest of Your Ops

RMD tracking is one workflow. It sits alongside meeting prep, advice documentation, client onboarding, and portfolio rebalancing. The same agent framework that automates RMD notifications can automate all of them.

A Meeting Prep Agent pulls portfolio performance, recent emails, and goal progress into a one-page brief before every client review. You walk into the meeting knowing exactly where the client stands. You’re not scrambling to remember whether they’re still funding their grandkids’ 529 or whether they mentioned selling the rental property.

An Advice Document Agent drafts your SOAs and ROAs from meeting transcripts and your compliance templates. You review the draft, make edits, and send it to the client. The cycle time drops from three weeks to three days. Your paraplanner isn’t spending $5,000 of their time on a single advice document.

A Client Onboarding Agent runs the fact-find with new clients, collects KYC documents, and prepares a clean onboarding pack for you. The client completes the process in a week instead of six weeks. They don’t lose momentum. You don’t lose the relationship.

These agents share the same infrastructure. They connect to the same CRM, the same custodian feeds, and the same document templates. You train them once on your firm’s voice and compliance requirements. They apply that training across every workflow. You’re not buying five different software tools and stitching them together. You’re deploying one agent platform that handles the full spectrum of advisory operations.

What the Audit Looks Like

The Omni Audit is 60 minutes. You bring your ops reality. I bring the agent framework. We walk through three workflows where your team is doing manual work that an agent can handle. RMD tracking is usually one of them. Meeting prep and advice documentation are the other two.

We don’t build anything in the audit. We map the current state, identify the highest-value automation targets, and estimate the time and cost savings. You walk away with three things: a process map of your RMD workflow, a draft agent spec that shows what the automation would do, and a cost-benefit model that ties the savings to your P&L.

No deck. No sales pitch. No hand-waving about AI’s potential. We’re looking at your specific workflows and your specific numbers. If the math doesn’t work, I’ll tell you. If it does, you’ll know exactly what to build and what it’s worth.

Most firms that go through the audit see a 12 to 18 month payback on the agent build. The savings come from three places: reduced paraplanner hours, faster client onboarding, and higher adviser capacity. For a firm doing $3M in revenue, the typical annual leakage from manual RMD tracking, meeting prep, and advice documentation sits between $70,000 and $200,000. That’s the recurring cost you’re paying every year to do work an agent can handle.

The audit is free. You’re paying with an hour of your time. If you decide to move forward, we scope the build and give you a fixed-price proposal. If you don’t, you keep the process maps and the agent spec. You can build it yourself, hire someone else to build it, or file it away and come back in six months.

The firms that get the most value from the audit are the ones that bring specifics. Don’t tell me RMD tracking is painful. Tell me you have 120 clients subject to RMD, your paraplanner spends 12 hours per month on it during the busy season, and you missed two distributions last year because the follow-up email didn’t go out. That’s the level of detail we need to build an agent that actually works.

The practical next step is the free Working With Claude field guide. Thirty-two pages covering the ecosystem, Claude Code, and how to govern a rollout properly. Get your copy.

Why This Matters Now

The IRS isn’t making RMD rules simpler. SECURE 2.0 added new age thresholds, new exceptions for Roth 401(k) accounts, and new penalty relief provisions. The 10-year rule for inherited IRAs is still generating confusion three years after it took effect. Your team is spending more time, not less, keeping up with the changes.

At the same time, your client base is aging. The leading edge of Gen X is turning 60. In five years, they’ll be subject to RMD. Your book is about to double the number of households that need annual distribution tracking. If you’re handling it manually today, you won’t be able to handle it manually in 2030.

The firms that automate now will absorb that growth without adding headcount. The firms that don’t will hit a capacity wall. You’ll either turn away new clients, hire more staff, or burn out your existing team. None of those options are good.

This isn’t a technology problem. It’s an operations problem. You’re running a service business that depends on skilled people doing repetitive work. AI agents let you keep the skilled people and eliminate the repetitive work. The math is straightforward. The build is straightforward. The only question is whether you move now or wait until your competitors have a two-year head start.

RMD tracking is the entry point. It’s visible, it’s recurring, and it’s easy to measure. Once you automate it, you see how the same framework applies to meeting prep, advice documentation, and client onboarding. You start thinking about your entire ops stack as a series of agent-automatable workflows. That’s when the real leverage kicks in.

Start with the audit. Bring your RMD workflow. We’ll map it, spec the agent, and show you the numbers. If it makes sense, we build it. If it doesn’t, you’ve lost an hour. The firms that are winning right now are the ones that took the hour.