What does an AI install at an RIA actually look like
Three days on-site at the firm's office, then 90 days of remote operation. The on-site days are the dig, the wiring, and the handoff. Most of the work happens at a conference table next to the principal — not in a Zoom window — because the install is in the firm's own folder, on the firm's own stack, and that needs the principal in the room.
Day-by-day, what actually happens
Sunday — travel
The installer flies in Sunday evening. Laptops, monitors, and any access tokens that need to be hand-keyed get set up at the firm before Monday morning so the team walks into a room that's already wired.
Monday — the dig
Interviews with the principal, every team member, and a sweep of every email, document, and CRM record so the brain learns the firm. By end of day Monday there's a working map of every workflow that hits the principal's calendar.
Tuesday — the wiring
The brain gets connected to email, calendar, CRM, document storage, and the firm's compliance review flow. The first prompts are written and tested against real cases. By Tuesday afternoon the firm can run a meeting prep through the brain and watch it work on real data.
Wednesday — the handoff
Every team member is trained on the workflows that touch their job. The first quarterly-letter draft, the first lead-scoring pass, and the first content piece all ship before the installer leaves. The brain is in production by Wednesday afternoon.
Days 4-90 — Lights-On
Remote operation. Weekly check-ins, prompt tuning, new workflows added as the team finds gaps. The principal always has a direct line. After 90 days the firm can either continue Lights-On month-to-month or take it fully in-house with the runbook.
What the principal has to be in the room for
- Voice training. The brain copies the principal's writing — that means the principal reads ten old letters with the installer and explains why each one sounds like them.
- Client tier sorting. Who the A clients are, who the B clients are, who you'd quietly fire — the brain needs to know.
- Compliance non-negotiables. What the principal will never say, what disclaimers always go on, what topics are off-limits.
What's intentionally not on the list
Quiet Machines does not rebuild the website. Does not migrate the CRM. Does not take over tool billing. Does not write the principal's book. The install sits on top of what already works — it does not replace the firm's stack.
What the team experiences during the three days
Day 1 is exhausting because every team member sits for an hour-long interview about how they actually do their job — not how the operations manual says they do it. The gap between the two is usually where the install finds its highest-leverage workflows. Day 2 feels quieter because the installer is heads-down wiring while the team continues normal work; the principal usually checks in for a 30-minute review at the end of the day to approve the prompts. Day 3 is loud again — every team member runs the brain on a real piece of work from their own pipeline, finds three things that are wrong, and the installer fixes them on the spot.
What "in production by Wednesday afternoon" actually means
By the time the installer leaves Wednesday, four things are running in real client data: meeting prep for the principal's next two scheduled reviews, lead scoring on every inbound from the past 30 days, a draft of the next quarterly letter, and a content piece in the principal's voice ready for compliance review. None of these are demos — they are work the firm will use that week. If any of the four isn't shipping by Wednesday afternoon, the install isn't done and the installer stays an extra day. That has happened twice in the QM history; both times it was a CRM permission issue, not a brain issue.
Sources
Three days on-site beats six months of Zoom. Free AI visibility audit →