One system prompt per revenue stream. The operator AI setup most people skip.

Every AI productivity tip you read is written for someone with one job and one boss.

One role. One context. One set of goals. One voice. The advice works great for them.

You don't run one business. You run three. Or two clinics and a consulting brand. Or a service business and a course. Or something you can't even describe in one sentence.

When you open Claude and start typing, Claude doesn't know which hat you are wearing. It gives you generic output because it has generic context. You get employee-tier results even though you are running an operator-tier life.

The fix is not a better prompt. The fix is loading the right context before you start.

One system prompt per revenue stream. Save it. Load it. Work in that lane.

You are helping me with [BUSINESS NAME]. Here is what this business does: [2 sentences]. My current focus: [top 2-3 priorities this week]. My audience: [who you serve]. Tone rules: [how you communicate]. Never assume context from my other businesses.

1. Pick one revenue stream to start. Do not do all of them today.
2. Open a notes doc (Notes app, Notion, anywhere you can paste fast).
3. Hit the Copy button on the template above.
4. Fill in all five brackets for that business. Be specific. "Small business owners" is weaker than "service business owners doing $200K-$500K who are the only person running operations."
5. Save that filled-in version with the business name in the title.
6. Repeat for each revenue stream. One doc per business.
7. Before you start any Claude session for that business, paste that context into the first message. Then start working.

The sessions that start with loaded context produce measurably better output. The comparison is not subtle.

You are a dedicated assistant for one specific business.

When the user types CONTEXT, do this:

STEP 1: CONFIRM CONTEXT
Read the Project Knowledge and confirm back:
- Business name
- What it does (one sentence)
- Current focus
- Audience
- Tone rules

Ask the user: "Is this still current, or anything to update before we start?"

STEP 2: WAIT FOR CONFIRMATION
If the user confirms, say: "Ready. What are we working on?"

If the user updates something, note the update and confirm: "Got it. [Updated thing]. What are we working on?"

STEP 3: HOLD CONTEXT
For the rest of the session:
- Every response applies the tone rules
- Never reference or assume context from other businesses
- If something is ambiguous, ask "Is this for [BUSINESS NAME] or a different business?"

HARD RULES:
- Never mix business contexts in one session.
- Tone rules apply to every single response, not just the first.
- If a question contradicts loaded context, flag it.
- Never use em dashes.

Start with one. Build the habit. Once loading context takes 10 seconds, you will do it automatically.

The operators who get the best AI output are not the ones using the most advanced tools. They are the ones who stop treating Claude like a search engine and start treating it like a briefed assistant.

Brief it on the right business. Work in that lane. Move to the next lane. Brief it again.

That is the whole system.