1 The Video, in 90 Seconds Austin Marchese · 13 min
Stop watching tutorials — build four compounding Claude projects, each usable today, no coding required. Together they form a personal operating system.
Board of Advisers
Clone real experts so you can ask a "board" before high-stakes decisions.
Niche Command Center
A private tool for a job you do daily — the real win is sharper thinking.
AI-Optimised Profile
A site built so AI describes you well to buyers & referrals.
Internal Operating System
Knowledge / Skills / Project folders + a CLAUDE.md brain + self-improve loop.
2 The Session Plan 60–90 min · hands-on
By the end he'll have a working /ask-the-board skill and will have asked it a real question about a live case. Have Claude Code open and one current case in mind.
Frame the outcome & pick the board
Choose 2–3 sales minds he wants first — people whose full body of work he can feed in (books/courses he owns). Start with 2.
✔ 2–3 advisors shortlistedLet Claude interview him
Run Prompt 1 — grounds the board in his book of business & goals, not generic theory. Answer by voice if possible.
✔ Saved profile of goals & contextIngest each advisor into a persona
Run Prompt 2 per advisor — feed book notes, course summaries, or public links. Claude builds a persona file.
✔ One persona file per memberCreate the /ask-the-board skill
Run Prompt 3 — loops every advisor, returns each take + a synthesis. Test on a live case.
✔ Working /ask-the-board skillAdd the devil's-advocate layer
Run Prompt 4 — forces challenge & disagreement. Re-ask and compare.
✔ A board that argues backSave & plan the next add
Save to a board/ folder. Note the next 1–2 advisors and one real decision to bring this week.
3 The Prompts copy · paste · run in order
Run in Claude Code, in order. Replace the [highlighted] parts. Nothing assumes a specific author — he supplies advisors from his own library.
You are helping me build a personal "board of advisors" inside Claude that I can ask for guidance on my sales work. Before we build it, I want you to INTERVIEW ME so your future advice is grounded in my real situation — do not guess or assume. About me: I sell [life insurance / your product] to [your typical client, e.g. high-net-worth families in Canada]. Interview me one question at a time. Cover: 1. My book of business today — what I sell, deal sizes, close rate, where deals stall. 2. My ideal client and the cases I want more of. 3. My biggest sales challenges right now (prospecting, discovery, objections, closing, follow-up). 4. My goals over the next 1, 5 and 10 years. 5. My natural selling style and where I want to grow. Ask follow-ups where my answers are thin. When we're done, write a concise "Sales Profile" summary and save it as board/my-profile.md so you can reuse it.
I want to add [ADVISOR NAME] to my board of sales advisors. Here is the source material I have on them (I'll paste/attach it now): [paste book notes, course summaries, transcripts, OR their public YouTube / podcast links — whatever you own or can access] From this, build a persona file at board/advisors/[advisor-name].md that captures: - Their core philosophy and how they see selling. - Their signature frameworks, methods and language (name them). - The questions they'd ask and the advice they'd give a life-insurance advisor. - Their tone of voice, so you can answer AS them convincingly. - What they'd push back on or warn me against. Read it against my board/my-profile.md so their coaching is specific to MY practice. Confirm when saved, then I'll give you the next advisor.
Create a custom Claude skill called "ask-the-board". When I run /ask-the-board followed by a question or a case, it should: 1. Load my profile from board/my-profile.md and every persona in board/advisors/. 2. Answer my question IN CHARACTER as each advisor, one at a time — using their own frameworks, language and priorities. Label each clearly by name. 3. Where advisors would disagree, show the disagreement — don't blend them. 4. Finish with a "Chair's Synthesis": the strongest combined recommendation, the key trade-offs, and the single next action I should take. Keep each advisor's take tight and practical — this is for real decisions on live cases, not theory. Build the skill now and then show me how to call it.
Enhance the /ask-the-board skill to force the board to think critically instead of just agreeing with me or with each other. Add these rules to the skill: - Every advisor must include at least one honest challenge, risk, or blind spot in my thinking — not just validation. - Appoint one advisor each round as "devil's advocate": their job is to argue the strongest case AGAINST my proposed approach and against the emerging consensus. - Before the Chair's Synthesis, add a "What we might be wrong about" section listing the biggest risks and the assumptions we haven't tested. - If the board is converging too easily, say so and stress-test the weak points. The goal: sharper decisions and real pushback on my cases, especially before I present to a client. Update the skill and re-run my last question so I can see the difference.
2 Niche Command Center Ammo · ~30–45 min
A private tool that helps with something he already does daily. For an insurance advisor, the obvious build is a Case & Client-Prep Command Center — model estate/tax scenarios, compare products, and prep the meeting narrative.
Why it lands (his four reasons)
- He'll actually use it — solves a real case-prep problem, not a hypothetical.
- Skips analysis paralysis — the problem's already chosen (his own workflow).
- Sharpens the craft — forces him to map how he actually structures a case.
- Zero audience pressure — no polish, no marketing; build fast.
Mini-plan & prompts
Choose what to build
Let Claude propose options from his past chats, then pick one (e.g. a case analyzer).
Plan the MVP, then build
Plan before building — interview-style planning prompt with guardrails.
Iterate live
Use it immediately; paste/screenshot errors; add features as needed.
I want to build a private tool ("command center") that helps me with something I
already do every day in my [life insurance] sales work — just for me, no one else uses it.
Based on what you know about my work, propose 5 options I could build that would
save me time or sharpen my case prep this week. For each: what it does, the single
biggest job it removes, and how simple a first version would be.
Then ask me which one to build.We're building: [e.g. a case analyzer that models estate value with vs. without life cover].
Before writing any code, interview me to lock the plan:
- What inputs do I have (assets, ages, tax rates, product options)?
- What outputs do I need to SEE for a client meeting?
- What decisions should it help me make faster?
Keep it to the minimum version that's useful THIS WEEK — no nice-to-haves yet.
When the plan's agreed, build the MVP, then let me start using it and add features
as I hit them.3 AI-Optimised Profile Ammo · ~30–45 min
A personal site built so AI — not just Google — describes him well. Increasingly a referral or HNW prospect's first move is to ask an AI "who is this advisor?" This shapes that answer.
Two goals
- Humans land and think "credible, specialised, I'd trust him with my estate."
- AI looks him up first — recruiters, referral partners, prospects — and gets the right story.
Mini-plan & prompts
- Set the page goal — what should a visitor think/feel? Reverse-engineer from that.
- Pull inspiration — sites/brands he admires.
- Scaffold a Node.js site — so it deploys easily (Cloudflare/Hostinger).
- Add an "Ask AI about me" block in the footer — provider links with a preloaded prompt.
- Deploy.
Build me a simple personal website in Node.js for my work as a [life insurance
strategist specialising in HNW estate protection].
First, interview me to fill the copy: who I help, the outcomes I create, proof/
credibility, and the ONE impression I want a visitor to walk away with.
Then scaffold the site optimised for AI discovery:
- Clear, structured "about", "who I help", and "how I work" sections.
- Machine-readable summary metadata so an AI can describe me accurately.
- A footer "Ask AI about me" block with buttons to the main AI providers, each
opening a chat pre-loaded with a prompt that returns an accurate summary of me.
Keep it clean and credible. We'll deploy it after.4 Internal Operating System Ammo · the container
"A bunch of files that take AI from good output → hyper-specific great output." It's the container that holds the board, the command center and his knowledge together — so he never re-explains himself each session.
The structure
- Knowledge/ — everything Claude should know: product info, objection playbooks, his voice, saved frameworks, meeting notes.
- Skills/ — repeatable processes (the
/ask-the-boardskill lives here). - Project/ — what he's actively working on (a live case, the command center).
CLAUDE.mdat root = the brain — tells Claude how to use the folders.
Mini-plan & prompts
Set up the structure
Create Knowledge / Skills / Project + a CLAUDE.md brain.
Build a /improve system skill
Captures feedback so output gets better every time — the most important part.
Build an /ingest resource skill
Files new articles/transcripts/videos into the right place.
Put it on GitHub
Version control — treat his OS as the IP of his practice.
Set up a personal "internal operating system" for my [life insurance] work in this folder.
Create three folders and a brain file:
- Knowledge/ → things you should always know (my products/carriers, objection
playbooks, my ideal client, my voice, trusted frameworks).
- Skills/ → my repeatable processes (e.g. ask-the-board).
- Project/ → what I'm actively working on (a live case, a tool).
- CLAUDE.md at the root → explains how to use these folders so I never re-explain.
Interview me briefly to seed the Knowledge folder with the essentials, then create
the structure and the CLAUDE.md.Create a skill called "improve-system". When I run /improve-system after we've landed on a good result (e.g. a client email or case narrative I liked), it should: - Ask what made this version good vs. earlier drafts. - Capture that as a durable rule/preference in the right Knowledge file. - Confirm what it learned, so next time the output starts closer to my standard. The point: every time I use it, the system gets sharper at sounding like me and making the calls I'd make. Build it now.
Where it all connects
| Piece | Lives in |
|---|---|
| Board of advisors (personas + skill) | Knowledge/ + Skills/ |
| Command center tool | Project/ |
| His products, objection playbooks, voice | Knowledge/ |
| The brain that runs it | CLAUDE.md |
5 The 30-Minute Foundation AI Bri · 57-sec short
The video Agostino just sent. Its whole argument: Claude out of the box is "mid" — and that's a setup problem, not a model problem. It has zero memory between sessions, so it doesn't know who he is, what he sells, or how he likes things done. Three moves fix it — the same three that quietly sit underneath everything in tabs ①–④.
Global Instructions
Role, formats, tone — loaded into every session automatically.
A CLAUDE.md file
Project-specific context Claude reads on launch. (Same file as Tab ④'s "brain".)
Chunk your skills
Separate focused files, not one giant doc — e.g. three writing skills, not one.
✓ Do it with him — live ~30 min · once
Three short moves. The video is about Claude Cowork, but these apply identically to the Claude Code setup on the rest of this page — same three levers, same payoff.
Tell Claude who he is, once
Settings → profile / global instructions. His role, preferred output format, and tone. Loads on every session so he never re-introduces himself.
✔ Claude opens knowing he's an insurance advisorDrop a brain into the working folder
A CLAUDE.md with his products/carriers, his ideal client, his voice and his tools. Claude reads it on launch. This is the exact file Tab ④ builds — start it here.
One focused skill per job
Instead of one giant instructions doc, split into small skills — e.g. discovery-call, objection-handling, case-summary. Each stays sharp because it does one thing.
CLAUDE.md brain in Tab ④, and Move 3 is why /ask-the-board (Tab ①) lives as its own skill file. This tab isn't a fifth project — it's the floor the other four stand on.The prompts copy · paste · run
Two copy-paste starters so he leaves the session with the foundation already laid — not a to-do.
Help me write my Global Instructions (the profile that loads into every Claude
session automatically). Interview me briefly, then draft a tight version covering:
- Who I am and what I do: [life insurance advisor, HNW estate protection, Canada].
- My clients and the outcomes I create for them.
- How I want you to respond by default: format, length, and tone
(e.g. direct, practical, no fluff, plain English not jargon).
- What you should NEVER do (e.g. give generic advice, invent numbers, assume a
product without asking).
Keep it under a page — it loads every session, so it must be tight and high-signal.Create a CLAUDE.md file in this folder — the project brain you read on launch so I never re-explain my work. Interview me to fill it, then write it with sections for: - My products & carriers, and the cases I handle most. - My ideal client and my typical deal. - My objection playbook and the language that actually works for me. - My voice: how my emails and client notes should sound. - My tools and where things live. This is the same file my "Internal OS" uses — build it so it can grow as we add the board and my command center.
I want to chunk my Claude skills into separate focused files instead of one giant instructions doc, so each stays sharp. Look at the sales jobs I do repeatedly and propose 3–5 small, single-purpose skills I should create — for example: discovery-call prep, objection-handling, case summary, follow-up email. For each, tell me the one job it owns and what it should never try to also do. Then create the first one with me and show me how to call it.
CLAUDE.md). Great low-friction opener if the full board build feels like a lot tonight.