Command the Machines
0 / 5
2
BAND I · TIME
Week 2 of 12 · FLORENCE · 50 m

Teach It Everything You Know

Everyone has the same models. Almost nobody has fed theirs.

Last week the machine met your business. This week it moves in. Ten documents, your voice, your meetings — and by Friday, a shelf that knows what it's missing and answers hard questions with receipts.

Not your desk? This week's moves work on any desk: load your documents once · capture your own voice · get answers with receipts.

Today · one task

Ask one real question about your company. Then load your ten core documents into the Project and ask the exact same question again — watch the difference.

Ten documents, once — and every answer you ever get is about YOUR company.

You'll have: your ten core documents on the shelf — and the same question answered twice, so you can watch the difference with your own eyes.

  1. Ask the before-question first, in a plain chat: something real about your own company — "What do we charge for {your main offer}, and what's included?" Read the answer. It's fluent, generic, and it doesn't know you. Keep it open.
  2. Load the shelf. Open your Project and add the ten documents on the card below. Don't hunt: the ten you can find in ten minutes are the right ten — stragglers join the shelf later, and Thursday's index will name what's missing.
  3. Ask the same question again, inside the Project. Same words. This time the answer cites your price list, your terms, your documents — by name. Put the two answers side by side. That difference is what you just built.
#The ten — chosen for you
1Your standard proposal or quote template
2Your price list
3Your key contract template
4Your policy pack or staff handbook
5Your last management accounts
6Your company profile
7Your main product or service sheet
8The FAQ you keep re-answering (or the mail where you last answered it)
9Your org chart
10A folder of last year's best mails and posts (a folder counts as one)

This list isn't random. Every document on it fuels a later lesson — the proposal template writes your proposals in Week 3, the price list answers your customers in Week 5, the accounts talk to you in Week 7. You're loading the course's fuel, once.

Rescue — Can't find a document? Skip it. The ten you can find in ten minutes are the right ten — Thursday's index will name the stragglers.

Did you get this done?

The same question, asked twice — and the second answer cited your own documents.

Want more — Add the eleventh: the one document you always wish people had read before asking you things. You know the one.

Tomorrow the shelf learns something no document can teach it: how you sound.

Today · one task

Paste in five emails you actually wrote, run the prompt above, and save what it hands back as MY VOICE.

The shelf taught it your facts. Today it learns your sound — so everything it drafts from now on reads like you wrote it on a good day.

You'll have: your voice, written down — a file in your Project that makes every future draft sound like you.

  1. Collect five things you actually wrote. Everyday mails, not marketing — the ones you typed in forty seconds are your real voice; the polished stuff is someone else's already. Forward them to yourself, or just have them open.
  2. Paste the five plus the press below into your Project. It studies how you open, how you close, how long your sentences run, what you'd never say — and hands back your voice file. Save it in the Project as MY VOICE.
  3. Test it on something real. Open an email you haven't answered yet and ask: "Using MY VOICE, draft my reply to this." Read the draft once. The only question that matters: would you send it?

Here are five things I actually wrote. Study them and build my voice file: how I open and close, sentence length and rhythm, words and phrases I clearly like, formality level, how I disagree, how I say no — and a short list of things I would never write. Make it an instruction you can follow every time you draft as me. Title it MY VOICE. Then prove it: rewrite the plain sentence "We received your message and will respond shortly" the way I would say it.

COPY

Rescue — Draft sounds stiff? Your samples were too polished. Swap in three ordinary mails — the ones you typed in forty seconds. That's your real voice.

You just built a machine. Give it a name.

Say what it does and what it's allowed to touch, then tap the button. It joins the count at the top of your screen — that count is your workforce, and it grows every week.
Did you get this done?

It drafted a reply to a real unanswered email — and you'd send it.

Want more — Add the negative list by hand: five phrases you'd never write ("per my last email", "circling back", whatever makes you wince). The banned list does more work than the rest of the file.

From today, nothing this course drafts for you sounds like a machine. Tomorrow your voice file gets its first job.

Today · one task

Run one real meeting transcript through the prompt above — then save that prompt as THE MEETING PRESS. You'll use it after every meeting.

Your voice file gets its first job: one real meeting in — and the summary, decisions and actions come out sounding like you. Because they are you.

You'll have: one real meeting turned into a summary, decisions and an action list you didn't write — correct without your editing.

  1. Find one meeting transcript from the last month. Teams and Zoom have been making them automatically all along — open a recent recording and copy the transcript. Any meeting with decisions in it will do.
  2. Run it through the press below inside your Project, so it uses MY VOICE and knows your people and your shorthand from the shelf. Save it as THE MEETING PRESS.
  3. Check the actions list only. Not the prose — the actions. Right names, right tasks, right deadlines? Then forward the summary to one person who was in the room and watch what happens. (From your next meeting onward: one sentence at the start — "recording this for the notes" — is all the consent this needs. Say it, always.)

Here's a meeting transcript. Using MY VOICE, give me three things: (1) a summary in five sentences or fewer; (2) the decisions made, one line each; (3) the action list — who, what, by when — as a table. If something was discussed but not decided, put it under "Parked" so it doesn't get lost. Flag anything assigned to me in bold.

