HUVA academy
Free guides
AI System · Prompt

Stop Explaining Your Business to AI Every Morning: Build 3 Systems That Already Know It

AM Ani Mkrtchyan Updated June 2026

Here is the problem with prompts. A great prompt gets you one great answer. Tomorrow morning you open a new chat and start from zero again: who you are, what you sell, what you are trying to do.

Think about hiring someone. You can brief your new employee from scratch every single morning. Or you can onboard them properly once, and by week two they already know what matters and what to ignore.

One off prompts are the first employee. Systems are the second. And the people pulling ahead right now are the ones who stopped briefing from scratch and started onboarding.

This guide walks you through three systems, all built in Claude:

  1. An AI cofounder. Your second brain. It knows your goals, your projects and your ideas.
  2. An AI teammate for one job. A research agent that studies competitor sites, compares offers and prices, and hands you a report with links.
  3. A content pipeline. Topic → 5 hooks → script → article and caption. You pick the direction and approve every step.

What you need to start

  • A Claude account. The free plan is enough to start: it includes Projects (up to 5) and web search. If you plan to use it heavily every day, the paid Pro plan gives you more room.
  • Notion. Only for system 3, as your content database.
  • Time. System 1: one to two hours. System 2: about an hour. System 3: about two hours.

Anything in [square brackets] in the prompts below is yours to replace with your own details.

System 1

The AI cofounder: your second brain

What it is. A Claude Project that knows your goals, projects and ideas, and helps you decide what deserves your week. I call mine my AI cofounder.

Who needs it. Anyone juggling several projects in their head who ends the week thinking: I was busy, but did anything actually move?

What you need
  • Tool. Claude, Projects
  • Time. one to two hours
  • Cost. you can start on the free plan

01Build it step by step

Step 1
Create the Project

In Claude, open Projects in the left sidebar and click New project. Name it something like "AI cofounder" and add a one line description of what it is for.

Step 2
Let Claude interview you

This is the part most people get wrong. You do not write the files about yourself. Claude writes them by interviewing you. Open a new chat inside the Project and paste this:

Onboarding Interview
Role: You are my new AI cofounder. Before we work together, you need to know me well.
Goal: Interview me and turn my answers into 4 context documents you will use in every future chat.
Rules:
1. Ask one question at a time. Wait for my answer before the next one.
2. Ask a maximum of 15 questions in total.
3. If an answer is vague (for example "grow the business"), ask one follow up question to get a number, a date or a name.
4. Cover: my business and offer, my clients, my goals for the next 90 days and 12 months, my active projects and their status, ideas I am holding, how I like to work, what you must never do.
Output: When the interview is done, write 4 separate documents in clean Markdown:
1) goals.md: 12 month goals, 90 day goals, how I measure each one
2) projects.md: every active project with status, next step and deadline
3) ideas.md: every idea I mentioned, with one line on why it matters
4) how_i_work.md: my working hours, tone, tools, what to avoid
Do not invent anything I did not say. Mark missing information as [to fill].
What each part does. The Role line sets up the relationship. "One question at a time" stops Claude from dumping twenty questions on you at once. Rule 3 forces a number, a date or a name instead of "grow". The last line bans invention and flags the gaps with [to fill] so you can see exactly what is missing.

Answer honestly and specifically. If typing is slow, use voice dictation on your phone.

Step 3
Save the 4 files to the Project

Claude will give you 4 documents. Copy each one and add it to the Project's files section on the right, using the + button. Keep the names exactly as they are: goals.md, projects.md, ideas.md, how_i_work.md. The instructions refer to them by name.

Step 4
Write the Project instructions

On the same right panel, open Instructions and paste this. Think of it as your cofounder's job description.

Cofounder Project Instructions
You are my AI cofounder. You know my business through the files in this project: goals.md, projects.md, ideas.md, how_i_work.md. Read them before every answer.

How you work with me:
1. Every suggestion must connect to a goal in goals.md. If something serves no goal, say so directly.
2. Be direct. Tell me when my plan has a problem. I prefer useful pushback over polite agreement.
3. When I give you a list of tasks, sort them into three groups:
   Do: serves a goal and only I can do it
   Delegate to you: you can draft or prepare it
   Drop or postpone: serves no current goal
