Build Your Team

I spent years in one chat. One model. One thread that forgot me when I closed the tab. I wrote better prompts. I trained one hire. I defined one outcome and watched one pair of hands try to hit it.

That was the right first move. It's not the job I'm in this week.

This week persistent Grok bots started working like a team I could lead. I stopped writing tasks. I wrote what DONE looks like. I staffed seats. I sat as CEO.

The handle for that job is Build Your Team.

[ fig ] You keep the chair. The seats get jobs.

Stop writing tasks. Write DONE. Staff a team. Sit as CEO.

The week persistent bots started working

I've had persistent bots for a while. They could hold a name. They could hold a tone. They still behaved like loners. Each one was a clever intern in a room with no door to the next room.

This week that broke in the useful direction.

I stopped treating them as lone agents and started treating them as a team. I assigned work the way a CEO assigns work. This seat owns the brief. That seat owns the build. A third seat owns the check. Sometimes one seat hands a slice to another seat and I'm not in the middle restating the plot.

They kept the clock. I assigned in one sitting. Hours later the same seat still owned the work. That's the first time persistent bots felt usable to me, not as a demo, as an office.

Grok is the office this week. Cloudflare is where each seat keeps a brain. Ari OS is the operator job that lets me stay in the chair while the team runs.

I'm not going to sell you a miracle week. I'm going to teach the move that made the week possible.

Old job vs new job

The old job is one chat.

You open a thread. You explain the world. You ask for a step. You correct the step. You ask for the next step. You're the hands and the eyes and the memory. When the tab dies, the company dies. You can be brilliant in that chat and still be a sole trader with a fast typist.

I already taught the first upgrade. Treat the model like a hire you train. Tell it how you work. Correct it when it misses. Save the correction so the next session isn't a stranger. That still holds for one seat.

The new job is CEO of a team.

You don't sit inside every keystroke. You name the outcome. You name who owns it. You name who isn't allowed to invent scope. You come back for the yes, the no, and the cut. The team can move while you're away. The team can hand work across a gap of hours without you performing the plot again.

One chat asks, "what should I type next?"

A team asks, "what does DONE look like, who owns it, and when do I stop?"

If you stay in the first question, you'll keep hiring a sharper assistant. If you move to the second, you start becoming a CEO.

[ fig ] Old job: one chat. New job: a team with …

Tasks keep you in the loop. DONE lets the team run.

DONE first, then staff

I already wrote the prequel. Stop Prompting. Start Defining Outcomes. was one brief and one hire. This chapter is what happens when the outcome gets a team.

A task is a route. Open the file. Write the function. Change the heading. Run the check. A task keeps you in the loop because only you can sequence the next one.

A DONE is a state you can inspect without watching anyone's hands.

• A visitor on a phone can read the promise, see the price, and open checkout.
• A weekly recap names what shipped, what is blocked, and what you'll cut.
• A review pass lists three failure states that look finished and still fail.

If you can't hand that sentence to a junior and check the result without watching their hands, you don't have a DONE. You have a vibe.

Write the DONE before you name a seat. If you staff first, the seats will invent work so they look busy. They'll add a feature you didn't ask for. They'll polish a page that can't sell. They'll write a recap that sounds like motion and names nothing.

Staff second.

[ fig ] Write DONE first. The chairs wait.

The CEO move is small and rude:

1. Write DONE as evidence, not as hope.
2. Write the stop. What the seat must not add.
3. Name the seat that owns the slice.
4. Name the seat that's allowed to say no.
5. Keep the final yes.

You're not allowed a fourth seat until the first three have jobs that don't overlap. If two seats own the same yes, you still have one chat with extra costumes.

One brain per seat

A team with one shared memory isn't a team. It's a group chat that argues with itself.

Each seat gets its own brain.

[ fig ] One brain per seat. No shared soup.

Grok can hold the conversation. Cloudflare holds the memory so the seat isn't a goldfish when the tab closes. Doctrine stays with the seat that must remember doctrine. Voice stays with the seat that must not drift. A builder doesn't need the reviewer's private scars. A reviewer doesn't need the builder's scratchpad.

I could stand up a brain in the time it takes to open the app. That is color. The company is knowing what DONE looks like.

