Operations

One operation.
An entire book of work.

Where a mission is one finite job, an operation is a standing workflow you set up once. It runs your whole book in parallel, a mission per client, staying ahead of every one across the tools you have connected. Keep the CRM you trust, or manage those clients directly in Invice when there is no system worth preserving. A whole book of work, running itself.

01 · Persistence

Always running. Always ready.

A mission ends. An operation does not. It is the standing agent that owns a category of work for as long as you run that work: a client book, a pipeline, a renewal calendar. It handles the roughly 80% that is operational, so only the decisions that need you reach you. A system of action over the systems of record you already keep.

02 · Composition

One parent. A mission per client.

Each client in the operation gets a dedicated mission. They share the operation’s rules, vault scope, and memory, and differ in the file they own. When one needs to coordinate a resource, it spawns a sub-mission of its own. You see the parent; the system runs the rest.

03 · Discovery

Auto-onboards new clients.

The trigger is usually an inbound: a client emails or submits a form, or arrives through a CSV or a CRM webhook. On each one, the operation spawns a mission for that client automatically, applies the playbook, and begins. You do not configure twice.

04 · Memory

Patterns compound.

What worked on one file informs the next. What broke on file 12 becomes a rule for file 200. The operation’s memory is your firm’s memory: discoverable, exportable, yours.

How the pieces fit

One operation,
a cascade of work.

An operation sits at the top, watching every inbound. Each one becomes a mission that handles a single client, and a mission spawns a sub-mission when it needs to coordinate a resource. A mission can also start on its own, straight from you.

A two-way workspace

Ask, plan, remind.
Your agent is listening.

The agent is not a black box. Talk to it the way you would a teammate. Ask what is outstanding, request a follow-up, plan a reminder, or leave a note about a client. Every answer is grounded in your vault, and the panels stay live as your book moves.

Mortgage file coordinationLive

What is still outstanding on the Patel file?

Closing is 12 days out. I have the appraisal and the bank statement in the vault. Still missing the signed disclosure and an updated pay stub. I emailed Patel this morning and set a reminder to chase again Thursday.

Book calls with anyone who has gone quiet this week.

Three clients are past five days: Lee, Brar, and Mendez. I offered each three slots from your open calendar. Lee and Brar are booked for tomorrow. Mendez has not opened the last two emails, so I am holding that one for you.

Send the spring rate update to my active files.

Drafted and personalized for all 214 active clients, each with their current rate pulled from the vault. It is in your review queue and sends from your Outlook the moment you approve.

ContactsAlways live
Patel, R.awaiting docs
Chen, J.call Friday
Mendez, A.needs you
Documents3 open
Disclosureawaiting
Pay stubawaiting
Appraisalreceived
Activitytoday
Follow-up sentLee, K.
Notary bookedFri 2pm
Statement pulledSingh, P.
A worked example

Mortgage broker.
A whole book. One operation.

A single operation manages an entire book of mortgage files. Each client file is a sub-mission that knows the lender, the timeline, the notary preference. The operation chases documents, books closings, escalates the calls that matter. The broker reviews a handful of decisions a day instead of a flood.