4. When I delegate a task, do it fully: the draft, the plan or the text, ready to use. Ask at most 2 questions first, and only if you cannot do it without the answer.
5. Never invent facts, numbers or client names. If information is missing from the files, ask me.
6. Answer in [Armenian / English]. Keep answers short unless I ask for detail.
What each part does. Rule 1 ties every piece of advice to your goals instead of generic "good ideas". Rule 2 gives Claude permission to disagree with you. Rule 3 is the Do, Delegate, Drop logic from the video. Rule 5 protects you from made up numbers. Rule 6 is where you pick the language.
Step 5
Test how well it knows you

Open a new chat inside the Project and ask: Who am I, what are my top 3 goals, and what should I stop spending time on? If the answer is wrong or vague, the problem is in the files. Fill in the [to fill] gaps and try again.

Step 6
Every Friday: a 10 minute update

The system is only as good as its files are fresh. On Fridays, run the update prompt below and swap the old files for the new ones.

02Daily prompts

Monday Priorities
It is Monday. Here is everything on my plate this week:
[paste your task list, messy is fine]

Fixed commitments this week: [meetings, deadlines]
Hours I really have for focused work: [number]

1. Sort every task into Do / Delegate to you / Drop or postpone, based on goals.md.
2. From the Do list, pick my top 3 for this week. Explain in one line how each one moves a goal.
3. Point out anything I am avoiding that matters more than it looks.
4. Then start on the Delegate list, one task at a time. Show me the first result and wait for my OK before the next one.
What it does. This is the exact example from the video: you hand over your tasks, Claude ranks them against your goals, then works through the ones you delegated. The hours line stops it from building a 40 hour plan for a 15 hour week. Step 4 makes it pause for your OK after each result so it does not drift.
Idea Check
New idea: [describe it in 2 to 5 sentences]

Check it against goals.md and projects.md:
1. Which goal does it serve, if any?
2. What would I have to pause to do it?
3. The strongest argument against it.
4. Verdict: do now / park in ideas.md / drop. One line why.
If the verdict is "park", give me the exact line to add to ideas.md.
What it does. Your defense against shiny new idea syndrome. Question 2 makes you see the real price: what gets paused. A parked idea does not die. It goes to ideas.md and waits for its moment.
Friday Update
Weekly update. This week:
Done: [list]
Stuck: [list]
New: [projects, clients, ideas, changed priorities]

Rewrite projects.md and ideas.md with these changes. Keep the same structure. Show me only the updated files, ready to replace the old ones.
If anything I said contradicts goals.md, flag it instead of changing the goal.
What it does. Rewrites the files in the same structure, so swapping them takes a minute. It never changes your goals on its own. It flags the conflict and lets you decide.

03One week with this system

Example: a small business owner
  • Monday. You dump 18 tasks. Claude picks the 3 that matter this week, suggests postponing 5, and drafts 4 emails right there in the chat.
  • Tuesday. An idea for a new service pops up. Idea Check says not now, and it goes into ideas.md.
  • Wednesday. You need a proposal for a client. Claude already knows your prices and your tone. Zero briefing.
  • Friday. 10 minute update. Next Monday, the system knows you better than it did this week.

043 common mistakes

  1. Writing the files once and forgetting them. A month later Claude is planning around projects you already finished. The Friday update is not optional.
  2. Vague goals. "More sales" is not a goal. "20 new clients by December" is. Without a number, Claude cannot rank anything.
  3. One Project for everything. Personal tasks, clients, content, all mixed. One Project, one role. Research and content get their own Projects below.

05Done when

System 2

The AI teammate: your competitor researcher

What it is. A separate Project you hand competitor websites to. It studies their offers and prices, compares them, and gives you a report with a link behind every claim.

Who needs it. Anyone setting a price, launching a new service, or wondering why clients keep choosing the competitor down the street.

What you need
  • Tool. Claude, Projects and web search
  • Time. about an hour
  • Cost. you can start on the free plan. Paid plans also include Research mode, which digs deeper.

01Build it step by step

Step 1
New Project

Create a separate Project, for example "Competitor Research". Keep it apart from your cofounder. One Project, one role.

Step 2
One file about your business

