Claude Code for Founders: How I Run Four Businesses

Claude Code for founders is the closest thing I have found to an extra operator who already knows every company. I run an agency, a software company, a community and a digital product, and Claude Code sits across all of them: planning the day, drafting the writing, researching decisions and building the small tools nobody has time to build.

Claude Code for founders means giving an AI agent a folder per company with the facts, goals, voice and open work for each, then using it every day for planning, research, writing and building. It drafts and prepares; the founder decides, approves and sends.

Here is how that looks in practice, and the rules that keep it useful.

Why founders get the most out of it

A founder's week is dozens of different jobs, each with its own context. A chat window forgets that context between conversations. Claude Code works inside folders, so each company's facts, numbers, voice and decisions sit in files it reads before every job.

For me that means separate workspaces for Executive Stride, StrideOps, Stride AI Academy and the AI Operator Kit, plus one for this site. Each has its own short instruction file and its own rules about what can and cannot be said.

Every morning: a plan that comes from real work

The day starts with a plan. It reads my notes from yesterday, follow-ups that are due, proposals waiting on a reply and the 90-day goal, then gives me three priorities, time blocks and the loose ends. Anything carried over for three days gets called out: do it, hand it off or drop it. I wrote up the full setup in Claude Code daily brief.

Decisions: research before opinions

Before a decision I ask for the research, not the answer:

• Market and competitor reads: what the top results, pricing pages and reviews say, with sources.
• Tool choices: the options, the trade-offs and the risks, checked against the official docs.
• Keyword and positioning calls: which searches each of my sites should own, so they never compete with each other. That exercise alone turned up several pages across my sites competing for the same searches this week.

The rule is evidence first. Every claim comes with a source I can open, and anything it cannot confirm is flagged.

Writing: the founder's biggest time sink

Most founder work is writing: proposals, emails to partners, investor or client updates, hiring posts, page copy, scripts. Claude Code drafts all of it from the right company's files, in that company's voice. I edit for two minutes rather than writing for twenty.

What makes it work is the voice file. Each workspace has real examples of how that brand writes, plus the words it never uses, and every draft goes through a quality check before I see it.

Building: the tools nobody else will build

The biggest change for me is building. Things that used to wait for a developer now take an afternoon: an internal dashboard, a quote calculator, a landing page, a script that cleans a spreadsheet, a skill that turns a recording into an SOP. This website is built and edited in Claude Code.

You do not need to code to do this. You describe the tool, look at the result and ask for changes. My guide to building a website with Claude Code walks through it.

Delegation: write it down once

Claude Code is also how my team gets better instructions. Record yourself doing a task, paste the transcript, and get a numbered SOP with checks. Write a delegation brief for a contractor in two minutes. Turn a messy call into a clear set of next steps with owners and dates.

A worked example: this week's portfolio review

Here is a real job from this week. I run four sites: this one, my agency's site, my software company's site and my community's site. Each had been getting new pages, and I wanted to know whether they were starting to compete with each other in Google.

I asked Claude Code to read each site's keyword list, its content folders and its live pages, then check every new page against the others. It found several pages on different sites aimed at the same searches. For each pair it measured how many search results they shared, recommended which site should own the topic based on who that site's readers are, and wrote the decision down in one shared document with linking rules for the future.

The whole review took an afternoon of Claude Code's work and an hour of my decisions. Done by hand, it would have been a week I never found. That is the pattern for most founder work: Claude Code gathers and organises the evidence, I make the call, and the decision gets written down so every future session follows it.

A week in the workspaces

• Monday: the plan for the week across all four businesses, built from notes and goals.
• Tuesday and Wednesday: writing and building, from proposals and page copy to new tools.
• Thursday: content day, ideas from the week's conversations turned into scripts and posts.
• Friday: review: what moved, what did not, and the lessons added to each workspace's files.

The rhythm matters more than any single prompt. Each week's notes make the next week's plan better.

The rules I keep

• Drafts, not decisions. It prepares; I decide and send. Nothing goes to a client, investor or team member without me reading it.
• One folder per company. Facts from one brand never leak into another's copy.
• Facts from files only. Prices, numbers and results come from the company's own files or from me.
• Short instruction files. Each workspace has a lean CLAUDE.md (my CLAUDE.md video covers why shorter works better); procedures live in skills that load only when needed.
• Protect focus. The plan runs the morning, not the inbox.

Mistakes founders make with AI

• Using it as a search engine. The value is in work done inside your files, not quick answers.
• One giant workspace. Separate companies need separate folders, voices and rules.
• Letting it decide. It should bring evidence and options; you make the call.
• No written decisions. If a decision is not in a file, the next session will not know about it.
• Skipping the review. A quick read before anything goes out protects your reputation.

Claude Code for founders: FAQ

Can Claude be used to build a business?

Claude can do a large share of the work of building a business: research, planning, writing, building simple tools and documenting processes. The founder still owns the decisions, the relationships and the judgment calls.

How do I set up rules in Claude Code?

Put standing rules in a short CLAUDE.md file in each workspace folder: what to read first, what never to do, where to save work. Keep it under 80 lines and move step-by-step procedures into skills.

Is Claude Code useful if I am not technical?

Claude Code is useful for non-technical founders because you work in plain English, and most of the value is in research, writing and planning. The Claude desktop app runs it without a terminal. Start with my guide to Claude Code for business owners.

How is this different from hiring an assistant?

An assistant brings judgment, relationships and accountability that software does not. Claude Code takes the drafting, research and preparation off both of you, so a human assistant spends their time on the work that needs a person.

Start with the operator setup

The AI Operator Kit is the one-business version of my setup: a workspace with your business facts, a daily plan, and commands for content, leads, outreach, proposals and building tools.