Installation

Start with one working pair.

A ten-week installation across the real work between one senior reviewer and one producer. The scope is deliberately small. The capability being tested is whole.

Talk to us →

Fixed fee · scoped up frontNo software deploymentNo systems integrationNo subscription

01 · The unit

The capability lives in the working relationship — not in one workflow.

The recurring reviewer–producer relationship is where consequential work is framed, produced, challenged, relied upon, redirected, and learned from. One memo can demonstrate a template. It cannot demonstrate a durable way of working.

In many expert-led firms, the reviewer and producer are a partner and an associate. Elsewhere the titles differ; the functional relationship is the same.

02 · Fit

Fit the discipline around the work — not the work around the discipline.

What stays the same

The active client, deal, case, or advisory work
Expected decks, memos, models, and recommendations
Existing review gates and cadence
The pair’s normal accountability
The firm’s approved AI environment
Specialist systems already in use

What changes

How the real problem is framed
How the inquiry is steered — without deferring to the model
When the work commits to an artifact
What state travels with the work
Where senior attention is spent
What judgment survives the review

The client still receives the professional artifact they expect. The operating system beneath and around it changes.

03 · Technology fit

Use the AI environment your firm already approves.

re:compound requires access to a current frontier model and is otherwise model-agnostic. It sits above the specialist tools your teams already use — Harvey at a law firm, for instance — integrating their output into the larger inquiry and review system.

re:compound sits above the tools.

No re:compound application
No API integration required
No new database or data connection
Nothing new for IT to security-review
Runs as project- or firm-level model instructions

04 · Practical answers

The questions your management committee will ask.

What does it cost?: The fee is scoped and fixed before we start — if the ten weeks slip, the fee doesn’t. It is sized to be absorbed by the budget of the engagement the pair is already working. We quote it after the fit conversation, once we have seen the pair and the work.
What technology do we need?: A current frontier model inside the AI environment your firm already approves. The system is model-agnostic and sits above your specialist tools, integrating their output rather than replacing them.
What will IT and security need to review?: Nothing new. There is no re:compound software, no API integration, no new database or data connection. The assets are plain-language instructions that run inside your approved environment, under your existing controls.
What about confidentiality?: The installation runs under your confidentiality terms, inside your tools, on your work. Protected workspaces remain firm-owned and subject to your ordinary policies; nothing routes through re:compound systems.
Won’t producers game the State of the Work?: The system is designed to make honesty instrumentally rational. Properly surfaced uncertainty is treated as evidence of governance — hidden uncertainty is the concern — and review is kept distinct from performance evaluation precisely so the state stays honest. Ownership is then tested live, in conversation. The evidence map is also not the whole visible world — the reviewer’s AI samples the underlying work beyond it, so what the producer chose to surface is itself testable.
Is this a fraud or misconduct control?: No. The discipline is designed for honest fallibility — well-intentioned people and models producing work whose polish outruns its support. Deliberate deception remains what it has always been: a conduct matter under the firm’s existing policies, which the installation doesn’t replace.
Can we speak to past clients?: We don’t name clients — the same protected-workspace stance that will cover your work. References are available in conversation, subject to client consent.
Who delivers it?: The founders, personally. That is why we take a small number of installations at a time.

05 · The 10-week arc

Observe. Co-run. Withdraw.

Support descends as the pair’s independent capability rises.

WEEKS 1–2

Observe the real system

Current and prior work, working meetings, review gates, reviewer judgment, AI use, and what the culture rewards or suppresses.

WEEKS 3–7

Configure and co-run

The pair learns the operating method, shared surfaces, and model-side assets through live production and review, with substantial hands-on support. One to two hours a week of structured instruction — the larger installation happens inside the work itself.

WEEKS 8–10

Transfer and withdraw

Responsibility moves to the pair. The installation succeeds when they can operate the discipline without us.

We watch closelyWe run it togetherYou run it while we watchYou run it

06 · What gets installed

A working capability, supported by operational assets.

A working method

Moves for framing, steering, integrating, committing, reviewing, and compounding — practiced until they hold under pressure.

The State of the Work

The flagship shared surface — with the evidence map, the Partner Attention Brief, and the decision + direction note around it.

Model-side assets

Plain-language operating frameworks the pair’s AI runs, fitted to the firm’s work, language, standards, and tools — and versioned and maintained like software.

The habit

Habits that hold under deadline, uncertainty, hierarchy, and real stakes.

The assets remain.

Configured model-side assets stay licensed to the organization for continued internal use after we leave. There is no recurring re:compound software license and no required advisory annuity.

07 · Real work

Installed on real work, not in a sandbox.

The deadline has to matter. The evidence has to be imperfect. The reviewer has to bring real priors. Someone has to act on the result.

re:compound works under the organization’s confidentiality terms and inside its approved tools and controls.

08 · Working rhythm

Learning inside work already underway.

The pair spends approximately one to two hours each week in structured instruction. The larger installation happens inside ordinary production and review.

The discipline is designed to replace hidden rework and inefficient reconstruction — not to add permanent process.

09 · Success

Installed means independent use.

Not attendance. Not artifact counts. Not continuing dependence on re:compound. So far, every completed installation has cleared this bar — and led to the next one.

The assets stay. The capability stays. re:compound leaves.

The pair invokes the machinery without prompting.
Review events surface what the old interface missed.
The producer demonstrates genuine ownership.
Direction changes the next interval of work.
The pair continues autonomously.
Additional pairs ask to extend it.

A practical first step

Identify the pair and the live work.

The right first pair has consequential work underway, a real review relationship, and enough willingness to operate differently for ten weeks.

Test the fit →