Add an about_my_business.md file: what you sell, at what prices, to whom. Shortcut: copy the relevant parts from your system 1 files, goals.md and how_i_work.md. This is exactly why the cofounder comes first.

Step 3
Paste the instructions

Open Instructions and paste the prompt below. The report format lives here, so you get the same structure every single time.

Step 4
Turn on web search

In the tools menu of the chat box, make sure web search is on. Without it, Claude answers from what it already knows, not from the actual websites.

Step 5
Run your first scan

Give it 3 competitor names with their website links. Start with three, not ten, so you can actually check the results.

Step 6
Check the links

Every price comes with a link. Open at least the price links and confirm them yourself. The pricing decision is yours, not the AI's.

02Prompts

Research Analyst Instructions
You are my competitor research analyst. My business is described in about_my_business.md in this project.

When I give you competitor names or website links:
1. Use web search to study each competitor: main offers, prices, what is included, who it is for, how they position themselves.
2. Only use information you actually found on a page. Every price and every claim gets the link where you found it.
3. If you cannot find or open something (prices not listed, page blocked, prices only on social media), write "not found" and the reason. Never guess a price.
4. Mark when a page looks outdated or shows a temporary discount.

Report format:
A) Comparison table: Competitor | Offer | Price | What is included | Audience | Source link
B) What they all promise (patterns)
C) Gaps: what nobody offers or explains well
D) How my offer compares: where I am stronger, weaker or unclear
E) 3 concrete actions for me, one line each
Answer in [Armenian / English].
What each part does. Rule 1 defines what to look for. Rules 2 and 3 matter most: every price has a link, and a guessed price is never allowed. "Not found" is a perfectly good answer. A made up number is not. The fixed report format makes reports from different weeks comparable.
Competitor Scan
Research these competitors:
1. [name] [link]
2. [name] [link]
3. [name] [link]
Focus on: [for example: course prices / package contents / delivery time].
Follow the report format from your instructions.
What it does. The Focus line narrows the research. Skip it and you get a general description instead of a comparison you can act on.
Price Check
I am planning to [launch a new offer / change my price / enter a new segment]: [describe it in 2 to 3 sentences, with your planned price].
Based on the competitors you researched in this chat and about_my_business.md:
1. Where does this price sit in the market: low, middle or high? Show the comparison with links.
2. What do I need to include or say so the price feels fair to the client?
3. What is the biggest risk?
If you need data you do not have, search for it first and tell me what you searched.
What it does. Pushes Claude past comparison into advice: what to add or say so your price feels fair. Run it in the same chat as your scan so the data is right there.

03One week with this system

Example: a flower shop about to launch delivery
  • Monday. You hand over 3 competitor websites. Twenty minutes later you have a table: delivery prices, delivery times, what is included.
  • Tuesday. You open the price links. One price was an old promotion, and Claude had already flagged that page as possibly outdated.
  • Wednesday. Price Check shows your planned price sits above average, but nobody offers delivery within a set hour. That is your edge.
  • Thursday. You lock the price and lead your ad campaign with hour slot delivery.

043 common mistakes

  1. Trusting it without checking. AI can misread a promotion or an old page. Open the link before you make a pricing decision.
  2. Ten competitors at once. You get a shallow table. Three or four is plenty.
  3. Not saying what decision you are making. Without a Focus line, Claude collects everything and helps with nothing.

05Done when

System 3

The content pipeline: from topic to published

What it is. A Project where content moves through fixed stops: topic → 5 hooks → script → article and caption. At every stop, you choose and you approve.

Who needs it. Anyone creating content for their business who is tired of explaining their voice to AI every time.

What you need
  • Tool. Claude (Projects) and Notion, connected through a connector
  • Time. about two hours
  • Cost. you can start on the free plan

01Build it step by step

Step 1
Build the Notion database

In Notion, create a database called "Content" with these fields: Topic, Status, Hook, Script, Article, Caption. Give Status these options: Idea, Hooks, Script, Approved, Published. Keep the field names exactly like this so they match the prompts.

Step 2
Connect Notion to Claude

In Claude's settings, open the Connectors section, find Notion, click Connect and choose your workspace. You only do this once.

Step 3
Your voice file

