After the working session

The thinking, and now the proposal.

Rod, Bryce, Nick, and Marvin: thank you for the two hours on the 9th, and for the trust that led to them. What we heard is here to correct, and what you asked for is here to weigh: the crux, the options, and the proposal. Argue with all of it, then fold it into your quarterly. The decision is yours there.

How this works

React, re-rank, and edit what you see on Listen, Frame, and Envision. The Article is the longer read of our point of view; the Proposal is the ask itself. Whatever you affirm gathers, quietly, into one page you can bring with you.

Before your quarterly

One small step, already moving

{{ meetingDate }}

The working session ended in decisions: scope narrow, help Rod move first, jumpstart in the cloud while the hardware is back-ordered, and work with Kevin to integrate the firm’s Microsoft 365, and potentially other systems, with the agent. What remained was sequencing and a price; the proposal carries both.

Don’t build the whole firm’s system first. Stand up one real thing that gives Rod relief now, and let it prove itself.

Listen→Frame→Envision→The proposal→A page to keep
A Dark Horse Works point of view

The Chief of Staff You Couldn’t Afford, and the One You Can Now Build

Why the most valuable role in a modern firm was, until recently, reserved for the few, and what changes when the administrative floor beneath it can finally be held by something other than a person.

By Dark Horse Works/For Fuller IP Law/8 min read

#{{ sec.heading }}

{{ p.text }}

{{ p.text }}

{{ p.text }}
A Dark Horse Works point of view
Listen

What we heard

Mostly from the two hours in your office on the 9th, with what Marvin raised on the 6th carried forward. Sorted by whose it is, and marked by where it comes from: said to us directly, structural, decided together, or still unspoken and inferred. Affirm what lands, correct what doesn’t, set aside what we should. Open the fuller context whenever it helps.

{{ listenProgress }}
reviewed
Where we start

The chaos is structural. The two holes are capture and follow-up. The deeper diagnosis is that people are the systems, and the gate everything must pass is trust. Our read can still be wrong in the details, and the most useful thing you can do before your quarterly is tell us where: what did we get right, what did we miss, and what would you say differently?

Whose
{{ listenStepLabel }}
{{ listenCurrent.num }} {{ listenCurrent.whoLabel }} {{ listenCurrent.layer }} · {{ listenCurrent.layerNote }}

{{ listenCurrent.headline }}

{{ listenCurrent.body }}

{{ listenCurrent.detail }}
What did we miss
Frame

One problem, five costumes

First the crux as it stands after the 9th, then the problem in your own framings: re-rank them by which feels truest, and say whose problem each is. Then the turn the rest of this rests on.

The crux

One stood-up workflow before your quarterly.

The working session settled whether this can help. Now it has to convert: one stood-up, trust-earning workflow that gives Rod felt relief within about two weeks, on a substrate the firm owns, visibly moving before the off-site. Two things would quietly defeat it: enthusiasm diffusing scope back into the whole firm’s state machine, and work left unpriced, so it never becomes a real decision. The proposal is shaped against both.

3A

The problem, in your own framings

Reorder by which feels most true to the firm, by dragging a row or using the arrows. Assign whose problem each is.

The master statement

The chaos Rod feels, the silos Bryce fights, the duct-taped systems Nick sees, and the trust anxiety all three name are not five problems. They are one problem wearing five costumes: the firm has outgrown the every-attorney-is-a-kingdom model, but the substrate a real business runs on, visible state, owned processes, captured knowledge, is not installed yet. People are filling that role, and people are single points of failure.

{{ p.rank }}
drag
{{ p.code }} · {{ p.source }}

{{ p.text }}

{{ p.read }}
Whose problem is this
A way to sort the work

Not human or machine. Three places the work can live, once it is visible.

{{ b.label }}

{{ b.items }}
3B

The turn

What most firms hear

AI replaces the assistant. The firm re-hires, or it doesn’t, and either way the work shrinks to a line on a spreadsheet.

The truer frame, and you said it first

The agent promotes the human.

You framed it as AI the power tool, amplifying the craftsman. Same move, one level up: when a bounded agent holds the administrative floor, everyone climbs. The partner rises to strategy and the client craft only he can do; the person who ran the floor rises to orchestration and judgment; the associate rises to growth work. The roles do not shrink. They grow.

