This website uses cookies

Read our Privacy policy and Terms of use for more information.

PraxisThe Company Builder's ManualISSUE 15 · WED AUG 26, 2026
BY MARC KLEINMANN
In this issue
01  The Breakdown02  The Build03  Signal
04  Translation05  Field Note06  Sign-off

Happy Wednesday. It's the last week of August, the quiet stretch before everything revs up again.

This issue answers the question owners ask me most: "Which AI assistant should I use?" The honest answer is that it matters less which one you pick, and more where you do the work with it. That is what this issue teaches, in one read.

Below: the four homes AI work can live in, three questions that sort any task into the right one, and a one-page decision sheet you can print and keep. Further down I show my own morning briefing moving through all four homes.

Also in here: three things worth your time and one AI word decoded.

Marc
01The BreakdownFour homes
Every task you hand to an AI assistant needs a home
The four homes AI work can live in, and the three questions that sort any task into the right one.

Every task I hand to Claude lives somewhere. That sounds obvious once you say it out loud. It took me a year of doing it wrong before I said it.

When I started, everything happened in the chat app. It is the door everyone comes in through, usually on a phone. Ask a question, get an answer, close the app. For a certain kind of work that is exactly right. Explain this clause in my lease. Rewrite this email so it sounds less annoyed. Sixty seconds, done, gone. And gone is fine, because that task never comes back.

The trouble started with the tasks that do come back. My Monday client update ran fine in the chat app. But back then the app forgot everything between chats, so every Monday I explained the template, the client list, and last week's update all over again. Ten minutes of re-explaining before ten minutes of work. This is the point where most people quit, frustrated, and go back to doing the task by hand. I almost did.

What saved it was the next step, the one most people never hear about: a project, inside the same chat app. Claude and ChatGPT both call this Projects; in Gemini they are called Gems. One space for one topic. It remembers what you have been talking about there, and it holds whatever you add to it: documents, PDFs, price lists. My Monday update finally started where it left off. Then I hit the next wall. A project can know about your files, but it cannot work in them. For that the work has to move again, to a desktop tool like Claude Cowork. That path is the whole lesson of this issue, so here is the full map: the four homes AI work can live in.

Four places your AI work can live: 1 the conversation, the chat app on your phone; 2 the project, chat with a filing cabinet attached; 3 the workspace, the assistant works inside your real files; 4 the autopilot, runs on a schedule while you sleep.

The conversation. The plain chat app, the one already on your phone. The right home for work that never comes back. Nothing needs to be remembered, because the task itself is done and gone.

The project. The step from my story above. Still chat, but with a filing cabinet attached. You type in the things you are tired of repeating, once: what your business does, who your customers are, how you like things written. Add the documents you always reach for. After that, every new chat on that topic starts already knowing. It takes about twenty minutes, and I walked through the setup step by step in Issue 02.

The workspace. A project knows about your business. A workspace works inside it. In Claude this is called Cowork and is a Mac or Windows Desktop app: the assistant sits in your actual folders, reads your real files, and writes into them. The weekly update stops being copy-pasted out of a chat; it gets drafted in the document where it lives, next to the last four. The instructions live in the folder too, so anyone on your team gets the same result you do. This home lives on a computer, not a phone. And most importantly, the files, the memory, and the outputs live on your local computer too, not in some AI assistant's cloud.

The autopilot. Work that runs while you sleep. Scheduled for 4:45 in the morning, connected to the calendar and the inbox, finished before you sit down. Last week I wrote about four AI sessions working a night shift while I slept. That work lives here, in a tool called Claude Code. The name says code. Nobody in that story wrote any. They wrote one page of instructions.

Three questions sort any task in your business into its home. Ask them in order.

 
The decision test · three questions

1. Does this task repeat, or is it a project you will come back to? No: leave it in the conversation and get on with your day. Yes: keep going.

2. Does the assistant need to work inside your files, or just know about your business? Know about: give it a project. Twenty minutes, this week, you can do it yourself. Work inside: it needs a workspace.

3. Should it run while you are not there? Yes: that is autopilot work, and it is the kind worth paying a builder to set up right.

The whole test fits on one page, and I made you one: the three questions, the map of the four homes, and what moving a task costs. Put your five most annoying tasks through it. And for those of you who still print, it is formatted for exactly that. White background and everything. Download the decision sheet here.

Here is where this changes a spending decision. The conversation and the project cost you an afternoon at most; you can set up both yourself this week. The workspace costs one careful setup. The autopilot is the one you scope with a builder. And after the test you can hand a builder your sorted list and say exactly what you want built. A builder can quote that. Nobody can quote "do something with AI."

Pick the home first. The tool choice gets easy after that.

