A starting point, not a proposal

A way of thinking, shared.

Rod, Bryce, Marvin: before we talk about what AI can or cannot do, we wanted to set down how we are thinking, plainly and early. This is not a proposal and not a price. It is our read of the real question, which sounds less like “can AI replace an assistant” and more like “where can the firm gain dependable leverage without spending down the trust it sells.” Read it, argue with it, keep what is useful. There is no obligation on the other side of it.

How this works

On Listen, Frame, and Envision you are invited to react, re-rank, and edit what you see. We came to understand the work before naming a solution, so nothing here is a pitch. The Article lays out our point of view in full if you want the longer read. Whatever you affirm gathers, quietly, into one page you can keep.

Working session

Monday’s agenda

{{ meetingDate }}  ·  30 minutes  ·  Rod, Bryce, Marvin, and Eric

The plan is simple: first we play back what we think we heard, you correct it, then we map the work together and decide what, if anything, is worth a first small step. Nothing here is fixed. If a thread matters more than the clock, we follow the thread.

We are not here to decide whether AI replaces an assistant. We are here to understand what support must protect, then decide which parts should stay human, which can be systematized, and which can safely be AI-assisted.

Listen→Frame→Envision→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

Sorted by whose it is, and marked by where it comes from: said to us directly, read from the public record, inferred, or structural. Only Marvin has actually spoken with us. Affirm what lands, correct what doesn’t, set aside what we should. Open the fuller context whenever it helps.

{{ listenProgress }}
reviewed
How we’d open

One thing first: we’ve only actually spoken with Marvin. Everything on here attributed to you, Rod, and to you, Bryce, is our inference from the outside, and the most useful thing you can do today is tell us where we’re wrong. With that said: before we talk about AI agents, we want to check whether we heard the real question. It sounds less like “can AI replace an assistant” and more like: where does Fuller IP need dependable leverage, and where would automation create unacceptable risk because the work depends on confidentiality, judgment, or relationship context? That’s our read. 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

Trusted leverage, and the turn

First the crux, then a few ways to hold the problem: re-rank them by which feels truest, and say whose problem each is. Then the move the rest of this rests on.

The crux

Tacit coordination, not AI capability.

The bottleneck may not be whether AI can do a task. It may be that the most valuable parts of executive support are tacit: knowing what matters, what can wait, what needs a human touch, what context is missing, and when to escalate. The strategic work is to make that hidden layer visible. Only then does it make sense to decide which parts belong with a person, a documented workflow, or a bounded agent.

3A

The problem, a few ways to hold it

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

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

{{ p.text }}

How we read it: {{ 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

AI promotes the assistant.

When the agent holds the administrative floor (the triage, the drafting, the status-chasing), the person who used to hold it is freed for the judgment a machine cannot do: reading the room, the discreet call, the email that is technically low-priority but matters enormously. Freed from the floor, one elevated person can serve several partners. The role does not shrink. It grows.

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

Choose the destination

Before we solve anything, pick which future is worth the change. These are not the same destination. Choose one, then choose the elements that describe where this should go.

{{ destinationNote }}

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 }}
The trade-offs to choose
{{ t.pair }}
{{ t.q }}

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.
If it’s useful

How we’d work together

We can give you a sense of how engagements like this usually work. We’d rather not pretend we’re ready to scope the real work yet. We’ve spoken with Marvin once, and this is our first conversation with you and Bryce. The responsible next step is to understand the problem, frame the future state, and then decide together whether there’s enough value to commit.

{{ o.key }} Start here

{{ o.title }}

{{ o.body }}

Timeline {{ o.timeline }} Best when {{ o.bestWhen }}

If we were advising you objectively today, we’d start with the diagnostic. It protects both sides from solving the wrong problem.

Engagement flow

A staged progression from diagnosis to controlled proof to capability build. Each gate is binary, and its off-ramp is a real answer, so we never drift into permanent-pilot syndrome.

The decision gates
  1. {{ g.label }} {{ g.q }}

The gates are managerial, not technical: baseline set, scope approved, controls documented, KPI delta observed, owner assigned.

Before a real proposal

We’d want to answer five questions first, so we neither over- nor under-scope. Scope, and therefore price, follows the shape of the work, so we’d rather discuss it once the shape is clear.

  1. {{ q.num }} {{ q.text }}
A page to keep

What we explored together

This gathers only what you affirmed or wrote across the pages. It is a keepsake of the thinking, not a proposal and not an agreement. 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’re aiming at

{{ memoDestination.key }} · {{ memoDestination.label }}. {{ memoDestination.vision }}
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.
No commitment. A conversation, whenever it’s useful to have one. {{ contactLink }}
Start a conversation