Found something good?

Zero employees. Zero burnout. Real system.

Most people think a one-person company means doing everything yourself.

It doesn't.

It means being the only human on the team.

The first version of it is 80-hour weeks and a quiet breakdown wearing a business hat. The second version is what I run right now. One person. Three products. Zero employees. The rest is delegated to a Claude Project that knows my business better than most employees ever would.

By the end of this issue, you'll get the full One-Person Company OS - every .md file template, every prompt, the exact Claude Project setup I use to run AI in Public. No fluff. No theory. Copy, paste, ship.

Last month I almost shut everything down.

I was writing newsletters, replying to sponsors, building products, fixing the site, and doing my taxes.

All in the same week. I sat down on a Sunday night, and I couldn't even open my laptop.

That was the moment I knew. The work wasn't the problem. The setup was.

I rebuilt everything that week. What you're about to read is what came out of it.

The proof, in case you needed it

Sam Altman said it out loud last year:

"We're going to see 10-person billion-dollar companies pretty soon. In my little group chat with CEO friends, there's this one-person billion-dollar company, which would have been unimaginable without AI."

A one-person company will hit a billion dollars in revenue.

Not a lean startup. Not a small team. One person.

The reason it's possible now: AI handles the execution layer. Research, writing, ops, content, customer replies - all of it.

You stay in the only seat AI can't fill yet.

The decision seat.

That's the company we're building here.

Old way vs new way

Old way: You sit down to write. You start from scratch. You bounce between four tabs, trying to remember what you decided last week. An hour passes. You have one paragraph. You feel behind before you've even started.

New way: You open a Project that already knows your voice, your audience, your goals, and last week's decisions. You give it a direction. It hands you a 90% draft in four minutes. You spend the next hour editing - not producing.

Old way: Every new task = full context dump. "Here's who I am, here's my audience, here's the tone..."

New way: The Project already has all of that. You say what you need. The context lives in the system. Not in your head.

That shift is the whole game.

If this is useful, share it with one person who's been trying to run everything alone. Takes 10 seconds.

Step 1: Build your Claude Project as a business brain

A regular Claude chat forgets you every time you close it. A Project doesn't. A Project is a folder where you can drop files, set system instructions, and have every chat inside it remember everything.

That's the foundation. Without it, nothing else works.

Quick setup:

This Project is your operating system. Every chat about your business lives here. Every file lives here. Every decision lives here.

"Stop opening a fresh chat for every task. That's how you stay the bottleneck."

Step 2: Load the four files that run everything

Every one-person company needs exactly four files inside the Project. These are the brain. Without them, Claude gives you generic output. With them, it gives you your output.

The four files:

Here's the full template for each one. Copy them into Notion or a Google Doc, edit once, then upload to your Project.

Template 1: who-i-am.md

Template 2: what-i-do.md

"The 'NO' list does more work than the 'YES' list. Most people skip it. That's why they stay stuck."

Template 3: style-rules.md

Template 4: operating-context.md

Update this file at the start of every week. Five minutes max. That's all it takes.

"This file is the single most important one. It's what stops Claude from giving you last month's advice this week."

Step 3: Write your weekly brief, not your weekly prompts

Most people treat Claude like a vending machine. Put in a prompt. Get out a result.

That's not a business system. That's a one-off.

Every Monday morning, instead of writing 12 separate prompts across the week, write one brief. Drop it into your Project. Now Claude has your week.

It doesn't need to guess. It doesn't fill gaps with assumptions. It works from what you actually need this week.

"The brief is the difference between a tool and a teammate."

Step 4: Assign Claude a role, not a task

This is the shift that changed everything for me.

The biggest mistake I made early on was assigning tasks. "Write a LinkedIn post." "Draft an email." "Summarize this." Tasks produce output. Roles produce systems.

When I gave Claude a role - "you are the operating partner for AI in Public" - the quality of everything jumped. It stopped just answering questions. It started thinking about the bigger picture.

[VISUAL 2: "Task → Role → System" - Vertical flow showing the leverage ladder from one-off task to durable system, with a leverage gauge on the left]

The role assignment prompt

Drop this into your Project once. Then never write it again.

"'Push back' is the line that turns Claude from an assistant into a partner."

This newsletter grows from your shares. If you've gotten value so far, pass it on to one person who needs it.

Step 5: Build one process file per output type

For every repeating deliverable in your business, you need a process file. Not a template. A process.

A template is a blank doc with headers. A process tells Claude exactly how to think through the work.

Here are the three I use most. Drop them straight into your Project as separate files.

Process file 1: Newsletter issue

Process file 2: X post

Process file 3: Sponsor reply email

"The process file is what makes a one-person company feel like a real company."

Step 6: Review, don't produce

This is the shift most people never make.

They use AI to help them produce. The one-person company model uses AI to handle the production and keeps you in the reviewer seat.

Reviewer work looks like this:

That's your only job inside the system. The typing, the structuring, the drafting, the formatting - that's the system's job.

