Implementation

Have the Lean Family Office operating system built into your existing office.

We diagnose how the office works today, design the rules and ownership, build the operating record, install the recurring workflows, and hand the finished system to your people to run.

This is not us taking over your family office. It is us building the system underneath it, then handing you the keys.

The outcome

Your office should not depend on one person’s memory and availability.

Many families already have capable advisers and people around them. The problem is often the space between them.

One person still holds the full picture, routes the questions, remembers the context, follows up the work and decides what needs to happen next.

Implementation replaces that personal dependency with a documented operating system.

The Principal stays involved where judgement or approval genuinely requires them. The rest moves through the system.

The transition

Being the system, to Principal of the system.

Stage one

Being the system

Stage two

Building the system

Stage three

Principal of the system

Who this is for

Built for families who want the system installed, not another project to manage.

Implementation is a good fit when:

  • you already have people, but the office still runs on memory and instinct
  • your team is too busy running the office to redesign it
  • a liquidity event, move, succession event or other deadline is approaching
  • you want the operating layer built once, then owned and run internally

The question is not whether you have a team. It is whether the operating model underneath the team is clear, documented and transferable.

What gets installed

Five connected operating layers.

01

Rules

Who decides what, what is delegated, what escalates and what genuinely requires the Principal.

02

Record

One reliable operating picture covering entities, advisers, obligations, authority, decisions and commitments.

03

Workflows

How recurring work moves from trigger to completion, including approvals, evidence and record updates.

04

Ownership

Who owns each process, who owns the joins between advisers, and who is accountable for the whole.

05

Rhythm

The weekly, monthly, quarterly and annual reviews that keep the system current.

This is not a bundle of documents. It is a working operating layer for the office.

How it works

Diagnose. Design. Install. Test. Handover.

  1. 01

    Diagnose

    We start with the Wealth Clarity Session to understand what already works, where complexity is outrunning structure, and where the Principal or another key person is still holding the system together.

  2. 02

    Design

    We define the operating model before we build it: scope, decision rights, Operator responsibility, adviser roles, escalation rules, information ownership and recurring workflows.

  3. 03

    Install

    We build the operating layer around your existing structure. Depending on the diagnosis, that can include:

    • Delegation of Authority
    • wealth and entity records
    • adviser and obligations registers
    • compliance and review calendars
    • payment and wire controls
    • decision and commitment records
    • recurring workflows
    • Operator role definition
    • Principal briefing structure

    We build only what the office actually needs.

  4. 04

    Test

    We test whether the system works in practice.

    • Can someone find the answer?
    • Can the Operator run the workflow?
    • Do advisers know what they own?
    • Does the Principal receive only what genuinely requires them?
    • Could the office continue if one key person were unavailable for two weeks?
  5. 05

    Handover

    Your Operator or internal team takes over the working system, with the rules, records, workflows and maintenance responsibilities made explicit. The objective is that the office can run without Circle 26 sitting in the middle.

See the difference

A capital call, before and after.

Before

One decision, and all the orchestration around it.

A notice arrives. The Principal or trusted person finds the commitment, checks the entity, confirms liquidity, works out who should approve, forwards the payment instruction, stores the evidence and remembers to update the record.

The Principal appears to be making one decision. They are also supplying the workflow.

After

Ten steps, one of them the Principal.

  1. 01 Notice arrives
  2. 02 Investment and entity identified
  3. 03 Commitment validated
  4. 04 Liquidity checked
  5. 05 Authority rule applied
  6. 06 Principal involved only if required
  7. 07 Payment executed
  8. 08 Evidence stored
  9. 09 Commitment record updated
  10. 10 Workflow closed

The Principal should make the decision that requires judgement. They should not provide the orchestration around it.

What changes for the Principal

Control without being the routing layer.

Before implementation

  • questions travel through you
  • context lives in memory
  • routine approvals reach you
  • advisers depend on you to connect the dots
  • follow-through depends on you noticing

After implementation

  • rules determine what reaches you
  • one operating record holds the context
  • the Operator owns follow-through
  • recurring work follows defined workflows
  • exceptions travel upward
  • decisions arrive with the right information

The goal is not less control. It is a better form of control.

What you have at handover

A working office someone else can run.

The exact build varies by family, but the finished office should have:

  • clear decision rights
  • a defined Operator role
  • one source of truth
  • mapped entities and advisers
  • a consolidated obligations calendar
  • documented controls
  • recurring operating procedures
  • defined workflows
  • escalation rules
  • evidence requirements
  • a review rhythm
  • continuity and handover instructions

More importantly, the office should know:

Who owns it. What happens next. What requires the Principal. What does not.

Your advisers

Your advisers stay yours.

Implementation does not replace your lawyer, accountant, investment manager, trustee, bank or other specialists. They keep their technical mandates.

We build the operating layer around them so:

  • responsibilities are clear
  • everyone works from a better shared picture
  • follow-through has an owner
  • the Principal does not have to connect every relationship personally

The Operator owns the joins.

Keeping it current

The build ends. The system continues.

A family office changes constantly. Entities, advisers, authority, investments and obligations all move.

At handover, we agree who keeps the operating record and workflows current. That can be:

  • your internal Operator or team
  • Circle 26 Continuity, where agreed
  • a combination of both

Membership can sit behind the people running the office as the ongoing standard, method and professional room.

The objective remains the same: capability, not dependency.

Boundaries

What we do, and what stays with your specialists.

  • We do not manage assets.
  • We do not take custody.
  • We do not sell products.
  • We do not give tax or legal advice.
  • We do not replace your investment advisers.
  • We do not become the family’s permanent day-to-day Operator.

Where specialist judgement is required, the relevant adviser remains responsible. Our role is to make sure the operating system around that work is clear, owned and complete.

Pricing

Fixed scope. Fixed fee.

Implementation is priced against a defined scope, never as a percentage of assets.

The Wealth Clarity Session comes first. Only once we understand the office do we define:

  • what needs to be built
  • what does not
  • the sequence
  • the deliverables
  • the fee

Complexity determines the work, not portfolio size.

You receive the scope and fee in writing before the build begins.

Questions

Questions principals ask

We already have a team. Is this still relevant?

Yes. A team gives you capacity. Implementation defines the operating model underneath it: authority, records, workflows, ownership and controls.

Do you install software?

The Operating System is not software. Software may hold parts of it, but the system itself is the rules, record, procedures, workflows and ownership through which the office runs.

Do we need an Operator before implementation starts?

Not necessarily. If someone already performs the role, we define and equip it. If the Principal is still filling it, implementation helps separate what should stay with the Principal from what should move into the system.

Do you replace our advisers?

No. Your advisers keep their specialist mandates. We coordinate the operating layer around them.

What happens when the build is finished?

Your Operator or internal team takes over the system. We complete the handover, define the maintenance rhythm and make clear what needs to stay current.

We do not build before we understand the office.

Start with the free assessment. If the situation warrants a proper diagnosis, the Wealth Clarity Session is the first formal step.