Microsoft 365 · Power Automate · No external AI
I'm a Senior at the Univeristy of Tampa. Over the summer I built two agents that now run every morning inside a wealth advisory practice's own Microsoft 365 tenant — no outside AI services, no client data leaving the firm. Here is exactly what one of them does.
When a message arrives
Where it goes
The work
Both were built on the firm's own approved toolchain and against the compliance constraints a registered advisory practice actually operates under. They run on the firm's systems and belong to the firm — what I'm describing here is the approach, not anything I carried out the door.
Every incoming message is checked against the client roster the firm already maintains, then filed by relationship tier before the adviser opens Outlook. Priority messages stay unread — the system sorts the inbox, it never decides something has been handled. Messages of lower tier clients get routed to other advisers or colleages for handling, with a note.
The CRM sends a birthday digest each morning; some of it is other people's clients. The agent reads it, confirms which names are assigned to that adviser, and drafts a personal note to those clients only. It sends nothing for a client it can't positively match — an unmatched name is a silent skip, not a guess.
How it works
There's no model making judgment calls about your clients. It's a sequence of rules that runs in your tenant, and you can read every one of them.
A spreadsheet the practice already keeps — client, tier, assigned adviser. It lives in your OneDrive and never moves.
A message hits the inbox, or the CRM sends its morning digest. That's the trigger — no polling, no separate app to open.
The sender or name is checked against the roster. A match determines the route; no match means the message is held, not acted on.
File, flag, notify, or send. Every run is logged, and a failure raises an alert rather than passing silently.
Worth saying plainly
Who I am
I'm a senior at the University of Tampa studying Finance. Over the past months an advisory practice handed me a real problem, real access to how the day actually runs, and allowed me to help. That's the only reason any of this exists, and it's not a small thing to have been trusted with.
Most of the work wasn't code. It was sitting with how a practice really triages a morning's mail, and then building something that respects it. I'm careful about compliance because I had to be — the constraints came first and the architecture came second, and that turned out to be the right order.
I'm open to project work and to full-time roles after I graduate. If you're an adviser losing an hour a day to sorting, that's the conversation I'd like to have.
Get in touch
noah@noahrychlick.com