02The BuildOne task, four homes
One task, four homes: my morning briefing
The same task, moved three times, and the wall that moved it each time.

The proof I keep coming back to is my own morning briefing, because it has lived in all four homes.

It started as a conversation. Every morning I asked in the chat app what mattered in my overnight email. It worked. But the next morning it listed the same emails again, plus the new ones. And the morning after, the same thing. So I moved it into a project, and that fixed the remembering. It worked until I needed what the project knew somewhere else, and I found myself exporting files out of one project just to load them into another. A lot of copying and pasting, all of a sudden.

That is when it moved into a workspace: one saved page saying what I care about, what I ignore, and where things get filed, sitting next to the real folders it works in. The copying stopped. One prompt, one briefing. That version is the one I wrote up in Issue 03.

Today it runs on autopilot. It reads the inboxes, the calendar, and the meeting notes on a schedule, and the briefing is waiting before I am at the desk. I put it on a clock in Issue 07. My whole job in that system is one page of instructions and a read with coffee.

Notice what moved it each time: a wall I kept hitting. It forgot everything, so it got a project. The copying and pasting piled up, so it moved into my real folders. I wanted my mornings back, so it stopped waiting for me.

What to ask your builder for, in one line: "set up the briefing so it runs on a schedule and reads these three sources, and show me the one page of instructions it follows."

03SignalThree from the week
Three things worth your time
Your bookkeeping software learns to talk, Claude stops forgetting you, and a scam warning worth taking seriously.

QuickBooks is raising prices and learning to talk to ChatGPT and Claude. Renewals from August 1 cost more on the Essentials, Plus and Advanced plans; the exact bump depends on your subscription, so check your renewal notice. The bigger news for daily life: QuickBooks now connects to ChatGPT and Claude, so you can ask about your own numbers in the chat app you already use. Your books just became something you can talk to. Kincaid CPA, August 21 · ckincaidjrcpa.com

Claude now remembers you, everywhere in the app. Chat and Cowork share one memory now: what Claude learns about you in one place, it keeps in the other. On by default, free plan included, and you can read, edit or delete anything it has stored. One thing memory does not change: remembering facts about you is not the same as working in your files. It ends the re-explaining; the four homes still decide where the work lives. TechCrunch, August 25 · techcrunch.com

The FTC ran a scam-protection webinar for small businesses, together with the Small Business Administration. Worth knowing even if you missed it: the scam to brief your team on is the voice clone. A few seconds of your voice from any posted video is enough to call your bookkeeper, sound exactly like you, and ask for a wire. The defense costs nothing: agree on a code word for money requests, and always call back on the number you know. FTC.gov, August 18 · ftc.gov

04TranslationOne term decoded
The term: "context"
The word underneath this whole issue, and the question it hands you for the next sales pitch.

Context is everything your assistant can see at the moment it answers you: your question, plus whatever instructions and files you have put in front of it. That is the whole trick behind this issue. A conversation sees only what you typed. A project also sees the files you saved into it once. A workspace sees your real folders. An autopilot sees all that, plus the clock and the tools you already pay for. So when a vendor says their product "understands your business," here is the question that cuts through the pitch: what exactly can it see, and who put that there? If the answer is "whatever you paste in," you are looking at a chat window with a logo.

05Field NoteTwo honest reviews
The reviews that made this issue and my website better
I asked two people I trust for the truth. I got it, twice.

I asked someone whose judgment I trust most to review my website. She has built successful businesses her whole life and run them well, and she does not sugarcoat. Her review was brutal. "This is so dense, this hurts my brain." "It's intimidating." She was not the first person to tell me this. She was the most honest about it, by a distance.

The same week, I talked to an executive I worked with at my previous startup VIRTUALhaus, who now runs his own winery in Napa Valley. He went through my offers and made me rethink how I explain them and re-evaluate my offer ladder. This issue is shorter and plainer because of the two of them, and my website is next. So here is my ask: if you have feedback on this newsletter, or on anything at The Company Builder's Manual, hit reply and tell me straight. The brutal version helps most.

06Sign-offTalk Wednesday
Talk Wednesday
Here is the one thing to do this week: find the task you keep re-explaining to your AI assistant, and give it a project. Twenty minutes, and your Mondays stop starting over. Then hit reply and tell me which task you picked. I read every reply, and they decide what I write next.

See you next Wednesday.

Marc
Marc Kleinmann · Praxis · New York

P.S. Want to build your own AI assistant instead of just reading about mine? I teach a small group live, four weeks, one session a week. You bring one task from your business, the one you keep re-explaining, and you build an assistant that runs it, with me walking you through every step. Starts Wednesday 30 September, with a Thursday group from 1 October. Ten seats, $1,295 for this first group. Reserve a seat, or see what the four weeks cover.