I'm not going to draw you a schema. I'm not going to walk you through a vendor console. The point isn't how pretty the memory is. The point is that the memory isn't a soup. One brain per seat. Separate jobs. Separate recall. A handoff is DONE plus evidence, written down, not a dump of everything one seat ever thought.

If two seats can reach into the same pile and rewrite each other's past, you'll spend the week settling fights about who said what. That's still one chat. You just gave it more mouths.

Name Cloudflare because that's the office this week. Don't make Cloudflare the product. The product is a seat that still knows its job tomorrow morning.

Ari OS is the operator job

Ari OS is the spine. That page is the chair, the loop, and the reason you stop doing the work with your own hands. You define. You send the work. You review. You ship only what passes.

This page is the team chapter of the same OS. Not a second product. Not a store SKU. Not a new logo next to the overview.

Ari OS is the operator job. Build Your Team is what that job looks like once more than one seat can hold a clock.

The overview teaches you to stay in the chair. This chapter teaches you to fill the other chairs on purpose. Same judgement. Same final yes. More hands, and those hands aren't allowed to become a cast.

If you skip the spine and jump to staffing, you'll collect seats the way people collect model subscriptions. If you sit in the overview and never staff, you'll stay a brilliant person in one thread.

Read the overview for the OS. Stay here for the company shape.

Forum time: handoffs across hours

The tell that you still have one chat is simple. The work dies when you stand up.

[ fig ] A handoff keeps a clock. The work surviv…

Forum time is the opposite. You assign in the afternoon. You close the lid. The seat still owns the slice at night. Another seat can pick up a handoff in the morning without you reciting the brief like a tour guide.

A handoff isn't a vibe note. A handoff is:

• the DONE, copied, not summarised into mush
• what already exists, with a place to look
• what must not be added
• who may say pass
• when the clock runs out

I watched this hold across hours. I assigned. I left. The ownership didn't snap back to me just because I was away. Seat to seat, the work kept a clock. That's the short-term future I trust. Not a louder assistant. A team that can survive a gap.

If your "team" needs you to paste the same context every time a new pair of hands shows up, you don't have forum time. You have a meeting.

Build the handoff so a stranger seat can start cold and still hit the DONE. If they can't, the missing piece isn't a better model. The missing piece is the written handoff.

What this is not

This isn't a cast. I won't name them like characters. I won't give them birthdays. Occupants are seats with jobs, memories, and a clock. They aren't people. They don't get bios. They get a DONE and a stop.

This isn't a five-minute company. I could stand up a brain fast. Call it five minutes if you want a number on the color. The speed is a trick of the wrist. It isn't the firm. If you replay my week as an install ritual, you'll own three empty seats and no company.

This isn't Ari OS for sale as a box. Ari OS is how I sit. You can steal the job. You can't buy the chair from me and skip the judgement.

This isn't a vendor pilgrimage. Grok and Cloudflare are named because they're the office I'm in. They aren't the thesis. I won't send you through a click path. I won't pretend either vendor endorsed this. Swap the office later if you must. Keep the job.

This isn't a remake of the one-hire essay and it isn't a remake of the outcome essay. Those still stand. This chapter starts after them.

This isn't "hire more assistants so you can type faster." Throughput without a DONE is just a mess with a clock.

Steal tonight

Don't open Grok first. Don't open Cloudflare first. Don't go looking for a new app so you can feel like a CEO.

Tonight, on paper or in a file, write three DONEs. Then name three seats.

Make the DONEs inspectable.

1. A page a stranger can use: promise, price, and a button that opens the real next step.
2. A recap a future you can trust: shipped, blocked, and one cut.
3. A check a fresh pair of eyes can run: three ways a fake finish could pass, and how you catch each one.

Make the seats boring.

[ fig ] Three seats. Brief. Hands. Eyes.

1. Brief. Owns the DONE and the voice. Doesn't implement.
2. Hands. Implements against the DONE. Doesn't invent scope.
3. Eyes. Checks evidence. Doesn't congratulate the Hands.

If you can't write the three DONEs, you aren't ready to staff. Stay there. That's the company.

If you can write them, assign one seat to each, write the stop under every DONE, and keep the final yes. That's Build Your Team. That's you in the chair.

Steal the job tonight. Leave the vendors for later.