Season 1 · Episode 10

Give the Business Its Own Brain

24 Legs, maximusPoints, and operations.

This lesson drops soon — check back here for the video and voiceover.

A small business runs on its owner’s working memory — and working memory drops things. This lesson gives the business its own brain: an operating map of products, owners, customers, revenue, systems, decisions, commitments, and risks, demonstrated through two real operations — 24 Legs, a games business, and maximusPoints, a consumer-data product. The assistant becomes the business’s memory; the owner keeps the authority.

The problem this lesson solves

B

e

t

w

e

e

n

b

u

r

s

t

s

o

f

a

t

t

e

n

t

i

o

n

,

b

u

s

i

n

e

s

s

e

s

l

e

a

k

:

t

h

e

w

a

i

t

i

n

g

-

f

o

r

e

m

a

i

l

n

o

b

o

d

y

f

o

l

l

o

w

e

d

u

p

,

t

h

e

l

a

u

n

c

h

g

a

t

e

n

o

b

o

d

y

c

h

e

c

k

e

d

,

t

h

e

i

n

v

o

i

c

e

t

h

e

a

s

s

i

s

t

a

n

t

w

a

s

n

e

v

e

r

a

u

t

h

o

r

i

z

e

d

t

o

s

e

n

d

.

D

e

c

i

s

i

o

n

s

l

i

v

e

i

n

c

h

a

t

h

i

s

t

o

r

y

,

c

o

m

m

i

t

m

e

n

t

s

l

i

v

e

i

n

h

e

a

d

s

,

a

n

d

“

w

e

’

l

l

g

e

t

t

o

i

t

”

m

e

a

n

s

n

e

v

e

r

.

T

h

e

p

r

o

b

l

e

m

t

h

i

s

l

e

s

s

o

n

s

o

l

v

e

s

i

s

a

n

o

p

e

r

a

t

i

n

g

s

y

s

t

e

m

f

o

r

t

h

e

b

u

s

i

n

e

s

s

t

h

a

t

s

u

r

v

i

v

e

s

t

h

e

o

w

n

e

r

’

s

a

t

t

e

n

t

i

o

n

g

a

p

s

.

The lesson, step by step

Create the operating map

Products, owners, customers, revenue model, systems, current decisions, commitments, risks — one map, kept current. It’s the business equivalent of the project map from Episode 2, and it serves the same purpose: no re-teaching, ever.

Run product ops on 24 Legs

Card inventory, revision status, print requirements, play-test feedback, launch gates. Physical products have physical constraints — the map tracks what’s printed, what’s revised, what’s blocking launch.

Run data-product ops on maximusPoints

Benefits catalog, account-connection boundaries, recurring refresh, trust. A consumer-data product lives or dies on trust, so the map tracks exactly what data moves, how often, and where the boundaries are.

Separate draft operations from financial authority

The assistant may prepare an invoice or reconcile information. Sending, charging, or changing an account is a distinct, explicitly approved action. This is Episode 1’s authorization stage, applied to money.

Hold a weekly review that surfaces only what matters

Decisions, blockers, deadlines, anomalies. Not a status dump — a decision surface. If it doesn’t need a human judgment, it doesn’t make the review.

Template the recurring, protect the sensitive

Use templates for recurring work, but keep real customer and financial data access-controlled. Efficiency for the routine; gates for the consequential.

Track every “waiting for” — and close the loop

Nothing disappears between bursts of attention because every waiting-for has an owner and a next check. Resolved commitments get closed with the result recorded — not just the plan, the outcome.

Worked example

Monday’s weekly review for 24 Legs: three decisions (approve the revised card back? switch printers? set the launch date?), one blocker (play-test feedback not yet collected from two groups), two deadlines (print file due Friday), and four waiting-for items with owners and check-dates. Twenty minutes, and the business’s entire state is visible. Without the map, that same review would have been an hour of “wait, where are we on…?”

Your takeaway

• Give the business an operating map: products, owners, customers, revenue, systems, decisions, commitments, risks.
• Track physical ops (inventory, revisions, launch gates) and data ops (boundaries, refresh, trust) the same way.
• Drafting is not authorizing — financial actions need explicit approval.
• Weekly reviews surface decisions, blockers, deadlines, anomalies — nothing else.
• Track every “waiting for”; close commitments with results, not plans.

The BRAVE lens

Every episode runs through the BRAVE method: brief the outcome, reveal relevant context, authorize the next action, verify the evidence, and evolve the system.