[VISUAL 3: "Two Seats" — Side-by-side split showing Producer seat (stressed, typing) vs Reviewer seat (calm, approving) with the bridging label "same person, different seat"]

To make this stick, use the review prompt before anything ships.

The review prompt

"The 'anyone test' is the most useful single sentence in this whole system."

Step 7: Run a Sunday close

Every Sunday night, for 20 minutes, you close the week.

Without this, the system slowly drifts. Files get out of date. Claude starts working from the old context. You end up rebuilding the whole thing two months from now.

The Sunday close prompt

20 minutes. Once a week. That's all it takes to keep the whole system sharp.

A pause before you keep going

Before you move on - slow down here.

You've just read seven steps. Maybe you're already thinking about which one you'll skip. Don't.

The system breaks if you skip the boring steps. The .md files are boring. The Sunday close is boring. The process files feel like extra work. They're not. They're the work.

Most people will read this issue, open Claude, paste one prompt, and call it a system. That's not a system. That's a vending machine.

The people who actually run a one-person company sit down for 90 minutes one Saturday, write the four .md files, set up the Project, and never go back to chaos. That's the whole gap.

Don't be the vending machine person. Be the 90-minute Saturday person.

Three more advanced prompts to drop in this week

Once your Project is set up and your four files are loaded, these three prompts unlock the rest.

Advanced prompt 1: The "build the system, not the one-off" check

Use this when you catch yourself doing the same task more than twice.

"Steps 2 and 3 turn a frustration into infrastructure. That's the move."

Advanced prompt 2: The subscriber reply batch

Use this every Friday. Paste in every reply that came in that week.

"The batch turns 45 minutes of inbox grind into 12 minutes of decisions."

Advanced prompt 3: The big decision call

Use this when you're stuck on a real call. Should I launch this? Take this sponsor? Quit this project?

"'Don't try to be agreeable' is the unlock. Without it, you get a yes-man. With it, you get a partner."

Best practices and real use cases

Five ways I actually use this OS every week.

The Monday production sprint: Sunday night, I drop my weekly brief into the Project. By Monday morning, I have first drafts of every piece of content for the week. I spend Monday editing only. Tuesday through Friday, everything else gets approved or rejected in under 30 minutes per piece.

The subscriber reply batch: Every Friday, replies have piled up. I paste them all into the Project as one batch. Claude categorizes, drafts the easy ones, and flags the ones that need my voice. I approve, customize, and send. 45 minutes turns into 12.

Competitive research without the headache: Standing instruction inside the Project: "Every Wednesday, give me a 5-bullet brief on what's new in the AI tools space that my readers don't know yet." I paste in 3 to 5 articles I spotted. Claude synthesizes. I decide what's worth covering. I never read a 31-page report myself.

The product page that updates itself: ClaudeKit pages used to be a manual update every time I shipped a feature. Now I have a process file Claude follows. Drop in the feature notes. Out comes an updated, on-brand product description. I read, approve, ship.

The big decision call: When I'm stuck on a real call - should I launch this? Should I take this sponsor? - I don't ask my friends. I open the Project and run the Advanced Prompt 3. The Project already knows my goals, my voice, my no-list. The answer is usually clear in five minutes.

These are the use cases that matter. Skip the rest until you've nailed these.

The honest part

I'm going to be honest about something.

This system took me four tries to get right.

The first time, I wrote the four .md files and forgot about them. Claude never opened them on its own. The output stayed generic. I gave up after two weeks.

The second time, I wrote the role prompt but skipped the process files. Every chat was still a one-off. I was just typing fewer words to get the same result.

The third time, I had everything except the Sunday close. Three weeks later, the files were so out of date that Claude was giving me advice based on goals I'd already abandoned.

The fourth time worked. The fourth time is what you just read.

Don't expect this to feel magical on day one. Expect it to feel like work for the first week, useful in the second week, and invisible by the third. That's the curve.

Here's the thing nobody tells you about building a one-person company.

The hard part isn't the work.

The hard part is letting go of the idea that the work has to come from you.

I spent three months using AI to help me write faster. It helped. But I was still the one producing. The day I handed Claude my style files and said, "Your job is to protect my voice, not copy it" - everything changed.

Good AI use isn't about typing less. It's about staying in the decisions that only you can make. Everything else is infrastructure.

If you build this system right, your job stops being "do the work." Your job becomes "decide what good looks like, and reject anything that isn't it."

That's the company we're building here.

Recap checklist - in 60 seconds

→ Build a Claude Project named after your business

→ Load .md files: who-i-am, what-i-do, style-rules, operating-context

→ Write a 5-minute weekly brief every Monday

→ Assign Claude a role with the role prompt - not a task

→ Write one process file per output type, starting with the one you ship most

→ Use the review prompt before anything goes live

→ Run a 20-minute Sunday close every week

Save this. Screenshot it. Come back to it.

Your gift - as promised

The One-Person Company OS - in one Notion workspace.

→ Go and get your gift:

Take 90 minutes this Saturday. Set it up once. Run on it for the next 12 months.

We tested it in public. Now use it in private.

- Hamza 💙