The system

The rules, the record,
and the procedures.

The Operating System is the foundation layer of a Lean Family Office. The rules: who decides what, and up to what limit. The record: what the family owns, owes, is due to do, and has already decided. The procedures: how the work that repeats gets done.

The test is not whether the office owns documents. The test is whether recurring work can move from trigger to completion without relying on one person’s memory to provide the orchestration.

See it inside membership Take the assessment →

A precision worth making

The system, not the software.

A workbook, an application, a well-kept set of documents, these are ways of holding the Operating System. None of them is the thing itself.

A family with disciplined procedures and a plain spreadsheet has an operating system. A family with an expensive platform and no written decision rights does not. The interface below is how we hold it; what matters is that the rules, the record and the procedures exist and are current.

The Circle 26 operating system, showing net worth across entities, cash runway, monthly close status, open exceptions, and the actions due this week, this month and this quarter. — One view of the record and the work due. The rules, the register and the procedures sit behind it.

Three ways to get one

Same system.
Different amount of us.

The Operating System is the same in every case. What varies is who does the building.

Do it yourself

The Blueprint, the templates and the operating system, worked through at your own pace. Many capable operators can do this.

Membership →

Do it with us

The same method, worked through together in the Monthly Sessions, with a room of people doing the same job at the same time.

Peer Circle →

Do it for you

Built with your advisers and your data, then handed over to your people. Fixed fee, defined scope, no dependency at the end.

Implementation →

What it holds

What the operating system holds

Wealth data platforms answer one question: what is it worth today. The operating system answers the questions that actually run an office.

What wealth dashboards show, compared with what the operating system holds
What wealth dashboards show	What the operating system holds
A portfolio summary	Every entity, asset, adviser and obligation, in one place
A net-worth figure	What's due, and when: filings, renewals and capital calls, across every jurisdiction
Account balances	Who's allowed to do what: thresholds and decision rights, documented
Performance charts	What was decided, and why: the decision record, kept as decisions are made

Scroll the table sideways on a narrow screen.

One is a reporting layer. This is the operating layer: the part no wealth platform has built, because coordination was never their job.

One place

One place for the whole picture

The wealth map

Every entity and what it holds, across every jurisdiction, on one canvas: the structure that usually lives only in the principal's memory, drawn once and kept current.

The obligations calendar

Filings, renewals, capital calls and review dates, consolidated across advisers and jurisdictions, so nothing surfaces as a surprise.

The authority register

Who can approve what, up to what limit, and who acts in whose absence: the decision rights of the office, written down.

The decision record

What was decided, when, and why, kept as decisions are made, so the reasoning survives the meeting.

How work moves

From trigger to close.

A recurring workflow is complete when the office can define:

Trigger: what starts the work?
Inputs: what information is required?
Owner: who is accountable for completion?
Rules: what can happen without escalation?
Sequence: what happens next?
Decision points: where is judgement required?
Escalation: what reaches the Principal?
Evidence: what proves completion?
Record update: what changes in the source of truth?
Close condition: when is the workflow actually finished?

A written procedure is useful.

A closed-loop workflow is what makes the office run.

Worked example

A capital call, twice.

The same event, run without a defined workflow and with one. The difference is not effort. It is whether the steps were defined before the notice arrived.

Without a workflow

Six steps, four of them the Principal.

01 Notice arrives Usually by email, to whoever the fund has on file.
02 Principal reconstructs Which fund? Which entity? How much is left to draw?
03 Principal checks cash Is the money there, or does something need to move?
04 Principal approves Because no rule says who else may.
05 Principal forwards Evidence sent on, by hand.
06 Someone remembers Or does not, and the register drifts.

With a defined workflow

Ten steps, one of them the Principal.

01 Notice received Arrives at a monitored destination, not an inbox.
02 Investment and entity A lookup against the register, not a question.
03 Commitment validated Called amount checked against what remains.
04 Liquidity checked Confirmed at intake, not at payment.
05 Authority rule applied The written rule decides what happens next.
06 Principal decides Only when the rule says so.
07 Payment executed Through the agreed channel and controls.
08 Evidence stored Filed against the investment.
09 Register updated Remaining commitment adjusted. The step most often missed.
10 Workflow closed The sequence has a stated end.

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

The principal interface

What should reach the Principal?

A Principal should not need to live inside every register, workflow and task. The operating system should compress its output into five states.

Decide: Judgement or approval is required.
Know: Material information, no action required.
Exceptions: Something is outside the rule.
In progress: Significant work is being handled.
No action: Everything else stays inside the system.

The purpose of the operating system is not to remove the Principal from control. It is to stop using the Principal as the routing layer.

Ownership

Where the record lives

Many systems a family relies on belong to someone else: the bank, the platform, the adviser. They serve the relationship, and they end when it does.

The operating system is different by design. The family’s data and completed client-specific records remain with the family in usable formats. Circle 26 retains its intellectual property in the underlying Blueprint, frameworks and templates, which are used inside the family office under the applicable terms. It runs on infrastructure the family controls.

The record you build stays with the family, in formats you can use without us.

A foundation

A foundation, not a finished box

This is the part families often underestimate. The operating system is not a fixed product you adopt as-is. it is a foundation you build on.

It begins as your single source of truth: structured, organised, and complete. From there, it grows with the office. New entities, new asset classes, new jurisdictions, new registers: the system extends to hold them. As your family's needs become more sophisticated, so does what sits on top of it.

Because the foundation is open and owned, what you build on it is your choice. Circle 26 members get more than the system: they get the use cases, the monthly sessions, and the growing library of guidance on how to extend it: how to connect it to the tools the family already uses, how to shape it around a workflow that's genuinely yours, how to take it further than a fixed product ever could.

We give you the foundation and the standard. What you build on top is yours to decide.

Owned, portable, living

The system should survive people, providers and change.

Ownership matters because the family should be able to change a bank, adviser, software tool or service provider without losing the operating record that makes the office intelligible.

Portability is only one part of durability. The system also needs to stay current.

Entities change. Authority changes. Advisers change. Obligations change. New workflows appear. Old ones stop being useful.

A Lean Family Office therefore needs a review rhythm: test the record against reality, capture exceptions, update the method and keep the system proportionate to the complexity it serves.

A system that is owned but stale is not resilient. A system that is current but trapped inside one provider is not portable. The goal is both.

Security

The security posture

The whole design rests on one principle: the family stays in control of its own record.

Your data lives in the environment the family chooses and controls rather than in a shared Circle 26 client database. That reduces dependency on Circle 26 as a hosting provider and makes portability easier. Security still depends on the family’s chosen infrastructure, access controls, configuration and operating practices.

Questions

Questions families ask

Is this connected to my bank accounts?

Your custodians already show you balances in real time. The operating system holds everything they don't: entities, authority, obligations, mandates and decisions, none of which comes from a feed. How the numbers get in, and how far you automate that, is one of the things members choose and build toward over time.

Do we own it, or subscribe to it?

The family's data and completed operating records remain under family control. The underlying Circle 26 frameworks and templates remain Circle 26 intellectual property and are used under the applicable membership or Services Agreement terms.

Can we extend it ourselves?

Yes. That's the point of a foundation. Members get the guidance, use cases and Monthly Sessions to shape the system around how their office actually runs, and to build on it as needs grow. You are never limited to a fixed set of features someone else decided on.

Who keeps it current?

Your operator, in the ordinary rhythm of running the office. For clients on the annual governance refresh (Implementation & Continuity), Circle 26 verifies the record against reality and helps the system keep pace as the structure changes.