{"id":"2072251637742137799","url":"https://x.com/humzaakhalid/status/2072251637742137799","text":"","author":{"name":"Hamza Khalid","username":"humzaakhalid","avatarUrl":"https://pbs.twimg.com/profile_images/2062191018670501888/M7jUEryG_200x200.jpg"},"createdAt":"Wed Jul 01 09:31:05 +0000 2026","engagement":{"replies":11,"retweets":54,"likes":262,"views":409097},"article":{"title":"How to Build $1B/ 1 Person Company Using AI","previewText":"Zero employees. Zero burnout. Real system.\nMost people think a one-person company means doing everything yourself.\nIt doesn't.\nIt means being the only human on the team.\nThe first version of it is","coverImageUrl":"https://pbs.twimg.com/media/HMHs2Z8a8AAivB5.jpg","content":"Zero employees. Zero burnout. Real system.\n\nMost people think a one-person company means doing everything yourself.\n\nIt doesn't.\n\nIt means being the only human on the team.\n\nThe 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.\n\nBy 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.\n\nLast month I almost shut everything down.\n\nI was writing newsletters, replying to sponsors, building products, fixing the site, and doing my taxes. \n\nAll in the same week. I sat down on a Sunday night, and I couldn't even open my laptop. \n\nThat was the moment I knew. The work wasn't the problem. The setup was.\n\nI rebuilt everything that week. What you're about to read is what came out of it.\n\n## The proof, in case you needed it\n\nSam Altman said it out loud last year:\n\n> \"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.\"\n\nA one-person company will hit a billion dollars in revenue.\n\nNot a lean startup. Not a small team. One person.\n\nThe reason it's possible now: AI handles the execution layer. Research, writing, ops, content, customer replies - all of it. \n\nYou stay in the only seat AI can't fill yet.\n\nThe decision seat.\n\nThat's the company we're building here.\n\n## Old way vs new way\n\nOld 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.\n\nNew 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.\n\nOld way: Every new task = full context dump. \"Here's who I am, here's my audience, here's the tone...\"\n\nNew way: The Project already has all of that. You say what you need. The context lives in the system. Not in your head.\n\nThat shift is the whole game.\n\n![](https://pbs.twimg.com/media/HMDt8q6XsAAILgx.jpg)\n\nIf this is useful, share it with one person who's been trying to run everything alone. Takes 10 seconds.\n\n## Step 1: Build your Claude Project as a business brain\n\nA 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.\n\nThat's the foundation. Without it, nothing else works.\n\nQuick setup:\n\n1. Go to claude.ai → Projects (left sidebar) → New Project\n\n1. Name it your actual business name. Not \"My Newsletter.\" Not \"AI Stuff.\" The brand.\n\n1. Add a one-line description: \"Operating system for [business name].\"\n\nThis Project is your operating system. Every chat about your business lives here. Every file lives here. Every decision lives here.\n\n\"Stop opening a fresh chat for every task. That's how you stay the bottleneck.\"\n\n## Step 2: Load the four files that run everything\n\nEvery 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.\n\nThe four files:\n\n1. who-i-am.md - your voice and standards\n\n1. what-i-do.md - your offers and current focus\n\n1. style-rules.md - the rules that protect your voice\n\n1. operating-context.md - the running log of your business\n\n![](https://pbs.twimg.com/media/HMDwiL0XoAEsW0y.jpg)\n\nHere's the full template for each one. Copy them into Notion or a Google Doc, edit once, then upload to your Project.\n\nTemplate 1: who-i-am.md\n\nTemplate 2: what-i-do.md\n\n\"The 'NO' list does more work than the 'YES' list. Most people skip it. That's why they stay stuck.\"\n\nTemplate 3: style-rules.md\n\nTemplate 4: operating-context.md\n\nUpdate this file at the start of every week. Five minutes max. That's all it takes.\n\n\"This file is the single most important one. It's what stops Claude from giving you last month's advice this week.\"\n\n## Step 3: Write your weekly brief, not your weekly prompts\n\nMost people treat Claude like a vending machine. Put in a prompt. Get out a result.\n\nThat's not a business system. That's a one-off.\n\nEvery Monday morning, instead of writing 12 separate prompts across the week, write one brief. Drop it into your Project. Now Claude has your week.\n\nIt doesn't need to guess. It doesn't fill gaps with assumptions. It works from what you actually need this week.\n\n\"The brief is the difference between a tool and a teammate.\"\n\n## Step 4: Assign Claude a role, not a task\n\nThis is the shift that changed everything for me.\n\nThe biggest mistake I made early on was assigning tasks. \"Write a LinkedIn post.\" \"Draft an email.\" \"Summarize this.\" Tasks produce output. Roles produce systems.\n\nWhen 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.\n\n[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]\n\nThe role assignment prompt\n\nDrop this into your Project once. Then never write it again.\n\n\"'Push back' is the line that turns Claude from an assistant into a partner.\"\n\n> This newsletter grows from your shares. If you've gotten value so far, pass it on to one person who needs it.\n\n## Step 5: Build one process file per output type\n\nFor every repeating deliverable in your business, you need a process file. Not a template. A process.\n\nA template is a blank doc with headers. A process tells Claude exactly how to think through the work.\n\nHere are the three I use most. Drop them straight into your Project as separate files.\n\nProcess file 1: Newsletter issue\n\n![](https://pbs.twimg.com/media/HMD18e6WAAA9aI9.jpg)\n\nProcess file 2: X post\n\n![](https://pbs.twimg.com/media/HMD2NssWoAAFTuq.jpg)\n\nProcess file 3: Sponsor reply email\n\n![](https://pbs.twimg.com/media/HMD2bl4XwAEiktQ.jpg)\n\n\"The process file is what makes a one-person company feel like a real company.\"\n\n## Step 6: Review, don't produce\n\nThis is the shift most people never make.\n\nThey use AI to help them produce. The one-person company model uses AI to handle the production and keeps you in the reviewer seat.\n\nReviewer work looks like this:\n\n- Is this on-brand?\n\n- Is this accurate?\n\n- Is this what I actually want to say?\n\n- What would make this 10% sharper?\n\nThat's your only job inside the system. The typing, the structuring, the drafting, the formatting - that's the system's job.\n\n[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\"]\n\nTo make this stick, use the review prompt before anything ships.\n\nThe review prompt\n\n\"The 'anyone test' is the most useful single sentence in this whole system.\"\n\n## Step 7: Run a Sunday close\n\nEvery Sunday night, for 20 minutes, you close the week.\n\nWithout 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.\n\n![](https://pbs.twimg.com/media/HMD4-GLXoAAcEbs.jpg)\n\nThe Sunday close prompt\n\n20 minutes. Once a week. That's all it takes to keep the whole system sharp.\n\n## A pause before you keep going\n\nBefore you move on - slow down here.\n\nYou've just read seven steps. Maybe you're already thinking about which one you'll skip. Don't.\n\nThe 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.\n\nMost 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.\n\nThe 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.\n\nDon't be the vending machine person. Be the 90-minute Saturday person.\n\n## Three more advanced prompts to drop in this week\n\nOnce your Project is set up and your four files are loaded, these three prompts unlock the rest.\n\nAdvanced prompt 1: The \"build the system, not the one-off\" check\n\nUse this when you catch yourself doing the same task more than twice.\n\n\"Steps 2 and 3 turn a frustration into infrastructure. That's the move.\"\n\nAdvanced prompt 2: The subscriber reply batch\n\nUse this every Friday. Paste in every reply that came in that week.\n\n\"The batch turns 45 minutes of inbox grind into 12 minutes of decisions.\"\n\nAdvanced prompt 3: The big decision call\n\nUse this when you're stuck on a real call. Should I launch this? Take this sponsor? Quit this project?\n\n\"'Don't try to be agreeable' is the unlock. Without it, you get a yes-man. With it, you get a partner.\"\n\n## Best practices and real use cases\n\nFive ways I actually use this OS every week.\n\nThe 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.\n\nThe 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.\n\nCompetitive 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.\n\nThe 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.\n\nThe 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.\n\nThese are the use cases that matter. Skip the rest until you've nailed these.\n\n## The honest part\n\nI'm going to be honest about something.\n\nThis system took me four tries to get right.\n\nThe 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.\n\nThe 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.\n\nThe 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.\n\nThe fourth time worked. The fourth time is what you just read.\n\nDon'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.\n\nHere's the thing nobody tells you about building a one-person company.\n\nThe hard part isn't the work.\n\nThe hard part is letting go of the idea that the work has to come from you.\n\nI 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.\n\nGood AI use isn't about typing less. It's about staying in the decisions that only you can make. Everything else is infrastructure.\n\nIf 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.\"\n\nThat's the company we're building here.\n\n## Recap checklist - in 60 seconds\n\n→ Build a Claude Project named after your business \n\n→ Load .md files: who-i-am, what-i-do, style-rules, operating-context\n\n→ Write a 5-minute weekly brief every Monday \n\n→ Assign Claude a role with the role prompt - not a task \n\n→ Write one process file per output type, starting with the one you ship most \n\n→ Use the review prompt before anything goes live \n\n→ Run a 20-minute Sunday close every week\n\nSave this. Screenshot it. Come back to it.\n\n## Your gift - as promised\n\nThe One-Person Company OS - in one Notion workspace.\n\n→ [Go and get your gift: ](https://humzakhalid.substack.com/p/how-to-build-1b-1-person-company?r=31a9dk)\n\nTake 90 minutes this Saturday. Set it up once. Run on it for the next 12 months.\n\nWe tested it in public. Now use it in private.\n\n- Hamza 💙"},"adhxContext":{"savedByCount":1,"publicTags":[],"previewUrl":"https://adhx.com/humzaakhalid/status/2072251637742137799"}}