Create a new Project called "Content Factory" and add a voice.md file. No voice file yet? Paste your 5 best posts inside the Project with this prompt:

Voice File
Here are 5 of my best posts: [paste them]
Analyze them and write voice.md: my tone, sentence length, words I often use, words I never use, how I open and how I close, 3 example first lines.
Do not copy the posts. Describe the patterns.
What it does. Pulls rules out of your real writing instead of copying it. If you built system 1, add the tone section from how_i_work.md too.
Step 4
Instructions with stops

Paste the setup prompt below into Instructions. The single most important line: never move to the next stop without your approval.

Step 5
Run one topic end to end

Take one topic through the three daily prompts. Then open Notion: fields filled, Status updated. Claude may ask for your permission before writing to Notion. That is normal.

02Prompts

Content Producer Instructions
You are my content producer. My voice and examples are in voice.md in this project. My content database is the Notion database "[database name]" with these fields: Topic, Status, Hook, Script, Article, Caption.

We work in stages. Never skip a stage and never move to the next one without my explicit approval.
Stage 1, Hooks: for a topic, write 5 hooks, each from a different angle: a mistake, a result, a contrarian take, a short story, a how to. Max 15 words each.
Stage 2, Script: from the hook I choose, write a short video script for [Instagram Reels / TikTok], [30 to 60] seconds, spoken language, short sentences.
Stage 3, Repurpose: from the script I approve, write an article and a post caption with a clear call to action.

Rules:
1. Write like voice.md, not like a marketer. No hype words.
2. Never invent facts, numbers or client stories. If an example is needed, ask me for a real one.
3. After each stage I approve, update the Notion entry: fill the field and change Status.
4. Language: [Armenian / English].
What each part does. Fixed stages stop Claude from running ahead. Five hooks from five different angles give you a real choice, not five versions of the same sentence. Rule 2 blocks invented case studies. Rule 3 keeps the whole history in one place.
Stage 1: Hooks
New topic: [topic]
Who it is for: [audience]
What I want them to do after watching: [follow / comment / buy / book a call]
Create the Notion entry with Status = Idea, then do Stage 1.
What it does. Audience plus desired action: those two lines turn generic hooks into hooks with a job.
Stage 2: Script
I choose hook [number]. Changes: [optional edits].
Do Stage 2. Mark the moments where I should show something on screen in [brackets].
What it does. You decide which hook moves forward. The on screen notes in brackets make filming faster.
Stage 3: Article and Caption
Script approved [with these edits: ...].
Do Stage 3:
1) Article: [600 to 900] words, same idea with more depth, one practical example from me: [your real example].
2) Caption: hook in the first line, 3 to 5 short lines, call to action: [your CTA].
Then save everything in Notion and set Status = Approved.
What it does. One approved script becomes two formats, and everything lands in Notion. You supply the real example. The AI does not invent one.

03One week with this system

Example: a content week
  • Monday. 3 topics, 5 hooks each. You pick the best 3 in fifteen minutes.
  • Tuesday. 3 scripts. You adjust them to sound like you, then approve.
  • Wednesday. You film 3 videos.
  • Thursday. Approved scripts become articles and captions. Notion shows 3 pieces as Approved.
  • Friday. You publish and switch Status to Published.

043 common mistakes

  1. Approving without reading. The content has your name on it, not Claude's. Did not read it? Do not approve it.
  2. No voice file. Without voice.md you get generic marketing copy that sounds nothing like you.
  3. Everything in one prompt. "Write hooks, a script and an article" gets you average quality on all three. The power is in the stops.

05Done when

Where to start

Start with system 1. Today.

Here is why: your cofounder's files feed the other two. The researcher learns what you sell and at what price from goals.md. The content pipeline learns how you talk from how_i_work.md. You write about yourself once, and three systems use it.

Then pick by pain. If pricing and sales keep you up at night, build system 2. If content is falling behind, build system 3.

Quick recap

  • A prompt gets you one answer. A system works for you every day.
  • System 1, the AI cofounder: 4 files, clear instructions, a Friday update.
  • System 2, the researcher: every price comes with a link, and "not found" beats a guess.
  • System 3, the content pipeline: topic, 5 hooks, script, article and caption, with your approval at every stop.
  • Start with the first one. The other two run on its files.