Why this isn’t “AI replaces a person”

The split between chief of staff up here and assistant down there was never a law of nature. It was a limit of human bandwidth: no one person could hold the relentless floor and rise to the strategic work at the same time. Redistribute the floor to a bounded system and the limit lifts. This is not removing a person. It is preserving the right human attention for the moments where trust and judgment actually matter.

The frame we’d start from

Preloaded, but yours to edit. It commits to nothing. It is just the sentence the rest would start from.
Envision

The destination, sharpened

On the 9th you collapsed the aim to a first observable (Rod unblocked) and kept the larger horizon in view. The vision is now two-layered and sequenced, not one diffuse ambition.

The beachhead First

Rod, unblocked

A read-only chief of staff that gives Rod back capture, prioritization, and follow-up: a morning brief that orients the day, an evening debrief that closes loops, and week bookends. Node one, moving before your quarterly.

Observable A follow-up that would have slipped instead lands, without Rod chasing it.

The horizon

People driving systems, not people who are systems

Nick’s state machine: the state of every matter visible to everyone, to the degree of their expertise; no human a single point of failure; Bryce’s flywheel learning each time the firm acts. The same memory substrate Rod’s chief of staff runs on grows into it.

Held In view, deliberately not first. Reached through the small first case, not around it.

“If you go too big, we’re not going to get anything done. Boil it down so it fits, so something gets done, then we keep expanding into everything we’re envisioning.”

Rod, naming the guard himself

What it looks like, ninety days in

Choose the elements that describe where this should go. Edit any that are close but not right.

{{ e.tagLabel }}

{{ e.title }}

{{ e.body }}
How we’ll know we’re there

Rod’s own success test, in his words: “You got clarity, alignment, and now you got movement.”

{{ t.title }}
{{ t.body }}

If this worked beautifully but did not immediately reduce headcount, would it still be worth doing?

What we are not claiming

A clear argument earns trust by naming its own limits. Edit these, or add your own.

{{ na.text }}
Passages you marked on the article

{{ fp.text }}
The choice

When the floor can be automated, a firm chooses: eliminate the role, or elevate the person.

The tools are identical. The firms are not. The question isn’t which vendor, or even how much it costs. It is what kind of firm you intend to be, and whether the leverage you gain protects the trust you sell.
Explore

A map to argue with

Before we decide what to build first, we mapped the candidate workflows against the dimensions that actually determine a good first proof: how much senior time it reclaims, how safely it can be trusted near client work, how measurable it is in ninety days, and how cleanly it runs behind your own firewall. Two candidate sets share the same map: your IP law-firm workflows (circles) and the EOS operating-cadence workflows (diamonds). Toggle either set, or any blast-radius band, on and off. The choice the room made on the 9th is ringed in red; the map stays for what comes after node one, and it is still a map to argue with.

Where the room landed

The map pointed at a matter-flow and open-loop copilot. On the 9th the room chose its open-loop half first: a chief of staff for Rod, read-only, on non-privileged surfaces, answering the dropped-follow-up pain where it hurts most. The matter-flow half, the “who’s got the potato” handoff, is exactly where it widens next, once trust is earned.

It lives in the green zone of both maps, needs no recording of client conversations, and can show a felt result in weeks. The proposal makes it concrete.

Dataset
Axes
Blast radius How much damage if the agent gets it wrong. Green is safe to try; red is high-exposure.
{{ plotSvg }}
How to read this

The best first proof sits up and to the right, runs often (a larger marker), and is green: high value, safe to fail, frequent, private. The flashiest work, patent drafting and live meeting capture, sits lower or redder. Real upside, wrong first step. Positions are relative rank on each axis, so no two workflows sit on top of each other; the detail card shows the underlying one-to-five scores. The red ring is node one, the chief of staff the room chose.

{{ activeBubble.zoneLabel }} · {{ activeBubble.dsLabel }}

{{ activeBubble.name }}

What it is

{{ activeBubble.what }}

Why it matters

{{ activeBubble.why }}

For example

{{ activeBubble.example }}

{{ sc.label }} {{ sc.val }}
The metric it would move {{ activeBubble.metric }}
Read a workflow

Hover or tap any workflow on the map to see what it is, why it matters, an example, its seven scores, and the one metric it would move.

