Applied AI and the Hundred-Year Advisory Relationship

Multi-generational wealth advice is the most personal, judgment-heavy work in finance. The question isn't whether to automate it, but where AI carries the weight and where a human still has to.

Keith Pattison

Keith Pattison

June 24, 2026 4 min read
A tree whose roots branch into smaller trees, with a human hand tending one tangled branch

The work that doesn't scale

The hardest promise in wealth management is continuity. A family hires an advisor not for a quarter or a year but for generations — to know that the trust structure set up for the grandparents still makes sense for grandchildren who haven't been born yet, to remember why a particular asset was never sold, to recognize the moment a twenty-five-year-old heir is about to make the same mistake an uncle made in 1998.

That kind of memory and judgment is exactly what doesn't scale. It lives in the head of one or two senior people. When they retire, or when the family grows from one household to nine, the relationship thins out. Reviews get shallower. Context gets lost between the estate attorney, the tax team, and the next-generation members who were never in the original meetings. The firm that sold a hundred-year relationship is quietly delivering a five-year one, renewed by hope.

The instinct is to reach for software that promises to "automate the advice." That instinct is wrong, and it's worth being precise about why.

Why robo-advice is the wrong answer

A robo-advisor solves a problem these families don't have. It allocates a portfolio cheaply against a risk score. But multi-generational advice is not a portfolio problem — it's a context problem. The value is in remembering, connecting, and anticipating: this child is about to start a business, that property has sentimental weight the spreadsheet can't see, this gift triggers a conversation about values, not just gift-tax exemptions.

When you automate the judgment itself, you get advice that is confident, fast, and occasionally catastrophic — because the cost of being wrong about a family's wealth is enormous and often irreversible. The right frame is not rules versus humans. It's separating the two. Build a rules engine that handles what is genuinely mechanical — deadlines, document assembly, threshold checks, surfacing what's changed since the last review. Keep a separate judgment engine, and keep a human inside it, for anything where being wrong is expensive.

Applied AI earns its place in the first category and as preparation for the second. It can read every document a family has ever signed and answer, in seconds, "which entities hold real estate in this state?" It can watch for the events that should trigger a human conversation. It can draft the first version of a review so the advisor edits rather than assembles. What it should not do is decide.

Start where judgment is expensive and repetitive

The place to begin is the work that is both high-stakes and maddeningly repetitive: preparing for the annual family review. Today a senior advisor spends days reconstructing context — pulling statements, re-reading the estate plan, remembering what was promised last year. It's expensive judgment spent on retrieval, not on actual advising.

In two days you can stand up something narrow and real. Point an AI layer at the family's own documents and meeting notes — nothing else. Have it produce, for each upcoming review, a structured brief: what changed, what's coming due, which decisions from last year are still open, and which life events suggest a conversation. Every claim links back to the source document, so the advisor can trust it at a glance or catch it when it's wrong. That explainability is what turns a tool from a liability into a teammate. An advisor will adopt something they can audit; they will never adopt a black box that occasionally invents a trust.

Do that, and the senior person's scarce judgment moves from reconstruction to the conversation itself. The relationship gets deeper, not thinner, as the family grows — because the memory now lives in a system the whole team can see, instead of in one person who will eventually leave.

The hundred-year relationship was always a systems problem disguised as a staffing problem. AI doesn't replace the advisor at the center of it. It makes that advisor possible to scale.

Black Flag Design builds applied-AI products for teams whose judgment is their product. If you're trying to scale a relationship that depends on memory and trust, spend two days with us — we call it a Foundation Sprint.

About the author

Keith Pattison
Keith Pattison

Founder, Black Flag Design

Keith leads Black Flag Design, a studio that ships production-ready software with AI-assisted development. He writes about the disciplines — small scope, weekly evidence, and human oversight — that keep AI-built systems reliable in the real world.

Related stories

More from the journal

Pen-and-ink sketch of a small clockwork robot working at a tool-covered workbench late at night while a human sleeps peacefully on a couch in the background, a wall clock reading 2:00 above
ai April 24, 2026 13 min read

The Agent Stays Up Late, Not Me

Every senior engineer knows the right way to set up a codebase. None of them do it. Here’s the four-stage framework we use — The Ratchet — to take a vibe-coded project all the way to a thing you’d trust in production, and the punchline about why this only just became worth doing.

Most teams have always known they should be running tests, type-checking, security audits, accessibility checks, dead-code analysis, prose linting, and a coverage floor. Most teams run two of those. Here’s why that math has finally inverted, and the four-stage framework we use to ratchet a vibe-coded project to a hardened one.

Keith Pattison

Keith Pattison

Founder, Black Flag Design

Read
Black Flag Journal
claude code April 20, 2026 5 min read

What a Year of Claude Code Trails Tells You About Your Team

Claude Code leaves evidence — sessions, commits, PRs, review notes. Read it like a logbook and you'll find what devs actually need to know before they go deeper.

After a year of shipping with Claude Code across real client work, the signal isn't in any single session — it's in the trails. Here's what those trails told us about where Claude Code shines, where it drifts, and the habits devs should build before they lean in harder.

Eli Wood headshot

Eli Wood

CEO, Black Flag Design

Read
Black Flag Journal
playbook April 20, 2026 6 min read

The Black Flag Playbook: Six Principles for Shipping with AI

Battle-tested principles for teams building real software with AI-generated code. Human judgment, tight scope, and weekly evidence — the disciplines that keep AI-built systems reliable.

The six rules we use to ship production software with AI. Small scope, weekly demos, human-led oversight, and continuous improvement — drawn from six months of real client engagements.

Keith Pattison

Keith Pattison

Founder, Black Flag Design

Read