COPY

Rescue — No transcript anywhere? Record today's very next call on your phone, speaker on, and run the lesson tonight — the press doesn't care about audio quality, only words.

You just built a machine. Give it a name.

Say what it does and what it's allowed to touch, then tap the button. It joins the count at the top of your screen — that count is your workforce, and it grows every week.
Did you get this done?

One real meeting processed — and the action list was right without you touching it.

Want more — Run last week's most important meeting through it too — the one where you suspect something was agreed that nobody wrote down. Find out.

You will never take meeting notes again, and you know it's true because it already happened once. Tomorrow, the shelf tells you what it's missing.

Today · one task

Make a folder called COMPANY BRAIN, drop three real files in, and run the prompt above — save it as THE INDEX PRESS.

The shelf you built Monday has a flaw: you're the only one who knows what's on it — and nobody knows what's missing. From today, one press answers both, whenever you ask.

You'll have: the COMPANY BRAIN folder in your files — and THE INDEX PRESS: one page, on demand, of what your shelf holds and what it's missing.

  1. Make the folder. One folder in your files called COMPANY BRAIN. From now on, anything that should live on the shelf gets dropped there — by you, on any device, in two seconds, without thinking about filing.
  2. Drop three real files in and run the press below inside your Project. Watch the page build: what the shelf holds, grouped in plain words — and the gaps, named. The gaps list is the product: it's your shelf telling you what to feed it next.
  3. Save it as THE INDEX PRESS. Run it whenever an answer comes back thin — the index will tell you why.

Read my Project shelf and the folder COMPANY BRAIN. Build me one page: (1) what I have — every document grouped under plain headings (money, customers, people, product, legal); (2) what's missing — the documents a company like mine should have on this shelf but doesn't, one line each on why it matters; (3) anything in COMPANY BRAIN not yet on the shelf, with the name you'd file it under. You read and report only — you move nothing, you delete nothing.

COPY

Rescue — The gaps list feels wrong? Tell it what your business actually is in one line — "we're a {x} that does {y}" — and run again. It can only judge the shelf against the company it thinks you are.

You just built a machine. Give it a name.

Say what it does and what it's allowed to touch, then tap the button. It joins the count at the top of your screen — that count is your workforce, and it grows every week.
Did you get this done?

One page exists — what you have, what's missing — and you know the next document to feed the shelf.

Want more — Want it done without you? Put the same order on a Friday-night schedule as your Librarian — new drops read, named properly, filed, with a one-line log. On demand today; standing order whenever you're ready.

The shelf knows what it's missing now. Tomorrow it answers your hardest questions — with receipts.

Today · one task

Ask three hard questions about your company and check every answer's citations — then save the prompt as THE ORACLE.

Five days ago, answers about your company lived in people's heads and inboxes. Today you ask your three hardest questions — and watch them come back with citations to your own documents.

You'll have: THE ORACLE saved — a standing press where any question about your company gets a straight, cited answer.

  1. Ask three hard questions inside your Project — about what's on the shelf: "What did we quote {client} and what did we exclude?" · "What exactly does our policy say about {the thing that keeps coming up}?" · "What payment terms are in our standard contract?" Real questions you'd normally ask a person and wait a day for.
  2. Check the citations, not just the answers. A straight answer that cites your document is the product. An answer that hedges with no citation is the shelf talking to you: that document is missing. Add it, ask again — that loop is how the shelf gets complete, and it's a feature, not a failure.
  3. Save the press below in the Project as THE ORACLE — name it, log it on The Roll like everything you build. Reads only — it changes nothing, sends nothing, deletes nothing. From now on, "ask the Oracle" replaces "ask around and wait."

You are my company Oracle. When I ask a question, answer only from the documents on my shelf, and cite the document and section for every claim. If the shelf doesn't contain the answer, say exactly that — "the shelf doesn't hold this" — and name the document that would fix it. Never guess, never pad, never answer from general knowledge without saying so. Straight answers, cited, or an honest gap. Nothing else.

COPY

Rescue — Answer came back vague, no citation? That document isn't on the shelf. Add it, ask again — that loop IS how the shelf gets complete.

You just built a machine. Give it a name.

Say what it does and what it's allowed to touch, then tap the button. It joins the count at the top of your screen — that count is your workforce, and it grows every week.
Did you get this done?

Three hard questions, three straight answers — each citing your own documents.

Want more — Ask the question you'd never ask a person because it would take them a week: "Across everything on the shelf, where do we contradict ourselves?" Read that answer sitting down.

Week two is in. The shelf is loaded, it sounds like you, it takes your meeting notes, it knows what it's missing, and it answers hard questions with receipts. One worker and a shelf of named tools on The Roll. Next week they start earning revenue.

Week 2

The machine knows your company now.

Five for five. Ten documents on the shelf, your voice in a file, one meeting that took its own notes, an index that names its own gaps, and an Oracle that answers hard questions with citations. Everything named, everything on The Roll — and everything it knows, you taught it this week.

0 of 5 done

The week's quiz · seven questionsNO PASS MARK · IT TEACHES
Continue → Week 3