Circles are IP law-firm workflows; diamonds are EOS operating-cadence workflows. The red ring is node one, chosen on the 9th.
The proposal

A chief of staff for Fuller IP

The concrete shape of what we discussed, with a plain price on it. A starting point, not a contract.

Dark Horse Works × Fuller IP Law · a charter engagement

A chief of staff for Fuller IP

Prepared for Rod Fuller, Bryce Burnham, Nick Gerovac, and Marvin Pearce · following the working session · an input to your quarterly planning

What we heard

You’re a firm becoming a business, and the chaos you’re feeling is structural, not personal. Rod named it plainly: the ideas are all there, but capture and follow-up can’t both be held at once, and the follow-up is where things quietly die. Nick named what sits underneath it: a lot of your systems are people. Libby is a system right now; if she’s out, that system is out. The firm has outgrown the model where every attorney is a kingdom, but the substrate a real business runs on, visible state, owned processes, captured knowledge, isn’t installed yet.

And under all of it, the thing Rod said is the whole issue of everything: trust. It’s what your clients pay for, the currency that lets the partners move fast together, and the gate any new system has to earn its way through.

The one idea

Don’t build the whole firm’s system first. Stand up one real thing that gives Rod relief now, and let it prove itself.

That first workflow is both the relief Rod needs this quarter and the first node of the state machine Nick described. The same memory foundation grows into everything else. You said the guard yourself, Rod: if you go too big, we’re not going to get anything done.

Where you are, and where this goes

Think of a chief of staff as a ladder. Most firms can only afford to put one human on the bottom rung, and only for the person at the very top. Because your chief of staff is an owned system rather than a scarce hire, every partner can climb the whole ladder over time, and you only pay for the rung you’re actually on.

Today Below the ladderThe EA left, and the chief-of-staff function collapsed back onto Rod. He’s doing his own air-traffic control, and it’s costing the firm its highest-value time.
Phase 1 The principal’s chief of staffWe give Rod back capture, prioritization, and follow-up: a morning brief that orients the day, an evening debrief that closes loops, and week bookends, running on a private model, reading only what Rod chooses to give it. The test is simple: Rod’s A-items rise to the top, and a follow-up that would have slipped instead lands, without Rod chasing it.
Phase 2 The matter-flow integratorOnce Rod’s chief of staff is trusted, the same substrate widens to the handoff: the “who’s got the potato” chase across the four to six hands a matter passes through. State becomes visible to everyone, to the degree of their expertise. People stop being systems and start driving them.
Phase 3 The firm’s operating brainThe substrate becomes the firm’s shared memory across partners: ten times the work without ten times the people, a firm that increasingly runs itself. This is where EOS stops being a meeting cadence and becomes how the business actually operates.

We are proposing to walk this with you one rung at a time. Phase 1 is the whole of what we’d start with. Phases 2 and 3 are the horizon, named so you can see where the first small step is heading, not scoped or priced today.

How we’d build it, and why it stays yours

You’re watching Claude and OpenAI both launch firm-wide AI platforms right now. They’re good, and they’ll keep getting better. But at the exact moment the frontier models are leapfrogging each other every few weeks, the last thing a firm whose product is trust should do is marry itself to any one vendor’s platform.

Own the firm. Rent the brains.

You own your firm: the captured process, the client context, the workflows, in plain files you control. You rent the brains: plug in whichever model is best for the job that week, and swap it the moment a better or cheaper one ships, without rebuilding anything. Nick and Bryce already said it in the room: slot in the best model; the institutional memory and the process stay the same. Your crown jewels never get held hostage to a vendor’s format or price, and you’re never rebuilding the firm because the tool changed. It’s the difference, Rod, between the typewriter and the computer lab.

Your model costs stay yours. You pay whichever AI you use directly, at cost. We add nothing on top. We don’t meter your intelligence.
You can run it behind your own firewall. As the private hardware comes online, the sensitive and deterministic work runs on a machine you own: zero token cost, nothing leaving the building. You rent frontier models only where they earn it.

Because your work is privileged, everything starts zero-trust: read-only, reviewable, a human owner for every step, and the system earning trust incrementally before it is relied on. The question of recording internal conversations raises real privilege and malpractice considerations; that is yours to weigh on your own timeline, and nothing in step one depends on it.

