I run a one-person business on Claude. Here's the setup.
One 45-minute call becomes a client-ready project plan, seven short scripts, a long-form outline, and a week of posts, all in my voice, without ever facing a blank page. Below are the six parts of Claude in the order that actually matters, the exact prompts I used, and a checklist to build your own version.
One call, a week of output
What you're about to watch me build, start to finish, from a single messy recording.
I recorded a 45-minute discovery call. By the end, that one recording becomes a project plan the client can open, a short video script, an outline for a longer video, and a week of posts. All of it in my voice, and I never sit in front of a blank page once.
There is one thread running through every part below: context. Every time an answer is off, the fix is almost always the same, give it more context. Hold onto that as you go.
A project plan
Commitments from the call, laid out as a client-ready page you can share as a link.
7 short scripts
Pulled from the strongest things I said on the call, in my voice.
A long-form outline
One longer video script, built from the same single conversation.
7 posts
A week of LinkedIn posts, all from the transcript, none from a blank page.
The six parts, in the order that matters
Each one does real work on that same call. Copy the prompts and follow along.
The front door
You type, it answers. The mistake is treating it like Google, firing off a vague question and hoping something useful comes back. Before you ask for anything, tell it three things: who it is acting as, what you actually want, and the shape you want the answer in. That is context.
Point Chat at your call
Act as an executive assistant to the CEO of an AI business. Go through this call transcript, pull the exact commitments I made to the client, give them to me as a short list, and flag the action items with their deadlines.
Don't like the answer? Say so, plainly
I want each action item to carry two deadlines: my internal one, and the one the client sees.
The move: when an answer is off, tell it what to change in plain language, the way you would tell a person. Be specific.
Where your context lives
Chat forgets the second you open a new window, so you re-explain your business from scratch every time. A Project is a space where Claude keeps your context permanently. You load it once with the things you would otherwise repeat: your services, your pricing, your tone, two or three examples of your best work, your rules for how you like things done. Then every chat you start inside it already knows all of that before you type a word.
On the left of Claude, click Projects, then New Project. Name it and write one line on what you are trying to achieve.
Instructions: describe your services, how you price, and how you want Claude to structure its answers.
Files: drop a few samples of past work, a couple of emails, a proposal or two. Add from your device, paste as text, or pull from Drive or GitHub.
Learned the hard way: don't stuff a Project with everything you own, it gets bloated and slow. Give it your best two or three examples, not your last thirty.
Ask for the thing, not the recipe
An Artifact is a real, almost-finished output that lives right beside the conversation: a document you can edit, a working calculator, a small web page, a checklist you can send straight to a client. Instead of handing you a wall of text to format yourself, Claude builds the page, designed and ready.
Turn the call into a client-ready plan
Take the commitments from the call and turn them into a simple project plan, laid out on a clean, well-designed page. Each commitment becomes a deliverable with a deadline, set up so I can move the dates around, and built to share as a link the client can open and follow.
The move: anytime you catch yourself asking Claude to explain how to make something, stop, and ask it to make the thing. Why ask for the recipe when you can have the hot meal in front of you?
Your tools come to you
A Connector links Claude to the apps where your work already lives: your calendar, your email, your call recorder, your drive. Once they are connected, the copy-paste-between-tabs part of your day basically disappears.
Open your settings, go to Connectors. You'll see the apps you can link.
Pick one, connect the account, and approve the access it asks for.
From then on, Claude can reach into that tool whenever you ask.
What actually happened in the video: I record calls in Fireflies and gave Claude permission to read it. I never downloaded a transcript or pasted anything. I opened my Project and told it to grab the latest meeting, and it pulled the transcript on its own.
Hand over the entire job
In a normal chat you go back and forth, driving every move. In Cowork, you give Claude an entire job and it carries it through, using your Projects, your Connectors, and your files together, and it even goes into your computer and takes action, checking in with you instead of waiting on you for every move.
A week of content, in one hand-off
Go into the downloads folder and grab discovery_call_transcripts. Give me a week's worth of content from it: 7 short video scripts from the strongest things I said, one long video script, and 7 LinkedIn posts in my voice.
Handle with the setup done first: Cowork is the most powerful piece and the most likely to go sideways if you skipped the earlier parts. It works because the Project was loaded and the call was already pulled in. Desktop app only; on your phone you get Dispatch, which acts on your computer from afar.
Why none of it sounds like a robot
A Skill is how you teach Claude your specific way of doing one recurring job, so it does it your way every time after that, whether you are in a Project, in Chat, or in Cowork. Mine holds my exact rules for content, no em dashes, no corporate fillers, plus some of my best past posts. Once you have used it enough, Claude loads it automatically.
Build a skill for your voice
Create a skill that helps me write in my voice. I'm building a content system for my startup. I'll add files with information about my startup and a few scripts I've written myself in the past. Use those to build the skill, and ask me any questions you need before you do.
How: press / and pick skill-creator to build one. To edit later: Customize → Skills → the three dots → Edit, or just ask Claude to edit it. The next video is all about this → Build a Closer Call-Prep Skill.
Claude Code
Claude Code is for building software, prototypes, real automations, and websites, the engineering layer underneath all of it. If you are a technical founder, it is incredible. But if you are running a coaching practice, a shop, or a service business, you do not need it yet, and pretending you do is just selling you anxiety with a subscription attached.
Work inside Projects, use Cowork, and get one good Skill running first. The day you genuinely hit the ceiling of what the other parts can do, Claude Code is sitting right there. Until then, skip it with a completely clear conscience.
The setup checklist
Tick these off as you build. It saves in your browser, so you can close the tab and come back. Print it if you want it on the desk.
If you do one thing after this: open Claude and set up a single Project for the work you do most often, then load it with two or three examples of your best work. That is how you start using AI to save time and grow the business.
Setup done. Want the roadmap for your business?
The free AI Audit takes 2 minutes and shows you where AI would actually make you money, and which process to start with. No call, no pitch, just the readout.