The charter engagement

We’d be glad to make this a charter engagement, in two senses. It is the founding engagement of our relationship with Fuller, and it is a genuine frontier: standing up AI as a working chief of staff inside the firm, not as a novelty but as trusted infrastructure. That carries a real rate concession, named plainly below, in exchange for the chance to build a reference together once you’ve felt the value.

Step one Start here

Stand up Rod’s chief of staff

$7,500 fixed · two to three weeks

Done with Kevin, who helps integrate the firm’s Microsoft 365, and potentially other systems, with the agent. Read-only to Rod’s calendar and admin email to start, a warm start from the last month of history, and the daily rhythm running live. One fixed number, no surprises: small enough to be an easy yes, real enough to matter.

Done when Rod feels the relief and a real follow-up lands.

Step two Only if step one earns it

The ongoing operating partnership

$6,000/mo charter rate, first two quarters · standard $8,000

We build and tune the workflows, run the weekly operating cadence, keep the light governance in place, and coach your team so the capability compounds in-house. It grows only as you widen it across the firm; you are never paying for a rung you are not on.

Model costs Separate, paid directly by you at cost, typically a few hundred to a thousand a month, with no markup from us.

How it renews: evergreen, never locked

A ninety-day initial stretch, then it simply continues month to month. Cancel any month on thirty days’ notice. At each of your quarterly planning sessions, a clean keep, adjust, or stop decision. It stays only as long as it keeps earning its place. A system whose whole value is trust cannot be sold with a lock on the door.

If, down the road, you’d like part of the fee tied to outcomes rather than a flat monthly, we can do that, measured on operational results like partner hours reclaimed and open loops closed. We’d keep it strictly to operating metrics, never anything touching legal fees or matter outcomes; the professional-responsibility rules are clear there, and we’d rather flag it than trip it.

What’s genuinely yours to decide

We are recommending the shape: prove it small, then grow at your pace. Three real choices are yours, and the quarterly is the right place for them.

  1. 01 Build it yourselves, or have us run it. We are glad either way: we can train Kevin or Marvin to run the build, or run it for you, or a blend. Your assets, your call.
  2. 02 How fast to widen it past Rod, after the first workflow proves out.
  3. 03 What Rod’s first workflow includes. Calendar and admin to start, or add one matter-flow piece.
The first small step

Let us get thirty minutes with Kevin next week; Tuesday, Wednesday, or Friday all work on our side, to scope the read-only setup and surface anything on the M365 or security side early. Tuesday or Wednesday gets ahead of your off-site, so if you like what you see, Rod’s chief of staff is already moving before your quarterly rather than waiting on it. Marvin, we’ll follow your lead on the introduction to Kevin.

Grateful for the trust so far, and to Adam Webster for the introduction that started this.

Eric · Dark Horse Works

This is a thinking document and a starting point, not a contract. Nothing here is fixed; the quarterly is exactly where the options get chosen. When you are ready, a short written agreement follows the path you pick.

Dark Horse Works
The first small step is thirty minutes with Kevin.
Next Tuesday, Wednesday, or Friday; the earlier, the more is moving before your quarterly.
Grab the thirty minutes
A page to keep

What we explored together

This gathers only what you affirmed or wrote across the pages, so you can bring it into your quarterly. It is a keepsake of the thinking, not an agreement; the proposal itself stands one page over. Take it with you, or forward it on.

Dark Horse Works · for Fuller IP Law

What we explored together

{{ sessionDate }}

As you move through the pages, what you affirm will gather here.
The frame we’d start from

{{ memoFrame }}
The destination we hold

The beachhead is Rod, unblocked; the horizon is the firm that runs itself. The same memory substrate serves both, so the small first step and the large ambition are one path, walked one rung at a time.

What we heard that landed
  • {{ m.headline }}. {{ m.body }} · {{ m.who }}
    •
How we’re holding the problem
  1. {{ m.text }} · {{ m.owners }}
    2.
The destination we pictured
  • {{ m.title }}. {{ m.body }}
    •
What we are not claiming
  • {{ n.text }}
    •
Passages you marked

{{ fp.text }}
Dark Horse Works
If the thinking is useful, let’s talk.
A conversation, whenever it’s useful to have one. {{ contactLink }}
Start a conversation